Re: [DISCUSS] Retiring Taverna from incubator?

[Ian Dunlop]

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,  wrote:

> 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] Release Apache Taverna Mobile 1.0-incubating-RC1

[Ian Dunlop]

Hello

I think I created a tagged rc2 in GitHub that I was going to use as the
basis for the release process. I also fixed most of the rc1 issues in it. I
think one of the problems was the name of the folders inside the file. I
was going to open the gz or zip, change the folder name and rezip it.

Cheers

Ian

On Wed, 12 Jun 2019, 05:36 Sagar,  wrote:

> Hi
>
> Could you guys share the guideline or step to create a release candidate.
> So that I can fix the issues of the rc1 and create the new release
> candidate.
>
> Thanks
>
> On Tue, Jun 11, 2019 at 11:29 PM Ian Dunlop  wrote:
>
> > Hello
> >
> > Sorry I've been really busy and struggling for any time. I did fix the
> > issues from rc1 and tagged an rc2 in the repo and I even started sorted
> out
> > the folder structure but then real life caught up and I didn't manage to
> > get it out. Maybe someone could pick it up and run with it.
> >
> > Cheers
> >
> > Ian
> >
> > On Wed, 5 Jun 2019, 15:47 Stian Soiland-Reyes,  wrote:
> >
> > > This went a bit tricky in the end.. so are we back to square 0 or can
> we
> > > try again for another RC2? It's not a blocker really if it says RC2
> > > inside the folder name.. just misleading.
> > > (if the vote passes then 1.0.0-RC2 == 1.0.0)
> > >
> > > On Thu, 4 Apr 2019 14:01:58 +0100, Ian Dunlop 
> > > wrote:
> > > > Hello,
> > > >
> > > > I think I know what you mean now. It’s the folder name inside the
> > > .tar.gz when you explode it. Hmm. That seems to be be automatically put
> > > together by GitHub based on the repo name and the tag name. Ie
> > > incubator-taverna-mobile & 1.0-incubating-RC2. That’s slightly
> annoying.
> > > > So  it looks like this GitHub release mechanism isn’t so great after
> > > all. Or at least I’ll have to open the file and change the name then
> gzip
> > > it back up. Oh well.
> > > >
> > > > Cheers,
> > > >
> > > > Ian
> > > >
> > > > Sent from Mail for Windows 10
> > > >
> > > > From: Ian Dunlop
> > > > Sent: 04 April 2019 13:40
> > > > To: dev@taverna.incubator.apache.org
> > > > Subject: RE: [DISCUSS] Release Apache Taverna Mobile
> 1.0-incubating-RC1
> > > >
> > > > Hello,
> > > >
> > > > @Stian I need a bit of clarification. Why did you say
> > > > -1 "-RC1" in folder name inside (not ideal)
> > > >
> > > > Having RC1 in the folder name seems to agree with the instructions I
> > > follow at
> > >
> >
> https://taverna.incubator.apache.org/community/releasing#uploading-to-distapacheorg
> > > > “Under source/, make a corresponding versioned folder for each
> product,
> > > and include the RC number, avoiding confusion in case you need to make
> a
> > > second release candidate:”
> > > >
> > > > Cheers,
> > > >
> > > > Ian
> > > >
> > > >
> > > > Sent from Mail for Windows 10
> > > >
> > > > From: Ian Dunlop
> > > > Sent: 04 April 2019 13:19
> > > > To: Sagar
> > > > Cc: dev@taverna.incubator.apache.org; Stian Soiland-Reyes
> > > > Subject: RE: [DISCUSS] Release Apache Taverna Mobile
> 1.0-incubating-RC1
> > > >
> > > > Hello,
> > > >
> > > > Ok so I’m cancelling the current RC1 vote, merging the changes into
> > > master and starting a vote on RC2.
> > > >
> > > > Cheers,
> > > >
> > > > Ian
> > > >
> > > > Sent from Mail for Windows 10
> > > >
> > > > From: Sagar
> > > > Sent: 03 April 2019 16:19
> > > > To: Ian Dunlop
> > > > Cc: dev@taverna.incubator.apache.org; Stian Soiland-Reyes
> > > > Subject: Re: [DISCUSS] Release Apache Taverna Mobile
> 1.0-incubating-RC1
> > > >
> > > > This looks good to me.
> > > >
> > > > On Wed, Apr 3, 2019 at 4:00 PM Ian Dunlop 
> > wrote:
> > > > Hello,
> > > >
> > > > Adding the gradle download into the travis file appears to work. See
> > > https://travis-ci.org/apache/incubator-taverna-mobile/builds/515120359
> .
> > I
> > > rolled the gradle changes back out of master and put them in branch
> > > ian_travis_gradle. If everyone thinks this is an ok direction then we
> can
> > > 

Re: [DISCUSS] Release Apache Taverna Mobile 1.0-incubating-RC1

[Ian Dunlop]

Hello

Sorry I've been really busy and struggling for any time. I did fix the
issues from rc1 and tagged an rc2 in the repo and I even started sorted out
the folder structure but then real life caught up and I didn't manage to
get it out. Maybe someone could pick it up and run with it.

Cheers

Ian

On Wed, 5 Jun 2019, 15:47 Stian Soiland-Reyes,  wrote:

> This went a bit tricky in the end.. so are we back to square 0 or can we
> try again for another RC2? It's not a blocker really if it says RC2
> inside the folder name.. just misleading.
> (if the vote passes then 1.0.0-RC2 == 1.0.0)
>
> On Thu, 4 Apr 2019 14:01:58 +0100, Ian Dunlop 
> wrote:
> > Hello,
> >
> > I think I know what you mean now. It’s the folder name inside the
> .tar.gz when you explode it. Hmm. That seems to be be automatically put
> together by GitHub based on the repo name and the tag name. Ie
> incubator-taverna-mobile & 1.0-incubating-RC2. That’s slightly annoying.
> > So  it looks like this GitHub release mechanism isn’t so great after
> all. Or at least I’ll have to open the file and change the name then gzip
> it back up. Oh well.
> >
> > Cheers,
> >
> > Ian
> >
> > Sent from Mail for Windows 10
> >
> > From: Ian Dunlop
> > Sent: 04 April 2019 13:40
> > To: dev@taverna.incubator.apache.org
> > Subject: RE: [DISCUSS] Release Apache Taverna Mobile 1.0-incubating-RC1
> >
> > Hello,
> >
> > @Stian I need a bit of clarification. Why did you say
> > -1 "-RC1" in folder name inside (not ideal)
> >
> > Having RC1 in the folder name seems to agree with the instructions I
> follow at
> https://taverna.incubator.apache.org/community/releasing#uploading-to-distapacheorg
> > “Under source/, make a corresponding versioned folder for each product,
> and include the RC number, avoiding confusion in case you need to make a
> second release candidate:”
> >
> > Cheers,
> >
> > Ian
> >
> >
> > Sent from Mail for Windows 10
> >
> > From: Ian Dunlop
> > Sent: 04 April 2019 13:19
> > To: Sagar
> > Cc: dev@taverna.incubator.apache.org; Stian Soiland-Reyes
> > Subject: RE: [DISCUSS] Release Apache Taverna Mobile 1.0-incubating-RC1
> >
> > Hello,
> >
> > Ok so I’m cancelling the current RC1 vote, merging the changes into
> master and starting a vote on RC2.
> >
> > Cheers,
> >
> > Ian
> >
> > Sent from Mail for Windows 10
> >
> > From: Sagar
> > Sent: 03 April 2019 16:19
> > To: Ian Dunlop
> > Cc: dev@taverna.incubator.apache.org; Stian Soiland-Reyes
> > Subject: Re: [DISCUSS] Release Apache Taverna Mobile 1.0-incubating-RC1
> >
> > This looks good to me.
> >
> > On Wed, Apr 3, 2019 at 4:00 PM Ian Dunlop  wrote:
> > Hello,
> >
> > Adding the gradle download into the travis file appears to work. See
> https://travis-ci.org/apache/incubator-taverna-mobile/builds/515120359. I
> rolled the gradle changes back out of master and put them in branch
> ian_travis_gradle. If everyone thinks this is an ok direction then we can
> merge back into master and go for RC2 without the binary.
> >
> > Cheers,
> >
> > Ian
> >
> > Sent from Mail for Windows 10
> >
> > From: Ian Dunlop
> > Sent: 02 April 2019 18:10
> > To: Sagar
> > Cc: dev@taverna.incubator.apache.org; Stian Soiland-Reyes
> > Subject: Re: [DISCUSS] Release Apache Taverna Mobile 1.0-incubating-RC1
> >
> > Hello
> >
> > The first answer on
> https://stackoverflow.com/questions/42818269/is-gradlew-mandatory-for-travis-ci-to-work/43493907
>  suggests
> that you can get travis to create a gradle wrapper for you. We could try
> that and see if it works. I'm just trying to make the process simple. For
> Devs you only need to install gradle and run the gradle wrapper command
> once and then you are all setup. I guess we could also write a shell script
> to create the bundle for us. Open to all suggestions.
> > Feel free to back out any of my changes if they are causing you problems
> but we need to think of a solution.
> >
> > Cheers
> >
> > Ian
> >
> > On Tue, 2 Apr 2019, 18:00 Ian Dunlop,  wrote:
> > Hello
> >
> > That makes it a tricky problem to solve. If we can't rely on the GitHub
> tag for the bundle then we will need to create our own after cloning and
> removing the gradle folder. Can Travis create a gradle wrapper before
> building? I'm happy to go with creating our own bundle but it is more work.
> Remove git folder, remove gradle etc.
> >
> > Cheers
> >
> > Ian
> &

RE: [DISCUSS] Release Apache Taverna Mobile 1.0-incubating-RC1

[Ian Dunlop]

Hello,

I think I know what you mean now. It’s the folder name inside the .tar.gz when 
you explode it. Hmm. That seems to be be automatically put together by GitHub 
based on the repo name and the tag name. Ie incubator-taverna-mobile & 
1.0-incubating-RC2. That’s slightly annoying.
So  it looks like this GitHub release mechanism isn’t so great after all. Or at 
least I’ll have to open the file and change the name then gzip it back up. Oh 
well.

Cheers,

Ian

Sent from Mail for Windows 10

From: Ian Dunlop
Sent: 04 April 2019 13:40
To: dev@taverna.incubator.apache.org
Subject: RE: [DISCUSS] Release Apache Taverna Mobile 1.0-incubating-RC1

Hello,

@Stian I need a bit of clarification. Why did you say 
-1 "-RC1" in folder name inside (not ideal)

Having RC1 in the folder name seems to agree with the instructions I follow at 
https://taverna.incubator.apache.org/community/releasing#uploading-to-distapacheorg
“Under source/, make a corresponding versioned folder for each product, and 
include the RC number, avoiding confusion in case you need to make a second 
release candidate:”

Cheers,

Ian


Sent from Mail for Windows 10

From: Ian Dunlop
Sent: 04 April 2019 13:19
To: Sagar
Cc: dev@taverna.incubator.apache.org; Stian Soiland-Reyes
Subject: RE: [DISCUSS] Release Apache Taverna Mobile 1.0-incubating-RC1

Hello,

Ok so I’m cancelling the current RC1 vote, merging the changes into master and 
starting a vote on RC2.

Cheers,

Ian

Sent from Mail for Windows 10

From: Sagar
Sent: 03 April 2019 16:19
To: Ian Dunlop
Cc: dev@taverna.incubator.apache.org; Stian Soiland-Reyes
Subject: Re: [DISCUSS] Release Apache Taverna Mobile 1.0-incubating-RC1

This looks good to me.

On Wed, Apr 3, 2019 at 4:00 PM Ian Dunlop  wrote:
Hello,
 
Adding the gradle download into the travis file appears to work. See 
https://travis-ci.org/apache/incubator-taverna-mobile/builds/515120359. I 
rolled the gradle changes back out of master and put them in branch 
ian_travis_gradle. If everyone thinks this is an ok direction then we can merge 
back into master and go for RC2 without the binary.
 
Cheers,
 
Ian
 
Sent from Mail for Windows 10
 
From: Ian Dunlop
Sent: 02 April 2019 18:10
To: Sagar
Cc: dev@taverna.incubator.apache.org; Stian Soiland-Reyes
Subject: Re: [DISCUSS] Release Apache Taverna Mobile 1.0-incubating-RC1
 
Hello
 
The first answer on 
https://stackoverflow.com/questions/42818269/is-gradlew-mandatory-for-travis-ci-to-work/43493907
 suggests that you can get travis to create a gradle wrapper for you. We could 
try that and see if it works. I'm just trying to make the process simple. For 
Devs you only need to install gradle and run the gradle wrapper command once 
and then you are all setup. I guess we could also write a shell script to 
create the bundle for us. Open to all suggestions.
Feel free to back out any of my changes if they are causing you problems but we 
need to think of a solution.
 
Cheers
 
Ian
 
On Tue, 2 Apr 2019, 18:00 Ian Dunlop,  wrote:
Hello
 
That makes it a tricky problem to solve. If we can't rely on the GitHub tag for 
the bundle then we will need to create our own after cloning and removing the 
gradle folder. Can Travis create a gradle wrapper before building? I'm happy to 
go with creating our own bundle but it is more work. Remove git folder, remove 
gradle etc.
 
Cheers
 
Ian
 
On Tue, 2 Apr 2019, 17:15 Sagar,  wrote:
Due to removing the wrapper. We will not able to build the project. It is 
required to build the android code. Travis is also failing because of this.
 
On Tue, Apr 2, 2019 at 8:53 PM Ian Dunlop  wrote:
Hello
 
I just commited some fixes. Hopefully all the files have the correct headers 
now. I also removed the gradle wrapper. Now you have to create the wrapper 
yourself when you first clone the project. Seems like the easiest way to avoid 
the binary issue. I think I've got the issues fixed so I can try and put RC2 
together soon. Hopefully my key issue is fixed as well. Maybe someone could 
check for me.
 
Cheers,
 
Ian
 
On Tue, 2 Apr 2019, 15:10 Sagar,  wrote:
@Ian Dunlop  Are you working on the issues or do I make the change?

 
 
On Mon, Apr 1, 2019 at 9:41 PM Ian Dunlop  wrote:
Hello,

The key fingerprint is the same as listed in the KEYS file. Does that mean the 
key is the same?

Cheers,

Ian

Sent from Mail for Windows 10

From: Stian Soiland-Reyes
Sent: 01 April 2019 16:43
To: Ian Dunlop
Cc: dev@taverna.incubator.apache.org
Subject: RE: [DISCUSS] Release Apache Taverna Mobile 1.0-incubating-RC1

You'll also need to update the KEYS file in dist.

On Mon, 1 Apr 2019 13:39:40 +0100, Ian Dunlop  wrote:
> Hello,
> 
> @Sagar don’t forget to give it a +1 on the [VOTE] thread if you think it 
> passes all the Apache release criteria. I think I just posted my VOTE to the 
> DISCUSS thread – not sure message threading is working correctly in my email 
> client. Apologies for any confusion.
> 
> I’ve updated my key on the keyservers

RE: [DISCUSS] Release Apache Taverna Mobile 1.0-incubating-RC1

[Ian Dunlop]

Hello,

@Stian I need a bit of clarification. Why did you say 
-1 "-RC1" in folder name inside (not ideal)

Having RC1 in the folder name seems to agree with the instructions I follow at 
https://taverna.incubator.apache.org/community/releasing#uploading-to-distapacheorg
“Under source/, make a corresponding versioned folder for each product, and 
include the RC number, avoiding confusion in case you need to make a second 
release candidate:”

Cheers,

Ian


Sent from Mail for Windows 10

From: Ian Dunlop
Sent: 04 April 2019 13:19
To: Sagar
Cc: dev@taverna.incubator.apache.org; Stian Soiland-Reyes
Subject: RE: [DISCUSS] Release Apache Taverna Mobile 1.0-incubating-RC1

Hello,

Ok so I’m cancelling the current RC1 vote, merging the changes into master and 
starting a vote on RC2.

Cheers,

Ian

Sent from Mail for Windows 10

From: Sagar
Sent: 03 April 2019 16:19
To: Ian Dunlop
Cc: dev@taverna.incubator.apache.org; Stian Soiland-Reyes
Subject: Re: [DISCUSS] Release Apache Taverna Mobile 1.0-incubating-RC1

This looks good to me.

On Wed, Apr 3, 2019 at 4:00 PM Ian Dunlop  wrote:
Hello,
 
Adding the gradle download into the travis file appears to work. See 
https://travis-ci.org/apache/incubator-taverna-mobile/builds/515120359. I 
rolled the gradle changes back out of master and put them in branch 
ian_travis_gradle. If everyone thinks this is an ok direction then we can merge 
back into master and go for RC2 without the binary.
 
Cheers,
 
Ian
 
Sent from Mail for Windows 10
 
From: Ian Dunlop
Sent: 02 April 2019 18:10
To: Sagar
Cc: dev@taverna.incubator.apache.org; Stian Soiland-Reyes
Subject: Re: [DISCUSS] Release Apache Taverna Mobile 1.0-incubating-RC1
 
Hello
 
The first answer on 
https://stackoverflow.com/questions/42818269/is-gradlew-mandatory-for-travis-ci-to-work/43493907
 suggests that you can get travis to create a gradle wrapper for you. We could 
try that and see if it works. I'm just trying to make the process simple. For 
Devs you only need to install gradle and run the gradle wrapper command once 
and then you are all setup. I guess we could also write a shell script to 
create the bundle for us. Open to all suggestions.
Feel free to back out any of my changes if they are causing you problems but we 
need to think of a solution.
 
Cheers
 
Ian
 
On Tue, 2 Apr 2019, 18:00 Ian Dunlop,  wrote:
Hello
 
That makes it a tricky problem to solve. If we can't rely on the GitHub tag for 
the bundle then we will need to create our own after cloning and removing the 
gradle folder. Can Travis create a gradle wrapper before building? I'm happy to 
go with creating our own bundle but it is more work. Remove git folder, remove 
gradle etc.
 
Cheers
 
Ian
 
On Tue, 2 Apr 2019, 17:15 Sagar,  wrote:
Due to removing the wrapper. We will not able to build the project. It is 
required to build the android code. Travis is also failing because of this.
 
On Tue, Apr 2, 2019 at 8:53 PM Ian Dunlop  wrote:
Hello
 
I just commited some fixes. Hopefully all the files have the correct headers 
now. I also removed the gradle wrapper. Now you have to create the wrapper 
yourself when you first clone the project. Seems like the easiest way to avoid 
the binary issue. I think I've got the issues fixed so I can try and put RC2 
together soon. Hopefully my key issue is fixed as well. Maybe someone could 
check for me.
 
Cheers,
 
Ian
 
On Tue, 2 Apr 2019, 15:10 Sagar,  wrote:
@Ian Dunlop  Are you working on the issues or do I make the change?

 
 
On Mon, Apr 1, 2019 at 9:41 PM Ian Dunlop  wrote:
Hello,

The key fingerprint is the same as listed in the KEYS file. Does that mean the 
key is the same?

Cheers,

Ian

Sent from Mail for Windows 10

From: Stian Soiland-Reyes
Sent: 01 April 2019 16:43
To: Ian Dunlop
Cc: dev@taverna.incubator.apache.org
Subject: RE: [DISCUSS] Release Apache Taverna Mobile 1.0-incubating-RC1

You'll also need to update the KEYS file in dist.

On Mon, 1 Apr 2019 13:39:40 +0100, Ian Dunlop  wrote:
> Hello,
> 
> @Sagar don’t forget to give it a +1 on the [VOTE] thread if you think it 
> passes all the Apache release criteria. I think I just posted my VOTE to the 
> DISCUSS thread – not sure message threading is working correctly in my email 
> client. Apologies for any confusion.
> 
> I’ve updated my key on the keyservers (gpg & ubuntu though they should both 
> sync anyway). Let’s see if that fixes things because I’m sure I’ve updated 
> them before.
> I guess we should give them 24 hours to sort themselves out and then gpg 
> --refresh-keys to update your local keys.


 
-- 
 
Warmest regards
Sagar
Software Developer
Lattice Innovations Pvt. Ltd.


 
-- 
 
Warmest regards
Sagar
Software Developer
Lattice Innovations Pvt. Ltd.
 



-- 

Warmest regards
Sagar
Software Developer
Lattice Innovations Pvt. Ltd.

RE: [DISCUSS] Release Apache Taverna Mobile 1.0-incubating-RC1

[Ian Dunlop]

Hello,

Ok so I’m cancelling the current RC1 vote, merging the changes into master and 
starting a vote on RC2.

Cheers,

Ian

Sent from Mail for Windows 10

From: Sagar
Sent: 03 April 2019 16:19
To: Ian Dunlop
Cc: dev@taverna.incubator.apache.org; Stian Soiland-Reyes
Subject: Re: [DISCUSS] Release Apache Taverna Mobile 1.0-incubating-RC1

This looks good to me.

On Wed, Apr 3, 2019 at 4:00 PM Ian Dunlop  wrote:
Hello,
 
Adding the gradle download into the travis file appears to work. See 
https://travis-ci.org/apache/incubator-taverna-mobile/builds/515120359. I 
rolled the gradle changes back out of master and put them in branch 
ian_travis_gradle. If everyone thinks this is an ok direction then we can merge 
back into master and go for RC2 without the binary.
 
Cheers,
 
Ian
 
Sent from Mail for Windows 10
 
From: Ian Dunlop
Sent: 02 April 2019 18:10
To: Sagar
Cc: dev@taverna.incubator.apache.org; Stian Soiland-Reyes
Subject: Re: [DISCUSS] Release Apache Taverna Mobile 1.0-incubating-RC1
 
Hello
 
The first answer on 
https://stackoverflow.com/questions/42818269/is-gradlew-mandatory-for-travis-ci-to-work/43493907
 suggests that you can get travis to create a gradle wrapper for you. We could 
try that and see if it works. I'm just trying to make the process simple. For 
Devs you only need to install gradle and run the gradle wrapper command once 
and then you are all setup. I guess we could also write a shell script to 
create the bundle for us. Open to all suggestions.
Feel free to back out any of my changes if they are causing you problems but we 
need to think of a solution.
 
Cheers
 
Ian
 
On Tue, 2 Apr 2019, 18:00 Ian Dunlop,  wrote:
Hello
 
That makes it a tricky problem to solve. If we can't rely on the GitHub tag for 
the bundle then we will need to create our own after cloning and removing the 
gradle folder. Can Travis create a gradle wrapper before building? I'm happy to 
go with creating our own bundle but it is more work. Remove git folder, remove 
gradle etc.
 
Cheers
 
Ian
 
On Tue, 2 Apr 2019, 17:15 Sagar,  wrote:
Due to removing the wrapper. We will not able to build the project. It is 
required to build the android code. Travis is also failing because of this.
 
On Tue, Apr 2, 2019 at 8:53 PM Ian Dunlop  wrote:
Hello
 
I just commited some fixes. Hopefully all the files have the correct headers 
now. I also removed the gradle wrapper. Now you have to create the wrapper 
yourself when you first clone the project. Seems like the easiest way to avoid 
the binary issue. I think I've got the issues fixed so I can try and put RC2 
together soon. Hopefully my key issue is fixed as well. Maybe someone could 
check for me.
 
Cheers,
 
Ian
 
On Tue, 2 Apr 2019, 15:10 Sagar,  wrote:
@Ian Dunlop  Are you working on the issues or do I make the change?

 
 
On Mon, Apr 1, 2019 at 9:41 PM Ian Dunlop  wrote:
Hello,

The key fingerprint is the same as listed in the KEYS file. Does that mean the 
key is the same?

Cheers,

Ian

Sent from Mail for Windows 10

From: Stian Soiland-Reyes
Sent: 01 April 2019 16:43
To: Ian Dunlop
Cc: dev@taverna.incubator.apache.org
Subject: RE: [DISCUSS] Release Apache Taverna Mobile 1.0-incubating-RC1

You'll also need to update the KEYS file in dist.

On Mon, 1 Apr 2019 13:39:40 +0100, Ian Dunlop  wrote:
> Hello,
> 
> @Sagar don’t forget to give it a +1 on the [VOTE] thread if you think it 
> passes all the Apache release criteria. I think I just posted my VOTE to the 
> DISCUSS thread – not sure message threading is working correctly in my email 
> client. Apologies for any confusion.
> 
> I’ve updated my key on the keyservers (gpg & ubuntu though they should both 
> sync anyway). Let’s see if that fixes things because I’m sure I’ve updated 
> them before.
> I guess we should give them 24 hours to sort themselves out and then gpg 
> --refresh-keys to update your local keys.


 
-- 
 
Warmest regards
Sagar
Software Developer
Lattice Innovations Pvt. Ltd.


 
-- 
 
Warmest regards
Sagar
Software Developer
Lattice Innovations Pvt. Ltd.
 



-- 

Warmest regards
Sagar
Software Developer
Lattice Innovations Pvt. Ltd.

RE: [VOTE] Release Apache Taverna Mobile 1.0-incubating-RC1

[Ian Dunlop]

Hello,

So we are cancelling this vote and will proceed with RC2 once the necessary 
changes are in place. Thanks everyone for your comments and help.

Cheers,

Ian

Sent from Mail for Windows 10

From: Stian Soiland-Reyes
Sent: 01 April 2019 16:31
To: Ian Dunlop
Cc: dev@taverna.incubator.apache.org
Subject: RE: [VOTE] Release Apache Taverna Mobile 1.0-incubating-RC1

On Mon, 1 Apr 2019 16:18:45 +0100, Ian Dunlop  wrote:
> No worries Stian. What files were missing headers? I’ll attempt to run Apache 
> RAT to figure it out. It’s an easy enough fix. I guess I need to remove the 
> gradle jar from the bundle as well.

See "???" in https://paste.apache.org/EUQI 

I had to run rat on the command line after downloading from 
https://creadur.apache.org/rat/download_rat.cgi
as I could not get my gradle to be happy with my open source android SDK
install..


> Hopefully my key will be the un-expired one next time round.
> “-1   wrong copyright year, should go to 2019”. What files?

Only NOTICE needs updating - although 2018 is in README as well.


> I thought the chances of getting it through first time were pretty
> small anyway since this is the first time we have tried this one.

No worries, there are always nitpicks like that for an initial release!
Thanks for having a go!

-- 
Stian Soiland-Reyes
The University of Manchester
https://www.esciencelab.org.uk/
https://orcid.org/-0001-9842-9718

RE: [DISCUSS] Release Apache Taverna Mobile 1.0-incubating-RC1

[Ian Dunlop]

Hello,

Adding the gradle download into the travis file appears to work. See 
https://travis-ci.org/apache/incubator-taverna-mobile/builds/515120359. I 
rolled the gradle changes back out of master and put them in branch 
ian_travis_gradle. If everyone thinks this is an ok direction then we can merge 
back into master and go for RC2 without the binary.

Cheers,

Ian

Sent from Mail for Windows 10

From: Ian Dunlop
Sent: 02 April 2019 18:10
To: Sagar
Cc: dev@taverna.incubator.apache.org; Stian Soiland-Reyes
Subject: Re: [DISCUSS] Release Apache Taverna Mobile 1.0-incubating-RC1

