This was extracted (@ 2025-06-16 17:10) from a list of minutes
which have been approved by the Board.
Please Note
The Board typically approves the minutes of the previous meeting at the
beginning of every Board meeting; therefore, the list below does not
normally contain details from the minutes of the most recent Board meeting.
WARNING: these pages may omit some original contents of the minutes.
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 unfinished issues to address before graduating:
1. Re-engage PPMC members
2. Release IP-fixed repositories
3. Graduate!
### Are there any issues that the IPMC or ASF Board need to be aware of?
Considering retiring.
### How has the community developed since the last report?
Very quiet through the summer. Podling considering retirement from
incubator.
### How has the project developed since the last report?
No development since last report.
Release Candidates planned during June has not progressed further to a
vote.
### 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
- [x] Nearing graduation
- [ ] Other:
### Date of last release:
2018-01-18
### When were the last committers or PPMC members elected?
2018-02-26 (PPMC)
### Have your mentors been helpful and responsive?
No answer
### Signed-off-by:
- [x] (taverna) Stian Soiland-Reyes
Comments: While the project has previously been active, done several
releases, and recruited PPMC and committers, it is now very
quiet.
For graduation it only needs a couple of maintenance releases
of the remaining code-bases (or not include those in
graduation).
I suggest the project use the next reporting period to
discuss retiring vs. graduation.
### IPMC/Shepherd notes:
Justin Mclean: I'm a little confused if you want to graduate or retire.
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 unfinished issues to address before graduating:
1. Re-engage PPMC members
2. Release IP-fixed repositories
3. Graduate!
### Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
Whimsy detected some PPMC members where not signed up to private@taverna
list, as well as false negatives on emiritus mentors and alternative
addresses.
Missing members have been requested added.
(our private list is quiet except for PPMC voting)
### How has the community developed since the last report?
Active in March/April, quiet in May.
### How has the project developed since the last report?
Release candidate of Taverna Mobile was in progress based on GitHub
release mechanism, but this became challenging as its Android source code
tend to include a Gradle binary and don't have good release-helpers like
in Maven.
This meant the Android release had to be delayed to be done "manually".
### 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
- [x] Nearing graduation
- [ ] Other:
### Date of last release:
2018-01-18
When were the last committers or PPMC members elected?
2018-02-26 (PPMC)
### Have your mentors been helpful?
Mentor was not too attentive in April - sorry.
### Signed-off-by:
- [x] (taverna) Stian Soiland-Reyes
Comments: The community is slow, but figuring out things together
### IPMC/Shepherd notes:
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 unfinished issues to address before graduating:
1. Re-engage PPMC members
2. Release IP-fixed repositories
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?
Gone quiet after Christmas.
More of PPMC member activity would be desired.
Lately more user questions than developer threads.
How has the project developed since the last report?
Moved Git repositories to GitHub via GitBox
Previous IP/licensing issues now resolved.
Pending release of updated git repositories.
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
[x] Nearing graduation
[ ] Other:
Date of last release:
2018-01-18
When were the last committers or PPMC members elected?
2018-02-26 (PPMC)
Have your mentors been helpful and responsive or are things falling
through the cracks? In the latter case, please list any open issues
that need to be addressed.
Down to one active mentor. Thanks to retiring mentor Andy for his
consistent and helpful effort since incubation.
Signed-off-by:
[ ](taverna) Marlon Pierce
Comments:
[x](taverna) Stian Soiland-Reyes
Comments:
Need a bit of push to do the remaining
releases after fixing IP issues.
[ ](taverna) Suresh Srinivas
Comments:
IPMC/Shepherd notes:
--------------------
The Training project aims to develop resources which can be used for
training purposes in various media formats, languages and for various
Apache and non-Apache target projects.
Training has been incubating since 2019-02-21.
Three most important issues to address in the move towards graduation:
1. Agree upon underlying technology stack and architecture for training
content
2. Develop first training topic contents
3. Set up our contribution process
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
- no critical issues at this point in time
How has the community developed since the last report?
- The project has been set up recently, so there is an initial
activation/development towards a community.
- The dev mailing list is active. Total number of posts in March were 160
(+48 from March). Total number of
subscribers is 28 (+3 from last month).
How has the project developed since the last report?
- This is our first report covering a full month
- We have decided on a Website technology and we have had our first few
commits (LICENSE, README etc.)
- The scope of the project deliverables, core procedures, details regarding
website, and code management are still under discussion
- First offers of content donations have been made
- We welcomed our first regular contributor to the mailing list from
outside of the original list of contributors
- There are plans to talk about the project at both ApacheCons this year
There are lots of parallel discussions happening. We have made some initial
decisions (e.g. website) but there are lots of topics still left to be
discussed. The major one is on whether or not to chose a canonical
technology into which we want to convert our training material and the
organization thereof (e.g. multilingual content and acceptance of material
in different formats e.g. PowerPoint, Google Slides).
The project is a bit different from most others which come with existing
code bases, existing communities. We have to start from "first principles"
so it's not unexpected that this takes a while.
How would you assess the podling's maturity?
[x] Initial setup
[ ] Working towards first release
[x] Community building
[ ] Nearing graduation
[ ] Other:
Date of last release:
n.a.
When were the last committers or PPMC members elected?
n.a.
Signed-off-by:
[X](training) Justin Mclean
Comments:
[x](training) Craig Russell
Comments:
[X](training) Christofer Dutz
Comments:
[x](training) Lars Francke
Comments:
IPMC/Shepherd notes:
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. Fix licence issues
3. Graduate
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
INFRA-16698 moved 2 repos out of Apache git although they are still
listed on https://git.apache.org/.
How has the community developed since the last report?
How has the project developed since the last report?
Clearing up the last couple of licence issues and merging or
removing pull requests. Project is ready for graduation
although more activity from PPMC and members would be good.
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
[x] Nearing graduation
[ ] Other:
Date of last release:
2018-01-18
When were the last committers or PPMC members elected?
2018-02-26 (PPMC)
Have your mentors been helpful and responsive or are things falling
through the cracks? In the latter case, please list any open issues
that need to be addressed.
Mentors are helpful but a bit thin on the ground. Overly reliant on
a small number of them.
Signed-off-by:
[x](taverna) Andy Seaborne
Comments:
The project has two mentors showing any level of activity although as
the project is "about to graduate" it should be almost self-sufficent.
Graduation is possible though close to the minimum requirements;
more active PPMC members would be very helpful.
Due to lack of time I have to resign as mentor.
[ ](taverna) Marlon Pierce
Comments:
[x](taverna) Stian Soiland-Reyes
Comments:
PPMC has increased activity levels and are resolving remaining licensing
issues.
Agree with Andy that more of the PPMC members being active would be ideal.
[ ](taverna) Suresh Srinivas
Comments:
IPMC/Shepherd notes:
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/b4672999838a64a1883407f0c827d7d40fdef13
f2424fa5465e944c3@%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:
[x](taverna) Andy Seaborne
Comments:
The PPMC needs to work on a graduation plan. Graduation should
not be a major task for Taverna but it does need doing.
[ ](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:
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
2. Release or Retire legacy git repositories
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?
Uptake in activity with GSOC students, already multiple merged pull
requests.
Little engagement from the wider PMC.
Email stats dev@taverna:
2018-05: 62
2018-04: 41
2018-03: 102
How has the project developed since the last report?
Moved to Java 9 (just in time for Java 10?).
PPMC voted on Taverna Language release, but it failed IPMC vote
due to CC-BY licensed schema files. Will refactor.
Some confusion as this seemed allowed by
http://www.apache.org/legal/resolved.html#category-b
See https://s.apache.org/lang-0.16.0-RC1-vote
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
[ ] Other:
Date of last release:
2018-01-18
When were the last committers or PPMC members elected?
2018-02-26 (PPMC)
Signed-off-by:
[x](taverna) Andy Seaborne
Comments:
There has been an encouraging pickup in development going on but the
PPMC remains quite quiet in terms of project graduation.
Mentor engagement, including mime, is low.
[ ](taverna) Daniel J Debrunner
Comments:
[ ](taverna) Marlon Pierce
Comments:
[x](taverna) Stian Soiland-Reyes
Comments:
If Taverna is to proceed to Graduation instead of Retirement from the
incubator, it needs to keep more of the PMC members engaged and
motivated.
[ ](taverna) Suresh Marru
Comments:
[ ](taverna) Suresh Srinivas
Comments:
IPMC/Shepherd notes:
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 towards community building
2. Release or Retire legacy git repositories
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?
Large interest from Google Summer of Code students.
Multiple pull requests, many already merged.
Elected new PPMC member Sagar.
Email stats dev@taverna:
2017-12: 18
2018-01: 120
2018-02: 156
How has the project developed since the last report?
Taverna Server release, addressed many IP/license issues.
Active development, but focused mainly on the Android app.
Some challenges with maintaining legacy git repositories as
they require different skills.
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
[ ] Other:
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:
While there has been an uptick in development activity recently, and the
contributor is a new PPMC member, the podling PPMC as a group is not moving
towards graduation.
Reiterating my comments from December: I am worried that pushing through
graduation will only result in the same situation as a TLP.
[ ](taverna) Daniel J Debrunner
Comments:
[ ](taverna) Marlon Pierce
Comments:
[x](taverna) Stian Soiland-Reyes
Comments:
I have been quite impressed by the uptick since New Year, which shows how just
a bit of PMC engagement can give lots of follow-on activitity. I would hope
Taverna can continue this move out of the "risk of retire" zone, but that
requires more PMC members to chip in now and then.
[ ](taverna) Suresh Marru
Comments:
[ ](taverna) Suresh Srinivas
Comments:
IPMC/Shepherd notes:
johndament: the discrepancies between the mentors seems to be a concern. In general it seems like good communication flow.
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 PMC to encourage regular activity
2. Retiring irrelevant git repositories
3. Graduate!
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
Community slow. Considering retiring, but will try one last push.
How has the community developed since the last report?
Quite a few pull requests, but need follow ups.
Non-PPMC committers have taken more charge in release preparation.
Email stats since 2017-09-01:
dev@taverna: 29
users@taverna: 2
How has the project developed since the last report?
Very slow progress towards graduation.
Some progress towards next releases - need implicit Release Manager delegation.
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
Signed-off-by:
[x](taverna) Andy Seaborne
Comments:
In Dec 2016, the report said "Preparing to graduate." In 2017, the dev@ list has been quiet and the last release was in 2016.
While the PPMC is large, not everyone has been active in incubation. I am worried that pushing through graduation will only result in the same situation as a TLP.
The community needs to consider what is the best environment for Taverna.
[ ](taverna) Daniel J Debrunner
Comments:
[ ](taverna) Marlon Pierce
Comments:
[x](taverna) Stian Soiland-Reyes
Comments: I have admitted lack of leadership. I think we should seriously consider retiring, but only after a 6 month push towards getting graduation done.
[ ](taverna) Suresh Marru
Comments:
[ ](taverna) Suresh Srinivas
Comments:
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
Signed-off-by:
[ ](taverna) Andy Seaborne
Comments:
[ ](taverna) Daniel J Debrunner
Comments:
[ ](taverna) Marlon Pierce
Comments:
[x](taverna) Stian Soiland-Reyes
Comments: Mailing list has gone very quiet
[ ](taverna) Suresh Marru
Comments:
[ ](taverna) Suresh Srinivas
Comments:
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:
[x](taverna) Andy Seaborne
Comments:
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.
[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.
[ ](taverna) Daniel J Debrunner
Comments:
[ ](taverna) Marlon Pierce
Comments:
[ ](taverna) Suresh Marru
Comments:
[ ](taverna) Suresh Srinivas
Comments:
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?
Reviewing licences and IP with a view to graduation.
https://cwiki.apache.org/confluence/display/TAVERNADEV/2016-09+License+review
How has the community developed since the last report?
List has gone a bit more quiet, while activity on the
Gitter chat https://gitter.im/apache/taverna
has remained at same level. Need to re-focus use of
mailing list and community development.
How has the project developed since the last report?
Preparing maturity report, almost ready for graduation vote.
Taverna has a lot of different code bases and we are reviewing
what code we should remove from the repo while leaving a core set
of modules for graduation.
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 taverna-engine-3.1.0-incubating
2016-07-01 taverna-common-activities-2.1.0-incubating
2016-07-01 taverna-commandline-3.1.0-incubating
When were the last committers or PPMC members elected?
2016-10-20 Committer
2015-12-09 PPMC member
Signed-off-by:
[x](taverna) Andy Seaborne
Comments:
Taverna dev@ has been quiet for this reporting period. The podling
is trying to establish which parts of the total software grant to
take through the incubator process into a TLP. There are still parts
that have not been released or at a minimum checked for IP.
The active PPMC membership is low and it would be better to work on
community growth to provide a stable PMC as a TLP.
[ ](taverna) Daniel J Debrunner
Comments:
[ ](taverna) Marlon Pierce
Comments:
[x](taverna) Stian Soiland-Reyes
Comments:
Activity has stalled a bit in the drive towards graduation, as some
(perhaps tedious) IP review remains. Ambition levels might need
adjustment, e.g. don't include all repositories in graduation to
TLP.
[ ](taverna) Suresh Marru
Comments:
[ ](taverna) Suresh Srinivas
Comments:
IPMC/Shepherd notes:
John D. Ament:
The concerns about IP review may be valid, but there seems to be a disconnect
on community graduation vs code graduation.
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 of unreleased repositories 3. Graduate! Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? Preparing to graduate. Stian added as new mentor. How has the community developed since the last report? Added 3 new committers who were introduced via the Google Summer of Code. 2 of them did not directly work on Apache Taverna through GSoC but this was where they heard about the project. How has the project developed since the last report? The Taverna Mobile Android application is nearing release standard with all licence checks passed. Most of the codebases under the Taverna banner are also nearing release standard with an extensive licence review currently underway. Preparing maturity report, almost ready for graduation vote. Email stats dev@taverna: 2016-09: 190 emails 2016-10: 69 emails 2016-11: 78 emails Email stats users@taverna: 2016-09: 0 emails 2016-10: 3 emails 2016-11: 16 emails Jira stats: 2016-09 (6 created, 0 resolved) 2016-10 (3 created, 7 resolved) 2016-11 (0 created, 15 resolved) Git stats: 2016-09: 158 commits 2016-10: 165 commits 2016-11: 34 commits Date of last release: 2016-07-01 taverna-engine-3.1.0-incubating 2016-07-01 taverna-common-activities-2.1.0-incubating 2016-07-01 taverna-commandline-3.1.0-incubating When were the last committers or PMC members elected? 2016-10-20 Signed-off-by: [x](taverna) Andy Seaborne [ ](taverna) Daniel J Debrunner [x](taverna) Stian Soiland-Reyes [ ](taverna) Suresh Srinivas [ ](taverna) Suresh Marru [ ](taverna) Marlon Pierce
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 and graduation
2. Complete IP/license review of unreleased repositories
3. Further engaging user/devops community
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
Preparing to graduate.
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
The community is moving towards graduation, by preparing a
Graduation Maturity Assessment
https://cwiki.apache.org/confluence/display/TAVERNADEV/2016-03+Taverna+Graduation+Maturity+Assessment
While we wished we could have released all of Taverna's git repositories
through the Incubator before graduating, we realize that with limited
developer time, getting all of them to a cleanly releasable state
could remove focus from development of the core repositories.
As we an important point of Incubator releases is to ensure the project
understands the ASF release process, including release review and voting,
IP management and licensing compatibility; as well as accepting
contributions. We believe we have gained that after 3 release votes
https://archive.apache.org/dist/incubator/taverna/source/
and 7 GSOC/student contributors.
We have however identified the need for a License Review of the remaining
git repositories that have not yet been formally released through the
Apache Incubator (e.g. to ensure ASF file headers), which we are now
completing:
https://cwiki.apache.org/confluence/display/TAVERNADEV/2016-09+License+review
We might consider not including all of these repositories as we move
towards graduation - we already have an alternative home
https://github.com/taverna-extras for dormant extensions.
dev@taverna mailing lists stats:
Jun 2016: 347
Jul 2016: 221
Aug 2016: 170
users@taverna:
Jun 2016: 4
Jul 2016: 2
Aug 2016: 4
JIRA issues over last 90 days:
34 created
12 resolved
How has the project developed since the last report?
We have seen an upsurge in activity with
two successful GSOC projects as well as several
new plugins from other students. Some of them have shown interest
in continued contributions, which we must take into account
for proposing new committers.
This have admittedly taken some focus from the committers
from the incubator graduation path - so we're now
putting effort back into finishing our License Review.
Date of last release:
2016-07-01 taverna-engine-3.1.0-incubating
2016-07-01 taverna-common-activities-2.1.0-incubating
2016-07-01 taverna-commandline-3.1.0-incubating
When were the last committers or PMC members elected?
2015-12-04
Signed-off-by:
[x](taverna) Andy Seaborne
[ ](taverna) Daniel J Debrunner
[ ](taverna) Suresh Srinivas
[ ](taverna) Suresh Marru
[ ](taverna) Marlon Pierce
Shepherd/Mentor notes:
Andy Seaborne:
The Taverna podling is hindered by a lack of active mentors (myself
included) - the project has appealled to general@ on a couple of
occasions
3 of the 4 active contributors are from one institution and contribution
is related to EU project commitments. The codebase is large and has a
long history. One option is to identify a "core" and move out the rest
until such time as they are sustainable. More active PMC/commiters
would be a big boost.
The comment from the last report applies:
Drew Farris (shepherd):
Little mentor activity on the mailing lists, could use another
active mentor. Healthy activity in the community.
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. Releasing main code base (RC under vote) 3. Engaging user/devops community Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? ASF guidance on US export ECCN cryptography registration https://www.apache.org/dev/crypto.html has not yet been updated for the 2010 rule changes, confusion around this classification caused Taverna delays. Lack of active mentors - would appreciate another volunteer. How has the community developed since the last report? Two new GSOC students now active. 2-3 other new potential contributors discussing new work. A total of 4 ICLAs registered - however these folks need further encouragement and guidance to submit regular pull requests. dev@taverna mailing lists stats: Mar 2016: 312 Apr 2016: 102 May 2015: 184 users@taverna: Mar 2016: 12 Apr 2016: 6 May 2015: 1 JIRA issues over last 90 days: 49 created 25 resolved How has the project developed since the last report? Preparations for release of the main workflow engine has had focus, including build stability across platforms, documentation update and US Export classifications of encryption items (which caused some delays). Taverna Engine/Command Line Release candidate now under vote. https://lists.apache.org/thread.html/Zpt11soyc7qf2so Traffic on users@ show interest mainly on Taverna Server, so this component should probably be the development focus after GSOC. Date of last release: 2016-03-11 taverna-osgi-0.2.1-incubating 2016-03-11 taverna-language-0.15.1-incubating Currently in [VOTE]: taverna-engine, taverna-common-activities, taverna-commandline https://lists.apache.org/thread.html/Zpt11soyc7qf2so When were the last committers or PMC members elected? 2015-12-04 Signed-off-by: [x](taverna) Andy Seaborne [ ](taverna) Daniel J Debrunner [ ](taverna) Suresh Srinivas [ ](taverna) Suresh Marru [x](taverna) Marlon Pierce Shepherd/Mentor notes: Andy Seaborne: There is still a lack of active mentors. I'm dipping in when I can. Drew Farris (shepherd): Little mentor activity on the mailing lists, could use another active mentor. Healthy activity in the community.
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. Community growth 2. Release more of the imported code to create engagement 3. Move to a sustainable development pattern Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? Our mentors have reported they have little or no time available as Taverna is picking up pace. Dan Debrunner volunteered from the incubator list and became a new mentor. How has the community developed since the last report? Welcomed new PPMC member. GSOC 2016 project ideas are already getting interest. dev@taverna mailing lists stats: Dec 2015: 42 Jan 2016: 128 Feb 2016: 325 users@taverna: Dec 2015: 2 Jan 2016: 0 Feb 2016: 2 JIRA issues over last 90 days: 50 created 32 resolved How has the project developed since the last report? Good buzz around release preparation, release candidate currently under vote. Date of last release: 2015-08-11 taverna-language-0.15.0-incubating (new release currently under vote) When were the last committers or PMC members elected? 2015-12-04 Signed-off-by: [x](taverna) Andy Seaborne [X](taverna) Chris Mattmann [ ](taverna) Suresh Srinivas [X](taverna) Suresh Marru [X](taverna) Marlon Pierce [ ](taverna) Dan Debrunner Shepherd/Mentor notes: Andy:: It would be good to have a second active mentor in addition to Dan. Chris: I have to retire as a Taverna mentor. That said - what's stopping Taverna from being ready to graduate? If it's just mentor activity then consider graduating. The community looks active, looks like it's releasing, looks like involved in GSoC, etc.
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. Community growth 2. Release more of the imported code to create engagement 3. Move to a sustainable development pattern Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? None How has the community developed since the last report? Vote on new committer. Passed by Apache Taverna, needs acceptance by IPMC. Mailing list activity Sep/Oct/Nov - dev 33/9/31 - users 2/5/4 - commits 50/103/16 How has the project developed since the last report? Fixed build problem in command-line package https://issues.apache.org/jira/browse/TAVERNA-874 Date of last release: 2015-08-11 taverna-language-0.15.0-incubating When were the last committers or PMC members elected? n/a Signed-off-by: [x](taverna) Andy Seaborne [ ](taverna) Chris Mattmann [ ](taverna) Suresh Srinivas [ ](taverna) Suresh Marru [x](taverna) Marlon Pierce Shepherd/Mentor notes: Andy Seaborne (andy): Dev discussions have slowed right down this quarter. Developer effort was strong for GSoC but there is now a minimum with no prospect of a change until Jan/Feb next year. A worry I have is that this was not communicated until considerable prompting applied. There are only 2 active mentors. Marlon Pierce (mpierce): +1 for Andy's comments. After a very promising summer, the project has come to a halt. Despite mentor prompting, the project did not take the opportunity to grow its community from active GSOC participants. John D. Ament (johndament): Reading through the report, it seems that there may be some issues to be raised up.
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. Motivate community engagement 2. Community growth 3. Continued release planning Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? Thank you to GSOC and three very successful students! How has the community developed since the last report? New contributor of documentation. 3 GSOC projects completed, all contributions merged. Mailing list activity for Jun/Jul/Aug 2015: - dev@taverna: 392/336/194 - users@taverna: 7/14/11 - commits@taverna: 338/367/211 How has the project developed since the last report? First Apache release: taverna-language-0.15.0-incubating. Documented release procedure and ironed out LICENSE/NOTICE. Focus on documentation. Date of last release: 2015-08-11 taverna-language-0.15.0-incubating When were the last committers or PMC members elected? n/a Signed-off-by: [x](taverna) Andy Seaborne [ ](taverna) Chris Mattmann [ ](taverna) Suresh Srinivas [ ](taverna) Suresh Marru [x](taverna) Marlon Pierce Shepherd/Mentor notes: Marlon Pierce (mpierce): Nice quarter with first Apache release and 3 successful GSOC projects.
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. First Apache release 2. Motivate community activity 3. Growing community Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? None. How has the community developed since the last report? 3 active GSOC students. How has the project developed since the last report? While the GSOC projects are progressing well, this has taken some focus away from the general progress towards our first release. The PPMC will focus on community engagement and motivation and push forwards the first release during June. Date of last release: n/a When were the last committers or PMC members elected? n/a Signed-off-by: [x](taverna) Andy Seaborne [ ](taverna) Chris Mattmann [ ](taverna) Suresh Srinivas [ ](taverna) Suresh Marru [x](taverna) Marlon Pierce Shepherd/Mentor notes: Justin Mclean (jmclean): Mentors active, but slow progress towards first release (as noted on list).
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. Growing community 2. Finish infrastructure move 3. First Apache release Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? None. How has the community developed since the last report? ~110 emails on dev@taverna in 2015-02. Quiet on users@taverna. Presented Apache Taverna at lbl.gov Workflows day. How has the project developed since the last report? - Taverna Software Grant received & filed 2014-02-23. - Git repositories moved to Apache. - Preparing for release - NOTICE/LICENSE handling. - Lots of content added on website. - Next: Wiki/issues to move to Apache. Date of last release: XXXX-XX-XX When were the last committers or PMC members elected? None Signed-off-by: [x](taverna) Andy Seaborne [ ](taverna) Chris Mattmann [ ](taverna) Suresh Srinivas [ ](taverna) Suresh Marru [x](taverna) Marlon Pierce Shepherd/Mentor notes: Andy Seaborne (andy): The podling should move to regular reporting now the software grant is on-file.
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. IP clearance 2. Release - understand/document release process 3. Grow community -- need to move forward from bootstrapping/IP issues Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? None How has the community developed since the last report? One new (potential) contributor One former plugin developer showing renewed interest There were 160 mail messages to dev@taverna.incubator.apache.org How has the project developed since the last report? The Taverna name search has been approved. IP clearance from University of Manchester was signed 2015-02-04. Helped release Apache extras Beanshell 2.0b5 to allow use in Taverna The dev community is dealing with licensing and discussing preparation for the first release. A partial website is in place and a full website is in-progress. Remaining infrastructure move includes - after IP clearance: * Github -> git.apache.org * Jira -> Jira (still discussing if this should be in bulk or manual) * Confluence -> Confluence * Web content (ongoing) Date of last release: None When were the last committers or PMC members elected? None Signed-off-by: [x](taverna) Andy Seaborne [ ](taverna) Chris Mattmann [ ](taverna) Suresh Srinivas [ ](taverna) Suresh Marru [x](taverna) Marlon Pierce Shepherd/Mentor notes: Andy Seaborne (andy): Taverna remained on the monthly reporting cycle because the Software Grant had not been received. If it arrives as per schedule, Taverna can go onto its normal reporting cycle. Drew Farris (drew): Podling is active, 2 mentors participating on the mailing lists.
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. IP clearance to be signed by Univ of Manchester 2. Move source code, wiki, issues to apache.org. 3. Re-awake community after migration, prepare a release Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? None. How has the community developed since the last report? Quiet month - dominated by migration issues. Involvement with students who are combining Taverna and Apache Storm. Email traffic December 2014: * dev@taverna: 50 messages * users@taverna: 12 messages How has the project developed since the last report? The project is waiting for the Software Grant from Univ of Manchester Solicitor and Contracts Manager as he needed to retrieve the existing CLAs from archive. He has replied (2015-01-05): "They should arrive back from storage this week and we can proceed with the [software grant] transfer" Taverna's WSDL-support modified to work with Apache Woden. About 45% of code base ready to be migrated (moved to slimmer git layout, modified to org.apache.taverna groupId and build). TODO: LICENSE and NOTICE plugins for Maven. Apache Taverna website live at http://taverna.incubator.apache.org/ -- not yet migrating content from http://www.taverna.org.uk/ until IP clearance sorted Discussions around packaging / Debian Date of last release: None When were the last committers or PMC members elected? None since incubation Signed-off-by: [X](taverna) Andy Seaborne [X](taverna) Chris Mattmann [ ](taverna) Suresh Srinivas [ ](taverna) Suresh Marru [X](taverna) Marlon Pierce Shepherd/Mentor notes: Andy Seaborne (andy): Given the podling has not yet got the software grant on ASF file, through no fault of the podling, I suggest keeping reporting Taverna monthly. Justin Mclean (jmclean): Off to a good start, with discussions about making builds and assembling LICENSE and NOTICE. Mentors (very) active.
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. IP clearance to be signed by Univ of Manchester 2. Move source code, wiki, issues to apache.org. Restructure git repos. 3. Invite contributors who volunteered at October workshop Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? Infrastructure bootstrapping takes a long time and requires a series of requests. E.g. Taverna incubator has been approved, but does not get a web-site without explicitly asking for it. Documentation for apache.org infrastructure assumes you are already a long-term committer. How has the community developed since the last report? Transition of mailing list successful (? - can we get some numbers?). Most of the proposed initial committers have sorted CLAs https://wiki.apache.org/incubator/TavernaProposal#Initial_Committers and received apache.org account - see https://people.apache.org/committers-by-project.html#taverna Many of the remaining initial committers have not been active in the recent years. We're following up these (and others) through private conversations. There's been some confusion with regards to the term "committer" - some were scared and thought it meant they had to make a commitment to work on the source code! Not much further development - worried that dev@taverna are scared away by the long-dragged bootstrapping which dominates the list. How has the project developed since the last report? Source code is being restructured at https://github.com/taverna-incubator before being staged to import into git.apache.org Normal development continues at https://github.com/taverna/ - due to prepare the final 2.5.1 non-Apache release. Stian Soiland-Reyes was at ApacheCon in Budapest, fruitful discussions with mentor Andy Seaborne and Gavin McDonald from INFRA with regards to the transitioning of Taverna's existing source code repository, wiki and issue tracker (luckily git->git, confluence->confluence and jira->jira). Date of last release: No release since incubation. When were the last committers or PMC members elected? No new committers or PMC members elected since incubation. Signed-off-by: [x](taverna) Andy Seaborne [ ](taverna) Chris Mattmann [ ](taverna) Suresh Srinivas [x](taverna) Suresh Marru [x](taverna) Marlon Pierce Shepherd/Mentor notes: As noted the email list just been migrated and code repo setup, but already show good signs of activity on the email list. Code activity seems good so far although it's still on it's own github repo.
Taverna is a domain-independent suite of tools used to design and execute data-driven workflows. Taverna has been incubating since 2014-10-20. The podling is currently working through the bootstrap process. Three most important issues to address in the move towards graduation: 1. Bootstrap at ASF. 2. Build community. 3. Migrate large existing codebase and processes. Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? None. How has the community developed since the last report? (First report) * Mailing lists are setup. * Currently, getting CLAs on file and accounts created. How has the project developed since the last report? (First report) Date of last release: None so far. When were the last committers or PMC members elected? Initial committers. Signed-off-by: [X](taverna) Andy Seaborne [ ](taverna) Chris Mattmann [ ](taverna) Suresh Srinivas [ ](taverna) Suresh Marru [ ](taverna) Marlon Pierce