HI Roman, I am one of the mentors for MetaModel podling. The initial discussion about bylaws come from me since I had some bad experience with some projects so I brought up the topic. But per recommendations by other mentors in the podling we decided to put off the bylaws effort for now.
But you are right, at this point the discussion is too early and we are now trying to get back to focus on delivering a release. Thanks for the report =) - Henry On Mon, Jan 6, 2014 at 9:46 PM, Roman Shaposhnik <r...@apache.org> wrote: > -------------------- > Aurora > > Justin Mclean (jmclean): > > Project is off to a good start with lots of activity on the mailing list > and in JIRA. Mentors are not very active but there are no issues that > need attention. > > -------------------- > BatchEE > > John Ament (johndament): > > BatchEE is a new podling, with a small team working on it currently. > It's a fork of the RI for Java Batch from Java EE 7. I think short term > they should focus on getting a release out there to draw in community > interest; which should help build the podling more and drive feature > interest. > > -------------------- > Celix > > Dave Fisher (wave): > > This podling is growing. They plan a release soon and let's see how that > goes. When it comes time for graduation I have some concerns that this > podling's community may be too small. > > -------------------- > log4cxx2 > > Christian Grobmeier (grobmeier): > > the podling is just getting started > > -------------------- > MetaModel > > Roman Shaposhnik (rvs): > > In general project seem to be on the right track with a healthy amount > of community interaction happening over the mailing list and a strong > desire to do a release. Two issues have caught my attention though: > > 1. I am not quite sure what motivated a strong drive towards having > by-laws this early in the game. In my experience the focus on by-laws > can, at times, put a damping factor on community growth. IOW, what > I've seen in the past is that communities try to come up with by-laws > when the usual process of consensus building starts to fail. Nothing > actionable here for the project -- just keep this in mind. > 2. The JIRA feels a bit empty for the project that has been developing > for more than 6 month (grand total of 33 issues). At the same time > the number of commits in the Git repo is on par with the development > pace. What it tells me is that there's no strong correlation between > JIRAs and commits. This raises a red flag of whether all of the > changes that are committed get a proper community vetting before they > go in. I couldn't find any traces of the review requests either: > https://reviews.apache.org/groups/metamodel/ > This in my opinion is a pretty big concern for the project. > > -------------------- > ODF Toolkit > > John Ament (johndament): > > ODF Toolkit has been incubating for a long time. Activity on their list > is in frequent, but active enough that it still is running. Considering > what the project is, I think the best resolution for this podling is to > graduate as a sub project under something like OpenOffice or POI. > > -------------------- > Olingo > > (No shepherd review filed.) > > -------------------- > Ripple > > Roman Shaposhnik (rvs): > > The project appears to be doing well > > -------------------- > Samza > > (No shepherd review filed.) > > -------------------- > Sirona > > (No shepherd review filed.) > > -------------------- > Spark > > Alan Cabrera (acabrera): > > Seems like a nice active project. IMO, there's no need to wait import > to JIRA to graduate. Seems like they can graduate now. > > -------------------- > Stratos > > Raphael Bircher (rbircher): > > The project looks realy active. Continue like this guys! > > -------------------- > Twill > > (No shepherd review filed.) > > -------------------- > VXQuery > > Raphael Bircher (rbircher): > > The mailing list traffic is not very high. However, the basic > discussions are on the lists. > > > -------------------- > Usergrid > > (No shepherd review filed.) > > --------------------------------------------------------------------- > > --------------------------------------------------------------------- > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
