community-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Aizhamal Nurmamat kyzy <>
Subject Re: on "meritocracy"
Date Fri, 29 Mar 2019 16:35:23 GMT
If you need volunteers, please count me in as well.


On Fri, Mar 29, 2019 at 9:33 AM Ross Gardler <> wrote:

> I'm in
> Get Outlook for Android<>
> ________________________________
> From: Sam Ruby <>
> Sent: Friday, March 29, 2019 9:07:59 AM
> To: Apache Community Dev
> Subject: Re: on "meritocracy"
> On Fri, Mar 29, 2019 at 11:37 AM Griselda Cuevas
> <> wrote:
> >
> > Another thing we should consider is creating a D&I council, PMC, working
> > group (or something alike) for the ASF, and I'd love to be part of it.
> >
> > Now, I have to share my feelings with discussions on this list.
> Sometimes I
> > struggle to understand when a conversation is ready for action. I feel
> like
> > I've seen so many great ideas, and I don't have visibility into when they
> > start to happen or when I should start working on things. This time I'm
> > offering to lead... so how could I do it?
> TL;DR: identify a list of tangible deliverables, and I'll help you
> make it happen.
> Longer answer:
> Organizationally, this could be one of the things that is done under
> the comdev umbrella, it could be something that reports to the
> president, or it could be something that reports to the board.
> The third option requires a board resolution.  The middle option is
> less clear, but in such cases we err on the side of clarity so a board
> resolution would be prepared.  No board interaction is required for
> the first option, though a notification in the next board report would
> be in order.
> Operationally, this would start pretty much the way everything starts
> at the ASF: with the creation of a mailing list.  What this will be is
> a quieter place where people who actually want to do the work get
> together and make it happen.  I will caution you that often times,
> those people don't show up, and this ultimately means that it becomes
> a place to ideas go to die.  And I will say that similar efforts have
> died this way in the past.
> Part of what makes PMCs work is that they have a tangle product (code)
> and deliverables (releases).  This helps keep things focused.
> Outside of the Code of Conduct, focus is not a word I would use to
> characterize most of the discussions to date on diversity.  We need to
> fix that.
> So... if we (and by that I'm specifically looking for volunteers) can
> identify tangible work products and there is a commitment to provide
> written monthly status reports detailing progress towards the
> production of those work products, I am prepared to support the
> creation of an officer and committee responsible.  I don't believe
> that this committee needs board authority (at least not yet), and Ross
> and I both clearly are interested in making this work.  This leads me
> to recommend a path of the creation of a President's committee.
> Circling back, board resolutions are generally evaluated monthly (out
> of band is possible, but there is no reason here to force the issue).
> The schedule is here:
> While shooting for April is definitely possible, I would recommend
> shooting for May.  And the setting up of a mailing list doesn't need
> to wait for the board resolution - if there is sufficient progress, I
> can ask the infrastructure team to make it happen.
> - Sam Ruby
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:


*Aizhamal Nurmamat kyzy*

Open Source Program Manager

646-355-9740 Mobile

601 North 34th Street, Seattle, WA 98103

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