Re: Taverna Mobile NOTICE

2016-09-20 Thread Gale Naylor 
Could we put the license and notice in the "read more" section of the play
store window that is used to describe the app? Or a summary of the info?

On Tue, Sep 20, 2016, 3:12 AM Stian Soiland-Reyes  wrote:

> Hi,
>
> If we're going to release a Taverna Mobile binary .apk (or whatever
> the extension is today) - then that would also bundle the third-party
> dependencies, right?
>
> We would then need to include a variant of the LICENSE and NOTICE file
> - but how can that be readable from within the app?  (As you wouldn't
> "unzip" the app before installing it).  Do we need to use a "About"
> menu button where the user can scroll through the license?
>
>
> Also it would be good to check on the dependencies if they have their
> own NOTICE files - it should be easy by just looking inside their JAR
> files and copy out whatever is there. If they don't have, and they are
> also Apache licensed, then there should be nothing more to do. BSD
> licensed ones however would need to comply with
>
> > 2. Redistributions in binary form must reproduce the above copyright
> notice, this list of conditions and the following disclaimer in the
> documentation and/or other materials provided with the distribution.
>
> I am not sure if we could get away with that by not providing
> documentation or materials :)
>
> --
> Stian Soiland-Reyes
> http://orcid.org/-0001-9842-9718
>

Taverna Mobile NOTICE

2016-09-20 Thread Stian Soiland-Reyes 
Hi,

If we're going to release a Taverna Mobile binary .apk (or whatever
the extension is today) - then that would also bundle the third-party
dependencies, right?

We would then need to include a variant of the LICENSE and NOTICE file
- but how can that be readable from within the app?  (As you wouldn't
"unzip" the app before installing it).  Do we need to use a "About"
menu button where the user can scroll through the license?


Also it would be good to check on the dependencies if they have their
own NOTICE files - it should be easy by just looking inside their JAR
files and copy out whatever is there. If they don't have, and they are
also Apache licensed, then there should be nothing more to do. BSD
licensed ones however would need to comply with

> 2. Redistributions in binary form must reproduce the above copyright notice, 
> this list of conditions and the following disclaimer in the documentation 
> and/or other materials provided with the distribution.

I am not sure if we could get away with that by not providing
documentation or materials :)

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

Re: Taverna Mobile Release

2016-09-20 Thread Stian Soiland-Reyes 
Brilliant!

Now let's think about the release procedure - it would be our first
release using Gradle instead of Maven.

I guess we would need to update/fork
https://taverna.incubator.apache.org/community/releasing after finding
out what are the equivalent commands/actions.


Perhaps add it as a RELEASING.md file to the taverna-mobile repository
as it would only apply for that one?


