Wiki write access for CharlesSimpson
Could I have wiki write access for CharlesSimpson to contribute to the Hoya incubator proposal? Thanks, Charles
Re: Wiki write access for CharlesSimpson
Done On 7 January 2014 15:15, Charles Simpson csimp...@gmail.com wrote: Could I have wiki write access for CharlesSimpson to contribute to the Hoya incubator proposal? Thanks, Charles - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Shepherding January 2014
Hey Roman The mentor activity for Aurora has occurred mostly on the private@ list and on irc regarding more process oriented questions than anything else due to a lot of previous involvement by new committers with Apache Mesos in some form or another. Overall project is off to a great start and no current issues as Justin mentioned. -Jake On Tue, Jan 7, 2014 at 12:46 AM, 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
Re: Shepherding January 2014
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
Re: Shepherding January 2014
On Tue, Jan 7, 2014 at 9:51 AM, Henry Saputra henry.sapu...@gmail.com wrote: 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 =) Glad it was helpful! Thanks, Roman. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Shepherding January 2014
Great to know! Thanks for the clarification! Thanks, Roman. On Tue, Jan 7, 2014 at 9:43 AM, Jake Farrell jfarr...@apache.org wrote: Hey Roman The mentor activity for Aurora has occurred mostly on the private@ list and on irc regarding more process oriented questions than anything else due to a lot of previous involvement by new committers with Apache Mesos in some form or another. Overall project is off to a great start and no current issues as Justin mentioned. -Jake On Tue, Jan 7, 2014 at 12:46 AM, 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
Re: January 2014 Incubator report timeline
Pardon the dumb question but how do I get the phoenix podling's first report to show on this page: http://wiki.apache.org/incubator/January2014 ? Thanks, St.Ack On Wed, Dec 25, 2013 at 5:22 PM, Roman Shaposhnik r...@apache.org wrote: January 2014 Incubator report timeline: http://wiki.apache.org/incubator/January2014 Wed January 01 -- Podling reports due by end of day Sun January 05 -- Shepherd reviews due by end of day Sun January 05 -- Summary due by end of day Tue January 07 -- Mentor signoff due by end of day Wed January 08 -- Report submitted to Board Wed January 15 -- Board meeting - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: transferring Github issues to JIRA?
So that means we need an INFRA ticket to plug that in and run an import? On Mon, Jan 6, 2014 at 4:16 PM, Steve Rowe sar...@gmail.com wrote: Atlassian provides a plugin for that: https://marketplace.atlassian.com/plugins/com.atlassian.jira.plugins.jira-importers-github-plugin On Mon, Jan 6, 2014 at 6:55 PM, James Taylor jamestay...@apache.org wrote: Hello, Anyone out there know of an automated way of transferring over Github issues to JIRA? We're in the process of transferring over our existing Phoenix Github-based open source project to our Apache incubator project and automating the seeding of the initial JIRAs would be very helpful. Thanks, James -- Best regards, - Andy Problems worthy of attack prove their worth by hitting back. - Piet Hein (via Tom White)
Re: Shepherding January 2014
Hi, Just a note to say I've updated the Aurora shepherd report to make it clear that one of the four mentors (Jake Farrell) has been very active. Thanks, Justin - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: January 2014 Incubator report timeline
On Tue, Jan 7, 2014 at 11:38 AM, Stack st...@duboce.net wrote: Pardon the dumb question but how do I get the phoenix podling's first report to show on this page: http://wiki.apache.org/incubator/January2014 ? Glad to see Phoenix's first report! As an anti-spam measure, ASF wikis must whitelist contributors. See the top of http://wiki.apache.org/incubator/. Please let us know your wiki username (not Apache ID) and we will add you to the ContributorsGroup whitelist. For future reference, please note that podling reports are due two weeks before the Board meeting and a week before the Incubator VP files the report. If a podling report shows up one day before we file, there's not enough time to go through shepherding, etc. So far, we've just been accepting late reports and asking nicely for future punctuality, but at some point we may start rejecting them like the Board does. Ostensibly the Board expects the IPMC to review all podling reports before we file the aggregate report; if we ever institute such a process, we'll almost certainly start rejecting late reports then. Marvin Humphrey - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: January 2014 Incubator report timeline
On Tue, Jan 7, 2014 at 1:42 PM, Marvin Humphrey mar...@rectangular.comwrote: On Tue, Jan 7, 2014 at 11:38 AM, Stack st...@duboce.net wrote: Pardon the dumb question but how do I get the phoenix podling's first report to show on this page: http://wiki.apache.org/incubator/January2014 ? Glad to see Phoenix's first report! Wait till you read it first! (smile). As an anti-spam measure, ASF wikis must whitelist contributors. See the top of http://wiki.apache.org/incubator/. Please let us know your wiki username (not Apache ID) and we will add you to the ContributorsGroup whitelist. MichaelStack For future reference, please note that podling reports are due two weeks before the Board meeting and a week before the Incubator VP files the report. If a podling report shows up one day before we file, there's not enough time to go through shepherding, etc. So far, we've just been accepting late reports and asking nicely for future punctuality, but at some point we may start rejecting them like the Board does. Ostensibly the Board expects the IPMC to review all podling reports before we file the aggregate report; if we ever institute such a process, we'll almost certainly start rejecting late reports then. Understood. All my fault: i.e. the mentor. Thanks for taking our report though late. I'll add it soon my credentials are blessed. Thanks Marvin, St.Ack
Re: January 2014 Incubator report timeline
On Tue, Jan 7, 2014 at 2:14 PM, David Crossley cross...@apache.org wrote: Stack wrote: Marvin Humphrey wrote: As an anti-spam measure, ASF wikis must whitelist contributors. See the top of http://wiki.apache.org/incubator/. Please let us know your wiki username (not Apache ID) and we will add you to the ContributorsGroup whitelist. MichaelStack Done. Thanks David. I went ahead and added up the Phoenix report (I removed us from the non-reporters list -- smile). I did not know what to fill in for the 'signed-off by' list so left it blank. Let me go ping our Shepherd for this period; hopefully he is just as forgiving of our late submission. Thanks for the help, St.Ack
Re: January 2014 Incubator report timeline
On Tue, Jan 7, 2014 at 3:49 PM, Stack st...@duboce.net wrote: I went ahead and added up the Phoenix report (I removed us from the non-reporters list -- smile). Great, thanks! I did not know what to fill in for the 'signed-off by' list so left it blank. It's a list of Mentors who have seen the report and approved it. I took the liberty of filling in the checkboxes for Enis Sözutar and Devaraj Das because they both sent +1 emails to dev@phoenix.incubator. Let me go ping our Shepherd for this period; hopefully he is just as forgiving of our late submission. The main thing we need shepherds for is to signal the IPMC when all Mentors have gone missing and a podling is adrift. The secondary function of providing outsider feedback can be helpful, but it's best not to add commentary late in the process because we want to give the podling the chance to respond if necessary. Clearly the Mentors for Phoenix are engaged, and I plan to file the Incubator report tomorrow regardless. Marvin Humphrey - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: January 2014 Incubator report timeline
On Tue, Jan 7, 2014 at 5:24 PM, Marvin Humphrey mar...@rectangular.comwrote: On Tue, Jan 7, 2014 at 3:49 PM, Stack st...@duboce.net wrote: I went ahead and added up the Phoenix report (I removed us from the non-reporters list -- smile). Great, thanks! I did not know what to fill in for the 'signed-off by' list so left it blank. It's a list of Mentors who have seen the report and approved it. I took the liberty of filling in the checkboxes for Enis Sözutar and Devaraj Das because they both sent +1 emails to dev@phoenix.incubator. Let me go ping our Shepherd for this period; hopefully he is just as forgiving of our late submission. The main thing we need shepherds for is to signal the IPMC when all Mentors have gone missing and a podling is adrift. The secondary function of providing outsider feedback can be helpful, but it's best not to add commentary late in the process because we want to give the podling the chance to respond if necessary. Thank you for the explanations. St.Ack
Re: January 2014 Incubator report timeline
Hi Marvin, I dropped the ball and didn’t get the Storm report in. But I also noticed that Storm wasn’t included in the template for this month’s report. I’m assuming that was just an oversight, correct? I imagine it’s too late for this month and that we should just report next month, but I’d be willing to put together a report tonight if it would be of any value. Thanks, Taylor On Jan 7, 2014, at 5:24 PM, Marvin Humphrey mar...@rectangular.com wrote: On Tue, Jan 7, 2014 at 3:49 PM, Stack st...@duboce.net wrote: I went ahead and added up the Phoenix report (I removed us from the non-reporters list -- smile). Great, thanks! I did not know what to fill in for the 'signed-off by' list so left it blank. It's a list of Mentors who have seen the report and approved it. I took the liberty of filling in the checkboxes for Enis Sözutar and Devaraj Das because they both sent +1 emails to dev@phoenix.incubator. Let me go ping our Shepherd for this period; hopefully he is just as forgiving of our late submission. The main thing we need shepherds for is to signal the IPMC when all Mentors have gone missing and a podling is adrift. The secondary function of providing outsider feedback can be helpful, but it's best not to add commentary late in the process because we want to give the podling the chance to respond if necessary. Clearly the Mentors for Phoenix are engaged, and I plan to file the Incubator report tomorrow regardless. Marvin Humphrey - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org signature.asc Description: Message signed with OpenPGP using GPGMail
Re: January 2014 Incubator report timeline
P. Taylor Goetz wrote: Hi Marvin, I dropped the ball and didn’t get the Storm report in. But I also noticed that Storm wasn’t included in the template for this month’s report. I’m assuming that was just an oversight, correct? But Storm is not due to report: http://incubator.apache.org/facilities.html#report-schedule -David I imagine it’s too late for this month and that we should just report next month, but I’d be willing to put together a report tonight if it would be of any value. Thanks, Taylor - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: January 2014 Incubator report timeline
On Tue, Jan 7, 2014 at 7:47 PM, P. Taylor Goetz ptgo...@gmail.com wrote: I dropped the ball and didn’t get the Storm report in. But I also noticed that Storm wasn’t included in the template for this month’s report. I’m assuming that was just an oversight, correct? Podlings only have to report monthly for the first three months of incubation; thereafter, they report quarterly. Storm's three months were October, November and December -- the monthly tag has now been removed from your podlings.xml metadata: http://svn.apache.org/viewvc/incubator/public/trunk/content/podlings.xml?r1=1550930r2=1552124 Storm's next report will be due in March: http://incubator.apache.org/report-groups.txt If a podling fails to report, it's now part of the Report Manager's workflow to add back the monthly tag so that the podling dev list gets an automated report reminder, but if the podling always reports on time the monthly tag is ordinarily gone for good. I imagine it’s too late for this month and that we should just report next month, but I’d be willing to put together a report tonight if it would be of any value. Missing a report and making it up the next month is not a big deal. That's true now for the Incubator, and it's also true for TLPs reporting to the Board. It's more convenient for us if a project misses a month rather than trying to squeeze in late in the cycle. Marvin Humphrey - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: January 2014 Incubator report timeline
Thanks for the clarification Marvin and David. I didn't realize our three months were up already. :) - Taylor On Jan 7, 2014, at 8:20 PM, Marvin Humphrey mar...@rectangular.com wrote: On Tue, Jan 7, 2014 at 7:47 PM, P. Taylor Goetz ptgo...@gmail.com wrote: I dropped the ball and didn’t get the Storm report in. But I also noticed that Storm wasn’t included in the template for this month’s report. I’m assuming that was just an oversight, correct? Podlings only have to report monthly for the first three months of incubation; thereafter, they report quarterly. Storm's three months were October, November and December -- the monthly tag has now been removed from your podlings.xml metadata: http://svn.apache.org/viewvc/incubator/public/trunk/content/podlings.xml?r1=1550930r2=1552124 Storm's next report will be due in March: http://incubator.apache.org/report-groups.txt If a podling fails to report, it's now part of the Report Manager's workflow to add back the monthly tag so that the podling dev list gets an automated report reminder, but if the podling always reports on time the monthly tag is ordinarily gone for good. I imagine it’s too late for this month and that we should just report next month, but I’d be willing to put together a report tonight if it would be of any value. Missing a report and making it up the next month is not a big deal. That's true now for the Incubator, and it's also true for TLPs reporting to the Board. It's more convenient for us if a project misses a month rather than trying to squeeze in late in the cycle. Marvin Humphrey - 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
Re: January 2014 Incubator report timeline
Belated +1 from me as well. From: Marvin Humphrey mar...@rectangular.com To: general@incubator.apache.org general@incubator.apache.org Sent: Tuesday, January 7, 2014 5:24 PM Subject: Re: January 2014 Incubator report timeline On Tue, Jan 7, 2014 at 3:49 PM, Stack st...@duboce.net wrote: I went ahead and added up the Phoenix report (I removed us from the non-reporters list -- smile). Great, thanks! I did not know what to fill in for the 'signed-off by' list so left it blank. It's a list of Mentors who have seen the report and approved it. I took the liberty of filling in the checkboxes for Enis Sözutar and Devaraj Das because they both sent +1 emails to dev@phoenix.incubator. Let me go ping our Shepherd for this period; hopefully he is just as forgiving of our late submission. The main thing we need shepherds for is to signal the IPMC when all Mentors have gone missing and a podling is adrift. The secondary function of providing outsider feedback can be helpful, but it's best not to add commentary late in the process because we want to give the podling the chance to respond if necessary. Clearly the Mentors for Phoenix are engaged, and I plan to file the Incubator report tomorrow regardless. Marvin Humphrey - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
