Pointed this out on the Gossip list: AirflowAmaterasuAnnotatorBatchEEGobblinGossipHAWQLivyMilagroMXNetNetBeansODF ToolkitPLC4XRyaS2GraphSensSoftServiceCombTraffic ControlWeex
Pointing out of this list 10 failed to report in July. On Thu, Jul 5, 2018 at 2:35 PM, Dave Fisher <dave2w...@comcast.net> wrote: > Hi - > > > On Jul 5, 2018, at 4:45 AM, Edward Capriolo <edlinuxg...@gmail.com> > wrote: > > > > Also at one point the project was assigned a "shepard" who never signed > off > > on a single report even when the project was active. His first > interaction > > for the project was vote to moth ball it. > > There is a difference between Mentors and Shepherds. A shepherd is > assigned for a reporting cycle to look into the podling to see how things > are going. I was assigned as shepherd this month and have left my comments > along with an email. Your mentors are supposed to provide guidance in the > Apache Way. If your mentors are absent then that is a different matter. If > you would like new mentors then please ask here on this list. > > If on the other hand the Gossip community feels that the Apache Way and > particularly the release process is too much process and not enough coding > then that is your choice. > > Regards, > Dave > > > > > > > On Thu, Jul 5, 2018 at 7:35 AM, Edward Capriolo <edlinuxg...@gmail.com> > > wrote: > > > >> I want to get this out there. I do not know why everyone is stuck on > >> gossip. There are some TLP that do not have activity for years and > podlings > >> much older then gossip. I can give numerous examples. > >> > >> On Thu, Jun 28, 2018 at 1:10 PM, John D. Ament <johndam...@apache.org> > >> wrote: > >> > >>> That sounds like retirement to me. The way I've always seen it is that > >>> podlings don't fail, the people behind them simply had a change in > >>> priorities. > >>> > >>> Gossip is a great toolkit that I believe people will continue to use. > >>> > >>> John > >>> > >>> > >>> On Thu, Jun 28, 2018, 12:44 PM Josh Elser <els...@apache.org> wrote: > >>> > >>>> I've been trying to be patient around this, but I think this month's > >>>> incubator report must be "Gossip is going to exit incubation" (I'm not > >>>> sure what the proper verb is here; I only know that "retire" is wrong) > >>>> > >>>> We've gone through many months where the only traffic I've seen on the > >>>> mailing list are the report reminders. > >>>> > >>>> This doesn't need to be interpreted as "Gossip is a failure at the > ASF" > >>>> or anything of the such. It just means "It's not the right time for > >>>> Gossip at the ASF incubator". By all means, we can bring it back into > >>>> incubation if we get some more community traction behind the project. > >>>> > >>>> On 6/27/18 5:41 PM, jmcl...@apache.org wrote: > >>>>> Dear podling, > >>>>> > >>>>> This email was sent by an automated system on behalf of the Apache > >>>>> Incubator PMC. It is an initial reminder to give you plenty of time > to > >>>>> prepare your quarterly board report. > >>>>> > >>>>> The board meeting is scheduled for Wed, 18 July 2018, 10:30 am PDT. > >>>>> The report for your podling will form a part of the Incubator PMC > >>>>> report. The Incubator PMC requires your report to be submitted 2 > weeks > >>>>> before the board meeting, to allow sufficient time for review and > >>>>> submission (Wed, July 04). > >>>>> > >>>>> Please submit your report with sufficient time to allow the Incubator > >>>>> PMC, and subsequently board members to review and digest. Again, the > >>>>> very latest you should submit your report is 2 weeks prior to the > >>> board > >>>>> meeting. > >>>>> > >>>>> Candidate names should not be made public before people are actually > >>>>> elected, so please do not include the names of potential committers > or > >>>>> PPMC members in your report. > >>>>> > >>>>> Thanks, > >>>>> > >>>>> The Apache Incubator PMC > >>>>> > >>>>> Submitting your Report > >>>>> > >>>>> ---------------------- > >>>>> > >>>>> Your report should contain the following: > >>>>> > >>>>> * Your project name > >>>>> * A brief description of your project, which assumes no knowledge > of > >>>>> the project or necessarily of its field > >>>>> * A list of the three most important issues to address in the move > >>>>> towards graduation. > >>>>> * Any issues that the Incubator PMC or ASF Board might wish/need to > >>> be > >>>>> aware of > >>>>> * How has the community developed since the last report > >>>>> * How has the project developed since the last report. > >>>>> * How does the podling rate their own maturity. > >>>>> > >>>>> This should be appended to the Incubator Wiki page at: > >>>>> > >>>>> https://wiki.apache.org/incubator/July2018 > >>>>> > >>>>> Note: This is manually populated. You may need to wait a little > before > >>>>> this page is created from a template. > >>>>> > >>>>> Mentors > >>>>> ------- > >>>>> > >>>>> Mentors should review reports for their project(s) and sign them off > >>> on > >>>>> the Incubator wiki page. Signing off reports shows that you are > >>>>> following the project - projects that are not signed may raise alarms > >>>>> for the Incubator PMC. > >>>>> > >>>>> Incubator PMC > >>>>> > >>>> > >>>> --------------------------------------------------------------------- > >>>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > >>>> For additional commands, e-mail: general-h...@incubator.apache.org > >>>> > >>>> > >>> > >> > >> > >