On 20 September 2016 at 10:56, Ian Dunlop  wrote:
> Hello,
>
> Infra sorted out the account. We can now release to google play.
>
> Cheers,
>
> Ian
>
> On 15 September 2016 at 09:32, Ian Dunlop  wrote:
>
>> Hello,
>>
>> I created https://issues.apache.org/jira/browse/INFRA-12614 to ask for
>> ASF google play account.
>>
>> Cheers,
>>
>> Ian
>>
>> On 13 September 2016 at 13:37, Ian Dunlop  wrote:
>>
>>> Hello,
>>>
>>> Some info via the general@incubator list http://mail-archives.apache.or
>>> g/mod_mbox/incubator-general/201609.mbox/%3Ccc28ae23-2f25-
>>> ef93-f6a7-40485ddcebc4%40apache.org%3E
>>> We may need to raise some infra tickets.
>>>
>>> Cheers,
>>>
>>> Ian
>>>
>>> On 13 September 2016 at 09:01, Rajan Maurya 
>>> wrote:
>>>
 Hello all,

 Yes, I think. Taverna mobile has much functionality to release and get
 the
 feedback from the user.

 Ok, I will check every functionality. so before release, we make sure
 everything working fine and simultaneously fix the small bugs If there is
 any.

 Thanks.


 On Tue, Sep 13, 2016 at 12:29 PM, Ian Dunlop 
 wrote:

 > Hello
 >
 > I think we are getting closer to a release. Once the latest version
 has the
 > ability to run a workflow then I think it will be time to go through
 the
 > release process. We can create the all and worry about app store later.
 > Doesn't harm to figure out the process in parallel and go for play
 release
 > if it is not too difficult.
 >
 > Cheers
 >
 > Ian
 >
 > On 13 Sep 2016 02:54, "Stian Soiland-Reyes"  wrote:
 >
 > > Androids and folks,
 > >
 > > There have been quite a bit of work on the Taverna Mobile over th
 > > esummer, thanks to all of you!
 > >
 > > I am wondering if we are now getting closer to a release? I don't
 > > think we need to be too ambitious - but I agree we shouldn't let too
 > > many things "hang in the air" either.
 > >
 > >
 > >
 > >
 > >
 > >
 > > I don't know if Apache Software Foundation has ever done a Google
 Play
 > > / .apk release - so it might be worth asking on dev@community or
 > > general@incubator about any tips on doing such a release.  I know
 ASF
 > > has a Apple store signing thing - but not sure if there's something
 > > similar for Android.
 > >
 > > But if that ends up being tricky - I think we can still do a first
 > > source release of Taverna Mobile - just to get a good milestone, and
 > > so we can make a download page etc - even just a .apk file to
 > > download.
 > >
 > > We can also always do the Play upload "out of bands" as long as we
 are
 > > careful with the Apache trade mark.
 > >
 > >
 > > BTW Here's a walk-through I did with the 2013
 > > https://github.com/myGrid/taverna-mobile (pre-Apache) prototype by
 > > Hyde Zhang.
 > >
 > > https://www.youtube.com/watch?v=XChZv_nXRa8=PLs1PhQrR0xxH3j-
 > > f6FXU2cp9fBVTDrl6T
 > >
 > > On 27 July 2016 at 15:39, Ian Dunlop  wrote:
 > > > Hello,
 > > >
 > > > I don't think the app is quite ready for release yet. It looks like
 > there
 > > > is now a lot of duplicated code in it. For example, there is
 > > > adapters/WorkflowAdpater and ui/adapter/WorkflowAdapter. I guess
 that
 > the
 > > > original one is not used any more. It would be nice if we could
 clean
 > uo
 > > > the codebase and remove the legacy bits. I think that was one of
 the
 > > > original ideas behind the GSoC plan but it may have got lost
 somewhere.
 > > > Another one of the ideas was to document what things do and use
 simple
 > > > design patterns so that other devs could add functionality. I'm not
 > sure
 > > we
 > > > have quite achieved that yet.
 > > > I think something that has been lost along the way is that the
 mobile
 > app
 > > > was to allow people to run workflows via a tav server/player.
 However,
 > we
 > > > have lost that functionality (well, it's not visible to the user
 > anyway).
 > > > I'm not too bothered if the favourites sync to their myExperiment
 > account
 > > > or not. The app was never meant to be a mobile version of
 myExperiment.
 > > > Showing workflows is great. Running them even

Re: Taverna Mobile Release

2016-09-20 Thread Ian Dunlop 
Hello,

Infra sorted out the account. We can now release to google play.

Cheers,

Ian

On 15 September 2016 at 09:32, Ian Dunlop  wrote:

