taverna-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Stian Soiland-Reyes <st...@apache.org>
Subject Re: Podling Report Reminder - September 2018
Date Tue, 04 Sep 2018 09:44:34 GMT
Thanks Andy for pinging.

I'm just back from annual leave.  It's not a good sign that no-one else from
the Taverna PPMC stepped up, that is pretty much what is our challenge for
graduating now.  

Here's draft report. Comments here.

--------------------
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. Re-engage PPMC members
  2. Graduate?
  3.

Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?

  INFRA-16698 is pending comments from Daniel Gruno / IPMC on how
  to manage incubator repositories on git-wip-us.apache.org that have 
  been retired (in our case transferred to another GitHub organizations).
  The suggestion is to do a "git rm" and leave a README on the head commit 
  pointing to the new location.

  See also 
https://lists.apache.org/thread.html/b4672999838a64a1883407f0c827d7d40fdef13f2424fa5465e944c3@%3Cgeneral.incubator.apache.org%3E


How has the community developed since the last report?

  2 Google Summer of Code students have been active over the summer with 
  strong guidance from mentors and getting pull requests merged. 

  However the rest of the community has been very quiet and not 
  commented much on the GSOC progress or pull requests.


How has the project developed since the last report?

  Good progress from GSOC students, which code bases are now
  due a new release to include their changes.

  Two legacy git repositories were retired to not go through 
  graduation (INFRA-16698).

  There is not much outstanding towards graduation, except
  re-engaging the PMC members. 

  We will have to admit we are a slow project, which is 
  OK (many Apache projects are), yet still there seems 
  to be some kind of incubator fatigue - for 
  instance no-one else picked up the job of doing this 
  report although prompted to do so by a mentor.


How would you assess the podling's maturity?
Please feel free to add your own commentary.


  [ ] Initial setup
  [ ] Working towards first release
  [x] Community building
  [ ] Nearing graduation
  [x] Other: PPMC dormant?


Date of last release:

  2018-01-18

When were the last committers or PPMC members elected?

  2018-02-26 (PPMC)


Signed-off-by:

  [ ](taverna) Andy Seaborne
     Comments:
  [ ](taverna) Daniel J Debrunner
     Comments:
  [ ](taverna) Marlon Pierce
     Comments:
  [x](taverna) Stian Soiland-Reyes
     Comments: 
     GSOC activity may have taken focus from work 
     towards graduation in this period.
  [ ](taverna) Suresh Marru
     Comments:
  [ ](taverna) Suresh Srinivas
     Comments:

IPMC/Shepherd notes:



On Sat, 1 Sep 2018 12:32:01 +0100, Andy Seaborne <andy@apache.org> wrote:
> Anyone from the PPMC can write the report.
> 
> (If you don't have wiki edit access,, just send it here and it'll be 
> transferred)
> On 31/08/18 23:19, jmclean@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, 19 September 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, September 05).
> > 
> > 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/September2018
> > 
> > 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
> > 

Mime
View raw message