Also, where should the ticket/issue get filed? Is this comdev? Is there Jira/GH-issues for Comdev and/or P&M? Naturally, also in relevant projects' codebases if implemented.
This doesn't seem the right location, as it seems a collection of issues related to many individual projects? https://issues.apache.org/jira/projects/COMDEV/ On Tue, Sep 27, 2022 at 3:35 PM Austin Bennett <whatwouldausti...@gmail.com> wrote: > If auto-messaging first time contributors on their first merge, is there a > specific message you'd like to 'advertise'/suggest that they reach out to > P&M ( including contact method )? > > On Tue, Sep 27, 2022 at 2:41 PM Melissa Logan <meli...@constantia.io> > wrote: > >> Great input, please keep it coming. Others, let us know if you/your >> community would like to participate. >> >> One of the things that seems important is making sure that projects >> are also engaged - or, more specifically, that we only promote first- >> contrib for projects that are engaged. >> > Rich, great feedback and we will be using this approach. And thanks for >> >> Happy to help with publicising and with reaching out to our contributors. >> I >> can get some good examples from the past and current (we have a >> more-or-less constant stream of new contributors at Airflow (in the order >> of 10 new contributors a week I think). >> > Jarek, fantastic! We will be in touch. >> >> We also just started an initiative together with a few people from Apache >> Beam (something that I wanted to mention at the talk) that we want to >> start >> measuring the behaviours of contributors, discussions, etc and eventually >> turn it into a tool of sorts that will help commiters and PMC members and >> encourage/engage new contributors or prospective contributors to our >> projects to continue/grow/make their first serious contributions. >> > Jarek, please do keep us informed as this progresses. There are >> additional ways M&P could help promote. >> >> Though concretely getting a PR >> created and merged is very straightforward, I also try to highlight the >> many ways to contribute that are not code. Interacting people right as >> they are addressing could prove useful and yield interesting stories, and >> there are ways to cast a net to find people that might want to opt into >> the >> initiative for sharing about their first contribution that is much 'lower >> touch'. >> > Austin, we agree completely. We would like to highlight all types of >> contributions. >> >> Should we get a general recipe together for projects >> can add this to their repos ( in that case, where to point >> first-time-contributors, a specific email/other?) ? >> > This is an interesting idea. Some projects may have a workflow/docs in >> place; let's find out! This campaign could serve the dual purpose of >> enabling us to aggregate best practices across communities for first-time >> contributors. >> >> On Tue, Sep 27, 2022 at 1:52 PM Austin Bennett >> <whatwouldausti...@gmail.com> wrote: >> > >> > Happy to help. Along with mentoring in Google Summer of Code, I've led >> > workshops in a number of capacities and conferences/venues/countries ( >> Beam >> > Summit, HOPE <https://hope.net/>, etc ) on helping people get their >> first >> > code contribution into a[n apache :-) ] project, outlining general paths >> > for contributing, and community overall. Though concretely getting a PR >> > created and merged is very straightforward, I also try to highlight the >> > many ways to contribute that are not code. Interacting people right as >> > they are addressing could prove useful and yield interesting stories, >> and >> > there are ways to cast a net to find people that might want to opt into >> the >> > initiative for sharing about their first contribution that is much >> 'lower >> > touch'. >> > >> > >> > To the specifics of publicizing/amplifying what is already happening: >> for >> > GitHub based projects, there are very low effort ways to let >> first-time-PR >> > contributors know to opt-in/contact marketing. For example, see: >> > https://github.com/behaviorbot/first-pr-merge ... and specifically: ' >> > firstPRMergeComment'. It would potentially be easy for any project to >> add >> > that, along with a message to contact >> > ComDev/P&M/specific-contact-information? The thought is that would help >> > grow our communities? Should we get a general recipe together for >> projects >> > can add this to their repos ( in that case, where to point >> > first-time-contributors, a specific email/other?) ? Then, potentially >> just >> > a matter of getting potentially interested PMCs to add to their repos. >> > >> > >> > My only concern would be ensuring that this gets updated/removed from >> > repos, once no longer an initiative from p&m. Said another way, if >> asking >> > new contributors to contact someone, we need those people to be >> responsive, >> > else it needs to be updated/removed. >> > >> > >> > >> > On Tue, Sep 27, 2022 at 12:02 PM Jarek Potiuk <ja...@potiuk.com> wrote: >> > >> > > Great idea. >> > > >> > > Happy to help with publicising and with reaching out to our >> contributors. I >> > > can get some good examples from the past and current (we have a >> > > more-or-less constant stream of new contributors at Airflow (in the >> order >> > > of 10 new contributors a week I think). >> > > Also happy to brainstorm/discuss at ApacheCon - we have a talk with >> Ismael >> > > "Growing your contributor's base" which is pretty relevant. >> > > >> > > We also just started an initiative together with a few people from >> Apache >> > > Beam (something that I wanted to mention at the talk) that we want to >> start >> > > measuring the behaviours of contributors, discussions, etc and >> eventually >> > > turn it into a tool of sorts that will help commiters and PMC members >> and >> > > encourage/engage new contributors or prospective contributors to our >> > > projects to continue/grow/make their first serious contributions. We >> could >> > > likely connect those efforts somehow. There is a (rather little) >> chance we >> > > will have some very early dashboard prototype by the ApacheCon, but I >> think >> > > all involved people will be at the ApacheCon and maybe we will find >> time to >> > > talk about it :)? >> > > >> > > J. >> > > >> > > >> > > On Tue, Sep 27, 2022 at 6:47 PM Rich Bowen <rbo...@rcbowen.com> >> wrote: >> > > >> > > > This is certainly something that we have talked about over the >> years, >> > > > but never got around to, so having M&P providing some steam behind >> > > > this is very welcome. >> > > > >> > > > One of the things that seems important is making sure that projects >> > > > are also engaged - or, more specifically, that we only promote >> first- >> > > > contrib for projects that are engaged. I say this because we had >> some >> > > > first contributor stuff around a recent Apachecon, and the target >> > > > project almost rejected the whole lot because it was "pizzas we >> didn't >> > > > order" and they hadn't been involved in the conversation. We managed >> > > > to get them to review and accept most of the contributions, >> > > > eventually, but it was an awkward situation. >> > > > >> > > > Anyways, count me in for mentoring and whatever, although time may >> be >> > > > limited. >> > > > >> > > > --Rich >> > > > >> > > > On Tue, 2022-09-27 at 11:23 -0400, Joe Brockmeier wrote: >> > > > > Hi all, >> > > > > >> > > > > We (M&P) would like to propose a collaboration with ComDev about >> > > > > encouraging new contributions to ASF projects. >> > > > > >> > > > > Melissa Logan and the Constantia team have drafted a set of >> > > > > messaging >> > > > > and plan for the campaign with an objective of reaching 50 or more >> > > > > people to share their first contribution to an ASF project on >> social >> > > > > media, etc. >> > > > > >> > > > > Much of this activity is happening *anyway* but we'd like to >> > > > > recognize >> > > > > and encourage it. I'd like to do that with ComDev to: >> > > > > >> > > > > 1) Amplify the effort: If folks in ComDev would like to >> participate >> > > > > in >> > > > > mentoring, boosting the signal on social media, and/or helping >> with >> > > > > the marketing side of things that would be awesome. >> > > > > 2) Get input: As I said, people are already making their first >> > > > > contributions and we could solicit contributors to speak up - but >> > > > > I'd >> > > > > like to make sure the campaign is aligned with ComDev! >> > > > > 3) Avoid unwelcome surprises! This is an area with a lot of >> overlap >> > > > > and we didn't want to spring it on folks without notice. Even if >> > > > > nobody in ComDev participates, having awareness and assent is >> > > > > important. >> > > > > >> > > > > Our current messaging draft is in Google Docs -- happy to give >> > > > > access >> > > > > or share out in Hackmd.io or something else. I can just shoot text >> > > > > to >> > > > > the mailing list, of course, but that's often painful when giving >> > > > > feedback on prose. >> > > > > >> > > > > Best, >> > > > > >> > > > > jzb >> > > > > >> > > > >> > > > >> > > > >> > > > >> > > > >> --------------------------------------------------------------------- >> > > > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org >> > > > For additional commands, e-mail: dev-h...@community.apache.org >> > > > >> > > > >> > > >> >> >> >> -- >> Melissa Logan (she/her) >> Principal, Constantia.io >> LinkedIn | Twitter >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org >> For additional commands, e-mail: dev-h...@community.apache.org >> >>