> Hello,
>
> I created https://issues.apache.org/jira/browse/INFRA-12614 to ask for
> ASF google play account.
>
> Cheers,
>
> Ian
>
> On 13 September 2016 at 13:37, Ian Dunlop  wrote:
>
>> Hello,
>>
>> Some info via the general@incubator list http://mail-archives.apache.or
>> g/mod_mbox/incubator-general/201609.mbox/%3Ccc28ae23-2f25-
>> ef93-f6a7-40485ddcebc4%40apache.org%3E
>> We may need to raise some infra tickets.
>>
>> Cheers,
>>
>> Ian
>>
>> On 13 September 2016 at 09:01, Rajan Maurya 
>> wrote:
>>
>>> Hello all,
>>>
>>> Yes, I think. Taverna mobile has much functionality to release and get
>>> the
>>> feedback from the user.
>>>
>>> Ok, I will check every functionality. so before release, we make sure
>>> everything working fine and simultaneously fix the small bugs If there is
>>> any.
>>>
>>> Thanks.
>>>
>>>
>>> On Tue, Sep 13, 2016 at 12:29 PM, Ian Dunlop 
>>> wrote:
>>>
>>> > Hello
>>> >
>>> > I think we are getting closer to a release. Once the latest version
>>> has the
>>> > ability to run a workflow then I think it will be time to go through
>>> the
>>> > release process. We can create the all and worry about app store later.
>>> > Doesn't harm to figure out the process in parallel and go for play
>>> release
>>> > if it is not too difficult.
>>> >
>>> > Cheers
>>> >
>>> > Ian
>>> >
>>> > On 13 Sep 2016 02:54, "Stian Soiland-Reyes"  wrote:
>>> >
>>> > > Androids and folks,
>>> > >
>>> > > There have been quite a bit of work on the Taverna Mobile over th
>>> > > esummer, thanks to all of you!
>>> > >
>>> > > I am wondering if we are now getting closer to a release? I don't
>>> > > think we need to be too ambitious - but I agree we shouldn't let too
>>> > > many things "hang in the air" either.
>>> > >
>>> > >
>>> > >
>>> > >
>>> > >
>>> > >
>>> > > I don't know if Apache Software Foundation has ever done a Google
>>> Play
>>> > > / .apk release - so it might be worth asking on dev@community or
>>> > > general@incubator about any tips on doing such a release.  I know
>>> ASF
>>> > > has a Apple store signing thing - but not sure if there's something
>>> > > similar for Android.
>>> > >
>>> > > But if that ends up being tricky - I think we can still do a first
>>> > > source release of Taverna Mobile - just to get a good milestone, and
>>> > > so we can make a download page etc - even just a .apk file to
>>> > > download.
>>> > >
>>> > > We can also always do the Play upload "out of bands" as long as we
>>> are
>>> > > careful with the Apache trade mark.
>>> > >
>>> > >
>>> > > BTW Here's a walk-through I did with the 2013
>>> > > https://github.com/myGrid/taverna-mobile (pre-Apache) prototype by
>>> > > Hyde Zhang.
>>> > >
>>> > > https://www.youtube.com/watch?v=XChZv_nXRa8=PLs1PhQrR0xxH3j-
>>> > > f6FXU2cp9fBVTDrl6T
>>> > >
>>> > > On 27 July 2016 at 15:39, Ian Dunlop  wrote:
>>> > > > Hello,
>>> > > >
>>> > > > I don't think the app is quite ready for release yet. It looks like
>>> > there
>>> > > > is now a lot of duplicated code in it. For example, there is
>>> > > > adapters/WorkflowAdpater and ui/adapter/WorkflowAdapter. I guess
>>> that
>>> > the
>>> > > > original one is not used any more. It would be nice if we could
>>> clean
>>> > uo
>>> > > > the codebase and remove the legacy bits. I think that was one of
>>> the
>>> > > > original ideas behind the GSoC plan but it may have got lost
>>> somewhere.
>>> > > > Another one of the ideas was to document what things do and use
>>> simple
>>> > > > design patterns so that other devs could add functionality. I'm not
>>> > sure
>>> > > we
>>> > > > have quite achieved that yet.
>>> > > > I think something that has been lost along the way is that the
>>> mobile
>>> > app
>>> > > > was to allow people to run workflows via a tav server/player.
>>> However,
>>> > we
>>> > > > have lost that functionality (well, it's not visible to the user
>>> > anyway).
>>> > > > I'm not too bothered if the favourites sync to their myExperiment
>>> > account
>>> > > > or not. The app was never meant to be a mobile version of
>>> myExperiment.
>>> > > > Showing workflows is great. Running them even better.
>>> > > >
>>> > > > Cheers,
>>> > > >
>>> > > > Ian
>>> > > >
>>> > > > On 26 July 2016 at 15:59, Rajan Maurya 
>>> > wrote:
>>> > > >
>>> > > >> Hi Folks,
>>> > > >>
>>> > > >> Now our main functionality are stable and ready for release.
>>> > > >> As stain told earlier that you are thinking to relaese first
>>> version
>>> > of
>>> > > >> Taverna mobile.
>>> > > >>
>>> > > >> I wanna know that Is there any date etc you throught to release
>>> the
>>> > app
>>> > > ?
>>> > > >>
>>> > > >> Sagar is working on Login Screen and Shifting code according to
>>> MVP
>>> >

Re: Taverna Mobile NOTICE

2016-09-20 Thread Stian Soiland-Reyes 
Yes, I think that would somewhat count as "provided with" in these cloud
days  :-)

(I am not a lawyer, etc)

On 20 Sep 2016 5:48 p.m., "Gale Naylor"  wrote:

> Could we put the license and notice in the "read more" section of the play
> store window that is used to describe the app? Or a summary of the info?
>
> On Tue, Sep 20, 2016, 3:12 AM Stian Soiland-Reyes 
> wrote:
>
> > Hi,
> >
> > If we're going to release a Taverna Mobile binary .apk (or whatever
> > the extension is today) - then that would also bundle the third-party
> > dependencies, right?
> >
> > We would then need to include a variant of the LICENSE and NOTICE file
> > - but how can that be readable from within the app?  (As you wouldn't
> > "unzip" the app before installing it).  Do we need to use a "About"
> > menu button where the user can scroll through the license?
> >
> >
> > Also it would be good to check on the dependencies if they have their
> > own NOTICE files - it should be easy by just looking inside their JAR
> > files and copy out whatever is there. If they don't have, and they are
> > also Apache licensed, then there should be nothing more to do. BSD
> > licensed ones however would need to comply with
> >
> > > 2. Redistributions in binary form must reproduce the above copyright
> > notice, this list of conditions and the following disclaimer in the
> > documentation and/or other materials provided with the distribution.
> >
> > I am not sure if we could get away with that by not providing
> > documentation or materials :)
> >
> > --
> > Stian Soiland-Reyes
> > http://orcid.org/-0001-9842-9718
> >
>