Those are all great topics for helping newcomers get started. If people want to 1) see what new committer docs we have, and 2) also suggest patches for it ;-) then start here, and see what things make sense to improve or include in any training/intros:
https://www.apache.org/dev/ https://community.apache.org/newcomers/index.html While some "how do I do X as a committer" information is elsewhere, the bulk of it is available from one or two clicks from those two pages. (And yes, we'd love it if any tech writer/editors wanted to improve the intros and descriptions on those pages) Just an idea... -- - Shane ComDev PMC The Apache Software Foundation Austin Bennett wrote on 2019-5-28 9:47PM EDT: > Yes, @Aizhamal I agree. > > Though, It is largely unclear to me the things that are core Apache as part > of commons and those that might be project specific. It is easy to take > the perspective of here's how a specific project works which is similar to > most others. It is another to dig into all projects. Perhaps incubator or > some other governance prescribes some bits? I suspect, at a minimum, there > are differences between each/all projects. > > Ex: > Differences??? > * user@ is not required (anecdotally, since Airflow just got) > * Slack groups > * GitHub > > Common??? > * dev@ > * JIRA > > > > On Tue, May 28, 2019 at 3:38 PM Aizhamal Nurmamat kyzy <aizha...@google.com> > wrote: > >> 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 ...snip... --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
