Running an Arrow hackathon

[David Li <li...@gmail.com>]

Hi all,

We're thinking of hosting an internal open-source hackathon in
September. I wanted to make Apache Arrow one of the projects we work
on, so I wanted to give maintainers here a heads up, and clarify a few
things.

I would be around to help set up environments and make sure that PRs
follow the expected format. I could also do first-pass reviews. We
would focus on Python/Java/Rust as those have the most interest
(though maybe we could snag a few Gophers).

At this point I'm not sure how many participants we'll have - most
likely no more than 10 or so.

- Is there a label we already use for easy-to-start-with issues? I see
variations on newbie/easy-fix/beginner on JIRA, is there a preference
for one?
- There would (hopefully) be an influx of PRs. We wouldn't expect any
sort of timeliness on reviews, but it could exacerbate the
Travis/AppVeyor capacity problem - should I encourage people to set up
personal Travis instances?

Thanks,
David

Re: Running an Arrow hackathon

[Micah Kornfield <em...@gmail.com>]

Hi David,
This is cool, thank you for doing it.

My thoughts:

> - Is there a label we already use for easy-to-start-with issues? I see
> variations on newbie/easy-fix/beginner on JIRA, is there a preference
> for one?

I think beginner would be my preferred label.  Note that I don't think it
has been consistently applied

- There would (hopefully) be an influx of PRs. We wouldn't expect any
> sort of timeliness on reviews, but it could exacerbate the
> Travis/AppVeyor capacity problem - should I encourage people to set up
> personal Travis instances?

A personal travis instance could be helpful but I think if there isn't a
rush for reviews, they could be staggered to not have too much of an impact
on development.

On Mon, Aug 12, 2019 at 6:55 AM David Li <li...@gmail.com> wrote:

> Hi all,
>
> We're thinking of hosting an internal open-source hackathon in
> September. I wanted to make Apache Arrow one of the projects we work
> on, so I wanted to give maintainers here a heads up, and clarify a few
> things.
>
> I would be around to help set up environments and make sure that PRs
> follow the expected format. I could also do first-pass reviews. We
> would focus on Python/Java/Rust as those have the most interest
> (though maybe we could snag a few Gophers).
>
> At this point I'm not sure how many participants we'll have - most
> likely no more than 10 or so.
>
> - Is there a label we already use for easy-to-start-with issues? I see
> variations on newbie/easy-fix/beginner on JIRA, is there a preference
> for one?
> - There would (hopefully) be an influx of PRs. We wouldn't expect any
> sort of timeliness on reviews, but it could exacerbate the
> Travis/AppVeyor capacity problem - should I encourage people to set up
> personal Travis instances?
>
> Thanks,
> David
>

Re: Running an Arrow hackathon

[David Li <li...@gmail.com>]

Hi all,

Thanks for the suggestions! I've gone ahead and tagged some
Python/Rust/Java issues, and I'll be sure to walk people through
setting up Travis/AppVeyor.

Andy, that is super awesome, thanks!

Best,
David

On 8/16/19, Andy Grove <an...@gmail.com> wrote:
> Hi David,
>
> I've tagged a few Rust issues with the beginner label. I'll try and think
> of more beginner issues over the next few days.
>
> Thanks,
>
> Andy.
>
> On Mon, Aug 12, 2019 at 7:55 AM David Li <li...@gmail.com> wrote:
>
>> Hi all,
>>
>> We're thinking of hosting an internal open-source hackathon in
>> September. I wanted to make Apache Arrow one of the projects we work
>> on, so I wanted to give maintainers here a heads up, and clarify a few
>> things.
>>
>> I would be around to help set up environments and make sure that PRs
>> follow the expected format. I could also do first-pass reviews. We
>> would focus on Python/Java/Rust as those have the most interest
>> (though maybe we could snag a few Gophers).
>>
>> At this point I'm not sure how many participants we'll have - most
>> likely no more than 10 or so.
>>
>> - Is there a label we already use for easy-to-start-with issues? I see
>> variations on newbie/easy-fix/beginner on JIRA, is there a preference
>> for one?
>> - There would (hopefully) be an influx of PRs. We wouldn't expect any
>> sort of timeliness on reviews, but it could exacerbate the
>> Travis/AppVeyor capacity problem - should I encourage people to set up
>> personal Travis instances?
>>
>> Thanks,
>> David
>>
>

Re: Running an Arrow hackathon

[Andy Grove <an...@gmail.com>]

Hi David,

I've tagged a few Rust issues with the beginner label. I'll try and think
of more beginner issues over the next few days.

Thanks,

Andy.

On Mon, Aug 12, 2019 at 7:55 AM David Li <li...@gmail.com> wrote:

> Hi all,
>
> We're thinking of hosting an internal open-source hackathon in
> September. I wanted to make Apache Arrow one of the projects we work
> on, so I wanted to give maintainers here a heads up, and clarify a few
> things.
>
> I would be around to help set up environments and make sure that PRs
> follow the expected format. I could also do first-pass reviews. We
> would focus on Python/Java/Rust as those have the most interest
> (though maybe we could snag a few Gophers).
>
> At this point I'm not sure how many participants we'll have - most
> likely no more than 10 or so.
>
> - Is there a label we already use for easy-to-start-with issues? I see
> variations on newbie/easy-fix/beginner on JIRA, is there a preference
> for one?
> - There would (hopefully) be an influx of PRs. We wouldn't expect any
> sort of timeliness on reviews, but it could exacerbate the
> Travis/AppVeyor capacity problem - should I encourage people to set up
> personal Travis instances?
>
> Thanks,
> David
>

Re: Running an Arrow hackathon

[Antoine Pitrou <so...@pitrou.net>]

Hi David,

On Mon, 12 Aug 2019 09:55:30 -0400
David Li <li...@gmail.com> wrote:
> Hi all,
> 
> We're thinking of hosting an internal open-source hackathon in
> September. I wanted to make Apache Arrow one of the projects we work
> on, so I wanted to give maintainers here a heads up, and clarify a few
> things.
> 
> I would be around to help set up environments and make sure that PRs
> follow the expected format.

Given our build chain, I expect setting up build environments to be the
most delicate step.

> - There would (hopefully) be an influx of PRs. We wouldn't expect any
> sort of timeliness on reviews, but it could exacerbate the
> Travis/AppVeyor capacity problem - should I encourage people to set up
> personal Travis instances?

I think you should, yes.  Our build capacity on Travis-CI and AppVeyor
is largely insufficient already.

Regards

Antoine.