Re: Beam's recent community development work

[Huxing Zhang]

Thanks for sharing, really nice post. I've learned a lot.

I think this can be a good example for incubating project like Dubbo,
which is facing the same issue here: not enough committer to review
the issue report and pull request.


On Sat, Jun 30, 2018 at 2:15 PM, Kenneth Knowles  
wrote:
> Hi all,
>
> The ASF board suggested that we (Beam) share some of what we've been doing
> for community development with dev@community.apache.org and
> memb...@apache.org. So here is a long description. I have included
> d...@beam.apache.org because it is the subject, really, and this is & should
> be all public knowledge.
>
> We would love feedback! We based a lot of this on reading the community
> project site, and probably could have learned even more with more study.
>
> # Background
>
> We face two problems in our contributor/committer-base:
>
> 1. Not enough committers to review all the code being contributed, in part
> due to recent departure of a few committers
> 2. We want our contributor-base (hence committer-base) to be more spread
> across companies and backgrounds, for the usual Apache reasons. Our user
> base is not active and varied enough to make this automatic. One solution
> is to make the right software to get a varied user base, but that is a
> different thread :-) so instead we have to work hard to build our community
> around the software we have.
>
> # What we did
>
> ## Committer guidelines
>
> We published committer guidelines [1] for transparency and as an
> invitation. We start by emphasizing that there are many kinds of
> contributions, not just code (we have committers from community
> development, tech writing, training, etc). Then we have three aspects:
>
> 1. ASF code of conduct
> 2. ASF committer responsibilities
> 3. Beam-specific committer responsibilities
>
> The best way to understand is to follow the link at the bottom of this
> email. The important part is that you shouldn't be proposing a committer
> for other reasons, and you shouldn't be blocking a committer for other
> reasons.
>
> ## Instead of just "[DISCUSS] Potential committer XYZ" we discuss every
> layer
>
> Gris (CC'd) outlined this: people go through these phases of relationship
> with our project:
>
> 1. aware of it
> 2. interested in it / checking it out
> 3. using it for real
> 4. first-time contributor
> 5. repeat contributor
> 6. committer
> 7. PMC
>
> As soon as we notice someone, like a user asking really deep questions, we
> invite discussion on private@ on how we can move them to the next level of
> engagement.
>
> ## Monthly cadence
>
> Every ~month, we call for new discussions and revisit ~all prior
> discussions. This way we do not forget to keep up this effort.
>
> ## Individual discussions
>
> For each person we have a separate thread on private@. This ensures we have
> quality focused discussions that lead to feedback. In collective
> discussions that we used to do, we often didn't really come up with
> actionable feedback and ended up not even contacting potential committers
> to encourage them. And consensus was much less clear.
>
> ## Feedback!
>
> If someone is brought up for a discussion, that means they got enough
> attention that we hope to engage them more. But unsolicited feedback is
> never a good idea. For a potential committer, we did this:
>
> 1. Send an email saying something like "you were discussed as a potential
> committer - do you want to become one? do you want feedback?"
> 2. If they say yes (so far everyone) we send a few bullet points from the
> discussion and *most important* tie each bullet to the committer
> guidelines. If we have no feedback about which guidelines were a concern,
> that is a red flag that we are being driven by bias.
>
> We saw a *very* significant increase in engagement from those we sent
> feedback to, and the trend is that they almost all will become committers
> over time.
>
> ## Results
>
>  - Q1 we had no process and we added no new committers or PMC members.
>  - Q2 when we tried these new things we added 7 committers and 1 PMC
> member, with ~3~4 obvious committer candidates for next time around, plus
> positive feedback from other contributors, spread across five companies.
>
> We've had a pretty major uptick in building Beam as a result.
>
> ## Review-then-commit
>
> We are dedicated to RTC as the best way to build software. Reviews not only
> make the code better, but (with apologies to ASF/GNU differences) as RMS
> says "The fundamental act of friendship among programmers is the sharing of
> programs" and reviews are where we do that.
>
> As a minor point, we also changed our "review-then-commit" policy to
> require that *either* the reviewer or the author be a committer. Previously
> the reviewer had to be a committer. Rationale: if we trust someone as a
> committer, we should trust their choice of reviewer. This also helps the
> community, as it engages non-committers as reviewers.
>
> 
>
> If you made it through this long email, thanks for re

Re: Speakers and booth support needed at the next Codemotion events

[Ismaël Mejía]

Hello,

Getting late to the party. This is great news and I write just to say
thanks to PJ for all his work to get this to happen, well done PJ!

Regards,
Ismaël

ps. From looking at the dates + already passed deadlines  I won’t be
able to make it but would have loved to submit a proposal for the
Milan one. Well maybe next year.


On Tue, Jul 10, 2018 at 10:25 PM Piergiorgio Lucidi
 wrote:
>
> Hi Lars,
>
> I will forward your request to understand if we have more time for any new
> submission for Berlin.
>
> Cheers,
> PJ
>
>
> Il giorno lun 9 lug 2018 alle ore 11:01 Lars Francke 
> ha scritto:
>
> > Hi,
> >
> > I only saw this whole thread now. I won't be able to make it to Madrid or
> > Milan but if help for Berlin is still needed let me know. I know that the
> > Deadline for Berlin has already ended but sometimes they are extended or
> > they need a last minute thing. I'm happy to talk about either Apache itself
> > or a technical thing (e.g. HBase, NiFi, ...).
> >
> > Cheers,
> > Lars
> >
> > On Sun, Jul 8, 2018 at 10:22 PM, Piergiorgio Lucidi <
> > piergior...@apache.org>
> > wrote:
> >
> > > Hi,
> > >
> > > here some news related to our involvement at Codemotion events.
> > >
> > > Berlin
> > > It seems that it could be tricky for them to give us enough space for a
> > > booth in Berlin, the space in that location seems limited compared to the
> > > other ones. So probably we could automatically exclude this location and
> > > consider only Madrid and Milan or we could join the event with less
> > > evidence of our presence.
> > >
> > > Considering that we have recently covered Berlin for the Apache EU
> > Roadshow
> > > it could be fine for us.
> > > If in Berlin we can't have a booth we only could have a presence as
> > > speakers with one or more sessions.
> > >
> > > If you have submitted a proposal for Codemotion with a beginner level,
> > > please try to rewrite it for at least as intermediate level sessions.
> > They
> > > would like to receive advanced topics.
> > >
> > > Madrid
> > > You could submit a proposal for Madrid (until July 17th) and please
> > > consider again that they would like to receive advanced topics from us
> > (for
> > > senior architects and developers):
> > > https://madrid2018.codemotionworld.com/es/call-for-papers-guia/
> > >
> > > Milan
> > > We will have a booth as said before.
> > >
> > > More details during the next weeks, please let me know your feedback.
> > > Thank you.
> > >
> > > Cheers,
> > > PJ
> > >
> > >
> > > Il giorno mer 4 lug 2018 alle ore 09:39 Piergiorgio Lucidi <
> > > piergior...@apache.org> ha scritto:
> > >
> > > > Hi Luciano,
> > > >
> > > > thank you for submitting your proposals.
> > > > I'll talk with them about this.
> > > >
> > > > PJ
> > > >
> > > > Il giorno mar 3 lug 2018 alle ore 22:26 Luciano Resende <
> > > > luckbr1...@gmail.com> ha scritto:
> > > >
> > > >> On Mon, Jul 2, 2018 at 10:28 AM Piergiorgio Lucidi <
> > > >> piergior...@apache.org>
> > > >> wrote:
> > > >>
> > > >> > Hi,
> > > >> >
> > > >> > Il giorno lun 2 lug 2018 alle ore 16:26 Rich Bowen <
> > > rbo...@rcbowen.com>
> > > >> ha
> > > >> > scritto:
> > > >> >
> > > >> > > I've added these three events to
> > > >> > >
> > > >> > >
> > > >> >
> > > >> https://docs.google.com/spreadsheets/d/13qjsoZBFXYz7LDqPLka8Wm4mwdwA3
> > > EitTYQBmcYnN5A/edit#gid=0
> > > >> > > and will try to get them into our @apachecommunity twitter
> > schedule
> > > >> > > soon. If you can provide the missing information (basically a URL
> > > and
> > > >> a
> > > >> > > twitter handle) that will help. Thanks.
> > > >> > >
> > > >> >
> > > >> > I have just added some informations in the spreadsheet.
> > > >> > I should be available to take care of the booth in Milan and also in
> > > >> > Berlin, we actually have Ignasi for Madrid :)
> > > >> >
> > > >> > I'll ask if we can send proposals also after the CFP, but anyway I
> > > think
> > > >> > that for the keynote we can have more time.
> > > >> >
> > > >> > Cheers,
> > > >> > PJ
> > > >> >
> > > >>
> > > >> I have submitted some technical proposals for Codemotion Berlin/Milan
> > > and
> > > >> if accepted I can help with booth and community sessions.
> > > >>
> > > >> --
> > > >> Luciano Resende
> > > >> http://twitter.com/lresende1975
> > > >> http://lresende.blogspot.com/
> > > >>
> > > >> --
> > > >> Piergiorgio
> > > >> 
> > > >
> > > >
> > >
> > > --
> > > Piergiorgio
> > >
> >
> > --
> > Piergiorgio
> >

-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org