Hello

The first answer on 
https://stackoverflow.com/questions/42818269/is-gradlew-mandatory-for-travis-ci-to-work/43493907
 suggests that you can get travis to create a gradle wrapper for you. We could 
try that and see if it works. I'm just trying to make the process simple. For 
Devs you only need to install gradle and run the gradle wrapper command once 
and then you are all setup. I guess we could also write a shell script to 
create the bundle for us. Open to all suggestions.
Feel free to back out any of my changes if they are causing you problems but we 
need to think of a solution.

Cheers

Ian

On Tue, 2 Apr 2019, 18:00 Ian Dunlop,  wrote:
Hello

That makes it a tricky problem to solve. If we can't rely on the GitHub tag for 
the bundle then we will need to create our own after cloning and removing the 
gradle folder. Can Travis create a gradle wrapper before building? I'm happy to 
go with creating our own bundle but it is more work. Remove git folder, remove 
gradle etc.

Cheers

Ian

On Tue, 2 Apr 2019, 17:15 Sagar,  wrote:
Due to removing the wrapper. We will not able to build the project. It is 
required to build the android code. Travis is also failing because of this.


On Tue, Apr 2, 2019 at 8:53 PM Ian Dunlop  wrote:
Hello

I just commited some fixes. Hopefully all the files have the correct headers 
now. I also removed the gradle wrapper. Now you have to create the wrapper 
yourself when you first clone the project. Seems like the easiest way to avoid 
the binary issue. I think I've got the issues fixed so I can try and put RC2 
together soon. Hopefully my key issue is fixed as well. Maybe someone could 
check for me.

Cheers,

Ian

On Tue, 2 Apr 2019, 15:10 Sagar,  wrote:
@Ian Dunlop  Are you working on the issues or do I make the change?




On Mon, Apr 1, 2019 at 9:41 PM Ian Dunlop  wrote:
Hello,

The key fingerprint is the same as listed in the KEYS file. Does that mean the 
key is the same?

Cheers,

Ian

Sent from Mail for Windows 10

From: Stian Soiland-Reyes
Sent: 01 April 2019 16:43
To: Ian Dunlop
Cc: dev@taverna.incubator.apache.org
Subject: RE: [DISCUSS] Release Apache Taverna Mobile 1.0-incubating-RC1

You'll also need to update the KEYS file in dist.

On Mon, 1 Apr 2019 13:39:40 +0100, Ian Dunlop  wrote:
> Hello,
> 
> @Sagar don’t forget to give it a +1 on the [VOTE] thread if you think it 
> passes all the Apache release criteria. I think I just posted my VOTE to the 
> DISCUSS thread – not sure message threading is working correctly in my email 
> client. Apologies for any confusion.
> 
> I’ve updated my key on the keyservers (gpg & ubuntu though they should both 
> sync anyway). Let’s see if that fixes things because I’m sure I’ve updated 
> them before.
> I guess we should give them 24 hours to sort themselves out and then gpg 
> --refresh-keys to update your local keys.



-- 

Warmest regards
Sagar
Software Developer
Lattice Innovations Pvt. Ltd.



-- 

Warmest regards
Sagar
Software Developer
Lattice Innovations Pvt. Ltd.

Re: [DISCUSS] Release Apache Taverna Mobile 1.0-incubating-RC1

[Ian Dunlop]

Hello

The first answer on
https://stackoverflow.com/questions/42818269/is-gradlew-mandatory-for-travis-ci-to-work/43493907
suggests
that you can get travis to create a gradle wrapper for you. We could try
that and see if it works. I'm just trying to make the process simple. For
Devs you only need to install gradle and run the gradle wrapper command
once and then you are all setup. I guess we could also write a shell script
to create the bundle for us. Open to all suggestions.
Feel free to back out any of my changes if they are causing you problems
but we need to think of a solution.

Cheers

Ian

On Tue, 2 Apr 2019, 18:00 Ian Dunlop,  wrote:

> Hello
>
> That makes it a tricky problem to solve. If we can't rely on the GitHub
> tag for the bundle then we will need to create our own after cloning and
> removing the gradle folder. Can Travis create a gradle wrapper before
> building? I'm happy to go with creating our own bundle but it is more work.
> Remove git folder, remove gradle etc.
>
> Cheers
>
> Ian
>
> On Tue, 2 Apr 2019, 17:15 Sagar,  wrote:
>
>> Due to removing the wrapper. We will not able to build the project. It is
>> required to build the android code. Travis is also failing because of this.
>>
>>
>>
>> On Tue, Apr 2, 2019 at 8:53 PM Ian Dunlop  wrote:
>>
>>> Hello
>>>
>>> I just commited some fixes. Hopefully all the files have the correct
>>> headers now. I also removed the gradle wrapper. Now you have to create the
>>> wrapper yourself when you first clone the project. Seems like the easiest
>>> way to avoid the binary issue. I think I've got the issues fixed so I can
>>> try and put RC2 together soon. Hopefully my key issue is fixed as well.
>>> Maybe someone could check for me.
>>>
>>> Cheers,
>>>
>>> Ian
>>>
>>> On Tue, 2 Apr 2019, 15:10 Sagar,  wrote:
>>>
>>>> @Ian Dunlop   Are you working on the issues or
>>>> do I make the change?
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> On Mon, Apr 1, 2019 at 9:41 PM Ian Dunlop  wrote:
>>>>
>>>>> Hello,
>>>>>
>>>>> The key fingerprint is the same as listed in the KEYS file. Does that
>>>>> mean the key is the same?
>>>>>
>>>>> Cheers,
>>>>>
>>>>> Ian
>>>>>
>>>>> Sent from Mail for Windows 10
>>>>>
>>>>> From: Stian Soiland-Reyes
>>>>> Sent: 01 April 2019 16:43
>>>>> To: Ian Dunlop
>>>>> Cc: dev@taverna.incubator.apache.org
>>>>> Subject: RE: [DISCUSS] Release Apache Taverna Mobile 1.0-incubating-RC1
>>>>>
>>>>> You'll also need to update the KEYS file in dist.
>>>>>
>>>>> On Mon, 1 Apr 2019 13:39:40 +0100, Ian Dunlop 
>>>>> wrote:
>>>>> > Hello,
>>>>> >
>>>>> > @Sagar don’t forget to give it a +1 on the [VOTE] thread if you
>>>>> think it passes all the Apache release criteria. I think I just posted my
>>>>> VOTE to the DISCUSS thread – not sure message threading is working
>>>>> correctly in my email client. Apologies for any confusion.
>>>>> >
>>>>> > I’ve updated my key on the keyservers (gpg & ubuntu though they
>>>>> should both sync anyway). Let’s see if that fixes things because I’m sure
>>>>> I’ve updated them before.
>>>>> > I guess we should give them 24 hours to sort themselves out and then
>>>>> gpg --refresh-keys to update your local keys.
>>>>>
>>>>>
>>>>
>>>> --
>>>>
>>>> Warmest regards
>>>> Sagar
>>>> Software Developer
>>>> Lattice Innovations Pvt. Ltd.
>>>>
>>>
>>
>> --
>>
>> Warmest regards
>> Sagar
>> Software Developer
>> Lattice Innovations Pvt. Ltd.
>>
>

Re: [DISCUSS] Release Apache Taverna Mobile 1.0-incubating-RC1

[Ian Dunlop]

Hello

That makes it a tricky problem to solve. If we can't rely on the GitHub tag
for the bundle then we will need to create our own after cloning and
removing the gradle folder. Can Travis create a gradle wrapper before
building? I'm happy to go with creating our own bundle but it is more work.
Remove git folder, remove gradle etc.

Cheers

Ian

On Tue, 2 Apr 2019, 17:15 Sagar,  wrote:

> Due to removing the wrapper. We will not able to build the project. It is
> required to build the android code. Travis is also failing because of this.
>
>
>
> On Tue, Apr 2, 2019 at 8:53 PM Ian Dunlop  wrote:
>
>> Hello
>>
>> I just commited some fixes. Hopefully all the files have the correct
>> headers now. I also removed the gradle wrapper. Now you have to create the
>> wrapper yourself when you first clone the project. Seems like the easiest
>> way to avoid the binary issue. I think I've got the issues fixed so I can
>> try and put RC2 together soon. Hopefully my key issue is fixed as well.
>> Maybe someone could check for me.
>>
>> Cheers,
>>
>> Ian
>>
>> On Tue, 2 Apr 2019, 15:10 Sagar,  wrote:
>>
>>> @Ian Dunlop   Are you working on the issues or do
>>> I make the change?
>>>
>>>
>>>
>>>
>>>
>>> On Mon, Apr 1, 2019 at 9:41 PM Ian Dunlop  wrote:
>>>
>>>> Hello,
>>>>
>>>> The key fingerprint is the same as listed in the KEYS file. Does that
>>>> mean the key is the same?
>>>>
>>>> Cheers,
>>>>
>>>> Ian
>>>>
>>>> Sent from Mail for Windows 10
>>>>
>>>> From: Stian Soiland-Reyes
>>>> Sent: 01 April 2019 16:43
>>>> To: Ian Dunlop
>>>> Cc: dev@taverna.incubator.apache.org
>>>> Subject: RE: [DISCUSS] Release Apache Taverna Mobile 1.0-incubating-RC1
>>>>
>>>> You'll also need to update the KEYS file in dist.
>>>>
>>>> On Mon, 1 Apr 2019 13:39:40 +0100, Ian Dunlop 
>>>> wrote:
>>>> > Hello,
>>>> >
>>>> > @Sagar don’t forget to give it a +1 on the [VOTE] thread if you think
>>>> it passes all the Apache release criteria. I think I just posted my VOTE to
>>>> the DISCUSS thread – not sure message threading is working correctly in my
>>>> email client. Apologies for any confusion.
>>>> >
>>>> > I’ve updated my key on the keyservers (gpg & ubuntu though they
>>>> should both sync anyway). Let’s see if that fixes things because I’m sure
>>>> I’ve updated them before.
>>>> > I guess we should give them 24 hours to sort themselves out and then
>>>> gpg --refresh-keys to update your local keys.
>>>>
>>>>
>>>
>>> --
>>>
>>> Warmest regards
>>> Sagar
>>> Software Developer
>>> Lattice Innovations Pvt. Ltd.
>>>
>>
>
> --
>
> Warmest regards
> Sagar
> Software Developer
> Lattice Innovations Pvt. Ltd.
>

RE: [DISCUSS] Release Apache Taverna Mobile 1.0-incubating-RC1

[Ian Dunlop]

Hello,

The key fingerprint is the same as listed in the KEYS file. Does that mean the 
key is the same?

Cheers,

Ian

Sent from Mail for Windows 10

From: Stian Soiland-Reyes
Sent: 01 April 2019 16:43
To: Ian Dunlop
Cc: dev@taverna.incubator.apache.org
Subject: RE: [DISCUSS] Release Apache Taverna Mobile 1.0-incubating-RC1

You'll also need to update the KEYS file in dist.

On Mon, 1 Apr 2019 13:39:40 +0100, Ian Dunlop  wrote:
> Hello,
> 
> @Sagar don’t forget to give it a +1 on the [VOTE] thread if you think it 
> passes all the Apache release criteria. I think I just posted my VOTE to the 
> DISCUSS thread – not sure message threading is working correctly in my email 
> client. Apologies for any confusion.
> 
> I’ve updated my key on the keyservers (gpg & ubuntu though they should both 
> sync anyway). Let’s see if that fixes things because I’m sure I’ve updated 
> them before.
> I guess we should give them 24 hours to sort themselves out and then gpg 
> --refresh-keys to update your local keys.

RE: [VOTE] Release Apache Taverna Mobile 1.0-incubating-RC1

[Ian Dunlop]

Hello,

No worries Stian. What files were missing headers? I’ll attempt to run Apache 
RAT to figure it out. It’s an easy enough fix. I guess I need to remove the 
gradle jar from the bundle as well.
Hopefully my key will be the un-expired one next time round.
“-1   wrong copyright year, should go to 2019”. What files?
I thought the chances of getting it through first time were pretty small anyway 
since this is the first time we have tried this one.

Cheers,

Ian

Sent from Mail for Windows 10

From: Stian Soiland-Reyes
Sent: 01 April 2019 15:34
To: Ian Dunlop
Cc: dev@taverna.incubator.apache.org
Subject: Re: [VOTE] Release Apache Taverna Mobile 1.0-incubating-RC1

Thanks for putting this RC together, Ian!

My vote I'm afraid:

-1  

because of missing ASF headers and embedded jar binary.



Checked:

-1 Some missing ASF file headers
-1 binaries included (gradle.jar)
+0 GPG signature correct
-1 your key from KEYS has expired!
+0 sha512 checksum correct
-1   *.sha512 file include spaces
+1 "incubator" in zip-name and folder
-1 "apache" missing from zip-name and folder-name inside
-1 "-RC1" in folder name inside (not ideal)
-0 NOTICE
-1   wrong copyright year, should go to 2019
+1 LICENSE
+1 DISCLAIMER
+0 Matches git 14815291d892231179c5408298fb3ad116294a47 
-0   commit id not provided in VOTE email
+0 build not tested

See RAT report at https://paste.apache.org/EUQI 
..about 16 of the .java files and 21 of the .xml
files are missing ASF headers.




Which version Android SDK do I need to build it? build.gradle says 28, 
I tried with https://wiki.debian.org/AndroidTools which was not a great
success so I guess the commercial platform must be installed.



On Thu, 28 Mar 2019 16:22:14 +, Ian Dunlop  wrote:
> Hello,
> 
> I am pleased to be calling this vote for the source release of
> Apache Taverna Mobile 1.0-incubating-RC1
> To discuss this release candidate, use the corresponding [DISCUSS] thread.
> 
> Apache Taverna Mobile is an Android Mobile application which can be used to 
> browse and run Apache Taverna workflows.
> 
> The release candidate to be voted on is available at:
> https://dist.apache.org/repos/dist/dev/incubator/taverna/source/incubator-taverna-mobile-1.0-incubating-RC1/
> 
> SHA-512 checksums: 
> 172FA334 9C8B2BB0 092CB23A 409B7D74 B91B1689 C426ECA0 694F8087 6DE54EE5 
> 6B5ABB01
>  BF528C65 2194CFCE 4394E249 9AD8C749 45814318 A4A2BCB7 040AA03E
> 
> MD5 checksums: 
> 3e73213dcc7569d47792752d2baed733
> 
> To build it:
> tar -xzvf incubator-taverna-mobile-1.0-incubating-RC1.tar.gz
> You will need the android sdk or android studio to build.
> If you have the android sdk installed then set ANDROID_HOME to point to it 
> and try:
> ./gradlew build
> 
> The release candidate corresponds to the following tag in git:
> https://github.com/apache/incubator-taverna-mobile/releases/tag/1.0-incubating-RC1
> Release candidates are signed with a GPG key available at:
> https://dist.apache.org/repos/dist/release/incubator/taverna/KEYS
> To verify it:
> First download the key file from 
> https://people.apache.org/keys/group/taverna.asc
> And import it to your gpg keyring
> gpg –import taverna.asc
> Then verify it:
> gpg --verify incubator-taverna-mobile-1.0-incubating-RC1.tar.gz.asc 
> incubator-taverna-mobile-1.0-incubating-RC1.tar.gz
> 
> Please vote on releasing these packages as:
> Apache Taverna Mobile 1.0-incubating-RC1
> The vote is open for at least 72 hours and passes if a majority of at least 
> three +1 Apache Taverna PPMC votes are cast.
> [ ] +1 Release this package [ ] 0 I don't feel strongly about it, but don't 
> object [ ] -1 Do not release this package because...

RE: [DISCUSS] Release Apache Taverna Mobile 1.0-incubating-RC1

[Ian Dunlop]

Hello,

@Sagar don’t forget to give it a +1 on the [VOTE] thread if you think it passes 
all the Apache release criteria. I think I just posted my VOTE to the DISCUSS 
thread – not sure message threading is working correctly in my email client. 
Apologies for any confusion.

I’ve updated my key on the keyservers (gpg & ubuntu though they should both 
sync anyway). Let’s see if that fixes things because I’m sure I’ve updated them 
before.
I guess we should give them 24 hours to sort themselves out and then gpg 
--refresh-keys to update your local keys.

Cheers,


Sent from Mail for Windows 10

From: Ian Dunlop
Sent: 29 March 2019 19:41
To: dev@taverna.incubator.apache.org
Subject: Re: [DISCUSS] Release Apache Taverna Mobile 1.0-incubating-RC1

Hello,

Sagar noted that the gpg key I used to sign the release had expired. I need to 
double check this and update it in the keyservers if necessary. I'm not sure 
whether it matters or not for the purposes of checking the release but 
something to fix for next time.

Cheers,

Ian

On Fri, 29 Mar 2019, 19:38 Ian Dunlop,  wrote:
Hello,

Please discuss the release of Apache Taverna Mobile 1.0-incubating-RC1 in this 
thread.

Cheers,

Ian

RE: [VOTE] Release Apache Taverna Mobile 1.0-incubating-RC1

[Ian Dunlop]

Hello,

Built successfully on ubuntu 16.04.
SHA1 & MD5 checksums match. GPG signed .tar.gz source bundle verified.
Licence, NOTICE, apache file headers all good.

+1

Cheers,

Ian

Sent from Mail for Windows 10

From: Ian Dunlop
Sent: 28 March 2019 16:22
To: dev@taverna.incubator.apache.org
Subject: [VOTE] Release Apache Taverna Mobile 1.0-incubating-RC1

Hello,

I am pleased to be calling this vote for the source release of
Apache Taverna Mobile 1.0-incubating-RC1
To discuss this release candidate, use the corresponding [DISCUSS] thread.

Apache Taverna Mobile is an Android Mobile application which can be used to 
browse and run Apache Taverna workflows.

The release candidate to be voted on is available at:
https://dist.apache.org/repos/dist/dev/incubator/taverna/source/incubator-taverna-mobile-1.0-incubating-RC1/

SHA-512 checksums: 
172FA334 9C8B2BB0 092CB23A 409B7D74 B91B1689 C426ECA0 694F8087 6DE54EE5 6B5ABB01
BF528C65 2194CFCE 4394E249 9AD8C749 45814318 A4A2BCB7 040AA03E

MD5 checksums: 
3e73213dcc7569d47792752d2baed733

To build it:
tar -xzvf incubator-taverna-mobile-1.0-incubating-RC1.tar.gz
You will need the android sdk or android studio to build.
If you have the android sdk installed then set ANDROID_HOME to point to it and 
try:
./gradlew build

The release candidate corresponds to the following tag in git:
https://github.com/apache/incubator-taverna-mobile/releases/tag/1.0-incubating-RC1
Release candidates are signed with a GPG key available at:
https://dist.apache.org/repos/dist/release/incubator/taverna/KEYS
To verify it:
First download the key file from 
https://people.apache.org/keys/group/taverna.asc
And import it to your gpg keyring
gpg –import taverna.asc
Then verify it:
gpg --verify incubator-taverna-mobile-1.0-incubating-RC1.tar.gz.asc 
incubator-taverna-mobile-1.0-incubating-RC1.tar.gz

Please vote on releasing these packages as:
Apache Taverna Mobile 1.0-incubating-RC1
The vote is open for at least 72 hours and passes if a majority of at least 
three +1 Apache Taverna PPMC votes are cast.
[ ] +1 Release this package [ ] 0 I don't feel strongly about it, but don't 
object [ ] -1 Do not release this package because...

Anyone can participate in testing and voting, not just committers, please feel 
free to try out the release candidate and provide your votes. 

Cheers,

Ian

Sent from Mail for Windows 10

RE: [DISCUSS] Release Apache Taverna Mobile 1.0-incubating-RC1

[Ian Dunlop]

Hello,

Built successfully on ubuntu 16.04.
SHA1 & MD5 checksums match. GPG signed .tar.gz source bundle verified.
Licence, NOTICE, apache file headers all good.

+1

Cheers,

Ian

Sent from Mail for Windows 10

From: Sagar
Sent: 29 March 2019 12:42
To: dev@taverna.incubator.apache.org
Subject: Re: [DISCUSS] Release Apache Taverna Mobile 1.0-incubating-RC1

Built successfully. md5 & sha1 checksums all match and also verified the
GPG keys but your key has expired. does it make any issue?




On Thu, Mar 28, 2019 at 9:53 PM Ian Dunlop  wrote:

> Hello,
>
> Please discuss the release of Apache Taverna Mobile 1.0-incubating-RC1 in
> this thread.
>
> Cheers,
>
> Ian
>
> Sent from Mail for Windows 10
>
>

-- 

Warmest regards
Sagar
Software Developer
Lattice Innovations Pvt. Ltd.

Re: [DISCUSS] Release Apache Taverna Mobile 1.0-incubating-RC1

[Ian Dunlop]

Hello,

Sagar noted that the gpg key I used to sign the release had expired. I need
to double check this and update it in the keyservers if necessary. I'm not
sure whether it matters or not for the purposes of checking the release but
something to fix for next time.

Cheers,

Ian

On Fri, 29 Mar 2019, 19:38 Ian Dunlop,  wrote:

> Hello,
>
> Please discuss the release of Apache Taverna Mobile 1.0-incubating-RC1 in
> this thread.
>
> Cheers,
>
> Ian
>
>

[DISCUSS] Release Apache Taverna Mobile 1.0-incubating-RC1

[Ian Dunlop]

Hello,

Please discuss the release of Apache Taverna Mobile 1.0-incubating-RC1 in
this thread.

Cheers,

Ian

[VOTE] Release Apache Taverna Mobile 1.0-incubating-RC1

[Ian Dunlop]

Hello,

I am pleased to be calling this vote for the source release of
Apache Taverna Mobile 1.0-incubating-RC1
To discuss this release candidate, use the corresponding [DISCUSS] thread.

Apache Taverna Mobile is an Android Mobile application which can be used to 
browse and run Apache Taverna workflows.

The release candidate to be voted on is available at:
https://dist.apache.org/repos/dist/dev/incubator/taverna/source/incubator-taverna-mobile-1.0-incubating-RC1/

SHA-512 checksums: 
172FA334 9C8B2BB0 092CB23A 409B7D74 B91B1689 C426ECA0 694F8087 6DE54EE5 6B5ABB01
 BF528C65 2194CFCE 4394E249 9AD8C749 45814318 A4A2BCB7 040AA03E

MD5 checksums: 
3e73213dcc7569d47792752d2baed733

To build it:
tar -xzvf incubator-taverna-mobile-1.0-incubating-RC1.tar.gz
You will need the android sdk or android studio to build.
If you have the android sdk installed then set ANDROID_HOME to point to it and 
try:
./gradlew build

The release candidate corresponds to the following tag in git:
https://github.com/apache/incubator-taverna-mobile/releases/tag/1.0-incubating-RC1
Release candidates are signed with a GPG key available at:
https://dist.apache.org/repos/dist/release/incubator/taverna/KEYS
To verify it:
First download the key file from 
https://people.apache.org/keys/group/taverna.asc
And import it to your gpg keyring
gpg –import taverna.asc
Then verify it:
gpg --verify incubator-taverna-mobile-1.0-incubating-RC1.tar.gz.asc 
incubator-taverna-mobile-1.0-incubating-RC1.tar.gz

Please vote on releasing these packages as:
Apache Taverna Mobile 1.0-incubating-RC1
The vote is open for at least 72 hours and passes if a majority of at least 
three +1 Apache Taverna PPMC votes are cast.
[ ] +1 Release this package [ ] 0 I don't feel strongly about it, but don't 
object [ ] -1 Do not release this package because...

Anyone can participate in testing and voting, not just committers, please feel 
free to try out the release candidate and provide your votes. 

Cheers,

Ian

Sent from Mail for Windows 10

[DISCUSS] Release Apache Taverna Mobile 1.0-incubating-RC1

[Ian Dunlop]

Hello,

Please discuss the release of Apache Taverna Mobile 1.0-incubating-RC1 in this 
thread.

Cheers,

Ian

Sent from Mail for Windows 10

RE: Taverna repository release plan

[Ian Dunlop]

Hello,

For the TavMob release I guess we have to:

Tag 
https://taverna.incubator.apache.org/community/releasing#tagging-and-next-snapshot-version
 eg 1.0-incubating-RC1
Sign the .tar.gz https://apache.org/dev/release-signing.html
Upload to dist 
https://taverna.incubator.apache.org/community/releasing#uploading-to-distapacheorg
Vote https://taverna.incubator.apache.org/community/releasing#voting

Cheers,

Ian

Sent from Mail for Windows 10

From: Ian Dunlop
Sent: 28 March 2019 11:36
To: dev@taverna.incubator.apache.org
Subject: RE: Taverna repository release plan

Hello,

I’ve started going through the release procedure for taverna-osgi using the 
guide at https://taverna.incubator.apache.org/community/releasing (it’s been a 
while!). I’m confused by what I need to do about apache-taverna-maven-parent 
since it seems to be depending on parent-4 which I don’t think has been 
released yet according to 
https://issues.apache.org/jira/plugins/servlet/project-config/TAVERNA/versions. 
Does this matter? Or does 

“Remember that in OSGi, as long as we follow semantic versioning and don't 
break API compatibility, an upstream dependency can be updated without forcing 
an update release of its downstream users.”

get around this issue. Ie can I release taverna-osgi to depend on an unreleased 
version of taverna-parent?

Cheers,

Ian


Sent from Mail for Windows 10

From: Ian Dunlop
Sent: 28 March 2019 11:00
To: dev@taverna.incubator.apache.org
Subject: RE: Taverna repository release plan

Hello,

I’ve created a GitHub tag for TavMob 
https://github.com/apache/incubator-taverna-mobile/releases/tag/v1.0. I propose 
we use the source .tar.gz bundle for the release. Shall I proceed with this 
release or does someone else want to try it? Let me know ASAP (today if 
possible). 
I will also attempt to release OSGI & engine. I’m going to assume that there is 
no new code to go in them since they have been quiet for a bit.

Cheers,

Ian

Sent from Mail for Windows 10

From: Sagar
Sent: 27 March 2019 12:36
To: dev@taverna.incubator.apache.org
Cc: Ian Dunlop
Subject: Re: Taverna repository release plan

Agree with stain. We can release using Github.

I have a question regarding the release files, which files we need to include 
in it?

On Wed, Mar 27, 2019 at 2:02 AM Stian Soiland-Reyes  wrote:
On Tue, 26 Mar 2019 10:54:17 +0000, Ian Dunlop  wrote:
> I’m not quite sure what the release process for 1) ie Taverna Mobile
> would be. Bundle up the source in a tgz? I have the feeling I
> suggested something a while back. I’ll need to dig through some old
> emails.

I think that's as good as it will get, we can just tag a release
candidate and then download the tar.gz from GitHub, that should exclude
.git


> Are you suggestion that OSGi & engine are released together? Or in the same 
> release vote anyway.

Yes, separate releases, just concurrent VOTEs.


> If we can think of how to approach 1) then I can put it together. I’m
> happy to try 3) as well which is probably a much easier process since
> it is maven/java.Well, as easy as that process ever gets.

