All, I'd just like to point out, the report is still not signed off.
John On 2017-06-13 04:54 (-0400), Andy Seaborne <[email protected]> wrote: > The other mentor comment: > > """ > [x](taverna) Stian Soiland-Reyes > Comments: > > Project needs to find a daily/weekly rhythm to engage the community > more. This is a general task for the podling PMC, it should not > have to rely on any one particular person. > """ > > > On 06/06/17 10:34, Andy Seaborne wrote: > > I think taverna needs to discuss what it considers to be a stable long > > term mode of operation. Graduating with a near minimum sized active PMC > > and 6 months quietness gets out of the incubator but the quietness then > > repeats as a TLP. > > > > Andy > > > > > > My Mentor comment: > > """ > > Taverna has been quiet for 6 months with low activity on the dev@ list. > > More community building would be valuable for the long-term success of > > the project. > > """ > > > > On 05/06/17 09:55, Stian Soiland-Reyes wrote: > >> Taverna's podling report is due this Wednesday. > >> > >> Although I think we are close to graduation, I'm afraid we have not made > >> much progress on that since the last report. > >> > >> My apologies for not pushing harder for this period - I am hoping I can > >> contribute more in the coming summer months and help get the remaining > >> IP review items out of the way so we can go for graduation soon! > >> > >> > >> Thanks to all who have contributed recently - I really think we should > >> try to > >> get a release of Taverna Mobile out now! I think Taverna Server is > >> also in a > >> state that can be released, but we seem to lack some overall developer > >> experience with testing here. > >> > >> > >> > >> > >> > >> Here's my draft report (also saved in the Incubator wiki). > >> Suggestions/edits > >> welcome! > >> > >> > >> Taverna > >> > >> Taverna is a domain-independent suite of tools used to design and execute > >> data-driven workflows. > >> > >> Taverna has been incubating since 2014-10-20. > >> > >> Three most important issues to address in the move towards graduation: > >> > >> 1. Project maturity evaluation > >> 2. IP/Licence Review > >> 3. Graduate! > >> > >> > >> Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be > >> aware of? > >> > >> > >> > >> How has the community developed since the last report? > >> > >> New contributor showing interest (some pull requests and Jira > >> issues). Need to get them engaged also on mailing list. > >> Project activity still slow overall - need more day-to-day > >> encouragement and follow-up? Suggested weekly telcons > >> > >> > >> How has the project developed since the last report? > >> > >> Taverna Mobile Android app (initially a GSOC contribution) has > >> matured and is ready for its first release. > >> > >> Some bugs raised on the Taverna Server, lacking contributors - need > >> more code insight from original author? > >> > >> > >> How would you assess the podling's maturity? > >> Please feel free to add your own commentary. > >> > >> [ ] Initial setup > >> [ ] Working towards first release > >> [ ] Community building > >> [x] Nearing graduation > >> [ ] Other: > >> > >> From the recent graduation/IP review it was agreed to skip some of > >> the auxiliary git repositories from the graduation process (move to > >> GitHub) - but this has not yet happened. > >> > >> Although the community is ready, we are lacking initiative on the > >> bureaucratic side and need to push ourselves harder. > >> > >> > >> Date of last release: > >> > >> 2016-07-01 > >> > >> When were the last committers or PPMC members elected? > >> > >> > >> 2016-10-20 Committer > >> 2015-12-09 PPMC member > >> > >> Signed-off-by: > >> > >> [ ](taverna) Andy Seaborne > >> Comments: > >> [ ](taverna) Daniel J Debrunner > >> Comments: > >> [ ](taverna) Marlon Pierce > >> Comments: > >> [ ](taverna) Stian Soiland-Reyes > >> Comments: > >> [ ](taverna) Suresh Marru > >> Comments: > >> [ ](taverna) Suresh Srinivas > >> Comments: > >> > >> IPMC/Shepherd notes: > >> > >> > >> > >> > >> > >> On Sun, 04 Jun 2017 22:19:20 -0000, [email protected] 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, 21 June 2017, 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, June 07). > >>> > >>> 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. > >>> > >>> 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/June2017 > >>> > >>> 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 >
