Here’s a draft report I added to the wiki for this quarter.  Edits at
https://wiki.apache.org/incubator/September2017 or comment in this
thread.





I think we need to gear up and try to get that Taverna Mobile release
out, finish the license review (retiring any dubious git repo to
tavern-extras) and get ourselves graduated.  I guess it’s naturally
been a bit more quiet over the summer, now is the time to pick up the
pace.



See also 
https://cwiki.apache.org/confluence/display/TAVERNADEV/2016-09+License+review





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. Complete the remaining IP review (by retiring irrelevant git repositories)

 2. Re-engage PMC to encourage regular activity

 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?



  Fairly quiet over the summer. Lack of progress towards graduation.
Need more active drive.



Email stats since 2017-07-01:



  dev@taverna: 74 emails

  users@taverna: 4 emails





How has the project developed since the last report?



  Progress towards release of the Taverna Mobile Android App.

  Been in contact with legal/infra to figure out how to do code
signing for Google Play store.





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:



Date of last release:



  2016-07-01



When were the last committers or PPMC members elected?



  2016-10-20



On 1 September 2017 at 00:40,  <johndam...@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, 20 September 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, September 06).
>
> 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/September2017
>
> 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



-- 
Stian Soiland-Reyes
http://orcid.org/0000-0001-9842-9718

Reply via email to