At least it's the same process every time :)

Thanks!


> Do we have a date in mind for all this or just ASAP.

ASAP -so we can graduate! :)



-- 

Warmest regards
Sagar
Software Developer
Lattice Innovations Pvt. Ltd.

RE: Taverna repository release plan

[Ian Dunlop]

Hello,

I’ve started going through the release procedure for taverna-osgi using the 
guide at https://taverna.incubator.apache.org/community/releasing (it’s been a 
while!). I’m confused by what I need to do about apache-taverna-maven-parent 
since it seems to be depending on parent-4 which I don’t think has been 
released yet according to 
https://issues.apache.org/jira/plugins/servlet/project-config/TAVERNA/versions. 
Does this matter? Or does 

“Remember that in OSGi, as long as we follow semantic versioning and don't 
break API compatibility, an upstream dependency can be updated without forcing 
an update release of its downstream users.”

get around this issue. Ie can I release taverna-osgi to depend on an unreleased 
version of taverna-parent?

Cheers,

Ian


Sent from Mail for Windows 10

From: Ian Dunlop
Sent: 28 March 2019 11:00
To: dev@taverna.incubator.apache.org
Subject: RE: Taverna repository release plan

Hello,

I’ve created a GitHub tag for TavMob 
https://github.com/apache/incubator-taverna-mobile/releases/tag/v1.0. I propose 
we use the source .tar.gz bundle for the release. Shall I proceed with this 
release or does someone else want to try it? Let me know ASAP (today if 
possible). 
I will also attempt to release OSGI & engine. I’m going to assume that there is 
no new code to go in them since they have been quiet for a bit.

Cheers,

Ian

Sent from Mail for Windows 10

From: Sagar
Sent: 27 March 2019 12:36
To: dev@taverna.incubator.apache.org
Cc: Ian Dunlop
Subject: Re: Taverna repository release plan

Agree with stain. We can release using Github.

I have a question regarding the release files, which files we need to include 
in it?

On Wed, Mar 27, 2019 at 2:02 AM Stian Soiland-Reyes  wrote:
On Tue, 26 Mar 2019 10:54:17 +0000, Ian Dunlop  wrote:
> I’m not quite sure what the release process for 1) ie Taverna Mobile
> would be. Bundle up the source in a tgz? I have the feeling I
> suggested something a while back. I’ll need to dig through some old
> emails.

I think that's as good as it will get, we can just tag a release
candidate and then download the tar.gz from GitHub, that should exclude
.git


> Are you suggestion that OSGi & engine are released together? Or in the same 
> release vote anyway.

Yes, separate releases, just concurrent VOTEs.


> If we can think of how to approach 1) then I can put it together. I’m
> happy to try 3) as well which is probably a much easier process since
> it is maven/java.Well, as easy as that process ever gets.

At least it's the same process every time :)

Thanks!


> Do we have a date in mind for all this or just ASAP.

ASAP -so we can graduate! :)



-- 

Warmest regards
Sagar
Software Developer
Lattice Innovations Pvt. Ltd.

RE: Taverna repository release plan

[Ian Dunlop]

Hello,

I’ve created a GitHub tag for TavMob 
https://github.com/apache/incubator-taverna-mobile/releases/tag/v1.0. I propose 
we use the source .tar.gz bundle for the release. Shall I proceed with this 
release or does someone else want to try it? Let me know ASAP (today if 
possible). 
I will also attempt to release OSGI & engine. I’m going to assume that there is 
no new code to go in them since they have been quiet for a bit.

Cheers,

Ian

Sent from Mail for Windows 10

From: Sagar
Sent: 27 March 2019 12:36
To: dev@taverna.incubator.apache.org
Cc: Ian Dunlop
Subject: Re: Taverna repository release plan

Agree with stain. We can release using Github.

I have a question regarding the release files, which files we need to include 
in it?

On Wed, Mar 27, 2019 at 2:02 AM Stian Soiland-Reyes  wrote:
On Tue, 26 Mar 2019 10:54:17 +0000, Ian Dunlop  wrote:
> I’m not quite sure what the release process for 1) ie Taverna Mobile
> would be. Bundle up the source in a tgz? I have the feeling I
> suggested something a while back. I’ll need to dig through some old
> emails.

I think that's as good as it will get, we can just tag a release
candidate and then download the tar.gz from GitHub, that should exclude
.git


> Are you suggestion that OSGi & engine are released together? Or in the same 
> release vote anyway.

Yes, separate releases, just concurrent VOTEs.


> If we can think of how to approach 1) then I can put it together. I’m
> happy to try 3) as well which is probably a much easier process since
> it is maven/java.Well, as easy as that process ever gets.

At least it's the same process every time :)

Thanks!


> Do we have a date in mind for all this or just ASAP.

ASAP -so we can graduate! :)



-- 

Warmest regards
Sagar
Software Developer
Lattice Innovations Pvt. Ltd.

RE: Taverna git repos moved to GitBox/GitHub

[Ian Dunlop]

Hello,

Woohoo. It’s sorted. All those little computer agents talking to each other. 
It’s so 21st century.

Cheers,

Ian

Sent from Mail for Windows 10

From: Ian Dunlop
Sent: 27 March 2019 14:59
To: dev@taverna.incubator.apache.org
Subject: RE: Taverna git repos moved to GitBox/GitHub

Hello,

So I went GitHub.com/apache and found that there was an old invite (sure I 
clicked that years ago but anyway). However I get a 404 on 
https://github.com/orgs/apache/teams/taverna-committers/members. Do I just have 
to wait for apache/gitbox/GitHub to talk to each other or is there something 
else I need to click.

Cheers,

Ian

Sent from Mail for Windows 10

From: Ian Dunlop
Sent: 27 March 2019 14:42
To: dev@taverna.incubator.apache.org
Subject: RE: Taverna git repos moved to GitBox/GitHub

Hello,

Just realised that I wasn’t a member of the ASF GitHub org. I tried setting up 
via gitbox but I get stuck at the “MFA Status” part where it tells me to add 
GitHub id to my id.apache.org page and wait for an email. I thought I did that 
years ago. Is this something that we have to do again?

Cheers,

Ian


Sent from Mail for Windows 10

From: Ian Dunlop
Sent: 18 January 2019 11:53
To: dev@taverna.incubator.apache.org
Subject: RE: Taverna git repos moved to GitBox/GitHub

Hello,

Sounds a good option to me Stian . I tend to use ssh for all my GitHub repos.

Cheers,

Ian

Sent from Mail for Windows 10

From: Stian Soiland-Reyes
Sent: 17 January 2019 23:27
To: dev@taverna.incubator.apache.org
Subject: Re: Taverna git repos moved to GitBox/GitHub

On Mon, 14 Jan 2019 11:06:00 +, Stian Soiland-Reyes  
wrote:
> Which git server should be the default  ?
> This is used by "mvn release:prepare" in the release procedure.
> 
> 
> [ ] gitbox.apache.org https
> [ ] GitHub https
> [x] GitHub ssh

Not hearing much (I guess it's not a thing to have strong opinions on!)
I went for the above option and updated the remaining repositories; 
editing straight in GitHub!

Also updated build jobs in https://builds.apache.org/view/taverna/
to check from gitbox, so apologies for all the automated emails
that then came all at once!

I think only thing remaining now is to see when we get a pull request if
the email notifications work as before.

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

RE: Taverna git repos moved to GitBox/GitHub

[Ian Dunlop]

Hello,

So I went GitHub.com/apache and found that there was an old invite (sure I 
clicked that years ago but anyway). However I get a 404 on 
https://github.com/orgs/apache/teams/taverna-committers/members. Do I just have 
to wait for apache/gitbox/GitHub to talk to each other or is there something 
else I need to click.

Cheers,

Ian

Sent from Mail for Windows 10

From: Ian Dunlop
Sent: 27 March 2019 14:42
To: dev@taverna.incubator.apache.org
Subject: RE: Taverna git repos moved to GitBox/GitHub

Hello,

Just realised that I wasn’t a member of the ASF GitHub org. I tried setting up 
via gitbox but I get stuck at the “MFA Status” part where it tells me to add 
GitHub id to my id.apache.org page and wait for an email. I thought I did that 
years ago. Is this something that we have to do again?

Cheers,

Ian


Sent from Mail for Windows 10

From: Ian Dunlop
Sent: 18 January 2019 11:53
To: dev@taverna.incubator.apache.org
Subject: RE: Taverna git repos moved to GitBox/GitHub

Hello,

Sounds a good option to me Stian . I tend to use ssh for all my GitHub repos.

Cheers,

Ian

Sent from Mail for Windows 10

From: Stian Soiland-Reyes
Sent: 17 January 2019 23:27
To: dev@taverna.incubator.apache.org
Subject: Re: Taverna git repos moved to GitBox/GitHub

On Mon, 14 Jan 2019 11:06:00 +, Stian Soiland-Reyes  
wrote:
> Which git server should be the default  ?
> This is used by "mvn release:prepare" in the release procedure.
> 
> 
> [ ] gitbox.apache.org https
> [ ] GitHub https
> [x] GitHub ssh

Not hearing much (I guess it's not a thing to have strong opinions on!)
I went for the above option and updated the remaining repositories; 
editing straight in GitHub!

Also updated build jobs in https://builds.apache.org/view/taverna/
to check from gitbox, so apologies for all the automated emails
that then came all at once!

I think only thing remaining now is to see when we get a pull request if
the email notifications work as before.

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

RE: Taverna git repos moved to GitBox/GitHub

[Ian Dunlop]

Hello,

Just realised that I wasn’t a member of the ASF GitHub org. I tried setting up 
via gitbox but I get stuck at the “MFA Status” part where it tells me to add 
GitHub id to my id.apache.org page and wait for an email. I thought I did that 
years ago. Is this something that we have to do again?

Cheers,

Ian


Sent from Mail for Windows 10

From: Ian Dunlop
Sent: 18 January 2019 11:53
To: dev@taverna.incubator.apache.org
Subject: RE: Taverna git repos moved to GitBox/GitHub

Hello,

Sounds a good option to me Stian . I tend to use ssh for all my GitHub repos.

Cheers,

Ian

Sent from Mail for Windows 10

From: Stian Soiland-Reyes
Sent: 17 January 2019 23:27
To: dev@taverna.incubator.apache.org
Subject: Re: Taverna git repos moved to GitBox/GitHub

On Mon, 14 Jan 2019 11:06:00 +, Stian Soiland-Reyes  
wrote:
> Which git server should be the default  ?
> This is used by "mvn release:prepare" in the release procedure.
> 
> 
> [ ] gitbox.apache.org https
> [ ] GitHub https
> [x] GitHub ssh

Not hearing much (I guess it's not a thing to have strong opinions on!)
I went for the above option and updated the remaining repositories; 
editing straight in GitHub!

Also updated build jobs in https://builds.apache.org/view/taverna/
to check from gitbox, so apologies for all the automated emails
that then came all at once!

I think only thing remaining now is to see when we get a pull request if
the email notifications work as before.

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

RE: Taverna repository release plan

[Ian Dunlop]

Hello,

I’m not quite sure what the release process for 1) ie Taverna Mobile would be. 
Bundle up the source in a tgz? I have the feeling I suggested something a while 
back. I’ll need to dig through some old emails.
Are you suggestion that OSGi & engine are released together? Or in the same 
release vote anyway.
If we can think of how to approach 1) then I can put it together. I’m happy to 
try 3) as well which is probably a much easier process since it is 
maven/java.Well, as easy as that process ever gets.
Do we have a date in mind for all this or just ASAP.

Cheers,

Ian

Sent from Mail for Windows 10

From: Stian Soiland-Reyes
Sent: 25 March 2019 17:14
To: dev@taverna.incubator.apache.org
Subject: Taverna repository release plan

On Mon, 25 Mar 2019 17:03:44 +, Stian Soiland-Reyes  
wrote:
> Three most important unfinished issues to address before graduating:
> 
>   1. Re-engage PPMC members
>   2. Release IP-fixed repositories

Here are the repositories that need to be released and get through
incubator PMC before graduation now that we have fixed their IP issues:

https://github.com/apache/incubator-taverna-language
https://github.com/apache/incubator-taverna-osgi
https://github.com/apache/incubator-taverna-engine
https://github.com/apache/incubator-taverna-workbench
https://github.com/apache/incubator-taverna-workbench-common-activities/
https://github.com/apache/incubator-taverna-workbench-product


Presuambly IP-clean (initiated after incubation), but also nice to
release:

https://github.com/apache/incubator-taverna-mobile
https://github.com/apache/incubator-taverna-plugin-gis
https://github.com/apache/incubator-taverna-databundle-viewer
https://github.com/apache/incubator-taverna-maven-parent


I'm afraid that would be quite a bit of [VOTE]s, so better chunk them
together somewhat? Suggested order:

1) taverna-mobile (src only?)
2) taverna-maven-parent + taverna-language
3) taverna-osgi + taverna-engine
4) taverna-workbench*
5) taverna-plugin-gis, databundle-viewer (src only)


Any volunteers for Release Manager of any of those? I can do 2) and 4)

> ..
> How has the project developed since the last report?
> 
>   Previous IP/licensing issues now resolved.
>   Pending release of updated git repositories.

Added:

  Moved Git repositories to GitHub via GitBox


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

RE: Inquire about Taverna services

[Ian Dunlop]

Hello,

There is a REST service plugin for the workbench 
https://taverna.incubator.apache.org/documentation/plugins/#rest which can 
handle authentication.
I’m not sure where the docs are for it but you could try installing it and see 
how you get on.

Cheers,

Ian

Sent from Mail for Windows 10

From: Rabia Ahmad
Sent: 07 March 2019 09:42
To: Stian Soiland-Reyes; dev@taverna.incubator.apache.org; Stian Soiland-Reyes
Subject: Inquire about Taverna services

How can I use rest service to use an API in a taverna workflow which
requires authentication?
If not in rest service then which one we can use?

[jira] [Updated] (TAVERNA-1061) t2flow does not work with T3 server

