couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Andy Wenk <andyw...@apache.org>
Subject Re: Suggestion: a few more details in new committer emails
Date Sun, 09 Nov 2014 19:42:14 GMT
I sugget to change the email template and ask the new commiter to introduce
himself. As it alreafy happened :)
On Nov 8, 2014 6:46 PM, "Noah Slater" <nslater@apache.org> wrote:

> Some comments on this, as I'm largely responsible for the current system:
>
> - The emails are templates, as this makes it much easier to run the
> project admin stuff. The wording has been changed over time to reflect
> our evolving election criteria. (It used to be very code focused.
> Thankfully, that is not the case any more.)
>
> - An intro would be nice. This could be done in two ways, the PMC
> member running the election could ask the new committer for one ahead
> of time, or the template email could be modified to ask the new
> committer to introduce themselves. Thoughts?
>
> - dev@ is the development list, i.e. the place where committers get
> together and work on CouchDB. This is not exclusively about code. This
> is about any sort of work on our product, project, or community. So
> yes, this is the appropriate list. users@ is a support forum, and
> those people don't care about committer announcements. none of the
> other lists are appropriate either.
>
> - It's fine and expected that some committers have never had reason to
> post there before. Part out our diversity efforts means recognising
> contributions in lots of different forms. Contributing to threads on
> dev@ is just one form.
>
>
> On 7 November 2014 11:46, Klaus Trainer <klaus_trainer@posteo.de> wrote:
> > +1 for asking new committers to introduce themselves
> >
> >
> > On 07.11.2014 10:13, Andy Wenk wrote:
> >> Hey Dirkjan,
> >>
> >> thanks a lot for your input. I personally think it's a great idea to add
> >> some info to the email for announcing a new committer. One other idea,
> and
> >> I would prefer this, is to ask the new committers to introduce them
> selfs
> >> after they have been announced. The ASF is doing this similarly with new
> >> members and it's a great way to get to know what people are doing. We
> would
> >> ask the committers in the done_committer email:
> >>
> https://git-wip-us.apache.org/repos/asf?p=couchdb-admin.git;a=blob_plain;f=email/done_committer.txt;hb=HEAD
> >> . Here is a very quick draft:
> >>
> >> "The community would like to know a bit about you. Please write a short
> >> email to [which lists?] and introduce yourself. Here is a list with some
> >> points you could cover:
> >>
> >> * in which areas do you contribute to CouchDB
> >> * what are your interests in IT
> >> * anything else you would like the community know about you
> >> "
> >>
> >> The fact, that the announcement email is solely sent to dev@ is also
> not
> >> really clear to me (and I stumbled over it while sending the
> announcement
> >> of Javier ;-) ). I think this is done because dev@ is still the biggest
> >> list and also the main list (historically in all ASF projects). I
> suggest
> >> to change this because we do have committers not only (and also not at
> all)
> >> committing code. So - maybe I will be mobbed for this :) - why not
> sending
> >> to all lists?
> >>
> >> We do also announce new committers via the social media channels and
> also
> >> in the weekly news. But still - we should change the announcement
> >> recipients.
> >>
> >> All the best
> >>
> >> Andy
> >>
> >> On 7 November 2014 09:31, Dirkjan Ochtman <dirkjan@ochtman.nl> wrote:
> >>
> >>> Hi there,
> >>>
> >>> I wanted to suggest that, in the emails announcing new committers, one
> >>> or two sentences could describe in what area the new committer has
> >>> been contributing. The emails currently feel pretty bland to me, and
> >>> adding a little personal content couldn't hurt. Another thing to add
> >>> could be how they are related to CouchDB (e.g. if they're contributing
> >>> on behalf of their employer, if they're using CouchDB or a related
> >>> project for some interesting project of their own).
> >>>
> >>> Another, related problem with the emails that I see: though I'm no
> >>> longer closely tracking what's happening in the broader CouchDB
> >>> ecosystem, it feels weird to me that the announcements happen on the
> >>> dev@ list, when some of the committers being announced have ostensibly
> >>> never even sent a single email there. I don't really have a suggestion
> >>> for solving this.
> >>>
> >>> Cheers,
> >>>
> >>> Dirkjan
> >>>
> >>
> >>
> >>
> >
>
>
>
> --
> Noah Slater
> https://twitter.com/nslater
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message