You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@taverna.apache.org by Stian Soiland-Reyes <so...@manchester.ac.uk> on 2019/09/05 09:27:36 UTC
[DISCUSS] Retiring Taverna from incubator?
Hi,
It saddens me, but we have to discuss the reality.
Taverna have progressed well in the incubator, if slowly.
But I think you will agree with me that the activity level has dropped
to a minimum during the last year.
Note that it is perfectly OK for an Apache project to not be in active
development. If you go through the ASF list you will find several mature
projects in that state.
We said we would release the remaining code bases (e.g. taverna-mobile,
taverna-workbench), which beyond "re-engate PPMC" is the only remaining
hurdle before we can graduate.
While we had some starts at this, we did not go through with it.
What distinguishes a "dead" project from a "sleeping" project at ASF
will be the ability to prepare, vote and publish releases. This requires
a PPMC that is engaged, and volunteer release managers.
Now I think we still have enough PPMC folks to do the vote (let's see
how many engages in this thread).
What we don't seem to have is enough energy/time to prepare and publish
releases. I am as guilty as anyone - I had promised to prepare several
release candidates for a vote, but dropped the ball.
I will admit that preparing release candidates at ASF does take a bit
more effort than a quick "git tag" - although we mostly have our
instructions and Maven tooling now set up to do it fairly easy.
As I pointed out in the September report - given the lack of progress I
think we need to seriously discuss the possibility of
retiring Taverna from the incubator.
There is no shame in this - we've had a good run and done lots of
progress - which could live on in a more lightweight fashion, e.g. a
GitHub organization. Recently even an active podling retired from the
incubator to do this, (although that was over political differences).
Retiring means giving up on the Apache name and *.apache.org resources.
We could simply change the name back to just "Taverna" and keep it under
the Apache License. Practically the package name and Maven coordinates
would need to change, as we did for modules we moved to taverna-extra
GitHub group earlier.
One alternative we have discussed before: shrink the size of Taverna
code-base so it's largely what we have already done releases for. We
could drop taverna-workbench-* and some plugins.
If we then just do a "token" release to show we are still alive then we
would be able to crawl into a graduation proposal.
After graduation to an ASF project we would need to do board reports and
any PMC-level management (typically respond to email requests), but ASF
board is not interferring in how often releases are done etc.
Given that taverna-mobile is freshly started in the incubator with ASF
copyright it would admitedly be a shame to "leave it behind" graduation,
but it could be possible to bring it back later. The easiest would
however be to do a incubator release of this now to verify that
the Intellectual Property is clean.
What are your views on the future directions of the Taverna project?
Please feel free to contribute, however small comment.
--
Stian Soiland-Reyes
https://orcid.org/0000-0001-9842-9718
Re: [DISCUSS] Retiring Taverna from incubator?
Posted by Gale Naylor <Ga...@noventussolutions.com>.
GitHub sounds like a good option to me.
Thanks, Ian! Working at Facebook is going great. I'm very happy. Hope you
and Stian are doing well also.
Gale
On Sun, Sep 22, 2019, 8:45 AM Ian Dunlop <ia...@gmail.com> wrote:
> Hello
>
> I think a "GitHub organisation" seems like a good idea. Staying in Apache
> would obviously be great but the release process seems to keep hitting
> barriers. I would have liked the minimal amount of projects to stay in
> Apache but who could do that. I almost got a release of mobile out and knew
> what to do but in the end couldn't find time plus I wasn't sure if
> releasing code without having a clear purpose or community was a good idea.
> Maybe getting core repos to graduation. Maybe mobile. Move the others to
> github. That could be an idea.
>
> Cheers
>
> Ian
>
> Ps nice to hear from you gale. Hope things are going well for you.
>
> On Tue, 10 Sep 2019, 10:12 Stian Soiland-Reyes, <st...@apache.org> wrote:
>
>> On Thu, 5 Sep 2019 05:41:34 -0700, Gale Naylor <
>> GaleN@noventussolutions.com> wrote:
>> > Stian, is an "incubator release ... to verify that the Intellectual
>> > Property is clean" the same thing as the "token release" that lets
>> Taverna
>> > graduate?
>>
>> That was not my intention, the release would be all proper, just that
>> its main purpose would be to clear IP rather than provide it to the
>> user.
>>
>> I think one challenge for us is the many git repositories for different
>> modules and we have released them separately, e.g. to correspond with
>> git tags.
>>
>> As some of the modules were not in a mature enough state code-wise or
>> build-wise they have not been released yet. We could do a incubator
>> release of these which would primarily be to ensure their code base has
>> been through the incubator and cleared their IP. Then their code can
>> join us in graduation.
>>
>> Some repos like Taverna Language we have already released, so they are
>> IP clear and have mature code/build systems. If we were to drop the
>> other repositories, with these it is almost trivial to do a release,
>> which we could do as a "token release" to show the IPMC is still working
>> and able to vote on releases.
>>
>>
>> The Taverna Mobile is dfferent - it is mature in a sense both in
>> code and build, and have clean IP as fresh project, but it has a
>> different build system without assisted release. Here I think just
>> manual work (or script) is needed - but it is a bit tedious.
>>
>> So in a sense we have many options, but I would say they all require
>> making and voting on releases.
>>
>>
>>
>>
Re: [DISCUSS] Retiring Taverna from incubator?
Posted by Ian Dunlop <ia...@gmail.com>.
Hello
I think a "GitHub organisation" seems like a good idea. Staying in Apache
would obviously be great but the release process seems to keep hitting
barriers. I would have liked the minimal amount of projects to stay in
Apache but who could do that. I almost got a release of mobile out and knew
what to do but in the end couldn't find time plus I wasn't sure if
releasing code without having a clear purpose or community was a good idea.
Maybe getting core repos to graduation. Maybe mobile. Move the others to
github. That could be an idea.
Cheers
Ian
Ps nice to hear from you gale. Hope things are going well for you.
On Tue, 10 Sep 2019, 10:12 Stian Soiland-Reyes, <st...@apache.org> wrote:
> On Thu, 5 Sep 2019 05:41:34 -0700, Gale Naylor <
> GaleN@noventussolutions.com> wrote:
> > Stian, is an "incubator release ... to verify that the Intellectual
> > Property is clean" the same thing as the "token release" that lets
> Taverna
> > graduate?
>
> That was not my intention, the release would be all proper, just that
> its main purpose would be to clear IP rather than provide it to the
> user.
>
> I think one challenge for us is the many git repositories for different
> modules and we have released them separately, e.g. to correspond with
> git tags.
>
> As some of the modules were not in a mature enough state code-wise or
> build-wise they have not been released yet. We could do a incubator
> release of these which would primarily be to ensure their code base has
> been through the incubator and cleared their IP. Then their code can
> join us in graduation.
>
> Some repos like Taverna Language we have already released, so they are
> IP clear and have mature code/build systems. If we were to drop the
> other repositories, with these it is almost trivial to do a release,
> which we could do as a "token release" to show the IPMC is still working
> and able to vote on releases.
>
>
> The Taverna Mobile is dfferent - it is mature in a sense both in
> code and build, and have clean IP as fresh project, but it has a
> different build system without assisted release. Here I think just
> manual work (or script) is needed - but it is a bit tedious.
>
> So in a sense we have many options, but I would say they all require
> making and voting on releases.
>
>
>
>
Re: [DISCUSS] Retiring Taverna from incubator?
Posted by Stian Soiland-Reyes <st...@apache.org>.
On Thu, 5 Sep 2019 05:41:34 -0700, Gale Naylor <Ga...@noventussolutions.com> wrote:
> Stian, is an "incubator release ... to verify that the Intellectual
> Property is clean" the same thing as the "token release" that lets Taverna
> graduate?
That was not my intention, the release would be all proper, just that
its main purpose would be to clear IP rather than provide it to the
user.
I think one challenge for us is the many git repositories for different
modules and we have released them separately, e.g. to correspond with
git tags.
As some of the modules were not in a mature enough state code-wise or
build-wise they have not been released yet. We could do a incubator
release of these which would primarily be to ensure their code base has
been through the incubator and cleared their IP. Then their code can
join us in graduation.
Some repos like Taverna Language we have already released, so they are
IP clear and have mature code/build systems. If we were to drop the
other repositories, with these it is almost trivial to do a release,
which we could do as a "token release" to show the IPMC is still working
and able to vote on releases.
The Taverna Mobile is dfferent - it is mature in a sense both in
code and build, and have clean IP as fresh project, but it has a
different build system without assisted release. Here I think just
manual work (or script) is needed - but it is a bit tedious.
So in a sense we have many options, but I would say they all require
making and voting on releases.
Re: [DISCUSS] Retiring Taverna from incubator?
Posted by Gale Naylor <Ga...@noventussolutions.com>.
Stian, is an "incubator release ... to verify that the Intellectual
Property is clean" the same thing as the "token release" that lets Taverna
graduate?
Gale
On Thu, Sep 5, 2019, 2:27 AM Stian Soiland-Reyes <
soiland-reyes@manchester.ac.uk> wrote:
> Hi,
>
> It saddens me, but we have to discuss the reality.
>
> Taverna have progressed well in the incubator, if slowly.
>
> But I think you will agree with me that the activity level has dropped
> to a minimum during the last year.
>
> Note that it is perfectly OK for an Apache project to not be in active
> development. If you go through the ASF list you will find several mature
> projects in that state.
>
>
> We said we would release the remaining code bases (e.g. taverna-mobile,
> taverna-workbench), which beyond "re-engate PPMC" is the only remaining
> hurdle before we can graduate.
>
>
> While we had some starts at this, we did not go through with it.
>
> What distinguishes a "dead" project from a "sleeping" project at ASF
> will be the ability to prepare, vote and publish releases. This requires
> a PPMC that is engaged, and volunteer release managers.
>
>
> Now I think we still have enough PPMC folks to do the vote (let's see
> how many engages in this thread).
>
> What we don't seem to have is enough energy/time to prepare and publish
> releases. I am as guilty as anyone - I had promised to prepare several
> release candidates for a vote, but dropped the ball.
>
> I will admit that preparing release candidates at ASF does take a bit
> more effort than a quick "git tag" - although we mostly have our
> instructions and Maven tooling now set up to do it fairly easy.
>
>
> As I pointed out in the September report - given the lack of progress I
> think we need to seriously discuss the possibility of
> retiring Taverna from the incubator.
>
>
> There is no shame in this - we've had a good run and done lots of
> progress - which could live on in a more lightweight fashion, e.g. a
> GitHub organization. Recently even an active podling retired from the
> incubator to do this, (although that was over political differences).
>
> Retiring means giving up on the Apache name and *.apache.org resources.
> We could simply change the name back to just "Taverna" and keep it under
> the Apache License. Practically the package name and Maven coordinates
> would need to change, as we did for modules we moved to taverna-extra
> GitHub group earlier.
>
>
> One alternative we have discussed before: shrink the size of Taverna
> code-base so it's largely what we have already done releases for. We
> could drop taverna-workbench-* and some plugins.
>
> If we then just do a "token" release to show we are still alive then we
> would be able to crawl into a graduation proposal.
>
>
> After graduation to an ASF project we would need to do board reports and
> any PMC-level management (typically respond to email requests), but ASF
> board is not interferring in how often releases are done etc.
>
> Given that taverna-mobile is freshly started in the incubator with ASF
> copyright it would admitedly be a shame to "leave it behind" graduation,
> but it could be possible to bring it back later. The easiest would
> however be to do a incubator release of this now to verify that
> the Intellectual Property is clean.
>
>
> What are your views on the future directions of the Taverna project?
> Please feel free to contribute, however small comment.
>
> --
> Stian Soiland-Reyes
> https://orcid.org/0000-0001-9842-9718
>
>