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
