On Sat, Oct 31, 2015, at 04:59 PM, Lenni Kuff wrote: > Thanks for all the comments. Based on the previous feedback, we have > tried > to bring any offline discussions back to the dev list and have been using > the dev list as the forum for any decision making (as David pointed out). > In addition, Sravya has organized a regular monthly Google hangout [1] to > help facilitate discussions which may be easier to have face-to-face/over > the phone. The hangout will be open for anyone to join and all meeting > notes will be posted back the dev mailing list.
"Have tried" is not the same as actually doing, nor am I comfortable at this stage saying "yes, as a mentor I feel this group has adopted best practices from Apache and is going to continue doing this on its own post-graduation." "Sravya has organized a regular monthly Google hangout" not quite. Sravya has sent out an email that appears to have gone directly to VOTE (no DISCUSS) for a 30-minute hangout. Note that this was about a week ago, and none of these hangouts have actually happened - so it's impossible to judge its effectiveness and describing it as "regular" at this point is a bit early. (As a side note, as much as I prefer discussions happen on a mailing list - if you're going to do a real-time conversation, I am not sure 30 minutes is sufficient. At least in my experience, it usually takes ~5 minutes for a distributed team to actually join a call and get started, and if you have any amount of discussion at all it would take some ruthless efficiency to get through a discussion *and* have time for an open floor for newcomers to ask questions.) > I apologize, but it's still bit unclear to me - based on the remaining > criteria you outlined - specifically what we still need to accomplish > before graduation. So - the discussion at ApacheCon happened, what, about a month ago? The types of things we're pointing out are not just checkboxes for the project to tick off, but fundamental practices we need to see in order to say "yes, this project is going to behave like an Apache project after graduation." Is Sentry producing code? Yes. Is Sentry producing releases? Yes. Is Sentry's infrastructure (Web site, Jira, mailing lists, and so on) in order? Yes.* All great! The tough one: Is Sentry creating an open and diverse community that allows anyone to participate? Right now, I don't think Sentry is there. What I see right now is a podling that has had a fair amount of communication about development out of the public eye and/or in channels that are difficult to join for the public at large. David and I have given feedback on steps Sentry can take to remedy this. What Sentry needs to accomplish now is to follow through on this and build a track record there. (See also [1]) * Pretty sure. I did a quick cursory glance and things look good. [1] http://incubator.apache.org/guides/community.html#communication Best, jzb -- Joe Brockmeier [email protected] Twitter: @jzb http://www.dissociatedpress.net/