[Ian Dunlop (JIRA)]

 [ 
https://issues.apache.org/jira/browse/TAVERNA-1061?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ian Dunlop updated TAVERNA-1061:

Attachment: tavmob_fail.txt

> t2flow does not work with T3 server
> ---
>
> Key: TAVERNA-1061
> URL: https://issues.apache.org/jira/browse/TAVERNA-1061
> Project: Apache Taverna
>  Issue Type: Bug
>  Components: Taverna Server
>Affects Versions: server 3.1.0
>    Reporter: Ian Dunlop
>Priority: Major
> Attachments: tavmob_fail.txt
>
>
> Sending a t2flow to a tomcat hosted T3 server results in a "failed to build 
> workflow run worker" and a report that the file is using the wrong namespace 
> when it does not appear to be.
> eg curl -k -X POST -d @Fetch_today_s_xkcd_comic-v1.t2flow --header 
> "Content-Type:application/vnd.taverna.t2flow+xml" 
> [http://taverna:taverna@192.168.0.5:8080/taverna-server/rest/runs]
> where the workflow file is [https://www.myexperiment.org/workflows/824.html]
> I have also tried with a t1 workflow using content-type "application/xml" 
> which also failed though I'm not sure whether the server is supposed to 
> support that or not.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (TAVERNA-1061) t2flow does not work with T3 server

[Ian Dunlop (JIRA)]

Ian Dunlop created TAVERNA-1061:
---

 Summary: t2flow does not work with T3 server
 Key: TAVERNA-1061
 URL: https://issues.apache.org/jira/browse/TAVERNA-1061
 Project: Apache Taverna
  Issue Type: Bug
  Components: Taverna Server
Affects Versions: server 3.1.0
Reporter: Ian Dunlop


Sending a t2flow to a tomcat hosted T3 server results in a "failed to build 
workflow run worker" and a report that the file is using the wrong namespace 
when it does not appear to be.

eg curl -k -X POST -d @Fetch_today_s_xkcd_comic-v1.t2flow --header 
"Content-Type:application/vnd.taverna.t2flow+xml" 
[http://taverna:taverna@192.168.0.5:8080/taverna-server/rest/runs]
where the workflow file is [https://www.myexperiment.org/workflows/824.html]
I have also tried with a t1 workflow using content-type "application/xml" which 
also failed though I'm not sure whether the server is supposed to support that 
or not.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

RE: Taverna git repos moved to GitBox/GitHub

[Ian Dunlop]

Hello,

Sounds a good option to me Stian . I tend to use ssh for all my GitHub repos.

Cheers,

Ian

Sent from Mail for Windows 10

From: Stian Soiland-Reyes
Sent: 17 January 2019 23:27
To: dev@taverna.incubator.apache.org
Subject: Re: Taverna git repos moved to GitBox/GitHub

On Mon, 14 Jan 2019 11:06:00 +, Stian Soiland-Reyes  
wrote:
> Which git server should be the default  ?
> This is used by "mvn release:prepare" in the release procedure.
> 
> 
> [ ] gitbox.apache.org https
> [ ] GitHub https
> [x] GitHub ssh

Not hearing much (I guess it's not a thing to have strong opinions on!)
I went for the above option and updated the remaining repositories; 
editing straight in GitHub!

Also updated build jobs in https://builds.apache.org/view/taverna/
to check from gitbox, so apologies for all the automated emails
that then came all at once!

I think only thing remaining now is to see when we get a pull request if
the email notifications work as before.

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

RE: FW: [NOTICE] Mandatory relocation of Apache gitrepositoriesongit-wip-us.apache.org

[Ian Dunlop]

Hello,

Looks we have an agreed consensus to move the repos. I’ll raise the INFRA issue 
and get it started.

Cheers,

Ian

Sent from Mail for Windows 10

From: Stuart Owen
Sent: 12 December 2018 15:15
To: dev@taverna.incubator.apache.org
Subject: Re: FW: [NOTICE] Mandatory relocation of Apache 
gitrepositoriesongit-wip-us.apache.org

+ 1 from me too, seems like a sensible move.

On 12/12/2018 15:03, Sagar wrote:
> +1, It will make things easier.
>
> On Wed, Dec 12, 2018 at 7:21 PM Ian Dunlop  wrote:
>
>> Hello,
>>
>> Thanks for that Andy. Lets go for +1s by 9 Jan 2019. I’ll give it mine.
>> Stian has already.
>>
>> +1
>>
>> Cheers,
>>
>> Ian
>>
>> Sent from Mail for Windows 10
>>
>> From: Andy Seaborne
>> Sent: 11 December 2018 15:18
>> To: dev@taverna.incubator.apache.org
>> Subject: Re: FW: [NOTICE] Mandatory relocation of Apache git
>> repositoriesongit-wip-us.apache.org
>>
>> On 10/12/2018 15:02, Ian Dunlop wrote:
>>> Hello,
>>>
>>> I guess this git move will affect Taverna. We need “Consensus in the
>> project (documented via the mailing list)” to go ahead. I don’t know what
>> constitutes consensus so I propose that we take silence as agreement. If
>> there are no objections to the repo moves documented below (with reasons)
>> before 9 Jan then we can raise the necessary INFRA tickets and get things
>> moved. Seems like it is going to happen anyway after Feb 7.
>>> Cheers,
>>>
>>> Ian
>> Here is an example:
>>
>> https://issues.apache.org/jira/projects/INFRA/issues/INFRA-17389
>>
>> and the comment asks for a link to the dev@ to show consensus.
>> Seems that some +1's to show the PMC has seen it is enough.
>> Tricky to link to the absence of something.
>>
>>  Andy
>>
>>
>>> Sent from Mail for Windows 10
>>>
>>> From: Daniel Gruno
>>> Sent: 07 December 2018 16:53
>>> To: us...@infra.apache.org
>>> Subject: [NOTICE] Mandatory relocation of Apache git repositories
>> ongit-wip-us.apache.org
>>> [IF YOUR PROJECT DOES NOT HAVE GIT REPOSITORIES ON GIT-WIP-US PLEASE
>>>DISREGARD THIS EMAIL; IT WAS MASS-MAILED TO ALL APACHE PROJECTS]
>>>
>>> Hello Apache projects,
>>>
>>> I am writing to you because you may have git repositories on the
>>> git-wip-us server, which is slated to be decommissioned in the coming
>>> months. All repositories will be moved to the new gitbox service which
>>> includes direct write access on github as well as the standard ASF
>>> commit access via gitbox.apache.org.
>>>
>>> ## Why this move? ##
>>> The move comes as a result of retiring the git-wip service, as the
>>> hardware it runs on is longing for retirement. In lieu of this, we
>>> have decided to consolidate the two services (git-wip and gitbox), to
>>> ease the management of our repository systems and future-proof the
>>> underlying hardware. The move is fully automated, and ideally, nothing
>>> will change in your workflow other than added features and access to
>>> GitHub.
>>>
>>> ## Timeframe for relocation ##
>>> Initially, we are asking that projects voluntarily request to move
>>> their repositories to gitbox, hence this email. The voluntary
>>> timeframe is between now and January 9th 2019, during which projects
>>> are free to either move over to gitbox or stay put on git-wip. After
>>> this phase, we will be requiring the remaining projects to move within
>>> one month, after which we will move the remaining projects over.
>>>
>>> To have your project moved in this initial phase, you will need:
>>>
>>> - Consensus in the project (documented via the mailing list)
>>> - File a JIRA ticket with INFRA to voluntarily move your project repos
>>> over to gitbox (as stated, this is highly automated and will take
>>> between a minute and an hour, depending on the size and number of
>>> your repositories)
>>>
>>> To sum up the preliminary timeline;
>>>
>>> - December 9th 2018 -> January 9th 2019: Voluntary (coordinated)
>>> relocation
>>> - January 9th -> February 6th: Mandated (coordinated) relocation
>>> - February 7th: All remaining repositories are mass migrated.
>>>
>>> This timeline may change to accommodate various scenarios.
>>>
>>> ## Using GitHub

RE: FW: [NOTICE] Mandatory relocation of Apache git repositoriesongit-wip-us.apache.org

[Ian Dunlop]

Hello,

Thanks for that Andy. Lets go for +1s by 9 Jan 2019. I’ll give it mine. Stian 
has already.

+1

Cheers,

Ian

Sent from Mail for Windows 10

From: Andy Seaborne
Sent: 11 December 2018 15:18
To: dev@taverna.incubator.apache.org
Subject: Re: FW: [NOTICE] Mandatory relocation of Apache git 
repositoriesongit-wip-us.apache.org

On 10/12/2018 15:02, Ian Dunlop wrote:
> Hello,
> 
> I guess this git move will affect Taverna. We need “Consensus in the project 
> (documented via the mailing list)” to go ahead. I don’t know what constitutes 
> consensus so I propose that we take silence as agreement. If there are no 
> objections to the repo moves documented below (with reasons) before 9 Jan 
> then we can raise the necessary INFRA tickets and get things moved. Seems 
> like it is going to happen anyway after Feb 7.
> 
> Cheers,
> 
> Ian

Here is an example:

https://issues.apache.org/jira/projects/INFRA/issues/INFRA-17389

and the comment asks for a link to the dev@ to show consensus.
Seems that some +1's to show the PMC has seen it is enough.
Tricky to link to the absence of something.

 Andy


> 
> Sent from Mail for Windows 10
> 
> From: Daniel Gruno
> Sent: 07 December 2018 16:53
> To: us...@infra.apache.org
> Subject: [NOTICE] Mandatory relocation of Apache git repositories 
> ongit-wip-us.apache.org
> 
> [IF YOUR PROJECT DOES NOT HAVE GIT REPOSITORIES ON GIT-WIP-US PLEASE
>DISREGARD THIS EMAIL; IT WAS MASS-MAILED TO ALL APACHE PROJECTS]
> 
> Hello Apache projects,
> 
> I am writing to you because you may have git repositories on the
> git-wip-us server, which is slated to be decommissioned in the coming
> months. All repositories will be moved to the new gitbox service which
> includes direct write access on github as well as the standard ASF
> commit access via gitbox.apache.org.
> 
> ## Why this move? ##
> The move comes as a result of retiring the git-wip service, as the
> hardware it runs on is longing for retirement. In lieu of this, we
> have decided to consolidate the two services (git-wip and gitbox), to
> ease the management of our repository systems and future-proof the
> underlying hardware. The move is fully automated, and ideally, nothing
> will change in your workflow other than added features and access to
> GitHub.
> 
> ## Timeframe for relocation ##
> Initially, we are asking that projects voluntarily request to move
> their repositories to gitbox, hence this email. The voluntary
> timeframe is between now and January 9th 2019, during which projects
> are free to either move over to gitbox or stay put on git-wip. After
> this phase, we will be requiring the remaining projects to move within
> one month, after which we will move the remaining projects over.
> 
> To have your project moved in this initial phase, you will need:
> 
> - Consensus in the project (documented via the mailing list)
> - File a JIRA ticket with INFRA to voluntarily move your project repos
> over to gitbox (as stated, this is highly automated and will take
> between a minute and an hour, depending on the size and number of
> your repositories)
> 
> To sum up the preliminary timeline;
> 
> - December 9th 2018 -> January 9th 2019: Voluntary (coordinated)
> relocation
> - January 9th -> February 6th: Mandated (coordinated) relocation
> - February 7th: All remaining repositories are mass migrated.
> 
> This timeline may change to accommodate various scenarios.
> 
> ## Using GitHub with ASF repositories ##
> When your project has moved, you are free to use either the ASF
> repository system (gitbox.apache.org) OR GitHub for your development
> and code pushes. To be able to use GitHub, please follow the primer
> at: https://reference.apache.org/committer/github
> 
> 
> We appreciate your understanding of this issue, and hope that your
> project can coordinate voluntarily moving your repositories in a
> timely manner.
> 
> All settings, such as commit mail targets, issue linking, PR
> notification schemes etc will automatically be migrated to gitbox as
> well.
> 
> With regards, Daniel on behalf of ASF Infra.
> 
> PS:For inquiries, please reply to us...@infra.apache.org, not your
> project's dev list :-).
> 
> 
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> For additional commands, e-mail: dev-h...@community.apache.org
> 
> 
> 

FW: [NOTICE] Mandatory relocation of Apache git repositories ongit-wip-us.apache.org

[Ian Dunlop]

Hello,

I guess this git move will affect Taverna. We need “Consensus in the project 
(documented via the mailing list)” to go ahead. I don’t know what constitutes 
consensus so I propose that we take silence as agreement. If there are no 
objections to the repo moves documented below (with reasons) before 9 Jan then 
we can raise the necessary INFRA tickets and get things moved. Seems like it is 
going to happen anyway after Feb 7.

Cheers,

Ian

Sent from Mail for Windows 10

From: Daniel Gruno
Sent: 07 December 2018 16:53
To: us...@infra.apache.org
Subject: [NOTICE] Mandatory relocation of Apache git repositories 
ongit-wip-us.apache.org

[IF YOUR PROJECT DOES NOT HAVE GIT REPOSITORIES ON GIT-WIP-US PLEASE
  DISREGARD THIS EMAIL; IT WAS MASS-MAILED TO ALL APACHE PROJECTS]

Hello Apache projects,

I am writing to you because you may have git repositories on the
git-wip-us server, which is slated to be decommissioned in the coming
months. All repositories will be moved to the new gitbox service which
includes direct write access on github as well as the standard ASF
commit access via gitbox.apache.org.

## Why this move? ##
The move comes as a result of retiring the git-wip service, as the
hardware it runs on is longing for retirement. In lieu of this, we
have decided to consolidate the two services (git-wip and gitbox), to
ease the management of our repository systems and future-proof the
underlying hardware. The move is fully automated, and ideally, nothing
will change in your workflow other than added features and access to
GitHub.

## Timeframe for relocation ##
Initially, we are asking that projects voluntarily request to move
their repositories to gitbox, hence this email. The voluntary
timeframe is between now and January 9th 2019, during which projects
are free to either move over to gitbox or stay put on git-wip. After
this phase, we will be requiring the remaining projects to move within
one month, after which we will move the remaining projects over.

To have your project moved in this initial phase, you will need:

- Consensus in the project (documented via the mailing list)
- File a JIRA ticket with INFRA to voluntarily move your project repos
   over to gitbox (as stated, this is highly automated and will take
   between a minute and an hour, depending on the size and number of
   your repositories)

To sum up the preliminary timeline;

- December 9th 2018 -> January 9th 2019: Voluntary (coordinated)
   relocation
- January 9th -> February 6th: Mandated (coordinated) relocation
- February 7th: All remaining repositories are mass migrated.

This timeline may change to accommodate various scenarios.

## Using GitHub with ASF repositories ##
When your project has moved, you are free to use either the ASF
repository system (gitbox.apache.org) OR GitHub for your development
and code pushes. To be able to use GitHub, please follow the primer
at: https://reference.apache.org/committer/github


We appreciate your understanding of this issue, and hope that your
project can coordinate voluntarily moving your repositories in a
timely manner.

All settings, such as commit mail targets, issue linking, PR
notification schemes etc will automatically be migrated to gitbox as
well.

With regards, Daniel on behalf of ASF Infra.

PS:For inquiries, please reply to us...@infra.apache.org, not your 
project's dev list :-).



-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org

Release Taverna Language or graduate?

[Ian Dunlop]

Hello,

Now that we merged in incubator-taverna-language#43 to fix some of the licence 
issues does that mean we can go for a release.
Or should we go for one final graduation push? I updated 
https://cwiki.apache.org/confluence/display/TAVERNADEV/License+review to remove 
the INFRA-16698 repos. 
We also started 
https://cwiki.apache.org/confluence/display/TAVERNADEV/2016-03+Taverna+Graduation+Maturity+Assessment
 but this seemed like the project being nice rather than essential.
Anyway, what licence checks are still needed? What NOTICE, LICENCE etc still 
need to be added to repos?

Cheers,

Ian

Sent from Mail for Windows 10

[jira] [Commented] (TAVERNA-118) JSON PUTs do not work to REST API

[Ian Dunlop (JIRA)]

[ 
https://issues.apache.org/jira/browse/TAVERNA-118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16688104#comment-16688104
 ] 

Ian Dunlop commented on TAVERNA-118:


This might be the same issue I noticed when trying to use the server via the 
taverna-player-portal. It seems to be the same stack trace. I also found it 
when using the t2-server-gem or via curl directly to a T3 server instance. I 
don't quite understand what is meant by " the problem is with clients just 
sending the wrong requests". What type of request should the client be sending? 
Is it the content type that is wrong? The clients were sending 
"application/vnd.taverna.t2flow+xml". Is this wrong?

> JSON PUTs do not work to REST API
> -
>
> Key: TAVERNA-118
> URL: https://issues.apache.org/jira/browse/TAVERNA-118
> Project: Apache Taverna
>  Issue Type: Bug
>  Components: Taverna Server
>Reporter: Stian Soiland-Reyes
>Priority: Critical
>
> The PUTting of JSON to the REST API gives a misinterpretation of the 
> namespaces
> {code}
> JAXBException occurred : unexpected element 
> (uri:"http://ns.taverna.org.uk/2010/xml/server/soap/;, local:"runInput"). 
> Expected elements are 
> <{http://ns.taverna.org.uk/2010/xml/server/rest/}runInput>. unexpected 
> element (uri:"http://ns.taverna.org.uk/2010/xml/server/soap/;, 
> local:"runInput"). Expected elements are 
> <{http://ns.taverna.org.uk/2010/xml/server/rest/}runInput>. 
> {code}
> The JSON support should be corrected but in the meantime, the documentation 
> should be updated to indicate it does not work



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

TavMob open pull requests + portal/tavserv3 issue

[Ian Dunlop]

Hello,

I’ve been looking at the open pull requests in TavMob and attempting to close 
them. Some I need some guidance on since I’m not sure if they have been merged 
already.
One of them (https://github.com/apache/incubator-taverna-mobile/pull/45) raises 
some issues about how TavMob would fit into the Taverna 3 ecosystem since it 
seems to highlight some issues with either the tavern player/portal/server ruby 
code or with the Tav3 server itself. There are lots of discussions under that 
pull request but here are the slightly paraphrased highlights (I’m doing this 
because I read an apache thread somewhere recently about how GitHub discussions 
don’t always get noticed by the general community):

Ian: “I tried running a couple of t2flow workflows and got a similar error with 
each from taverna-server-3. @stain I imagine this must be a known bug:
Hello-abcd:
Caused by: javax.xml.bind.UnmarshalException: unexpected element 
(uri:"http://ns.taverna.org.uk/2010/xml/server/;, local:"workflow"). Expected 
elements are 
<{http://taverna.sf.net/2008/xml/t2flow}abstractConfigBean>,<{}net.sf.taverna.t2.activities.externaltool.ExternalToolActivityConfigurationBean>,<{}net.sf.taverna.t2.activities.interaction.InteractionActivityConfigurationBean>,<{}net.sf.taverna.t2.activities.rest.RESTActivityConfigurationBean>,<{}net.sf.taverna.t2.activities.usecase.UseCaseActivityConfigurationBean>,<{}net.sf.taverna.t2.activities.xpath.XPathActivityConfigurationBean>,<{}net.sf.taverna.t2.component.ComponentActivityConfigurationBean>,<{http://taverna.sf.net/2008/xml/t2flow}workflow>
Fetch xkcd:
Caused by: javax.xml.bind.UnmarshalException: unexpected element 
(uri:"http://ns.taverna.org.uk/2010/xml/server/;, local:"workflow"). Expected 
elements are 
<{http://taverna.sf.net/2008/xml/t2flow}abstractConfigBean>,<{}net.sf.taverna.t2.activities.externaltool.ExternalToolActivityConfigurationBean>,<{}net.sf.taverna.t2.activities.interaction.InteractionActivityConfigurationBean>,<{}net.sf.taverna.t2.activities.rest.RESTActivityConfigurationBean>,<{}net.sf.taverna.t2.activities.usecase.UseCaseActivityConfigurationBean>,<{}net.sf.taverna.t2.activities.xpath.XPathActivityConfigurationBean>,<{}net.sf.taverna.t2.component.ComponentActivityConfigurationBean>,<{http://taverna.sf.net/2008/xml/t2flow}workflow>”
Stian: “Exactly how did you submit how? It seems to do with wrapping XML 
element or not.. Donal, did something change in the XML requirements for 
workflow upload in T3? It might be easier to try to do it as a 
application/vnd.taverna.t2flow+xml upload (Sending binary file as-is) than 
wrapp it in a  as application/xml.”

Ian: “I sent it via taverna-player-portal. I was testing whether they could 
both be started via docker and play nicely with each other. I haven't tried 
sending from mobile to portal to server.”
“I think the problem might be in 
https://github.com/myGrid/t2-server-gem/blob/master/lib/t2-server/server.rb#L261
 but if you look at the call sequence it seems to be sending as Post with type 
"application/vnd.taverna.t2flow+xml".
I actually managed to recreate the issue by using the t2-server-gem directly in 
irb. T2Server::Run.create() seems to be where the issue occurs. Doesn't mean it 
is to blame though. It could be the server that is wrong. Would need to run 
directly against TavServ3 using curl or similar to find out.”

So it looks like there is an issue with running T2 workflows via the portal in 
T3 server but it is not 100% clear where the fault lies. Sounds like it needs 
to be raised in Jira if it hasn’t been already.

Cheers,

Ian

Sent from Mail for Windows 10

RE: Advanced Report Reminder for December 2018

[Ian Dunlop]

Hello,

I closed tavmob#97 without merging since it was clearly just some spam. The 
other open ones I am not so sure about without either merging and testing or 
getting Sagar or someone else to comment.
Eg Tavmob#68 looked like it was ready to merge but Sagar wanted the committer 
to use RxJava/Retrofit patterns in it. I probably wouldn’t mind so much. #93 
looks like there is a library missing so it failed to build in travis.

I had a look at the TavLanguage thread to remind myself of the issue which 
contained this from you Stian (I think)

“Although our use of Creative Commons should be allowed by Legal's
resolved FAQ, we recognize that IPMC feelings are otherwise, so we'll
have to recode to avoid including these schema files.” 

It’s not clear to me what the approach should be. Are you saying that legal 
think it is ok but the IPMC don’t? If so then shouldn’t legal and IPMC discuss 
this issue and get some clarity – did this happen?

Then you mention 
“So do you think we need to look again at that idea of putting them in Taverna 
Extras on GitHub and then pull them down at build-time as Maven
dependencies?“
Is this now the only option and if so what does it involve. Let’s just get it 
done. (I’ve got the feeling I starting looking into this but got distracted by 
reality).

Cheers,

Ian

Sent from Mail for Windows 10

From: Stian Soiland-Reyes
Sent: 09 November 2018 13:29
To: dev@taverna.incubator.apache.org
Cc: Majdi Haouech
Subject: Re: Advanced Report Reminder for December 2018

On Thu, 8 Nov 2018 12:00:22 +, Andy Seaborne  wrote:
> Taverna is due to report in December.
> December 2016 said "Preparing to graduate."
> 
> There was a burst of activity in the first half of this year after a 
> quiet 2017.
> 
> http://mail-archives.apache.org/mod_mbox/taverna-dev/
> 

Thanks for the reminder, Andy - it just popped up on my mind as well.



OK, Taverna PMC folks, it's crunch time.  Could anyone help draft the
report? The previous one is here:

https://lists.apache.org/thread.html/a0490dbc2454c85ae385a5dc38835541f7b09859b2ca47c8bd54759d@%3Cdev.taverna.apache.org%3E



Sagar/Ian: 6 open pull requests for Taverna Mobile:
https://github.com/apache/incubator-taverna-mobile/pulls
Shall we close or chase these?
Can we roll a Mobile release now after GSOC contributions?


https://taverna.incubator.apache.org/download/code/ shows a few other
open pull request, I think most of those are abandoned, but then we need
to close them. Do a dummy commit (e.g. whitespace change in README.md)
on the corresponding git repository with "This closes #1337" to close
that issue.


Majdi has just contacted me saying he wants to do more work on the CWL
support in Taverna Language. Majdi, could you fill in on your plan?


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

I think this is mostly done, but there might be the odd XSD file here
and there, or something that is Creative Commons-licensed, that is what
blocked the latest Taverna Language release vote:

https://lists.apache.org/thread.html/ce33070595757666241d8b60e0416c95ae11fa1e579a6866e650de40@%3Cdev.taverna.apache.org%3E

Any effort welcome.

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

RE: Possible TAVERNA update in the NAR Web Server Issue

[Ian Dunlop]

Hello,

Here is a link to the publication they are talking about: 
https://doi.org/10.1093/nar/gkt328
It’s not a hugely detailed document. Just lists the different applications that 
make up the taverna universe. I don’t think it mentions Tav-Mobile so that 
could be added. Could also add the apache Tav-3 updates.

Cheers,

Ian

Sent from Mail for Windows 10

From: Andy Seaborne
Sent: 08 October 2018 09:39
To: d...@taverna.apache.org
Subject: Possible TAVERNA update in the NAR Web Server Issue

Forwarded with permission:


 Forwarded Message 
Subject:Possible TAVERNA update in the NAR Web Server Issue
Date:   Sat, 6 Oct 2018 18:12:24 -0400
From:   Gary Benson 
To: andy.seabo...@topquadrant.com, narwbsrv , Dominik 
Seelow 



Dear Dr. Seaborne,

An article about the TAVERNA software was published in the Web Server 
issue of Nucleic Acids Research in 2013.  [...] Because the software 
receives heavy usage,  We're writing to ask if you'd be interested in 
submitting an update for the 2019 Web Server issue published in July.  
The deadline for manuscript submission is January 31, 2019.

If you're interested, your manuscript would undergo standard review and 
standard publication charges would apply.  Because this would be an 
update, the manuscript would best include a general introduction to your 
online tools, and a description of major changes since the last 
publication.  If required, we can give you more space than the standard 
4-5 pages, however, be aware that the publisher charges an extra £100 
per page over 10 pages.

For planning purposes, we would appreciate a response one way or the 
other within the next week or so.

Sincerely,

Gary Benson and Dominik Seelow
Executive Editors
Nucleic Acids Research Web Server Issue
Boston, MA, USA and Berlin, Germany

RE: Taverna logo as SVG?

[Ian Dunlop]

Hello,

That logo looks good enough to me. Makes me wonder why one of the cogs is 
disappearing off the right hand edge. I never noticed that before but looks 
like it has always been the case.

Cheers,

Ian

Sent from Mail for Windows 10

From: Stian Soiland-Reyes
Sent: 05 September 2018 12:07
To: dev@taverna.incubator.apache.org
Subject: Taverna logo as SVG?

Hi,

The ASF Community folks were asking for SVG or high-res versions of
product logos, and I realized Taverna didn't really have one, as we only
have a 256x256 PNG:

https://taverna.incubator.apache.org/img/taverna-logo-256x256.png

For years I have been looking for the original vector version of our
logo, but this is the best I've found so far.  Anyone else have
something in their email archives..?


A bitmap format like PNG is bad because it can't scale well with web
pages, particularly relevant for mobile/tablet phones or if scaled up on
a poster printout. A vector format like SVG should be preferable and is
now supported in all major browsers.


Now I had a quick trace of the png in Inkscape and managed to come up with:

http://taverna.staging.apache.org/img/apache-taverna-logo.svg


Comments?


Vectorizing by tracing the bitmap is a bit of cheating, so you will
notice this file is actually larger in file size (216 kB) than the PNG
(72 kB). This is basically the coastline measuring paradox. If I click
"Simplify" in Inkscape I can reduce the details to a managable 32 kB,
but then the cogs turn into wobbly circles!


Here you can see what the svg might look like used in larger size:

http://taverna.staging.apache.org/


Try zooming in on a high-res tablet or screen to check the details. 

For comparison if we use the old PNG:

http://taverna.staging.apache.org/tmp/logo-png.html

or even a PNG (56 kB) exported from the new SVG

http://taverna.staging.apache.org/tmp/logo-png2.html

.. then we see a clear difference in the SVG. For the logo in the top
corner there is practically no visual difference as it's so tiny.


Comparing the SVG with the original PNG will show information lost in
the trace, e.g. the inner edges of the cog.

An alternative might be to try to recreate some cogs in Inkscape or
Adobe Illustrator, this should bring back the details and probably
shrink the SVG size. But that would take more time... any volunteers?


I've updated the banner which should then be better for print:
http://taverna.staging.apache.org/img/apache-taverna-banner.svg

I've not played with removing the gradient to a single-color, that can
reduce file size, but makes it harder to pick the right orange..


What do you think? Just keep the SVG as a side-resource for anyone
interested?

-- 
Stian Soiland-Reyes
The University of Manchester
https://www.esciencelab.org.uk/
https://orcid.org/-0001-9842-9718

RE: [VOTE] Retire legacy taverna repos to taverna-extras

[Ian Dunlop]

+1

I shall mourn their passing but it’s the natural cycle of life.

Cheers,

Ian

Sent from Mail for Windows 10

From: Sagar
Sent: 11 June 2018 08:36
To: dev@taverna.incubator.apache.org
Subject: Re: [VOTE] Retire legacy taverna repos to taverna-extras

+1

On Mon 11 Jun, 2018, 7:16 AM Gale Naylor, 
wrote:

> +1
>
> On Wed, Jun 6, 2018 at 4:04 PM Stian Soiland-Reyes 
> wrote:
>
> >
> > We don't seem to get much progress in these legacy git repositories:
> >
> > https://github.com/apache/incubator-taverna-plugin-component
> > https://github.com/apache/incubator-taverna-plugin-bioinformatics
> >
> > Both have been failing in Jenkins for a long time.
> >
> >
> > The Component plugin I think still needs some more work for Taverna 3. I
> > just fixed now some typos like broken  > not enough to get it to compile.
> >
> >
> > The Bioinformatics plugin has activities for Biomart, Biomoby,
> > NCBI and Soaplab web services. I don't believe any of these are
> > particularly relevant anymore. The plugin also have some dependencies
> > with unclear or incompatible open source license (martj.jar)
> >
> >
> >
> > I propose we retire these repos and ask to transfer their ownership to:
> > https://github.com/taverna-extras/
> >
> > Their license and file headers would remain.
> >
> > As this would mean ASF giving up on holding their code base I think we
> > should decide this formally.
> >
> > Please Vote:
> >
> > [ ] +1: Yes, retire them to taverna-extras
> > [ ]  0: Either way
> > [ ] -1: No, don't retire
> >
> > This vote will be open for at least 72 hours. Anyone can vote, not just
> > Taverna PPMC members.
> >
> > --
> > Stian Soiland-Reyes
> > https://orcid.org/-0001-9842-9718
> >
> >
>

RE: [DISCUSS] Release Apache Taverna Language 0.16.0-incubating RC1

[Ian Dunlop]

Hello,

You wait ages for a new JDK and then 3 come along at once.
I think 9 is what Oracle want people to use. Then maybe it will be 11. 10 seems 
to be a passing fad.

I posted this on the gitter chat but might be useful on the website as well:

If anyone is interested in testing with JDK9 (or greater) you can use the 
openjdk docker images. Start by creating a Dockerfile with

FROM openjdk:9
CMD ["/bin/bash"]

Then docker build -t java-openjdk .
Then docker run --name openjdk9 -ti java-openjdk

You can substitute openjdk:9 for 10 or 11 as well I believe.

Cheers,

Ian

Sent from Mail for Windows 10

From: Stian Soiland-Reyes
Sent: 14 May 2018 15:40
To: dev@taverna.incubator.apache.org
Subject: [DISCUSS] Release Apache Taverna Language 0.16.0-incubating RC1

This is the accompanying discussion thread for the release candidate for
Apache Taverna Language 0.16.0-incubating RC1

For the VOTE thread and download details, see
https://lists.apache.org/thread.html/29405e13efcd3282e978982c2c4c02b1d1bf683460ce618c7248617a@%3Cdev.taverna.apache.org%3E



To kick this off - I just realised Java 9 is already out of support
(!) - see http://www.oracle.com/technetwork/java/eol-135779.html

So when I tried with JDK 10.0.1 on Windows I got an error in the new
cxf-xjc-plugin plugin config:

[INFO] --- cxf-xjc-plugin:3.2.1:xsdtojava (default) @ taverna-robundle ---
WARNING: An illegal reflective access operation has occurred
WARNING: Illegal reflective access by
com.sun.xml.bind.v2.runtime.reflect.opt.Injector
(file:/C:/Users/stain/.m2/repository/com/sun/xml/bind/jaxb-impl/2.2.11/jaxb-impl-2.2.11.jar)
to method java.lang.ClassLoader.defineClass(java.lang.String,byte[],int,int)
WARNING: Please consider reporting this to the maintainers of
com.sun.xml.bind.v2.runtime.reflect.opt.Injector
WARNING: Use --illegal-access=warn to enable warnings of further
illegal reflective access operations
WARNING: All illegal access operations will be denied in a future release
[ERROR] 
C:\1\apache-taverna-language-0.16.0-incubating\taverna-robundle\src\main\xsd\container.xsd
[94:28]: Property "Any" is already defined. Use jaxb:property> to
resolve this conflict.
com.sun.istack.SAXParseException2: Property "Any" is already defined.
Use jaxb:property> to resolve this conflict.
at com.sun.tools.xjc.ErrorReceiver.error (ErrorReceiver.java:86)
at com.sun.tools.xjc.reader.ModelChecker.checkPropertyCollision
(ModelChecker.java:112)
at com.sun.tools.xjc.reader.ModelChecker.check (ModelChecker.java:98)
at com.sun.tools.xjc.reader.ModelChecker.check (ModelChecker.java:71)
at com.sun.tools.xjc.reader.xmlschema.BGMBuilder._build
(BGMBuilder.java:183)
at com.sun.tools.xjc.reader.xmlschema.BGMBuilder.build (BGMBuilder.java:119)


Is this a blocker? I don't understand quite Oracle's schedule.. it
seems JDK8 is still LTS until January 2019 while even JDK10 will
expire earlier in Sep 2018. (JDK11 being next LTS) -- so I am not sure
what would be the point to chase JDK10 either..


.. btw if you get "gpg key expired" then remember to update your KEYS
(gpg --import) as I updated my release key.



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

RE: [VOTE] Release Apache Taverna Language 0.16.0-incubating RC1

[Ian Dunlop]

Hello,

+1 

Built ok using mvn clean install in both JDK8 & 9 (openjdk)
Sha1, 256 & 512 sums verified.
Zip signature confirmed (although it did say “gpg: Note: This key has 
expired!”).

Cheers,

Ian

Sent from Mail for Windows 10

From: Stian Soiland-Reyes
Sent: 12 May 2018 15:34
To: dev@taverna.incubator.apache.org
Subject: [VOTE] Release Apache Taverna Language 0.16.0-incubating RC1

I am pleased to be calling this vote for the source release of

  Apache Taverna Language 0.16.0-incubating

To discuss this release candidate, use the corresponding [DISCUSS] thread. 



Apache Taverna Language is a set of APIs for workflow definitions (SCUFL2),
Research Object Bundles and workflow inputs/outputs/run (DataBundle), as
consumed and produced by the Apache Taverna workflow system.

The API includes support for the legacy formats from Taverna 2 and Taverna 1,
and can be also used independently of Apache Taverna 3.  The command line tool
tavlang can be used for conversion and inspection of research objects and
workflow bundles.




The release candidate to be voted over is available at:

https://dist.apache.org/repos/dist/dev/incubator/taverna/source/taverna-language-0.16.0-incubating-RC1/


Checksums:

$ sha1sum *zip
1f6050994b4bd2661f343119cdcb18b83dc362cf  
apache-taverna-language-0.16.0-incubating-source-release.zip

$ sha256sum *zip
bcdba80fbea54b1532cb81b6846e5711f1efe98ad289ecd4a2c6dd2833767115  
apache-taverna-language-0.16.0-incubating-source-release.zip

$ sha512sum *zip
008672c7f7cb1e6e461a2d5113aa111208970cfe9e0b3507fb3a34bc95957db094f0d8e8829beca9496cfa6a6d023943409335839bacd0bdedc82db87d14b9aa
  apache-taverna-language-0.16.0-incubating-source-release.zip
s




Build the release candidate using:

mvn clean install

We are particularly interested in testing of the RC on JDK 9 or newer.



The release candidates correspond to the following git commit:

https://git-wip-us.apache.org/repos/asf?p=incubator-taverna-language.git;a=commit;h=c48ef9d339d7d68791691617ef2ddc56d195131e


The release candidate is signed with an (updated) GPG key:
https://www.apache.org/dist/incubator/taverna/KEYS
Verify using: 

gpg --verify *.asc


A staged Maven repository is available for review at:
https://repository.apache.org/content/repositories/orgapachetaverna-1019


The changelog for this release is available from JIRA:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12334881=12318322



Please vote on releasing these packages as:

  Apache Taverna Language 0.16.0-incubating


The vote is open for at least 72 hours and passes if a majority of at least
three +1 Apache Taverna PPMC votes are cast.

[ ] +1 Release this package
[ ]  0 I don't feel strongly about it, but don't object
[ ] -1 Do not release this package because...


Anyone can participate in testing and voting, not just committers,
please feel free to try out the release candidate and provide your
votes!

How to review a release? https://s.apache.org/review-release


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

RE: Swagger & Taverna

[Ian Dunlop]

Hello,

That sounds like a really interesting idea. I wonder if it could be a 
generalised approach as well for annotating swagger docs so that 
taverna/CWL/knime/PP etc could use them. Maybe that exists already?

Cheers,

Ian

Sent from Mail for Windows 10

From: Stian Soiland-Reyes
Sent: 18 February 2018 17:50
To: dev@taverna.incubator.apache.org
Subject: Re: Swagger & Taverna

I think consuming Swagger APIs for building pre-configured REST
service activities in Taverna is indeed a good idea - we've already
got similar for WSDL/SOAP - should we propose this as a potential GSOC
project? Would need a mentor..

On 17 February 2018 at 00:17, Mark Fortner  wrote:
> I'm curious if there's a way to incorporate Swagger REST service metadata
> into a workflow? For example, you could add ontology URIs to parts of the
> Swagger metadata, which Taverna could then consume and expose. This would
> make it easier to orchestrate REST service-based workflows.
>
> Regards,
>
> Mark Fortner



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

RE: The app URI scheme -> IANA

[Ian Dunlop]

Hello,

Is “fluctual” actually a word?
Anyway, what’s the headline news here? Jena can’t parse app:// URLs because 
they aren’t an approved standard but we need them for the RO bundle. Couldn’t 
we change the Jena code to play nicely and parse app://? I appreciate getting 
standards correct but how long will it take?

Cheers,

Ian

Sent from Mail for Windows 10

From: Stian Soiland-Reyes
Sent: 17 January 2018 19:35
To: dev@taverna.incubator.apache.org
Subject: The app URI scheme -> IANA

In TAVERNA-1027 we came across the app URI scheme
not being IANA registered, and since been abandoned
by W3C (as the working group collapsed).

Well I'm trying to fix that - at least with a provisional registration
and an Internet-Draft:

https://tools.ietf.org/html/draft-soilandreyes-app-00

Comments welcome - preferably as issues/pull requests
in https://github.com/stain/I-D


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

RE: Taverna Server documentation

[Ian Dunlop]

Hello,

Styling seems to have gone a bit crazy on the install guide “Configuration 
Property List” part, lot’s of bold headers. 
(http://taverna.staging.apache.org/documentation/server/3.1/install)  
In http://taverna.staging.apache.org/documentation/server/3.1/usage some of the 
code blocks haven’t rendered correctly, you can still see the ```xml markup in 
some places.
Also why is the workflow state not rendered as a Taverna workflow (BTW that’s a 
joke )

Overall, good job.
@Gale Happy New Year. Great to hear from you. Hope things are going well for 
you.

Cheers,

Ian

Sent from Mail for Windows 10

From: Stian Soiland-Reyes
Sent: 18 January 2018 12:41
To: dev@taverna.incubator.apache.org
Subject: Re: Taverna Server documentation

I think we can say the distinction is if the documentation is
code-related (stays in git aka GitHub) or user-related (stays on our
website).  With Taverna Server it's a bit tighter together.. all the
API examples could change from one release to another and easily be
outdated.

Agree on that the headers and code sections looks better in GtHub rendering.

It could be that we can make some tweaks to our website CSS to make it
more similar?
I think we are using Bootstrap and a couple of custom overrides in
https://github.com/apache/incubator-taverna-site/tree/trunk/content/css

On 5 January 2018 at 15:50, Gale Naylor  wrote:
> Happy New Year, all!
>
> I was only able to take a quick look on my phone. But the docs look pretty
> good!
>
> Stian, what would be the advantage of the docs being on the Apache site vs
> GitHub? I do like the headers and code sections better in GitHub.
> Personally, the Apache CMS headings seem large and h1/h2 are fairly
> similar. Also, I like the gray code rendering. But not a big deal.
>
> Cheers!
>
> Gale
>
> On Thu, Jan 4, 2018, 7:18 AM Stian Soiland-Reyes  wrote:
>
>> I updated
>> https://github.com/apache/incubator-taverna-server/blob/master/usage.md
>> to include some table of content - it's still very long and could
>> probably be split into multiple pages.
>>
>> As I fixed some things in its example XML I think it would be cumbersome
>> to also maintain a OpenOffice version, so I removed those.
>>
>> Would this documentation live in GitHub as it is now, or as
>> separate pages under
>> https://taverna.incubator.apache.org/documentation/server/ ?
>>
>> I had a quick go:
>>
>> http://taverna.staging.apache.org/documentation/server/3.1/
>> http://taverna.staging.apache.org/documentation/server/3.1/install
>> http://taverna.staging.apache.org/documentation/server/3.1/usage
>>
>> Stylistically I think those look quite nice.. your views?
>>
>> (Compare with GitHub rendering
>> https://github.com/apache/incubator-taverna-server/blob/master/README.md
>> https://github.com/apache/incubator-taverna-server/blob/master/install.md
>> https://github.com/apache/incubator-taverna-server/blob/master/usage.md
>> )
>>
>> Note as I just copied from GitHub, that there are a couple of MarkDown
>> differences that makes the /usage examples look broken or perhaps too red.
>>
>>
>>
>> On Wed, 6 Dec 2017 11:12:04 +, Stian Soiland-Reyes 
>> wrote:
>> > I had a look at the documentation included in the Taverna Server git
>> > repository https://github.com/apache/incubator-taverna-server
>> >
>> > Both install and usage are quite extensive, and describes both how to
>> > install it and how the services are invoked.
>> >
>> > For some reason these where in the repository as binary PDF and DOCX
>> > files which personally I find a bit odd for a server product.
>> >
>> > They also had some outdated references to Univ of Manchester and
>> > Taverna 2.5.
>> >
>> >
>> > So I changed it to more open formats MarkDown and ODT and added the
>> > Apache License headers:
>> >
>> >
>> https://github.com/apache/incubator-taverna-server/blob/master/install.md
>> >
>> https://github.com/apache/incubator-taverna-server/blob/master/install.odt
>> > https://github.com/apache/incubator-taverna-server/blob/master/usage.md
>> > https://github.com/apache/incubator-taverna-server/blob/master/usage.odt
>> >
>> > Some more tidy-up could be done (e.g. use ```code``` blocks for the XML
>> > examples).
>> >
>> >
>> > The documentation seems very overlapping (or equal) to the 2.5
>> > Taverna Server documentation that also lives online in the old wiki:
>> >
>> > https://taverna.incubator.apache.org/documentation/server/
>> >
>> > .. but I have not checked this page by page.
>> >
>> >
>> >
>> > What do you think:
>> >
>> > Is the Markdown version more or less maintainable?
>> >   (e.g. the tables can get messy)
>> >
>> > Do we keep maintaining the OpenDocument versions (packaged as PDF in
>> release)?
>> >
>> > Do we keep the Markdown documentation as part of the git repository (and
>> > hence the Taverna Server distribution), or move it to the
>> > taverna.apache.org website? (it would probably work out of the
>> > box)
>> >
>> >
>> 

RE: TavMob source, binary or both

[Ian Dunlop]

Hello,

I’ll check and add the NOTICE & apache licence into that page inside the app if 
necessary.
I think creating the apk then adding it, an apache licence, notice & the 
dependencies list to a zip seems like a good idea. I assume that we can push 
this zip to the “binaries” area on dist and the actual source zip to the source 
“dist” area  
https://dist.apache.org/repos/dist/dev/incubator/taverna

Which I guess means we need to wait until the current release is moved out.

Cheers,

Ian
Sent from Mail for Windows 10

From: Stian Soiland-Reyes
Sent: 15 January 2018 15:57
To: dev@taverna.incubator.apache.org
Subject: Re: TavMob source, binary or both

I think this sounds like a good approach, Ian!

Generally it is simpler to do just a source release - if we are doing
a binary release we also need to have a complete LICENSE/NOTICE for
our bundled dependencies:
https://www.apache.org/dev/licensing-howto.html#binary


However you already did the external licenses here:
https://github.com/apache/incubator-taverna-mobile/blob/master/app/src/main/assets/licences.html


And so we should be able to refer to this in the binary distribution -
that's the file that can be viewed form within the app, right?
(This seem to be missing our own NOTICE and the complete text of
Apache LICENSE, is that added in somehow?)


Given that the work of dependency licenses is done I would vote for
TavMobile as a source+binary release.

It might be easiest to put the apk manually (or with a shell script)
inside a zip next to a LICENSE and NOTICE and a copy of that
licenses.html? Otherwise you have to install and run the app to view
its (shrink-wrap) license..

Signing of the apk with Google Play does not need to be part of the
release process, in particular if that might mean "distributing" the
apk to Google Play prematurely.


If it is too much work, let's do just a source release (as we did with
server/cmd line) avoid more delays. But then we should not put it in
Google Play as an official "Apache Taverna Mobile" release, just
personally add it as "Taverna Mobile".


On 15 January 2018 at 12:00, Ian Dunlop <ianwdun...@gmail.com> wrote:
> Hello,
>
> I'm going to try a release of TavMob soon. I'm not sure whether this
> should just be of the source code or whether we need to include a binary
> apk file as well. We could include an apk that people can test on their
> phones without needing Android studio etc. What we will need to do after
> release is then to sign it with the appropriate key for release via
> google play.
>
> Cheers,
>
> Ian
>
>



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

TavMob source, binary or both

[Ian Dunlop]

Hello,

I'm going to try a release of TavMob soon. I'm not sure whether this
should just be of the source code or whether we need to include a binary
apk file as well. We could include an apk that people can test on their
phones without needing Android studio etc. What we will need to do after
release is then to sign it with the appropriate key for release via
google play.

Cheers,

Ian




signature.asc
Description: OpenPGP digital signature

RE: [VOTE] Release Apache Taverna Server 3.1.0-incubating RC3

[Ian Dunlop]

+1

Built ok, tests passed. Md5 & sha1 match. gpg keys ok. LICENCE, DISCLAIMER and 
NOTICE seem ok and in accordance with the Apache way. 3rd part dependency 
licences all seem ok.

Cheers,

Ian

Sent from Mail for Windows 10

From: Stuart Owen
Sent: 11 January 2018 12:51
To: dev@taverna.incubator.apache.org
Subject: Re: [VOTE] Release Apache Taverna Server 3.1.0-incubating RC3

+1 from me

all build and tests passed. checked md5, sha1 and gpg signing. Checked & 
grepped over the package names to check they are now correct, and didn't 
find any org.taverna and that have been updated to org.apache.taverna.

Stuart


On 10/01/18 03:15, Stian Soiland-Reyes wrote:
> I am pleased to be calling this vote for the source release of
>
>Apache Taverna Maven Parent 3-incubating
>Apache Taverna Server 3.1.0-incubating
>
> To discuss this release candidate, use the corresponding [DISCUSS] thread.
>
>
> Taverna Server allows remote execution of Apache Taverna workflows, exposed as
> REST Web APIs and WSDL Web Services. This release is based on Apache Taverna
> Command-line 3.1.0.
>
> This third release candidate fixes the Java package names.
>
>
>
> Release candidates to be voted over are available at:
>
> https://dist.apache.org/repos/dist/dev/incubator/taverna/source/taverna-parent-3-incubating-RC3/
>
> https://dist.apache.org/repos/dist/dev/incubator/taverna/source/taverna-server-3.1.0-RC3/
>
>
> SHA-1 checksums:
> 6d779941bec29d327e22d2a76ec1069d82c4c28d  
> apache-taverna-parent-3-incubating-source-release.zip
> 4aebfdeecb78645365cab868878dc85c34f04ecc  
> apache-taverna-server-3.1.0-incubating-source-release.zip
>
>
> MD5 checksums:
> 11b15c0065541645976658387e4c5030  
> apache-taverna-parent-3-incubating-source-release.zip
> a1ed882e11b2e5a7af58486800f5e8aa  
> apache-taverna-server-3.1.0-incubating-source-release.zip
>
>
> Build the release candidate *in the above order* using:
>
>  mvn clean install
>
>
> The release candidates correspond to the following git commits:
>
> https://git-wip-us.apache.org/repos/asf?p=incubator-taverna-maven-parent.git;a=commit;h=adecb277e6179ee3f8cbd099b0bffe7aa3e38223
> https://git-wip-us.apache.org/repos/asf?p=incubator-taverna-server.git;a=commit;h=77884cbcc96a065671d920766931819b60f40b53
>
>
>
> Release candidates are signed with a GPG key available at:
> https://dist.apache.org/repos/dist/release/incubator/taverna/KEYS
>
>
> A staged Maven repository is available for review at:
> https://repository.apache.org/content/repositories/orgapachetaverna-1018
>
>
> The changelog for this release is available from JIRA:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12334882=12318322
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12332252=12318322
>
>
>
> Please vote on releasing these packages as:
>
> Apache Taverna Maven Parent 3-incubating
> Apache Taverna Server 3.1.0-incubating
>
> The vote is open for at least 72 hours and passes if a majority of at least
> three +1 Apache Taverna PPMC votes are cast.
>
> [ ] +1 Release this package
> [ ]  0 I don't feel strongly about it, but don't object
> [ ] -1 Do not release this package because...
>
>
> Anyone can participate in testing and voting, not just committers,
> please feel free to try out the release candidate and provide your
> votes!
>
> How to review a release? https://s.apache.org/review-release
>
>

RE: [VOTE] Release Apache Taverna Server 3.1.0-incubating RC2

[Ian Dunlop]

Hello,

Sha1 & MD5 match. Gpg keys confirmed. Both projects build and pass all tests.
+1

(BTW If you want to import the gpg key try “gpg --keyserver pgpkeys.mit.edu 
--recv-key CC1699A6” and enjoy Stian’s many identities!)

Cheers,

Ian

Sent from Mail for Windows 10

From: Stuart Owen
Sent: 09 January 2018 15:39
To: dev@taverna.incubator.apache.org
Subject: Re: [VOTE] Release Apache Taverna Server 3.1.0-incubating RC2

Hi,


On 08/01/18 17:31, Stian Soiland-Reyes wrote:
> I am pleased to be calling this vote for the source release of
>
>Apache Taverna Maven Parent 3-incubating
>Apache Taverna Server 3.1.0-incubating
>
> To discuss this release candidate, use the corresponding [DISCUSS] thread.
>
>
> Taverna Server allows remote execution of Apache Taverna workflows, exposed as
> REST Web APIs and WSDL Web Services. This release is based on Apache Taverna
> Command-line 3.1.0.
>
> This second release candidate fixes a problem identified in RC1 which
> failed to build when .git was missing.
>
>
>
> Release candidates to be voted over are available at:
>
> https://dist.apache.org/repos/dist/dev/incubator/taverna/source/taverna-parent-3-incubating-RC2/
>
> https://dist.apache.org/repos/dist/dev/incubator/taverna/source/taverna-server-3.1.0-RC2/
>
>
> SHA-1 checksums:
> 354fdbf4c3425d66061badf6b435fd6806d3d6c4  
> apache-taverna-parent-3-incubating-source-release.zip
> cdc0b10ee133e9a78971dced3385a382b7fe983e  
> apache-taverna-server-3.1.0-incubating-source-release.zip
>
> MD5 checksums:
> 99b9a0e9edfb467bb4f63874a31d2478  
> apache-taverna-parent-3-incubating-source-release.zip
> 3a78b4a01d138939f21a456bac02b3e5  
> apache-taverna-server-3.1.0-incubating-source-release.zip
>
>
>
>
>
> Build the release candidate *in the above order* using:
>
>  mvn clean install
>
>
> The release candidates correspond to the following git commits:
>
> https://git-wip-us.apache.org/repos/asf?p=incubator-taverna-maven-parent.git;a=commit;h=f25693204e505067580c52a1e36db1ddb7f0f047
> https://git-wip-us.apache.org/repos/asf?p=incubator-taverna-server.git;a=commit;h=135a77ec8fe5fdc3fa6e878e3b991f4d74ae2baf
>
>
>
> Release candidates are signed with a GPG key available at:
> https://dist.apache.org/repos/dist/release/incubator/taverna/KEYS
>
>
> A staged Maven repository is available for review at:
> https://repository.apache.org/content/repositories/orgapachetaverna-1017
>
>
> The changelog for this release is available from JIRA:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12334882=12318322
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12332252=12318322
>
>
>
> Please vote on releasing these packages as:
>
> Apache Taverna Maven Parent 3-incubating
> Apache Taverna Server 3.1.0-incubating
>
> The vote is open for at least 72 hours and passes if a majority of at least
> three +1 Apache Taverna PPMC votes are cast.
>
> [ ] +1 Release this package
> [ ]  0 I don't feel strongly about it, but don't object
> [ ] -1 Do not release this package because...
>
>
> Anyone can participate in testing and voting, not just committers,
> please feel free to try out the release candidate and provide your
> votes!
>
> How to review a release? https://s.apache.org/review-release
>
>

I checked both the md5 and sha1 sums for the downloads, which matched 
fine. I verified the gpg keys, which looked good, apart from "WARNING: 
This key is not certified with a trusted signature!".

I've run mvn clean and install for both sets of sources (on a clean 
Ubuntu 16.04 with Oracle java 8), which compiled fine and successfully 
ran all tests. Also mvn package, which successfully resulted in a built 
war file with no errors.

so, +1 from me.

Stuart

Re: Taverna Mobile release plan

[Ian Dunlop]

Hello,

To make a good start on this could everyone have a quick read of the 
LICENCE, NOTICE and README.md in 
https://github.com/apache/incubator-taverna-mobile to make sure that 
they make sense and comply with the Apache rules. Once we are happy I 
can start the release process. Hopefully a little bit of pre-work will 
help to reduce the number of times we go round the release process. Here 
is some info about the process 
https://www.apache.org/legal/release-policy.html


Cheers,

Ian


On 07/12/2017 15:05, Ian Dunlop wrote:

Hello,

I think we cannot release an apk on google play until the release 
candidate code has been voted on by the rest of the project and (I 
think) the incubator PMC.


Cheers,

Ian


On 06/12/2017 16:10, Sagar wrote:

Hello,

I also agree with the Ian.
I am building a release candidate APK then Ian can go ahead with the
release process.
And I will share all the private details with you on
priv...@taverna.incubator.apache.org.
Sorry for late reply.

Thanks

‌
<https://mailtrack.io/> Sent with Mailtrack
<https://chrome.google.com/webstore/detail/mailtrack-for-gmail-inbox/ndnaehgpjlnokgebbaldlmgkapkpjkkb?utm_source=gmail_medium=signature_campaign=signaturevirality> 



On Wed, Dec 6, 2017 at 8:26 PM, Ian Dunlop <ianwdun...@gmail.com> wrote:


Hello,

There is nothing blocking it except time and people. I think we should
just go for the tar-ball and then worry about the market place 
after. I'm

happy to be release manager but I also don't want to end up being the
blocker due to time constraints. If we make the assumption that the 
code as
in the repo is good to go then we can make a start at the release 
process.


How much of the existing release process applies? Is it just a case of
tarring it up and pushing to the release repo?

Cheers,

Ian



On 06/12/2017 11:03, Stian Soiland-Reyes wrote:


Who is willing to be Release Manager?

What is blocking?  What do people need help with?


Should we release just the source tar-ball right awawy and then 
package

binary for Android Market "privately"?

Re: Taverna Mobile release plan

[Ian Dunlop]

Hello,

I think we cannot release an apk on google play until the release 
candidate code has been voted on by the rest of the project and (I 
think) the incubator PMC.


Cheers,

Ian


On 06/12/2017 16:10, Sagar wrote:

Hello,

I also agree with the Ian.
I am building a release candidate APK then Ian can go ahead with the
release process.
And I will share all the private details with you on
priv...@taverna.incubator.apache.org.
Sorry for late reply.

Thanks

‌
<https://mailtrack.io/> Sent with Mailtrack
<https://chrome.google.com/webstore/detail/mailtrack-for-gmail-inbox/ndnaehgpjlnokgebbaldlmgkapkpjkkb?utm_source=gmail_medium=signature_campaign=signaturevirality>

On Wed, Dec 6, 2017 at 8:26 PM, Ian Dunlop <ianwdun...@gmail.com> wrote:


Hello,

There is nothing blocking it except time and people. I think we should
just go for the tar-ball and then worry about the market place after. I'm
happy to be release manager but I also don't want to end up being the
blocker due to time constraints. If we make the assumption that the code as
in the repo is good to go then we can make a start at the release process.

How much of the existing release process applies? Is it just a case of
tarring it up and pushing to the release repo?

Cheers,

Ian



On 06/12/2017 11:03, Stian Soiland-Reyes wrote:


Who is willing to be Release Manager?

What is blocking?  What do people need help with?


Should we release just the source tar-ball right awawy and then package
binary for Android Market "privately"?

Re: Taverna Mobile release plan

[Ian Dunlop]

Hello,

There is nothing blocking it except time and people. I think we should 
just go for the tar-ball and then worry about the market place after. 
I'm happy to be release manager but I also don't want to end up being 
the blocker due to time constraints. If we make the assumption that the 
code as in the repo is good to go then we can make a start at the 
release process.


How much of the existing release process applies? Is it just a case of 
tarring it up and pushing to the release repo?


Cheers,

Ian


On 06/12/2017 11:03, Stian Soiland-Reyes wrote:

Who is willing to be Release Manager?

What is blocking?  What do people need help with?


Should we release just the source tar-ball right awawy and then package
binary for Android Market "privately"?

Re: TavMob release process

[Ian Dunlop]

Hello,

@stain haven't used gradle-release but thought it looked like a good idea
@mark We had planned to just use the standard android packaging tools. If
there is a better way or a reason that we shouldn't then we are up for
anything.

Cheers,

Ian

On 23 October 2017 at 14:46, Mark Fortner <phidia...@gmail.com> wrote:

> Just out of curiosity, I was wondering if you were using Java's packager
> for this? It has the ability to do native packaging, including desktop and
> mobile (both iOS android).
>
> Regards,
>
> Mark
>
> On 20 Oct 2017 8:55 a.m., "Stian Soiland-Reyes" <st...@soiland-reyes.com>
> wrote:
>
> > Gradle-release sounds brilliant! Avoid pitfalls like snapshot
> dependencies
> > etc, as well as helping multiple people be release manager.
> >
> > Is it difficult to get it to work with android sdk..?
> >
> >
> >
> > On 19 Oct 2017 1:39 pm, "Ian Dunlop" <ianwdun...@gmail.com> wrote:
> >
> > > Hello,
> > >
> > > When we release Taverna Mobile I imagine we will need to modify
> > > https://taverna.incubator.apache.org/community/releasing. Do we want
> to
> > > use
> > > a maven  like release process for gradle
> > > https://github.com/researchgate/gradle-release ? Or do we just want to
> > > build, tag source code, upload .apk to staging repo?
> > >
> > > Cheers,
> > >
> > > Ian
> > >
> >
>

TavMob release process

[Ian Dunlop]

Hello,

When we release Taverna Mobile I imagine we will need to modify
https://taverna.incubator.apache.org/community/releasing. Do we want to use
a maven  like release process for gradle
https://github.com/researchgate/gradle-release ? Or do we just want to
build, tag source code, upload .apk to staging repo?

Cheers,

Ian

App signing for google play

[Ian Dunlop]

Hello,

We are trying to get Apache Taverna Mobile released via google play. To do
that we need various bits of info to generate key store certification:

   - First and Last name
   - Organizational unit
   - Organization
   - City or Locality
   - State or Province
   - Country Code

I guess this should be provided by Apache org rather than the individual
Apache member/project.

I'm not sure whether this is covered by https://blogs.apache.org/
infra/entry/code_signing_service_now_available

Any info you have would be much appreciated.

Cheers,

Ian

Re: Taverna Mobile play store release.

[Ian Dunlop]

Hello,

Hi Sagar. I've replied to your query on legal in the hope that it might get
actioned. Assuming it gets through the spam filter!

Cheers,

Ian

On 14 August 2017 at 06:46, Sagar <kumarsagar15...@gmail.com> wrote:

> Hi,
> I have emailed on legal-discuss but I have not received any reply.
> Please tell me what do now.
>
>
> On Fri, Jul 28, 2017 at 7:56 PM, Ian Dunlop <ianwdun...@gmail.com> wrote:
>
> > Hello,
> >
> > Yes I think it's one for legal. I believe that other projects have
> created
> > iPhone apps so they must have gone through a similar process. @sagar feel
> > free to send an email off to legal-discuss with your questions.
> >
> > Cheers,
> >
> > Ian
> >
> > On 28 July 2017 at 11:18, alaninmcr <alanin...@googlemail.com> wrote:
> >
> > > On 28/07/2017 08:01, Sagar wrote:
> > >
> > >> Hi,
> > >>
> > >
> > > Hello
> > >
> > > For generating Key Store certification, I need following details
> > >>
> > >> - First and Last name
> > >> - Organizational unit
> > >> - Organization
> > >> - City or Locality
> > >> - State or Province
> > >> - Country Code
> > >>
> > >> Please provide me with the details.
> > >>
> > >
> > > I assume that is for Apache. I think we may need to ask on
> > > legal-disc...@apache.org . What do others think?
> > >
> > > Alan
> > >
> >
>
>
>
> --
>
> Warmest regards
> Sagar
> Software Developer
> Lattice Innovations Pvt. Ltd.
>

Re: Taverna Mobile play store release.

[Ian Dunlop]

Hello,

I don't the answer to the "key" question.Sounds like one to ask the general
incubator list. Apache has created iOS apps (I think) so they probably
encountered a similar issue.
https://blogs.apache.org/infra/entry/code_signing_service_now_available
could be of interest. It mentions Android code signing.

Cheers,

Ian

On 18 July 2017 at 11:06, Sagar <kumarsagar15...@gmail.com> wrote:

> Hi,
> I have setup the release build which is in the build script itself. I have
> a question. Please, clear my question.
> do we need to share the passwords and keystore publicly or not?
> and any particular suggestion for the value of keyAlias , keyStore's
> password and key password.
>
> Thanks
>
> On Fri, Jul 14, 2017 at 7:52 PM, Ian Dunlop <ianwdun...@gmail.com> wrote:
>
> > Hello,
> >
> > I found an email where I was invited to the " Google Play Developer
> > Console"
> > by r...@apache.org. I guess you may need an invite as well Sagar. Raise
> an
> > issue with Infra just in case. The google play account expires in
> September
> > so Apache may need to pay another years subscription.
> >
> > Cheers,
> >
> > Ian
> >
> > On 11 July 2017 at 13:09, Ian Dunlop <ianwdun...@gmail.com> wrote:
> >
> > > Hello,
> > >
> > > Go for it Sagar. Apache is all about doing things so please go ahead.
> As
> > > Alan mentioned, the usual Apache rules about release candidates and
> votes
> > > etc apply here. Apache have a google play 'account' (can't remember
> > > official terminology) that infra set up a few months back. I have some
> > sort
> > > of admin rights on it. You could get infra to add you to the list as
> > well.
> > > I can't remember the exact details but I'll try and dig them out of my
> > mail
> > > archive.
> > >
> > > Cheers,
> > >
> > > Ian
> > >
> > > On 9 July 2017 at 17:05, Sagar <kumarsagar15...@gmail.com> wrote:
> > >
> > >> For signing the APK, we need to setup Keystore and Key as per android
> > blog
> > >> <https://developer.android.com/studio/publish/app-signing.html>. For
> > >> this,
> > >> I need to know what will be the password for Keystore and where to
> store
> > >> these credentials and Keystore.
> > >>
> > >>
> > >>
> > >> On Sun, Jul 9, 2017 at 5:44 PM, Mailtrack Reminder <
> > >> remind...@mailtrack.io>
> > >> wrote:
> > >>
> > >> > ⚠ Your email to dev@taverna.incubator.apache.org has not been
> opened
> > >> yet. Be
> > >> > reminded in 24H
> > >> > <https://mailtrack.io/reauth?url=https%3A%2F%2Fmailtrack.io%
> > >> 2Freminder%2Fschedule%3Fid%3De32bbc464a53424da731b64758f3bed
> > >> 7749aefdd%26delay%3D1_DAY_hint=kumarsagar15795%40gmail.com>
> > >> >  or 48H
> > >> > <https://mailtrack.io/reauth?url=https%3A%2F%2Fmailtrack.io%
> > >> 2Freminder%2Fschedule%3Fid%3De32bbc464a53424da731b64758f3bed
> > >> 7749aefdd%26delay%3D2_DAYS_hint=kumarsagar15795%40gmail.com>
> > >> >  (disable
> > >> > <https://mailtrack.io/reauth?url=https%3A%2F%2Fmailtrack.io%
> > >> 2Freminder%2Fdisable%3Fid%3De32bbc464a53424da731b64758f3bed7
> > >> 749aefdd_hint=kumarsagar15795%40gmail.com>)
> > >> >
> > >> >
> > >>
> > >>
> > >>
> > >> --
> > >>
> > >> Warmest regards
> > >> Sagar
> > >> Student,(8th Semester )
> > >> B.Tech IT and Mathematical innovation
> > >> Cluster Innovation Centre
> > >> University of Delhi
> > >>
> > >
> > >
> >
>
>
>
> --
>
> Warmest regards
> Sagar
> Student,(8th Semester )
> B.Tech IT and Mathematical innovation
> Cluster Innovation Centre
> University of Delhi
>

Re: Taverna Mobile play store release.

[Ian Dunlop]

Hello,

I found an email where I was invited to the " Google Play Developer Console"
by r...@apache.org. I guess you may need an invite as well Sagar. Raise an
issue with Infra just in case. The google play account expires in September
so Apache may need to pay another years subscription.

Cheers,

Ian

On 11 July 2017 at 13:09, Ian Dunlop <ianwdun...@gmail.com> wrote:

> Hello,
>
> Go for it Sagar. Apache is all about doing things so please go ahead. As
> Alan mentioned, the usual Apache rules about release candidates and votes
> etc apply here. Apache have a google play 'account' (can't remember
> official terminology) that infra set up a few months back. I have some sort
> of admin rights on it. You could get infra to add you to the list as well.
> I can't remember the exact details but I'll try and dig them out of my mail
> archive.
>
> Cheers,
>
> Ian
>
> On 9 July 2017 at 17:05, Sagar <kumarsagar15...@gmail.com> wrote:
>
>> For signing the APK, we need to setup Keystore and Key as per android blog
>> <https://developer.android.com/studio/publish/app-signing.html>. For
>> this,
>> I need to know what will be the password for Keystore and where to store
>> these credentials and Keystore.
>>
>>
>>
>> On Sun, Jul 9, 2017 at 5:44 PM, Mailtrack Reminder <
>> remind...@mailtrack.io>
>> wrote:
>>
>> > ⚠ Your email to dev@taverna.incubator.apache.org has not been opened
>> yet. Be
>> > reminded in 24H
>> > <https://mailtrack.io/reauth?url=https%3A%2F%2Fmailtrack.io%
>> 2Freminder%2Fschedule%3Fid%3De32bbc464a53424da731b64758f3bed
>> 7749aefdd%26delay%3D1_DAY_hint=kumarsagar15795%40gmail.com>
>> >  or 48H
>> > <https://mailtrack.io/reauth?url=https%3A%2F%2Fmailtrack.io%
>> 2Freminder%2Fschedule%3Fid%3De32bbc464a53424da731b64758f3bed
>> 7749aefdd%26delay%3D2_DAYS_hint=kumarsagar15795%40gmail.com>
>> >  (disable
>> > <https://mailtrack.io/reauth?url=https%3A%2F%2Fmailtrack.io%
>> 2Freminder%2Fdisable%3Fid%3De32bbc464a53424da731b64758f3bed7
>> 749aefdd_hint=kumarsagar15795%40gmail.com>)
>> >
>> >
>>
>>
>>
>> --
>>
>> Warmest regards
>> Sagar
>> Student,(8th Semester )
>> B.Tech IT and Mathematical innovation
>> Cluster Innovation Centre
>> University of Delhi
>>
>
>

Re: TAVERNA-550

[Ian Dunlop]

Hello,

I tried building the tavern-workbench on Windows 10 and Linux and got a
different set of failures from you. This was with a fresh clone of
https://github.com/apache/incubator-taverna-workbench.

Using:
Apache Maven 3.5.0 (ff8f5e7444045639af65f6095c62210b5713f426;
2017-04-03T20:39:06+01:00)
Maven home: C:\Program Files\apache-maven-3.5.0\bin\..
Java version: 1.8.0_131, vendor: Oracle Corporation
Java home: C:\Program Files\Java\jdk1.8.0_131\jre
Default locale: en_GB, platform encoding: Cp1252
OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"

"mvn clean install" stack trace:

---
 T E S T S
---
Running
org.apache.taverna.workbench.ui.impl.configuration.colour.ColourManagerTest
Tests run: 3, Failures: 0, Errors: 3, Skipped: 0, Time elapsed: 0.074 sec
<<< FAILURE! - in
org.apache.taverna.workbench.ui.impl.configuration.colour.ColourManagerTest
saveAsWrongArrayType(org.apache.taverna.workbench.ui.impl.configuration.colour.ColourManagerTest)
Time elapsed: 0.038 sec  <<< ERROR!
java.lang.NullPointerException
at
org.apache.taverna.workbench.ui.impl.configuration.colour.ColourManagerTest.setup(ColourManagerTest.java:45)
testConfigurableness(org.apache.taverna.workbench.ui.impl.configuration.colour.ColourManagerTest)
Time elapsed: 0 sec  <<< ERROR!
java.lang.NullPointerException
at
org.apache.taverna.workbench.ui.impl.configuration.colour.ColourManagerTest.setup(ColourManagerTest.java:45)
testGetPreferredColourEqualsWhite(org.apache.taverna.workbench.ui.impl.configuration.colour.ColourManagerTest)
Time elapsed: 0 sec  <<< ERROR!
java.lang.NullPointerException
at
org.apache.taverna.workbench.ui.impl.configuration.colour.ColourManagerTest.setup(ColourManagerTest.java:45)
Running
org.apache.taverna.workbench.ui.impl.configuration.ConfigurationManagerTest
Tests run: 3, Failures: 0, Errors: 2, Skipped: 1, Time elapsed: 0.001 sec
<<< FAILURE! - in
org.apache.taverna.workbench.ui.impl.configuration.ConfigurationManagerTest
saveColoursForDummyColourable(org.apache.taverna.workbench.ui.impl.configuration.ConfigurationManagerTest)
Time elapsed: 0 sec  <<< ERROR!
java.lang.NullPointerException
at
org.apache.taverna.workbench.ui.impl.configuration.ConfigurationManagerTest.setup(ConfigurationManagerTest.java:43)
createConfigManager(org.apache.taverna.workbench.ui.impl.configuration.ConfigurationManagerTest)
Time elapsed: 0 sec  <<< ERROR!
java.lang.NullPointerException
at
org.apache.taverna.workbench.ui.impl.configuration.ConfigurationManagerTest.setup(ConfigurationManagerTest.java:43)

Results :
Tests in error:
  ConfigurationManagerTest.setup:43 ╗ NullPointer
  ConfigurationManagerTest.setup:43 ╗ NullPointer
  ColourManagerTest.setup:45 ╗ NullPointer
  ColourManagerTest.setup:45 ╗ NullPointer
  ColourManagerTest.setup:45 ╗ NullPointer
Tests run: 6, Failures: 0, Errors: 5, Skipped: 1
[INFO]

[INFO] Reactor Summary:
[INFO]
[INFO] Apache Taverna Workbench ... SUCCESS [
0.969 s]
[INFO] Apache Taverna Activity icon manager API ... SUCCESS [
7.361 s]
[INFO] Apache Taverna Workbench API ... SUCCESS [
1.257 s]
[INFO] Apache Taverna Edits API ... SUCCESS [
10.675 s]
[INFO] Apache Taverna BeanInfo extensions . SUCCESS [
0.757 s]
[INFO] Apache Taverna Activity Palette API  SUCCESS [
12.074 s]
[INFO] Apache Taverna Configuration Management UI API . SUCCESS [
0.783 s]
[INFO] Apache Taverna User interface (Swing) utilities  SUCCESS [
1.595 s]
[INFO] Apache Taverna File opening API  SUCCESS [
2.089 s]
[INFO] Apache Taverna Help System . SUCCESS [
15.279 s]
[INFO] Apache Taverna Contextual Views API  SUCCESS [
28.257 s]
[INFO] Apache Taverna Selection API ... SUCCESS [
1.765 s]
[INFO] Apache Taverna Menu generation API . SUCCESS [
2.481 s]
[INFO] Apache Taverna Design UI ... SUCCESS [
2.589 s]
[INFO] Apache Taverna Workflow View ... SUCCESS [
2.840 s]
[INFO] Apache Taverna IO utility classes .. SUCCESS [
0.663 s]
[INFO] Apache Batik OSGi .. SUCCESS [01:14
min]
[INFO] Apache Taverna Graph Model . SUCCESS [
19.067 s]
[INFO] Apache Taverna Graph View .. SUCCESS [
3.191 s]
[INFO] Apache Taverna Activity tools .. SUCCESS [
1.750 s]
[INFO] Apache Taverna Edits implementation  SUCCESS [
2.903 s]
[INFO] Apache Taverna File opening implementation . SUCCESS [
31.991 s]
[INFO] Apache Taverna Dataflow Activity UI  SUCCESS [
3.972 s]
[INFO] Apache Taverna StringConstant Activity UI .. SUCCESS [

Re: Taverna Mobile play store release.

[Ian Dunlop]

Hello,

Go for it Sagar. Apache is all about doing things so please go ahead. As
Alan mentioned, the usual Apache rules about release candidates and votes
etc apply here. Apache have a google play 'account' (can't remember
official terminology) that infra set up a few months back. I have some sort
of admin rights on it. You could get infra to add you to the list as well.
I can't remember the exact details but I'll try and dig them out of my mail
archive.

Cheers,

Ian

On 9 July 2017 at 17:05, Sagar  wrote:

> For signing the APK, we need to setup Keystore and Key as per android blog
> . For this,
> I need to know what will be the password for Keystore and where to store
> these credentials and Keystore.
>
>
>
> On Sun, Jul 9, 2017 at 5:44 PM, Mailtrack Reminder  >
> wrote:
>
> > ⚠ Your email to dev@taverna.incubator.apache.org has not been opened
> yet. Be
> > reminded in 24H
> >  io%2Freminder%2Fschedule%3Fid%3De32bbc464a53424da731b64758f3
> bed7749aefdd%26delay%3D1_DAY_hint=kumarsagar15795%40gmail.com>
> >  or 48H
> >  io%2Freminder%2Fschedule%3Fid%3De32bbc464a53424da731b64758f3
> bed7749aefdd%26delay%3D2_DAYS_hint=kumarsagar15795%40gmail.com>
> >  (disable
> >  io%2Freminder%2Fdisable%3Fid%3De32bbc464a53424da731b64758f3
> bed7749aefdd_hint=kumarsagar15795%40gmail.com>)
> >
> >
>
>
>
> --
>
> Warmest regards
> Sagar
> Student,(8th Semester )
> B.Tech IT and Mathematical innovation
> Cluster Innovation Centre
> University of Delhi
>

Re: Podling graduation rally on incubator list

[Ian Dunlop]

Hello,

I think we could release TavMob as it is. As long as the licences are
all ok. The infra folks set up a google play account as well so we could
push it to that. We could also just release the APK independently of
that. I'll investigate doing an APK release.

I think we have to be a bit ruthless with the codebases and prune
everything except the currently released repos, server and (maybe)
workbench. The rest can be moved somewhere else (tav-extras?) and can be
brought back in later

Cheers,

Ian


On 01/03/17 19:17, Gale Naylor wrote:
>> Decide which code is in/out: "... keep
> our future options open
>> to bring in the rest of the code later without a second software grant."
> That sounds like a good plan. What do we have to do to find out if we can
> bring the rest of the code in later without a new grant?
>
> A weekly status sounds like a good way to keep this moving.
>
> Gale
>
> On Wed, Mar 1, 2017, 8:49 AM Stian Soiland-Reyes  wrote:
>
>> On Fri, 17 Feb 2017 17:31:59 +, Andy Seaborne  wrote:
 There is a recent thread regarding getting podlings to graduate on the
 incubator mailing list. Perhaps we can add Taverna to their list. We
>> may
 have stalled again. Any thoughts? What really, really, really needs
>> done
 to graduate? Let's move out any non essential components. We've already
 released several so they are ready to go. Of the rest what do we really
 need to keep? I can't see any that are essential.
>>> I think you've described the situation accurately.
>>>
>>> * Decide which code is in and which is not.
>> This is the tricky bit.. I guess we have been undecided, as there is
>> more we think "should" keep than we have been able to get ready.
>>
>> We have to be more realistic and cut our ambitions to align with the
>> actual effort we have available. It would be good if we can still keep
>> our future options open to bring in the rest of the code later without a
>> second software grant.
>>
>>
>>> * Release the "in" code.
>> Agreed. This should be not be too much work for taverna-server, and even
>> for taverna-workbench-* (although they might not be release-ready for
>> the public).
>>
>>
>>> * Don't stall :-)
>> Let's start a weekly status roll to avoid stalling. We can do it
>>
>>
>>> Good would be to have more PPMC diversity of organisation.
>> Technically we've got higher diversity now that Ian no longer
>> works at The University of Manchester, Christian and Donal are in a
>> different group and Gale got a new job :-) - but I see your point -
>> particularly in consideration of what is effectively the *active* PPMC.
>>
>>> Graduation needs the codebase to be ASF-clean and verified; that's
>>> Tavernas main item in my view.  A release does that best.
>> I suggest we do a source code release of what we have, and don't promote
>> too much on the website anything that is not at user-ready.
>>
>> Taverna Mobile would be interesting to release as well - as there's
>> never been an Android release through the incubator before, and those
>> have their own (it turns out) proprietary build chains.
>>
>>
>>> Maybe Taverna isn't quite at the point to be rallied.  The other
>>> podlings are mostly all done, just need to do the grdauation step itself.
>> Agree on this ; while we're pretty much ready to graduate, for the IPMC
>> to evaluate that this is the case would take a bit longer than in the
>> projects in the rally.
>>
>> I think Ian has done well on our license review under
>>
>> https://cwiki.apache.org/confluence/display/TAVERNADEV/2016-09+License+review
>> and sub pages, which fits into
>>
>> https://cwiki.apache.org/confluence/display/TAVERNADEV/2016-03+Taverna+Graduation+Maturity+Assessment
>>
>> However the above still needs filling in for the remaining parts, from
>> RE40 and below.
>>
>> --
>> Stian Soiland-Reyes
>> The University of Manchester
>> http://www.esciencelab.org.uk/
>> http://orcid.org/-0001-9842-9718
>>
>>

Re: Podling Report Reminder - March 2017

[Ian Dunlop]

Hello,

I've added a few notes.

Cheers,

Ian


On 28/02/17 10:19, Andy Seaborne wrote:
> Ping?
>
> On 27/02/17 02:37, 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, 15 March 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, March 01).
>>
>> 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/March2017
>>
>> 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
>>

Podling graduation rally on incubator list

[Ian Dunlop]

Hello,

There is a recent thread regarding getting podlings to graduate on the
incubator mailing list. Perhaps we can add Taverna to their list. We may
have stalled again. Any thoughts? What really, really, really needs done
to graduate? Let's move out any non essential components. We've already
released several so they are ready to go. Of the rest what do we really
need to keep? I can't see any that are essential.

Cheers,

Ian




signature.asc
Description: OpenPGP digital signature

Re: Graduation? BioMoby and CDDL xsds

[Ian Dunlop]

Hello,

I created a new taverna-extras repo called taverna-xsds
https://github.com/taverna-extras/taverna-xsds

If you clone it and maven install you should get a jar with the xsds
inside it.

I also created a branch of taverna server in my own fork
https://github.com/ianwdunlop/incubator-taverna-server/tree/ian_shared_resources

This uses the shared resources in the taverna-server-webapp and
taverna-server-usagerecord modules. You have to go inside these modules
and run mvn remote-resources:process to get the xsds into the correct
directories. Then you can go to the root and run mvn install.

I couldn't figure out how to:

1) Only copy the resource required rather than all the resources from
the jar.

2) Run the remote-resources:process goal automatically on build/install
rather than manually.

TODO:

If this seems the way to go then we need to get the jar into an existing
maven repo. Or create a new one.

Cheers,

Ian

On 27/01/17 11:04, Ian Dunlop wrote:
> Hello,
>
> Maybe we should attempt to create a mvn repo on the taverna-extras
> github site with https://github.com/github/maven-plugins#readme.
>
> Cheers,
>
> Ian
>
>
> On 27/01/17 10:37, Ian Dunlop wrote:
>> Hello,
>>
>> Perhaps we can use something like
>> http://maven.apache.org/components/plugins/maven-remote-resources-plugin/
>> to bundle up the XSDs in a jar and then pull them into the required
>> projects.
>>
>> Cheers,
>>
>> Ian
>>
>>
>> On 26/01/17 18:37, Dmitry wrote:
>>> Hello,
>>>
>>> There is virtually no access to our biomoby registry. I am for putting
>>> biomoby support as extra.
>>> If there is a demand for biomoby we could rewrite it using my
>>> MobyCore/MobyCentral libraries.
>>> They have no any third-party dependencies and I can put them under
>>> Apache.
>>>
>>> Dmitry
>>>
>>>
>>> On 1/26/2017 6:01 PM, Stian Soiland-Reyes wrote:
>>>> Thanks for pushing this forward, Ian! In had hoped to have more time for
>>>> this in January, but all these grant proposals are coming up :-/
>>>>
>>>> +1 to move biomoby-activity out to extras. I think it also depends on
>>>> the
>>>> monster biomoby.jar which shadows lots of libs of various licenses.
>>>>
>>>>   I think Dmitri has access to the biomoby registry hosted in Spain,
>>>> do you
>>>> have any access numbers, Dmitri..?
>>>>
>>>>
>>>> I think for CDDL of the XSD files we want to keep it as "binary" so
>>>> it is
>>>> clearly not source code that can be modified under AL2 - while we
>>>> want to
>>>> keep it as dual license so much it remains usable from GPL (e.g.
>>>> AstroTaverna).
>>>>
>>>> Perhaps the ideal is to move the XSD out as a separate Maven dependency
>>>> under its own license, say from GitHub. (Donal said that original lives
>>>> inside a PDF  )
>>>>
>>>> ..or we can also leave it as a zip file in the GitHub repo, which is
>>>> not as
>>>> clean (and would require LICENCE changes)?
>>>>
>>>> Middle ground : make a taverna-extras repo with a Release JAR of just
>>>> the
>>>> XSDs, and download straight from GH; I think the Maven plugin could do
>>>> that. Does not work as nicely with caches and proxies.
>>>>
>>>> On 26 Jan 2017 3:40 pm, "Ian Dunlop" <ianwdun...@gmail.com> wrote:
>>>>
>>>> Hello,
>>>>
>>>> Taverna server includes an xsd (https://github.com/apache/
>>>> incubator-taverna-server/blob/master/taverna-server-webapp/
>>>> src/misc/xsd/persistence_1_0.xsd) which can be licensed under CDDL (read
>>>> the source file - the user can select either gpl or cddl).
>>>>
>>>> https://www.apache.org/legal/resolved#category-b states the following
>>>> regarding CDDL (among others):
>>>>
>>>> For small amounts of source that is directly consumed by the ASF
>>>> product at
>>>> runtime in source form, and for which that source is unmodified and
>>>> unlikely to be changed anyway (say, by virtue of being specified by a
>>>> standard), inclusion of appropriately labeled source is also permitted.
>>>>
>>>> So it looks like that file can be included but it begs the question
>>>> of what
>>>> "appropriately labeled" means. Any ideas? Point to this licence in
>>>> NOTICE?
>>>>
>>>> Cheers,
>>>>
>>>> Ian
>>>>
>>>>
>>>> On 26/01/17 13:09, Gale Naylor wrote:
>>>>
>>>>
>>>> +1
>>>>
>>>> On Thu, Jan 26, 2017, 3:38 AM Alan Williams <alanin...@googlemail.com>
>>>> <alanin...@googlemail.com>
>>>> wrote:
>>>>
>>>>
>>>> On 26-Jan-17 11:33, Ian Dunlop wrote:
>>>>
>>>> Hello,
>>>>
>>>> This sounds like a horribly tangled web that we should just ignore for
>>>> the moment. Perhaps the biomoby-activity-ui can be moved to the
>>>> taverna-extras repo until we clear this up. To me it doesn't seem worth
>>>> expending  effort when most of the other apache taverna repos are almost
>>>> there regards licences.
>>>>
>>>>
>>>> +1
>>>>
>>>>
>>>> Cheers,
>>>>
>>>> Ian
>>>>
>>>>
>>>> Alan
>>>>
>




signature.asc
Description: OpenPGP digital signature

Re: Graduation? BioMoby and CDDL xsds

[Ian Dunlop]

Hello,

Maybe we should attempt to create a mvn repo on the taverna-extras
github site with https://github.com/github/maven-plugins#readme.

Cheers,

Ian


On 27/01/17 10:37, Ian Dunlop wrote:
> Hello,
>
> Perhaps we can use something like
> http://maven.apache.org/components/plugins/maven-remote-resources-plugin/
> to bundle up the XSDs in a jar and then pull them into the required
> projects.
>
> Cheers,
>
> Ian
>
>
> On 26/01/17 18:37, Dmitry wrote:
>> Hello,
>>
>> There is virtually no access to our biomoby registry. I am for putting
>> biomoby support as extra.
>> If there is a demand for biomoby we could rewrite it using my
>> MobyCore/MobyCentral libraries.
>> They have no any third-party dependencies and I can put them under
>> Apache.
>>
>> Dmitry
>>
>>
>> On 1/26/2017 6:01 PM, Stian Soiland-Reyes wrote:
>>> Thanks for pushing this forward, Ian! In had hoped to have more time for
>>> this in January, but all these grant proposals are coming up :-/
>>>
>>> +1 to move biomoby-activity out to extras. I think it also depends on
>>> the
>>> monster biomoby.jar which shadows lots of libs of various licenses.
>>>
>>>   I think Dmitri has access to the biomoby registry hosted in Spain,
>>> do you
>>> have any access numbers, Dmitri..?
>>>
>>>
>>> I think for CDDL of the XSD files we want to keep it as "binary" so
>>> it is
>>> clearly not source code that can be modified under AL2 - while we
>>> want to
>>> keep it as dual license so much it remains usable from GPL (e.g.
>>> AstroTaverna).
>>>
>>> Perhaps the ideal is to move the XSD out as a separate Maven dependency
>>> under its own license, say from GitHub. (Donal said that original lives
>>> inside a PDF  )
>>>
>>> ..or we can also leave it as a zip file in the GitHub repo, which is
>>> not as
>>> clean (and would require LICENCE changes)?
>>>
>>> Middle ground : make a taverna-extras repo with a Release JAR of just
>>> the
>>> XSDs, and download straight from GH; I think the Maven plugin could do
>>> that. Does not work as nicely with caches and proxies.
>>>
>>> On 26 Jan 2017 3:40 pm, "Ian Dunlop" <ianwdun...@gmail.com> wrote:
>>>
>>> Hello,
>>>
>>> Taverna server includes an xsd (https://github.com/apache/
>>> incubator-taverna-server/blob/master/taverna-server-webapp/
>>> src/misc/xsd/persistence_1_0.xsd) which can be licensed under CDDL (read
>>> the source file - the user can select either gpl or cddl).
>>>
>>> https://www.apache.org/legal/resolved#category-b states the following
>>> regarding CDDL (among others):
>>>
>>> For small amounts of source that is directly consumed by the ASF
>>> product at
>>> runtime in source form, and for which that source is unmodified and
>>> unlikely to be changed anyway (say, by virtue of being specified by a
>>> standard), inclusion of appropriately labeled source is also permitted.
>>>
>>> So it looks like that file can be included but it begs the question
>>> of what
>>> "appropriately labeled" means. Any ideas? Point to this licence in
>>> NOTICE?
>>>
>>> Cheers,
>>>
>>> Ian
>>>
>>>
>>> On 26/01/17 13:09, Gale Naylor wrote:
>>>
>>>
>>> +1
>>>
>>> On Thu, Jan 26, 2017, 3:38 AM Alan Williams <alanin...@googlemail.com>
>>> <alanin...@googlemail.com>
>>> wrote:
>>>
>>>
>>> On 26-Jan-17 11:33, Ian Dunlop wrote:
>>>
>>> Hello,
>>>
>>> This sounds like a horribly tangled web that we should just ignore for
>>> the moment. Perhaps the biomoby-activity-ui can be moved to the
>>> taverna-extras repo until we clear this up. To me it doesn't seem worth
>>> expending  effort when most of the other apache taverna repos are almost
>>> there regards licences.
>>>
>>>
>>> +1
>>>
>>>
>>> Cheers,
>>>
>>> Ian
>>>
>>>
>>> Alan
>>>
>




signature.asc
Description: OpenPGP digital signature

Re: Graduation? BioMoby and CDDL xsds

[Ian Dunlop]

Hello,

Perhaps we can use something like
http://maven.apache.org/components/plugins/maven-remote-resources-plugin/
to bundle up the XSDs in a jar and then pull them into the required
projects.

Cheers,

Ian


On 26/01/17 18:37, Dmitry wrote:
> Hello,
>
> There is virtually no access to our biomoby registry. I am for putting
> biomoby support as extra.
> If there is a demand for biomoby we could rewrite it using my
> MobyCore/MobyCentral libraries.
> They have no any third-party dependencies and I can put them under
> Apache.
>
> Dmitry
>
>
> On 1/26/2017 6:01 PM, Stian Soiland-Reyes wrote:
>> Thanks for pushing this forward, Ian! In had hoped to have more time for
>> this in January, but all these grant proposals are coming up :-/
>>
>> +1 to move biomoby-activity out to extras. I think it also depends on
>> the
>> monster biomoby.jar which shadows lots of libs of various licenses.
>>
>>   I think Dmitri has access to the biomoby registry hosted in Spain,
>> do you
>> have any access numbers, Dmitri..?
>>
>>
>> I think for CDDL of the XSD files we want to keep it as "binary" so
>> it is
>> clearly not source code that can be modified under AL2 - while we
>> want to
>> keep it as dual license so much it remains usable from GPL (e.g.
>> AstroTaverna).
>>
>> Perhaps the ideal is to move the XSD out as a separate Maven dependency
>> under its own license, say from GitHub. (Donal said that original lives
>> inside a PDF  )
>>
>> ..or we can also leave it as a zip file in the GitHub repo, which is
>> not as
>> clean (and would require LICENCE changes)?
>>
>> Middle ground : make a taverna-extras repo with a Release JAR of just
>> the
>> XSDs, and download straight from GH; I think the Maven plugin could do
>> that. Does not work as nicely with caches and proxies.
>>
>> On 26 Jan 2017 3:40 pm, "Ian Dunlop" <ianwdun...@gmail.com> wrote:
>>
>> Hello,
>>
>> Taverna server includes an xsd (https://github.com/apache/
>> incubator-taverna-server/blob/master/taverna-server-webapp/
>> src/misc/xsd/persistence_1_0.xsd) which can be licensed under CDDL (read
>> the source file - the user can select either gpl or cddl).
>>
>> https://www.apache.org/legal/resolved#category-b states the following
>> regarding CDDL (among others):
>>
>> For small amounts of source that is directly consumed by the ASF
>> product at
>> runtime in source form, and for which that source is unmodified and
>> unlikely to be changed anyway (say, by virtue of being specified by a
>> standard), inclusion of appropriately labeled source is also permitted.
>>
>> So it looks like that file can be included but it begs the question
>> of what
>> "appropriately labeled" means. Any ideas? Point to this licence in
>> NOTICE?
>>
>> Cheers,
>>
>> Ian
>>
>>
>> On 26/01/17 13:09, Gale Naylor wrote:
>>
>>
>> +1
>>
>> On Thu, Jan 26, 2017, 3:38 AM Alan Williams <alanin...@googlemail.com>
>> <alanin...@googlemail.com>
>> wrote:
>>
>>
>> On 26-Jan-17 11:33, Ian Dunlop wrote:
>>
>> Hello,
>>
>> This sounds like a horribly tangled web that we should just ignore for
>> the moment. Perhaps the biomoby-activity-ui can be moved to the
>> taverna-extras repo until we clear this up. To me it doesn't seem worth
>> expending  effort when most of the other apache taverna repos are almost
>> there regards licences.
>>
>>
>> +1
>>
>>
>> Cheers,
>>
>> Ian
>>
>>
>> Alan
>>
>




signature.asc
Description: OpenPGP digital signature

Re: Graduation?

[Ian Dunlop]

Hello,

What is the issue with
https://github.com/apache/incubator-taverna-server/blob/master/taverna-server-usagerecord/src/main/java/org/ogf/usage/JobUsageRecord.java
since it has the Apache header? Is it the class it extends that is the
problem - org.ogf.usage.v1_0.UsageRecordType or the XSDs that it uses?

For the usage record XSD I found
https://www.ogf.org/documents/GFD.98.pdf. In section 18 it has a feel
free to use but don't change type copyright notice. Since we have no
reason to change it and it puts no restrictions on its use or the terms
of the Apache Licence (I believe - go on I dare you to ask legal) I
think it is ok under the category-b weak copyleft type license. So maybe
it just needs added to NOTICE.

Cheers,

Ian


On 26/01/17 15:51, Ian Dunlop wrote:
>
> Hello,
>
> Note that the persistence XSD also states that
> https://glassfish.java.net/public/CDDL+GPL.html should be included in
> any distribution. Though I suppose only the CDDL part of it. So how do
> we included external licences. Place them in NOTICE?
>
> Cheers,
>
> Ian
>
>
> On 26/01/17 15:40, Ian Dunlop wrote:
>>
>> Hello,
>>
>> Taverna server includes an xsd
>> (https://github.com/apache/incubator-taverna-server/blob/master/taverna-server-webapp/src/misc/xsd/persistence_1_0.xsd)
>> which can be licensed under CDDL (read the source file - the user can
>> select either gpl or cddl).
>>
>> https://www.apache.org/legal/resolved#category-b states the following
>> regarding CDDL (among others):
>>
>>> For small amounts of source that is directly consumed by the ASF
>>> product at runtime in source form, and for which that source is
>>> unmodified and unlikely to be changed anyway (say, by virtue of
>>> being specified by a standard), inclusion of appropriately labeled
>>> source is also permitted.
>> So it looks like that file can be included but it begs the question
>> of what "appropriately labeled" means. Any ideas? Point to this
>> licence in NOTICE?
>>
>> Cheers,
>>
>> Ian
>>
>>
>> On 26/01/17 13:09, Gale Naylor wrote:
>>
>>> +1
>>>
>>> On Thu, Jan 26, 2017, 3:38 AM Alan Williams <alanin...@googlemail.com>
>>> wrote:
>>>
>>>> On 26-Jan-17 11:33, Ian Dunlop wrote:
>>>>> Hello,
>>>>>
>>>>> This sounds like a horribly tangled web that we should just ignore for
>>>>> the moment. Perhaps the biomoby-activity-ui can be moved to the
>>>>> taverna-extras repo until we clear this up. To me it doesn't seem worth
>>>>> expending  effort when most of the other apache taverna repos are almost
>>>>> there regards licences.
>>>> +1
>>>>
>>>>> Cheers,
>>>>>
>>>>> Ian
>>>> Alan
>>>>
>>>>
>>
>



signature.asc
Description: OpenPGP digital signature

Re: Graduation?

[Ian Dunlop]

Hello,

Note that the persistence XSD also states that
https://glassfish.java.net/public/CDDL+GPL.html should be included in
any distribution. Though I suppose only the CDDL part of it. So how do
we included external licences. Place them in NOTICE?

Cheers,

Ian


On 26/01/17 15:40, Ian Dunlop wrote:
>
> Hello,
>
> Taverna server includes an xsd
> (https://github.com/apache/incubator-taverna-server/blob/master/taverna-server-webapp/src/misc/xsd/persistence_1_0.xsd)
> which can be licensed under CDDL (read the source file - the user can
> select either gpl or cddl).
>
> https://www.apache.org/legal/resolved#category-b states the following
> regarding CDDL (among others):
>
>> For small amounts of source that is directly consumed by the ASF
>> product at runtime in source form, and for which that source is
>> unmodified and unlikely to be changed anyway (say, by virtue of being
>> specified by a standard), inclusion of appropriately labeled source
>> is also permitted.
> So it looks like that file can be included but it begs the question of
> what "appropriately labeled" means. Any ideas? Point to this licence
> in NOTICE?
>
> Cheers,
>
> Ian
>
>
> On 26/01/17 13:09, Gale Naylor wrote:
>
>> +1
>>
>> On Thu, Jan 26, 2017, 3:38 AM Alan Williams <alanin...@googlemail.com>
>> wrote:
>>
>>> On 26-Jan-17 11:33, Ian Dunlop wrote:
>>>> Hello,
>>>>
>>>> This sounds like a horribly tangled web that we should just ignore for
>>>> the moment. Perhaps the biomoby-activity-ui can be moved to the
>>>> taverna-extras repo until we clear this up. To me it doesn't seem worth
>>>> expending  effort when most of the other apache taverna repos are almost
>>>> there regards licences.
>>> +1
>>>
>>>> Cheers,
>>>>
>>>> Ian
>>> Alan
>>>
>>>
>



signature.asc
Description: OpenPGP digital signature

Re: Graduation?

[Ian Dunlop]

Hello,

Taverna server includes an xsd
(https://github.com/apache/incubator-taverna-server/blob/master/taverna-server-webapp/src/misc/xsd/persistence_1_0.xsd)
which can be licensed under CDDL (read the source file - the user can
select either gpl or cddl).

https://www.apache.org/legal/resolved#category-b states the following
regarding CDDL (among others):

> For small amounts of source that is directly consumed by the ASF
> product at runtime in source form, and for which that source is
> unmodified and unlikely to be changed anyway (say, by virtue of being
> specified by a standard), inclusion of appropriately labeled source is
> also permitted.
So it looks like that file can be included but it begs the question of
what "appropriately labeled" means. Any ideas? Point to this licence in
NOTICE?

Cheers,

Ian


On 26/01/17 13:09, Gale Naylor wrote:

> +1
>
> On Thu, Jan 26, 2017, 3:38 AM Alan Williams <alanin...@googlemail.com>
> wrote:
>
>> On 26-Jan-17 11:33, Ian Dunlop wrote:
>>> Hello,
>>>
>>> This sounds like a horribly tangled web that we should just ignore for
>>> the moment. Perhaps the biomoby-activity-ui can be moved to the
>>> taverna-extras repo until we clear this up. To me it doesn't seem worth
>>> expending  effort when most of the other apache taverna repos are almost
>>> there regards licences.
>> +1
>>
>>> Cheers,
>>>
>>> Ian
>> Alan
>>
>>



signature.asc
Description: OpenPGP digital signature

Re: Graduation?

[Ian Dunlop]

Hello,

Does anyone know who Martin Senger is so we can clear up the licence on
taverna-biomoby-activity-ui/src/main/java/net/sf/taverna/t2/activities/biomoby/query/CacheImpl.java

As it stands it's LGPL. Is CacheImpl.java used anywhere? A quick search
didn't reveal anything. Can we just delete it and worry about it later?

Cheers,

Ian

On 25/01/17 10:50, Ian Dunlop wrote:
> Hello,
>
> If we move any of the codebases with licences that need to be checked to
> taverna-extras does that cause problems in the future. Can we then fix
> them outside of the the apache repo and then move them back in when they
> are ready?
>
> Out of all of these codebases what ones do we really, really, really
> need to part of Apache Taverna at graduation. I think it would be good
> to have taverna-server. I'm not fussed about workbench right now.
>
> Cheers,
>
> Ian
>
> On 24/01/17 11:01, Ian Dunlop wrote:
>> Hello,
>>
>> We've stalled a bit on the graduation discussion. To help a bit I
>> created a few sub-pages with apache rat licence/header output for
>> various projects - see
>> https://cwiki.apache.org/confluence/display/TAVERNADEV/2016-09+License+review.
>> Which of these source files etc needs changed? Some of them are just for
>> test purposes so can we just exclude them? Some of them are used by
>> source code to build workflow activities. I was concerned that adding
>> headers to them could break them - is that the case? Which things do we
>> need to capture in NOTICE files?
>>
>> What do we need to do for graduation? We've had a few releases. The
>> community has grown. What is there stopping the project from going for
>> graduation?
>>
>> Cheers,
>>
>> Ian
>>
>>
>




signature.asc
Description: OpenPGP digital signature

Re: Graduation?

[Ian Dunlop]

Hello,

If we move any of the codebases with licences that need to be checked to
taverna-extras does that cause problems in the future. Can we then fix
them outside of the the apache repo and then move them back in when they
are ready?

Out of all of these codebases what ones do we really, really, really
need to part of Apache Taverna at graduation. I think it would be good
to have taverna-server. I'm not fussed about workbench right now.

Cheers,

Ian

On 24/01/17 11:01, Ian Dunlop wrote:
> Hello,
>
> We've stalled a bit on the graduation discussion. To help a bit I
> created a few sub-pages with apache rat licence/header output for
> various projects - see
> https://cwiki.apache.org/confluence/display/TAVERNADEV/2016-09+License+review.
> Which of these source files etc needs changed? Some of them are just for
> test purposes so can we just exclude them? Some of them are used by
> source code to build workflow activities. I was concerned that adding
> headers to them could break them - is that the case? Which things do we
> need to capture in NOTICE files?
>
> What do we need to do for graduation? We've had a few releases. The
> community has grown. What is there stopping the project from going for
> graduation?
>
> Cheers,
>
> Ian
>
>




signature.asc
Description: OpenPGP digital signature

Workbench product build failure

[Ian Dunlop]

Hello,

While going through the repos checking licences with rat I noticed that
workbench product fails to build on my machine. Seems it doesn't like
${taverna.osgi.verion}. Any ideas why or how to get round this?

mvn 3.3.9

Java 1.8

Ubuntu 16.04

Cheers,

Ian

[INFO] Scanning for projects...
[WARNING] The POM for
org.apache.taverna.maven.plugins:taverna-maven-plugin:jar:${taverna.osgi.verion}
is missing, no dependency information available
[ERROR] [ERROR] Some problems were encountered while processing the POMs:
[ERROR] Unresolveable build extension: Plugin
org.apache.taverna.maven.plugins:taverna-maven-plugin:${taverna.osgi.verion}
or one of its dependencies could not be resolved: Failure to find
org.apache.taverna.maven.plugins:taverna-maven-plugin:jar:${taverna.osgi.verion}
in https://repo.maven.apache.org/maven2 was cached in the local
repository, resolution will not be reattempted until the update interval
of central has elapsed or updates are forced @
[ERROR] Unknown packaging: taverna-application @
org.apache.taverna.workbench:apache-taverna-workbench-product:[unknown-version],
/home/ian/code/incubator-taverna-workbench-product/pom.xml, line 13,
column 13
[ERROR] 'build.plugins.plugin.version' for
org.apache.taverna.maven.plugins:taverna-maven-plugin must be a valid
version but is '${taverna.osgi.verion}'. @
org.apache.taverna.workbench:apache-taverna-workbench-product:[unknown-version],
/home/ian/code/incubator-taverna-workbench-product/pom.xml, line 139,
column 14
 @
[ERROR] The build could not read 1 project -> [Help 1]
[ERROR]  
[ERROR]   The project
org.apache.taverna.workbench:apache-taverna-workbench-product:2-incubating
(/home/ian/code/incubator-taverna-workbench-product/pom.xml) has 3 errors
[ERROR] Unresolveable build extension: Plugin
org.apache.taverna.maven.plugins:taverna-maven-plugin:${taverna.osgi.verion}
or one of its dependencies could not be resolved: Failure to find
org.apache.taverna.maven.plugins:taverna-maven-plugin:jar:${taverna.osgi.verion}
in https://repo.maven.apache.org/maven2 was cached in the local
repository, resolution will not be reattempted until the update interval
of central has elapsed or updates are forced -> [Help 2]
[ERROR] Unknown packaging: taverna-application @
org.apache.taverna.workbench:apache-taverna-workbench-product:[unknown-version],
/home/ian/code/incubator-taverna-workbench-product/pom.xml, line 13,
column 13
[ERROR] 'build.plugins.plugin.version' for
org.apache.taverna.maven.plugins:taverna-maven-plugin must be a valid
version but is '${taverna.osgi.verion}'. @
org.apache.taverna.workbench:apache-taverna-workbench-product:[unknown-version],
/home/ian/code/incubator-taverna-workbench-product/pom.xml, line 139,
column 14
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the
-e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions,
please read the following articles:
[ERROR] [Help 1]
http://cwiki.apache.org/confluence/display/MAVEN/ProjectBuildingException
[ERROR] [Help 2]
http://cwiki.apache.org/confluence/display/MAVEN/PluginManagerException




signature.asc
Description: OpenPGP digital signature

Re: Taverna server and users

[Ian Dunlop]

Hello,

Well I guess my question is now "How do you authenticate against it". Is
it basic auth http://username:passw...@tavernaserver.com ?

Cheers,

Ian


On 02/12/16 13:57, alaninmcr wrote:
> On 02/12/2016 12:55, Ian Dunlop wrote:
>> Hello,
>
> Hello Ian
>
>> I've figured out how to secure it and admin it to add users but I
>> haven't managed to figure out how you tell the server that a run is for
>> a specific user. I guess it is something  around "Resource:
>> /runs/{id}/security" but I can't figure out what.
>
> I'm not sure I understand the problem. Isn't the run "for" the user
> who authenticates and creates the run?
>
>> What is the "workflow"
>> for telling the server that a run is created for a specific user so that
>> no one else can see it? Is there a user guide rather than the API
>> listing?
>>
>> I think if we want Apache to set up a tavserv for us then we will need
>> this per user auth. Plus we will need it if we want to use it directly
>> from TavMob rather than via the player portal.
>>
>> Cheers,
>>
>> Ian
>
> Alan




signature.asc
Description: OpenPGP digital signature

Taverna server and users

[Ian Dunlop]

Hello,

I've figured out how to secure it and admin it to add users but I
haven't managed to figure out how you tell the server that a run is for
a specific user. I guess it is something  around "Resource:
/runs/{id}/security" but I can't figure out what. What is the "workflow"
for telling the server that a run is created for a specific user so that
no one else can see it? Is there a user guide rather than the API listing?

I think if we want Apache to set up a tavserv for us then we will need
this per user auth. Plus we will need it if we want to use it directly
from TavMob rather than via the player portal.

Cheers,

Ian




signature.asc
Description: OpenPGP digital signature

Re: Towards graduation of Taverna

[Ian Dunlop]

Hello,

There are some 'test' files in workbench that rat complains about:

 
incubator-taverna-workbench/taverna-renderers-impl/src/test/resources/test.svg
 
incubator-taverna-workbench/taverna-renderers-impl/src/test/resources/test.html
 
incubator-taverna-workbench/taverna-renderers-impl/src/test/resources/test.xml
 
incubator-taverna-workbench/taverna-renderers-impl/src/test/resources/test.txt
 
incubator-taverna-workbench/taverna-renderers-impl/src/test/resources/test.csv

These may or may not need headers according to
https://www.apache.org/legal/src-headers.html#faq-exceptions. You
probably can't have comments in csv anyway.

We may have to add an excludes file to each project
http://creadur.apache.org/rat/apache-rat-plugin/check-mojo.html#excludesFile

Cheers,

Ian

On 30/11/16 10:11, Ian Dunlop wrote:
> Hello,
>
> There are lots of files in
> incubator-taverna-workbench-common-activities-ian/taverna-localworker-activity-ui/src/main/resources/
> which do not have apache headers. Some of these look like t2flows and
> others are JSON. The ones which look like t2flows do not have a file
> extension. Is it safe to put the header in them? Will it break something
> later. As far as I know you can't put a comment in a JSON file so what
> is the best way to handle this? Do they need the apache headers at all?
> Is a licence file which lists all these files the way to approach it. Or
> is this the thing that a NOTICE file would cover?
>
> Cheers,
> Ian
>
> On 30/11/16 09:49, Ian Dunlop wrote:
>> Hello,
>>
>> I've put a couple of pull requests in for taverna server xsd headers and
>> workbench-common-activities pom headers. It's worth a quick scan by
>> someone to check they look ok.
>>
>> Cheers,
>>
>> Ian
>>
>>
>> On 28/11/16 15:16, Sagar wrote:
>>> Hello,
>>>
>>> Congratulations @stain for promotion.
>>>
>>> On Mon 28 Nov, 2016 7:29 pm Ian Dunlop, <ianwdun...@gmail.com> wrote:
>>>
>>>> Hello,
>>>>
>>>> Congrats on the Incubator promotion Stian. Sounds like a good idea if
>>>> you become a Taverna mentor. Now, I've got this idea for a project I'd
>>>> like to pitch to you...;)
>>>>
>>>> Cheers,
>>>>
>>>> Ian
>>>>
>>>>
>>>> On 23/11/16 22:25, Gale Naylor wrote:
>>>>> Congratulations, Stian! Even though we appear to be close to graduation,
>>>> is
>>>>> there any reason, *not* to add yourself as a mentor? You can add it to
>>>> your
>>>>> resume. ;)
>>>>>
>>>>> On Wed, Nov 23, 2016, 6:42 AM Stian Soiland-Reyes <st...@apache.org>
>>>> wrote:
>>>>> On 23 November 2016 at 14:10, Andy Seaborne <a...@apache.org> wrote:
>>>>>> PS Stian - I don't see why you can't add your self as a mentor.
>>>>> No need for that if we graduate? :-)
>>>>>
>>>>>
>>>>> Folks - Andy is referring to the fact I was just voted to be a member
>>>>> of the Incubator PMC.  So technically I could now be a mentor for
>>>>> Taverna (and i guess Andy relax slightly).
>>>>>
>>>>> Should I add myself as mentor?
>>>>>
>>>>>
>>>>> BTW, I see we also need to update
>>>>> http://incubator.apache.org/projects/taverna.html to list the new
>>>>> committers.
>>>>>
>>>>> --
>>>>> Stian Soiland-Reyes
>>>>> http://orcid.org/-0001-9842-9718
>>>>>
>




signature.asc
Description: OpenPGP digital signature

Re: Towards graduation of Taverna

[Ian Dunlop]

Hello,

There are lots of files in
incubator-taverna-workbench-common-activities-ian/taverna-localworker-activity-ui/src/main/resources/
which do not have apache headers. Some of these look like t2flows and
others are JSON. The ones which look like t2flows do not have a file
extension. Is it safe to put the header in them? Will it break something
later. As far as I know you can't put a comment in a JSON file so what
is the best way to handle this? Do they need the apache headers at all?
Is a licence file which lists all these files the way to approach it. Or
is this the thing that a NOTICE file would cover?

Cheers,
Ian

On 30/11/16 09:49, Ian Dunlop wrote:
> Hello,
>
> I've put a couple of pull requests in for taverna server xsd headers and
> workbench-common-activities pom headers. It's worth a quick scan by
> someone to check they look ok.
>
> Cheers,
>
> Ian
>
>
> On 28/11/16 15:16, Sagar wrote:
>> Hello,
>>
>> Congratulations @stain for promotion.
>>
>> On Mon 28 Nov, 2016 7:29 pm Ian Dunlop, <ianwdun...@gmail.com> wrote:
>>
>>> Hello,
>>>
>>> Congrats on the Incubator promotion Stian. Sounds like a good idea if
>>> you become a Taverna mentor. Now, I've got this idea for a project I'd
>>> like to pitch to you...;)
>>>
>>> Cheers,
>>>
>>> Ian
>>>
>>>
>>> On 23/11/16 22:25, Gale Naylor wrote:
>>>> Congratulations, Stian! Even though we appear to be close to graduation,
>>> is
>>>> there any reason, *not* to add yourself as a mentor? You can add it to
>>> your
>>>> resume. ;)
>>>>
>>>> On Wed, Nov 23, 2016, 6:42 AM Stian Soiland-Reyes <st...@apache.org>
>>> wrote:
>>>> On 23 November 2016 at 14:10, Andy Seaborne <a...@apache.org> wrote:
>>>>> PS Stian - I don't see why you can't add your self as a mentor.
>>>> No need for that if we graduate? :-)
>>>>
>>>>
>>>> Folks - Andy is referring to the fact I was just voted to be a member
>>>> of the Incubator PMC.  So technically I could now be a mentor for
>>>> Taverna (and i guess Andy relax slightly).
>>>>
>>>> Should I add myself as mentor?
>>>>
>>>>
>>>> BTW, I see we also need to update
>>>> http://incubator.apache.org/projects/taverna.html to list the new
>>>> committers.
>>>>
>>>> --
>>>> Stian Soiland-Reyes
>>>> http://orcid.org/-0001-9842-9718
>>>>
>>>
>




signature.asc
Description: OpenPGP digital signature

Re: Towards graduation of Taverna

[Ian Dunlop]

Hello,

I've put a couple of pull requests in for taverna server xsd headers and
workbench-common-activities pom headers. It's worth a quick scan by
someone to check they look ok.

Cheers,

Ian


On 28/11/16 15:16, Sagar wrote:
> Hello,
>
> Congratulations @stain for promotion.
>
> On Mon 28 Nov, 2016 7:29 pm Ian Dunlop, <ianwdun...@gmail.com> wrote:
>
>> Hello,
>>
>> Congrats on the Incubator promotion Stian. Sounds like a good idea if
>> you become a Taverna mentor. Now, I've got this idea for a project I'd
>> like to pitch to you...;)
>>
>> Cheers,
>>
>> Ian
>>
>>
>> On 23/11/16 22:25, Gale Naylor wrote:
>>> Congratulations, Stian! Even though we appear to be close to graduation,
>> is
>>> there any reason, *not* to add yourself as a mentor? You can add it to
>> your
>>> resume. ;)
>>>
>>> On Wed, Nov 23, 2016, 6:42 AM Stian Soiland-Reyes <st...@apache.org>
>> wrote:
>>> On 23 November 2016 at 14:10, Andy Seaborne <a...@apache.org> wrote:
>>>> PS Stian - I don't see why you can't add your self as a mentor.
>>> No need for that if we graduate? :-)
>>>
>>>
>>> Folks - Andy is referring to the fact I was just voted to be a member
>>> of the Incubator PMC.  So technically I could now be a mentor for
>>> Taverna (and i guess Andy relax slightly).
>>>
>>> Should I add myself as mentor?
>>>
>>>
>>> BTW, I see we also need to update
>>> http://incubator.apache.org/projects/taverna.html to list the new
>>> committers.
>>>
>>> --
>>> Stian Soiland-Reyes
>>> http://orcid.org/-0001-9842-9718
>>>
>>
>>




signature.asc
Description: OpenPGP digital signature

Re: Towards graduation of Taverna

[Ian Dunlop]

Hello,

Congrats on the Incubator promotion Stian. Sounds like a good idea if
you become a Taverna mentor. Now, I've got this idea for a project I'd
like to pitch to you...;)

Cheers,

Ian


On 23/11/16 22:25, Gale Naylor wrote:
> Congratulations, Stian! Even though we appear to be close to graduation, is
> there any reason, *not* to add yourself as a mentor? You can add it to your
> resume. ;)
>
> On Wed, Nov 23, 2016, 6:42 AM Stian Soiland-Reyes  wrote:
>
> On 23 November 2016 at 14:10, Andy Seaborne  wrote:
>> PS Stian - I don't see why you can't add your self as a mentor.
> No need for that if we graduate? :-)
>
>
> Folks - Andy is referring to the fact I was just voted to be a member
> of the Incubator PMC.  So technically I could now be a mentor for
> Taverna (and i guess Andy relax slightly).
>
> Should I add myself as mentor?
>
>
> BTW, I see we also need to update
> http://incubator.apache.org/projects/taverna.html to list the new
> committers.
>
> --
> Stian Soiland-Reyes
> http://orcid.org/-0001-9842-9718
>




signature.asc
Description: OpenPGP digital signature

Re: Tav Server admin

[Ian Dunlop]

Hello,

I have added some notes about default users in pull request
https://github.com/taverna-extras/taverna-server-docker/pull/1

Cheers,

Ian

On 17/11/16 19:55, Alan Williams wrote:
> On 17-Nov-16 16:21, Stian Soiland-Reyes wrote:
>> The docker job adds this users.properties:
>>
>> https://github.com/taverna-extras/taverna-server-docker/blob/master/users.properties
>>
>>
>> which claims to have admin/ADMIN - remember casing in the password!
>
> Interesting! I checked the server code and that isn't the default
> there. I guess that's why it was changed :)
>
> Is it in the documentation of the docker image, because otherwise it
> will be very confusing (as it was for Ian).
>
>> (See that repo for the rest of the Docker stuff)
>
> Alan
>




signature.asc
Description: OpenPGP digital signature

Re: Tav Server admin

[Ian Dunlop]

Hello,

That's better. Upper case. Really! Security by obscurity worked in this
case :) I looked at that file but didn't realise that was the default
password.

Thanks Stian. And also Alan for the docker exec tip - you learn
something new every day, in this case

"docker exec -i -t taverna /bin/bash" to access the container shell.

Cheers,

Ian

On 17/11/16 16:21, Stian Soiland-Reyes wrote:
> The docker job adds this users.properties:
>
> https://github.com/taverna-extras/taverna-server-docker/blob/master/users.properties
>
> which claims to have admin/ADMIN - remember casing in the password!
>
>
> (See that repo for the rest of the Docker stuff)
>
>
> On 17 November 2016 at 16:07, Ian Dunlop <ianwdun...@gmail.com> wrote:
>> Hello,
>>
>> I have docker exec'd into the container and looked at tomcat/logs. The
>> access is being logged and reported as 403 but not the reason (well, 403
>> is the reason I guess!). It doesn't even give me a chance to enter
>> username password now. I might delete the container and try again.
>>
>> Cheers,
>>
>> Ian
>>
>> On 17/11/16 15:01, Alan Williams wrote:
>>> On 17-Nov-16 14:55, Ian Dunlop wrote:
>>>> Hello,
>>>>
>>>> That's the page I would like to see :) but it's not letting me. docker
>>>> logs doesn't reveal a whole lot beyond server startup. Nothing after:
>>>>
>>>> "Nov 17, 2016 2:04:03 PM org.apache.catalina.startup.Catalina start
>>>> INFO: Server startup in 10757 ms"
>>> Can you ssh into the docker using docker exec?
>>>
>>>> Cheers,
>>>>
>>>> Ian
>>> Alan
>>>
>>
>
>




signature.asc
Description: OpenPGP digital signature

Re: Tav Server admin

[Ian Dunlop]

Hello,

That's the page I would like to see :) but it's not letting me. docker
logs doesn't reveal a whole lot beyond server startup. Nothing after:

"Nov 17, 2016 2:04:03 PM org.apache.catalina.startup.Catalina start
INFO: Server startup in 10757 ms"

Cheers,

Ian

On 17/11/16 14:22, Alan Williams wrote:
> On 17-Nov-16 14:06, Ian Dunlop wrote:
>> Hello,
>>
>> I get a 403 Access Denied with what the admin guide says are the default
>> username/password. Debugging this docker stuff is way harder than it
>> should be. I'm tempted to go back to bare metal Tomcat.
>
> OK. Can you check in the docker what it receives and what it expects?
>
> I have checked on the Taverna Server behind the BioVeL portal, and
> there is an admin page. Not sure if an attachment will come through so
> look at https://www.dropbox.com/s/i8dc6wmyrwzipwy/server.PNG?dl=0
>
>> Cheers,
>>
>> Ian
>
> Alan




signature.asc
Description: OpenPGP digital signature

Re: Tav Server admin

[Ian Dunlop]

Hello,

I get a 403 Access Denied with what the admin guide says are the default
username/password. Debugging this docker stuff is way harder than it
should be. I'm tempted to go back to bare metal Tomcat.

Cheers,

Ian


On 17/11/16 13:52, Alan Williams wrote:
> On 17-Nov-16 12:27, Ian Dunlop wrote:
>> Hello,
>>
>> I'm using the docker taverna/taverna-server image and want to add
>> users/change passwords etc.So.
>>
>> 1) Is it possible to admin a Taverna Server instance through a web
>> interface? Is "Component: Taverna/Server/Users" in the admin guide
>> (http://dev.mygrid.org.uk/wiki/display/tav250/Administration+Guide)
>> referring to Java code or a web app?
>
> There is definitely an admin web page. It is normally at
> /tavernaserver/admin . I am not sure what can be administered from there.
>
>> 2) How do you access the WEB-INF/user.properties file in a docker image
>> so that you can change it? How can you persist it between container
>> restarts?
>
> I think (but am not completely certain) that the changes done in the
> admin pane are saved in the server's database. That is read in
> preference to the user.properties file. user.properties specifies the
> properties to be used initially (when there are no values in the
> database).
>
>> Cheers,
>>
>> Ian
>
> Alan
>




signature.asc
Description: OpenPGP digital signature

Tav Server admin

[Ian Dunlop]

Hello,

I'm using the docker taverna/taverna-server image and want to add
users/change passwords etc.So.

1) Is it possible to admin a Taverna Server instance through a web
interface? Is "Component: Taverna/Server/Users" in the admin guide
(http://dev.mygrid.org.uk/wiki/display/tav250/Administration+Guide)
referring to Java code or a web app?

2) How do you access the WEB-INF/user.properties file in a docker image
so that you can change it? How can you persist it between container
restarts?

Cheers,

Ian




signature.asc
Description: OpenPGP digital signature

[jira] [Deleted] (TAVERNA-943) Implementing MVP Framework in the code structure

[Ian Dunlop (JIRA)]

 [ 
https://issues.apache.org/jira/browse/TAVERNA-943?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ian Dunlop deleted TAVERNA-943:
---


> Implementing MVP Framework in the code structure
> 
>
> Key: TAVERNA-943
> URL: https://issues.apache.org/jira/browse/TAVERNA-943
> Project: Apache Taverna
>  Issue Type: New Feature
> Environment: Android Studio 1.5.1
>Reporter: Rajan Maurya
>  Labels: features
>   Original Estimate: 168h
>  Remaining Estimate: 168h
>
> Currently everything is written at same place like initiating view , Calling 
> API for data, saving data for offline. there are fully dependent to each 
> other. so if any developer want to change or add the feature, he have to 
> read, configure the whole code. that is not a good practice to write the code 
> and it make very hard to contribute.
> After long time current project will be depreciated. if no one will 
> contribute to project.
> Implementing The MVP framework in the project so that every work will be run 
> in the different layer architecture. and every layer have its own work and 
> fully independent to other layer. Layers call to other layer for data ,for 
> loading data, for calling REST API etc.
> The layers are :
> 1. View (UI Layer) : this is where Activities, Fragments and other standard 
> Android components live. It's responsible
>for displaying the data received from 
> the presenters to the user.
> 2.Presenter: Presenters subscribe to RxJava Observables provided by the 
> DataManager. They are in charge of handling the subscription lifecycle, 
> analysing/modifying the data returned by the DataManager and calling the 
> appropriate methods in the View in order to display the data.
> 3.Model (Data Layer): this is responsible for retrieving, saving, 
> caching and messaging data. It can communicate with local databases and other 
> data stores as well as with restful APIs or third party SDKs. It is divided 
> in two parts: a group of helpers and a DataManager.
> These are some basic layers that will be in the project architecture:
> Source: https://github.com/ribot/android-boilerplate  and 
> https://msdn.microsoft.com/en-us/library/ff649571.aspx



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (TAVERNA-984) Code Analysis Tools Implementation

[Ian Dunlop (JIRA)]

[ 
https://issues.apache.org/jira/browse/TAVERNA-984?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15670022#comment-15670022
 ] 

Ian Dunlop commented on TAVERNA-984:


I think the build system is using Checkstyle already (I should know - I keep 
getting pinged by it - sorry!). Not sure about PMD & Findbugs. Are we using 
these. If not do we need them?

> Code Analysis Tools Implementation
> --
>
> Key: TAVERNA-984
> URL: https://issues.apache.org/jira/browse/TAVERNA-984
> Project: Apache Taverna
>  Issue Type: Bug
>  Components: Taverna Mobile
>Affects Versions: parent 1
> Environment: Android Studio 2.1.2
>Reporter: Rajan Maurya
>  Labels: features
> Fix For:  mobile 1.0.0
>
>   Original Estimate: 72h
>  Remaining Estimate: 72h
>
> Implementing Code Analysis tools so future development has the standard for 
> code style and some logical error will not occur and  checking the java 
> standard  rule and warning to the developer and some logical and generic 
> warning will also be displayed. 
> There are three Tools for implementation :
> 1. CheckStyle
> 2. PMD tool
> 3. Findbugs



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (TAVERNA-1012) Add "Open-source licenses" to menu

[Ian Dunlop (JIRA)]

[ 
https://issues.apache.org/jira/browse/TAVERNA-1012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15670017#comment-15670017
 ] 

Ian Dunlop commented on TAVERNA-1012:
-

Licences added to dashboard menu option. All the original licences & copyrights 
are now shown. Notices still to do - what exactly do we need to include?

> Add "Open-source licenses" to menu
> --
>
> Key: TAVERNA-1012
> URL: https://issues.apache.org/jira/browse/TAVERNA-1012
> Project: Apache Taverna
>  Issue Type: New Feature
>  Components: Taverna Mobile
>Reporter: Stian Soiland-Reyes
>Priority: Critical
> Fix For:  mobile 1.0.0
>
>
> As discussed on 
> [dev@taverna|https://lists.apache.org/thread.html/b374b2aa60af1231cd63bf405ed7a3fa557d5882d958e0bfd334f5bb@%3Cdev.taverna.apache.org%3E]:
> Add a menu item, something like
> > Settings -> Help & feedback -> Open-source licenses
> to show the LICENSE.txt and NOTICE.txt
> including those we are required to propagate from third-party libraries 
> bundled inside the .apk.
> To check what we are required to propagate it should be sufficient to check 
> the licenses of our dependencies and look if the inside of the JARs already 
> have a NOTICE or LICENSE file or similar.  
> (E.g. an Apache-licensed JAR with no NOTICE file? Nothing more to do.  A JAR 
> with a BSD-3 LICENSE file? We need to show that)
> Sadly tooling for this is still a bit abysmal, so we probably have to create 
> that text file manually.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: Create 'develop' branch for tavmob

[Ian Dunlop]

Hello,

So maybe we just have a policy of always creating a branch for pull
requests. Then if no one merges it within a week you can merge it
yourself. This means that any contributors can just branch off master.
Then we can create a branch for releases as well based off master. I'm
not sure how we would deal with fixes that need to be applied to a
release, some git fu may be needed to sort that one out.

Cheers,

Ian


On 07/11/16 14:33, Stuart Owen wrote:
>
>
> On 07/11/16 14:15, Alan Williams wrote:
>> On 07-Nov-16 13:45, Gale Naylor wrote:
>>> I was thinking the master was the latest release, too, but I have no
>>> strong
>>> feelings either way.
>>
>> I think the releases are tagged on the master branch, and the master
>> branch is the main development one, with "side" branches for new
>> features. That is how it is done in, for example,
>> incubator-taverna-commandline. That is also how other open source
>> projects I use work.
>>
>> It does have the drawback that you cannot easily be preparing a
>> release and continuing to develop at the same time. I don't think we
>> have a large enough community to worry about that though.
> I've always worked with having the 'master' branch for main
> development, working on feature branches and branches for preparing
> releases. There is nothing to prevent work continuing when preparing a
> release, as you just fork off a branch for that release version and
> start stabilizing and polishing it, whilst risky new development
> continues on the master branch. You also then always have a branch to
> come back to for small bug fixes for past releases which get
> increasingly more stable.
>
> Keeping development on the master branch also has the advantage of
> making your project appear as active as it is, and also makes it
> simpler for pull requests.
>
> Stuart.
>>
>> Alan
>>
>>
>




signature.asc
Description: OpenPGP digital signature

To pull or not to pull

[Ian Dunlop]

Hello,

I think we need a policy decision on how to add new code to existing
projects. Apache Taverna commiters can just merge straight into master
but perhaps we should have a policy of using pull requests so that we
can review the code first. It might mean there is a slight overhead but
maybe long term it means we get better code out of it. Myself and Sagar
were just having a chat about this with respect to the TavMob project so
it might not be appropriate for every repo.

Discuss.

Cheers,

Ian




signature.asc
Description: OpenPGP digital signature

Re: Create 'develop' branch for tavmob

[Ian Dunlop]

Hello,

Yes we can tag the master branch and then create develop from it.

Cheers,

Ian

On 03/11/16 13:56, Rajan Maurya wrote:
> It's one of the Cool thing to manage the code, It's awesome but I think, we
> should make at least a github relase before shifting the master a main
> default branch.
>
> Thanks.
>




signature.asc
Description: OpenPGP digital signature

Re: Welcome to Sagar and Rajan

[Ian Dunlop]

Hello

I guess the quick way to find out is to try pushing to the Apache repo 
If not then it is pull request  (until someone gives you commit access).

Cheers

Ian

On 2 Nov 2016 14:39, "Rajan Maurya" <rajanmaurya...@gmail.com> wrote:

> Yeah, It's ok.
>
> I want to ask one thing, for changing "role". I have to open PR for that or
> I can push the commit directly to the repository.
>
> Thanks.
>
> On Wed, Nov 2, 2016 at 6:51 PM, Stian Soiland-Reyes <st...@apache.org>
> wrote:
>
> > Rajan, would you be OK to add yourself to the pom.xml here?
> >
> > https://github.com/apache/incubator-taverna-maven-
> > parent/blob/master/pom.xml
> >
> > You can change your  to Committer like Sagar.
> >
> >
> > (I know taverna-maven-parent as a super-pom is not used by Taverna
> > Mobile, as it probably would not make sense for Taverna Mobile to be
> > deployed to Maven Central.. although it is possible:
> >   https://docs.gradle.org/current/userguide/maven_plugin.html
> >   https://docs.gradle.org/current/userguide/publishing_maven.html
> > )
> >
> >
> > Also if you would want to update the website for your listing on
> >
> > https://taverna.incubator.apache.org/about/
> >
> > then see
> > https://taverna.incubator.apache.org/community/edit
> > on how to edit the Taverna website.
> >
> >
> >
> > On 1 November 2016 at 12:44, Gale Naylor <ga...@noventussolutions.com>
> > wrote:
> > > Welcome, Sagar and Rajan!
> > >
> > > On Nov 1, 2016 2:05 AM, "Ian Dunlop" <ianwdun...@gmail.com> wrote:
> > >
> > >> Hello,
> > >>
> > >> The Apache Taverna PPMC would like to formally welcome Rajan Maurya
> > >> (rajanmaurya...@apache.org) and Sagar (sa...@apache.org) to the
> Apache
> > >> Taverna community. They have both been helping out a lot with many
> great
> > >> code contributions over the last few months and are now Apache Taverna
> > >> committers. Welcome to you both.
> > >>
> > >> Cheers,
> > >>
> > >> Ian
> > >>
> > >>
> > >>
> >
> >
> >
> > --
> > Stian Soiland-Reyes
> > http://orcid.org/-0001-9842-9718
> >
>
>
>
> --
> *Thanks*
> *Namaste*
>
> Rajan Maurya
> Contact Number : +91 8010665248
> Github : https://github.com/therajanmaurya
> College : Cluster Innovation Centre, University of Delhi
> Student : B.Tech. (Information Technology & Mathematical Innovations)
>

Re: Fwd: Re: ASF for Google Code-In

[Ian Dunlop]

Hello,

Looking at the apache ComDev list there may be some legal issues with
the code-in so I wouldn't get too excited about it yet. We could still
make the app apk available for testers to use anyway.

Cheers,

Ian


On 01/11/16 10:03, Sagar wrote:
> Hello,
>
> I also agree with @stain and @ian.
> And It will help us to know first user view of taverna mobile before
> release. If we found some bug we can remove it.
> Finally, We will get fewer bugs product.
>
> On Tue, Nov 1, 2016 at 3:09 PM, Ian Dunlop <ianwdun...@gmail.com> wrote:
>
>> Hello,
>>
>> Testing the android app on real phones would be great. They would have
>> to compile the app themselves though or connect it via android studio
>> since we have no release yet. Maybe we could set up jenkins or similar
>> to build the app and create a dev apk after each code push.
>>
>> Cheers,
>>
>> Ian
>>
>> On 01/11/16 04:44, Gale Naylor wrote:
>>> I like the ideas Stian suggested. Sounds like a good way to give back!
>>>
>>> Gale
>>>
>>> On Oct 31, 2016 7:35 AM, "Stian Soiland-Reyes" <st...@apache.org> wrote:
>>>
>>> Google Code In was mentioned on the chat, now there is ASF interest to
>>> register as well. (See below)
>>>
>>> I think we can have a go, it is true that it will be many small efforts
>> as
>>> the participants are high-school age (13-17) with perhaps not much coding
>>> experience, but we can ask them to do non-coding things as well.
>>>
>>> Some ideas:
>>>
>>> * Test Android app on phones in the wild, report bugs/glitches
>>> * Style up our homepage, just some css and bootstrap skills
>>> * Make a new Taverna cog logo, preferably in svg
>>> * Twitter rep - find Taverna stuff and blog/tweet it
>>>
>>> Views..?
>>> -- Forwarded message --
>>> From: "Stian Soiland-Reyes" <st...@apache.org>
>>> Date: 31 Oct 2016 2:27 pm
>>> Subject: Re: ASF for Google Code-In
>>> To: <d...@community.apache.org>
>>> Cc:
>>>
>>> +1 to have a go, we discussed it in Taverna as well, we could give them
>>>> something to do in the Android app.
>>>>
>>>> It would be a bit similar to HelpWanted.apache.org I guess, but with
>>>> mentoring..? It would have to be quite bite-sized for high school
>>> students,
>>>> but you would probably also be surprised as to what some of them can do!
>>>>
>>>> On 30 Oct 2016 11:22 pm, "Roman Shaposhnik" <ro...@shaposhnik.org>
>> wrote:
>>>>> Hi!
>>>>>
>>>>> a project I mentor got interested in:
>>>>>  https://developers.google.com/open-source/gci/
>>>>>
>>>>> Has there been any attempts to have ASF
>>>>> as a mentoring organization there?
>>>>>
>>>>> The current list of orgs is pretty eclectic:
>>>>>https://codein.withgoogle.com/archive/2015/organization/
>>>>> but given that folks like Ubuntu are on the list
>>>>> I don't see why ASF shouldn't be.
>>>>>
>>>>> Thanks,
>>>>> Roman.
>>>>>
>>>>> -
>>>>> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
>>>>> For additional commands, e-mail: dev-h...@community.apache.org
>>>>>
>>>>>
>>
>>
>




signature.asc
Description: OpenPGP digital signature

Re: Access to Jankins for Apache Taverna Mobile

[Ian Dunlop]

Hello,

The process is detailed here
http://wiki.apache.org/general/Jenkins?action=show=Hudson#How_do_I_get_an_account

I'm not sure whether one of the Taverna PPMC can run these commands to
grant access - @Stian do you know?

Cheers,

Ian

On 31/10/16 10:52, Sagar wrote:
> Hi forks,
>
> May I get access to jankins for Apache Taverna Mobile So that i am able to
> retify the issue in jankins builds.
>




signature.asc
Description: OpenPGP digital signature

Re: Fwd: Re: ASF for Google Code-In

[Ian Dunlop]

Hello,

Testing the android app on real phones would be great. They would have
to compile the app themselves though or connect it via android studio
since we have no release yet. Maybe we could set up jenkins or similar
to build the app and create a dev apk after each code push.

Cheers,

Ian

On 01/11/16 04:44, Gale Naylor wrote:
> I like the ideas Stian suggested. Sounds like a good way to give back!
>
> Gale
>
> On Oct 31, 2016 7:35 AM, "Stian Soiland-Reyes"  wrote:
>
> Google Code In was mentioned on the chat, now there is ASF interest to
> register as well. (See below)
>
> I think we can have a go, it is true that it will be many small efforts as
> the participants are high-school age (13-17) with perhaps not much coding
> experience, but we can ask them to do non-coding things as well.
>
> Some ideas:
>
> * Test Android app on phones in the wild, report bugs/glitches
> * Style up our homepage, just some css and bootstrap skills
> * Make a new Taverna cog logo, preferably in svg
> * Twitter rep - find Taverna stuff and blog/tweet it
>
> Views..?
> -- Forwarded message --
> From: "Stian Soiland-Reyes" 
> Date: 31 Oct 2016 2:27 pm
> Subject: Re: ASF for Google Code-In
> To: 
> Cc:
>
> +1 to have a go, we discussed it in Taverna as well, we could give them
>> something to do in the Android app.
>>
>> It would be a bit similar to HelpWanted.apache.org I guess, but with
>> mentoring..? It would have to be quite bite-sized for high school
> students,
>> but you would probably also be surprised as to what some of them can do!
>>
>> On 30 Oct 2016 11:22 pm, "Roman Shaposhnik"  wrote:
>>
>>> Hi!
>>>
>>> a project I mentor got interested in:
>>>  https://developers.google.com/open-source/gci/
>>>
>>> Has there been any attempts to have ASF
>>> as a mentoring organization there?
>>>
>>> The current list of orgs is pretty eclectic:
>>>https://codein.withgoogle.com/archive/2015/organization/
>>> but given that folks like Ubuntu are on the list
>>> I don't see why ASF shouldn't be.
>>>
>>> Thanks,
>>> Roman.
>>>
>>> -
>>> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
>>> For additional commands, e-mail: dev-h...@community.apache.org
>>>
>>>




signature.asc
Description: OpenPGP digital signature

Welcome to Sagar and Rajan

[Ian Dunlop]

Hello,

The Apache Taverna PPMC would like to formally welcome Rajan Maurya
(rajanmaurya...@apache.org) and Sagar (sa...@apache.org) to the Apache
Taverna community. They have both been helping out a lot with many great
code contributions over the last few months and are now Apache Taverna
committers. Welcome to you both.

Cheers,

Ian




signature.asc
Description: OpenPGP digital signature

Re: Virtual machine for Taverna Player..?

[Ian Dunlop]

Hello,

I don't think there was any particular reason really. It just sort of
happened. Maybe it would be good to go for a purely t-server solution
just to reduce the deployment dependencies. The app is now modular
enough that swapping out one for the other shouldn't be too
horrible..maybe. JIRA issue perhaps?I really like the player though,
it's got a nice API (JSON :) )and a great UI. It's almost quicker to set
up a player user along with the server than it is to figure out how to
configure the server for multiple users. Especially with docker.

Cheers,

Ian


On 21/10/16 16:18, Stian Soiland-Reyes wrote:
> Could anyone remind me again as to why the Mobile app doesn't use Taverna
> server directly..?

Preparing for Taverna Mobile Release

[Ian Dunlop]

Hello,

In preparation for the TMobile release I have made a list of the
libraries/dependencies that I think are included in the Taverna Mobile
codebase:

https://cwiki.apache.org/confluence/display/TAVERNADEV/Taverna+Mobile+Licence+Review

We need to know all the licence details for these to ensure that they
are Apache compatible and include the list in the app - see
https://issues.apache.org/jira/browse/TAVERNA-1012.

Also, we may not require all of these libraries so now is a good time to
start removing them.

According to apache rat the source code all has the correct headers etc
as reflected at the top of that web page (you may remember I did the
check a few weeks ago).

Cheers,

Ian



0xDAEA877B.asc
Description: application/pgp-keys


signature.asc
Description: OpenPGP digital signature

[jira] [Commented] (TAVERNA-1012) Add "Open-source licenses" to menu

[Ian Dunlop (JIRA)]

[ 
https://issues.apache.org/jira/browse/TAVERNA-1012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15548268#comment-15548268
 ] 

Ian Dunlop commented on TAVERNA-1012:
-

See 
https://cwiki.apache.org/confluence/display/TAVERNADEV/Taverna+Mobile+Licence+Review
 for list of dependencies.

> Add "Open-source licenses" to menu
> --
>
> Key: TAVERNA-1012
> URL: https://issues.apache.org/jira/browse/TAVERNA-1012
> Project: Apache Taverna
>  Issue Type: New Feature
>  Components: Taverna Mobile
>Reporter: Stian Soiland-Reyes
>Priority: Critical
> Fix For:  mobile 1.0.0
>
>
> As discussed on 
> [dev@taverna|https://lists.apache.org/thread.html/b374b2aa60af1231cd63bf405ed7a3fa557d5882d958e0bfd334f5bb@%3Cdev.taverna.apache.org%3E]:
> Add a menu item, something like
> > Settings -> Help & feedback -> Open-source licenses
> to show the LICENSE.txt and NOTICE.txt
> including those we are required to propagate from third-party libraries 
> bundled inside the .apk.
> To check what we are required to propagate it should be sufficient to check 
> the licenses of our dependencies and look if the inside of the JARs already 
> have a NOTICE or LICENSE file or similar.  
> (E.g. an Apache-licensed JAR with no NOTICE file? Nothing more to do.  A JAR 
> with a BSD-3 LICENSE file? We need to show that)
> Sadly tooling for this is still a bit abysmal, so we probably have to create 
> that text file manually.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: Taverna release guidelines

[Ian Dunlop]

Hello,

Looking at http://www.apache.org/dev/release.html seems a good place to
start.

Cheers,

Ian

On 3 October 2016 at 10:02, Ian Dunlop <ianwdun...@gmail.com> wrote:

> Hello,
>
> It is probably better placed on the wiki with a link from the website. I
> guess the mobile release is all about building the apk. I guess we can GPG
> the release candidate. Not sure where we upload to on the apache
> infrastructure. Not every apache project is maven so we could just look at
> what they do.
>
> Cheers,
>
> Ian
>
> On 1 October 2016 at 19:30, Stian Soiland-Reyes <st...@apache.org> wrote:
>
>> The Juneau incubator podling has taken inspiration from our Taverna
>> release guidelines [1]
>> and produced a more detailed guidelines:
>>
>> https://cwiki.apache.org/confluence/display/JUNEAU/New+release+guidelines
>>
>>
>> Is there something here we could "merge back"? :) We also need to add
>> something about how to do the release for Taverna Mobile (which don't
>> use mvn) -- should we move our release guideline to the wiki or keep
>> it on the website?
>>
>>
>> [1] https://taverna.incubator.apache.org/community/releasing
>> --
>> Stian Soiland-Reyes
>> http://orcid.org/-0001-9842-9718
>>
>
>

Re: Taverna release guidelines

[Ian Dunlop]

Hello,

It is probably better placed on the wiki with a link from the website. I
guess the mobile release is all about building the apk. I guess we can GPG
the release candidate. Not sure where we upload to on the apache
infrastructure. Not every apache project is maven so we could just look at
what they do.

Cheers,

Ian

On 1 October 2016 at 19:30, Stian Soiland-Reyes  wrote:

> The Juneau incubator podling has taken inspiration from our Taverna
> release guidelines [1]
> and produced a more detailed guidelines:
>
> https://cwiki.apache.org/confluence/display/JUNEAU/New+release+guidelines
>
>
> Is there something here we could "merge back"? :) We also need to add
> something about how to do the release for Taverna Mobile (which don't
> use mvn) -- should we move our release guideline to the wiki or keep
> it on the website?
>
>
> [1] https://taverna.incubator.apache.org/community/releasing
> --
> Stian Soiland-Reyes
> http://orcid.org/-0001-9842-9718
>

Re: Website community updates

[Ian Dunlop]

Hello,

There is some new committer info https://community.apache.org/contributors/
and https://www.apache.org/dev/new-committers-guide.html. We can link or
crib a few notes from there.

Cheers,

Ian

On 28 September 2016 at 00:02, Gale Naylor 
wrote:

> I like the changes! (Especially the Who Are We page and separators for the
> web menu.) I also like the extended Incubator status.
>
> I wonder if we need to have the incubator status on the Who Are We page? It
> seems to me it's enough to put it on the home page.
>
> >>   Community -> Contribute now goes to
> >>
> https://taverna.incubator.apache.org/download/code/#
> contribute-to-apache-taverna
> >>   instead of the confusing section
> >>   https://taverna.incubator.apache.org/community/#contribute
>
> I like changing the Contribute link to the download/code page. And I agree
> that the contribute section on the community home page was confusing.
>
> I reformatted the contribute section on the Community/home page to make it
> less confusing (I hope). Let me know what you think about the change. (I
> also put mailing lists/ chat/ report bugs in it's own section called How to
> Communicate. Otherwise, it seemed like chat and bug reporting were a subset
> of mailing list.)
>
> If we create a separate page for How to Contribute would it include what's
> on the home page and the download/code page? Would it be useful to add more
> content about contributing workflows and hosting services, etc?
>
> Do we have something written about "How to become a committer?" It seems
> logical to me to put that information on a future How to Contribute page.
>
> Thanks!
> Gale
>
> On Sun, Sep 25, 2016 at 8:07 PM Stian Soiland-Reyes 
> wrote:
>
> > Hi, I've updated the Taverna website
> >
> > https://taverna.incubator.apache.org/community/lists
> > * Added ASF Code of conduct
> >
> > https://taverna.incubator.apache.org/community/irc
> > * Redirects to /community/chat
> >
> >
> > https://taverna.incubator.apache.org/community/chat
> > * Describe Gitter room
> > * ..but use mailing list for decisions!
> >
> > https://taverna.incubator.apache.org/about/
> > * Added Thilina as committer
> > * Listed contributors (including recent GSOC students)
> > * Incubator status: Linked to Graduation assessment
> >
> > https://taverna.incubator.apache.org/community/
> > * Moved Incubator status to the bottom
> > * Added Incubator disclaimer and link to Graduation assessment
> > * Added Web chat link
> >
> >
> > Menu changes:
> >
> > Added:
> > Community -> Who Are We?
> > https://taverna.incubator.apache.org/about/
> > (This was just linked to from the /community/ text before)
> >
> >
> > Community -> Contribute
> > now goes to
> >
> > https://taverna.incubator.apache.org/download/code/#
> contribute-to-apache-taverna
> > instead of the confusing section
> > https://taverna.incubator.apache.org/community/#contribute
> >
> > (should these merge to become a linkable /community/contribute page to
> > include non-code contribs -- perhaps this could also show how to
> > become a committer?)
> >
> >
> > Community ->
> > * Reordered items
> > * Added separators
> >
> >
> > You may have to do a Ctrl-Shift-R reload to see the changes.
> >
> >
> > Spot any Norwenglish typos or other comments?
> >
> >
> >
> > --
> > Stian Soiland-Reyes
> > http://orcid.org/-0001-9842-9718
> >
>