Hi Rich, We are doing a contributor's workshop for Beam in the upcoming summit in Europe, but most of the content should be easily adjustable to any Apache projects. For example, instead of subscribing to dev@beam.a.o. we can teach them how to subscribe to dev@community.a.o. Introduction to ICLA, Jira, GitHub and other similar tools and processes should be the same across all projects. WDYT Austin?
On Tue, May 28, 2019 at 3:28 PM Rich Bowen <rbo...@rcbowen.com> wrote: > This sounds like a great thing to have as part of the hackathon. Perhaps > cover part of this at the start of each day? None of these things are > specific to Beam but apply to all projects right? > > On Tue, May 28, 2019, 12:09 Austin Bennett <whatwouldausti...@gmail.com> > wrote: > > > Hi Rich, > > > > Great; sounds like we'll plan on a hands-on developing things > *in*/*using* > > Beam. What about contributing workshop? It sounds like a Hackathon > space > > might help people understand things like: specifics of getting Jira > > username, finding issues, ?signing ICLA?, knowing to subscribe to > dev/user > > lists, etc? Many of us not having attended previous ApacheCon(s) are > > unsure the audience, alternate tracks, etc etc. > > > > Cheers, > > Austin > > > > > > > > On Tue, May 28, 2019 at 5:35 AM Rich Bowen <rbo...@rcbowen.com> wrote: > > > >> > >> > >> On 5/27/19 6:11 PM, Austin Bennett wrote: > >> > Great to hear this is coming together. I'm happy to help getting > >> movement > >> > from the Beam Community. > >> > > >> > Very interested to hear concrete plans for hackathon, it will inform > the > >> > rest of what content we offer in the Beam tracks. At prior beam > summits > >> > (ex: beamsummit.org), we've had intro to contributing workshops, and > >> > working with (hands-on) beam. We think these things are good for > >> people to > >> > do, though it sounds like getting setup for contributing code would > >> largely > >> > be covered in a hackathon? What about getting something working -- > >> hacking > >> > on a project (ex: getting a beam pipeline or something like a spark ml > >> job > >> > running). > >> > > >> > Wanting to ensure that we don't unnecessarily have > overlapping/competing > >> > content. > >> > > >> > @rob, @Kevin, @Steve -- maybe let me know as you start to get this > >> worked > >> > out. Happy to attempt to listen in on history lesson, should you > >> arrange > >> > something with @rich. > >> > >> The kind of session you're talking about - hands-on, mentored workshops > >> - are awesome and encouraged, and do not, in my opinion, conflict with a > >> more passive "come join us" central hackathon space. Indeed, they > >> complement one another, and each should promote the other. > >> > >> > >> > > >> > On Mon, May 27, 2019 at 1:55 PM Rich Bowen <rbo...@rcbowen.com> > wrote: > >> > > >> >> Awesome. It sounds like we have the three hackathon leads/volunteers > - > >> >> Rob Tompkins, Steve Blackmon, and Kevin McGrail - which seems like > the > >> >> ideal number for a leadership group. Do feel free to recruit more > >> >> volunteers to help with the work. I'll reach out every month for > >> updates > >> >> for my board report. > >> >> > >> >> And, of course, I'm very willing to share history, expectations, > >> >> insight, advice, and so on. And you, in turn, are very welcome to > take > >> >> the reins and drive it in a new direction if you have the inspiration > >> to > >> >> do so. > >> >> > >> >> Thanks! > >> >> > >> >> On 5/27/19 1:35 PM, Steve Blackmon wrote: > >> >>> I am willing to lead (or to assist) hackathon coordination. I have > >> >> participated over the past several years and run similar local > events, > >> so I > >> >> think I have a decent idea of what needs to happen on site, and > >> believe I > >> >> can do a decent job of motivating project participation. > >> >>> > >> >>> The more volunteers the better I suspect, as there will be a lot of > >> >> threads to start and follow-up on. > >> >>> On May 27, 2019, 9:37 AM -0500, Rob Tompkins <chtom...@gmail.com>, > >> >> wrote: > >> >>>> > >> >>>> > >> >>>>> On May 27, 2019, at 7:50 AM, Rich Bowen <rbo...@rcbowen.com> > wrote: > >> >>>>> > >> >>>>> > >> >>>>> > >> >>>>>> On 5/27/19 9:45 AM, Kevin A. McGrail wrote: > >> >>>>>> Is the hackathon run all the days of the event? > >> >>>>> > >> >>>>> Yes. All day, every day, in Laughlin 3. Round tables. Power and > >> >> network. Nothing else provided. > >> >>>>> > >> >>>> > >> >>>> Happy to help on this one. As I haven’t owned anything like this, > >> I’ll > >> >> need guidance. > >> >>>> > >> >>>> -Rob > >> >>>> > >> >>>>>> -- > >> >>>>>> Kevin A. McGrail > >> >>>>>> Member, Apache Software Foundation > >> >>>>>> Chair Emeritus Apache SpamAssassin Project > >> >>>>>> https://www.linkedin.com/in/kmcgrail - 703.798.0171 > >> >>>>>>> On Mon, May 27, 2019 at 9:44 AM Rich Bowen <rbo...@rcbowen.com> > >> >> wrote: > >> >>>>>>> I need 1 to 3 volunteers to own the Hackathon for ACNA. > >> >>>>>>> > >> >>>>>>> The Hackathon has long been a central part of ApacheCon. > However, > >> the > >> >>>>>>> success of the hackathon waxes and wanes over the years, due > >> largely > >> >> to > >> >>>>>>> whether someone steps up to drive it. > >> >>>>>>> > >> >>>>>>> The hackathon has multiple intertwined purposes: > >> >>>>>>> > >> >>>>>>> * Attract and mentor new committers > >> >>>>>>> * Strengthen personal bonds within project community > >> >>>>>>> * Foster cross-project cooperation > >> >>>>>>> * Knock out difficult bugs/features/documentation projects > >> >>>>>>> > >> >>>>>>> For this to be successful, the following things need to happen > >> >>>>>>> > >> >>>>>>> * Projects need to know about it > >> >>>>>>> * They need to prepare ahead of time. In particular, they need > to > >> >> think > >> >>>>>>> about what they will be working on > >> >>>>>>> * The plan (ie, what we'll be working on) must be promoted both > >> >> within > >> >>>>>>> the project (so that core project members show up prepared) and > >> >> outside > >> >>>>>>> (so that curious people show up and play along) > >> >>>>>>> * There needs to be great signage on-site, and we need to > mention > >> it > >> >> at > >> >>>>>>> every plenary > >> >>>>>>> > >> >>>>>>> To this end, I need someone(s) to step up to own this. I do not > >> have > >> >>>>>>> time to be the point person on this. > >> >>>>>>> > >> >>>>>>> I need someone who cares about building project communities, is > >> >>>>>>> enthusiastic about working directly with projects to build their > >> >>>>>>> hackathon plans, and who plans to attend ACNA to do the on-site > >> stuff > >> >>>>>>> necessary to support the above. I need someone who is willing to > >> take > >> >>>>>>> the reins on this and drive it without much direction from me or > >> >> anyone > >> >>>>>>> else, and just report back periodically on progress. > >> >>>>>>> > >> >>>>>>> Please let me know if you are willing to lead this effort. Thank > >> you. > >> >>>>>>> > >> >>>>>>> (Note: If you're on the other side of the pond, I expect that > >> Myrle > >> >> will > >> >>>>>>> also be looking for someone to do this for ACEU, too.) > >> >>>>>>> > >> >>>>>>> -- > >> >>>>>>> Rich Bowen - rbo...@rcbowen.com > >> >>>>>>> http://rcbowen.com/ > >> >>>>>>> @rbowen > >> >>>>>>> > >> >>>>>>> > >> --------------------------------------------------------------------- > >> >>>>>>> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org > >> >>>>>>> For additional commands, e-mail: dev-h...@community.apache.org > >> >>>>>>> > >> >>>>>>> > >> >>>>> > >> >>>>> -- > >> >>>>> Rich Bowen - rbo...@rcbowen.com > >> >>>>> http://rcbowen.com/ > >> >>>>> @rbowen > >> >>>>> > >> >>>>> > >> --------------------------------------------------------------------- > >> >>>>> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org > >> >>>>> For additional commands, e-mail: dev-h...@community.apache.org > >> >>>>> > >> >>>> > >> >>>> > --------------------------------------------------------------------- > >> >>>> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org > >> >>>> For additional commands, e-mail: dev-h...@community.apache.org > >> >>>> > >> >>> > >> >> > >> >> -- > >> >> Rich Bowen - rbo...@rcbowen.com > >> >> http://rcbowen.com/ > >> >> @rbowen > >> >> > >> > > >> > >> -- > >> Rich Bowen - rbo...@rcbowen.com > >> http://rcbowen.com/ > >> @rbowen > >> > >> --------------------------------------------------------------------- > >> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org > >> For additional commands, e-mail: dev-h...@community.apache.org > >> > >> >
