RE: TavMob source, binary or both

2018-01-16 Thread 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  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

[GitHub] incubator-taverna-server pull request #5: Moved copyright notices to META-IN...

2018-01-16 Thread stain 
GitHub user stain opened a pull request:

https://github.com/apache/incubator-taverna-server/pull/5

Moved copyright notices to META-INF/LICENSE.*

On genera@incubator, [Justin 
commented](https://lists.apache.org/thread.html/78aa01f01b377e0d1fae38706ab94c51380ee10fad89cd2ee5c8a5a0@%3Cgeneral.incubator.apache.org%3E)
 that we do not need to list the OGF license text within NOTICE.


We do however need to be careful not to imply that the full OGF Document 
license applies to our taverna-server-usagerecord Java files, as they are 
considered _"derivative work"_, which are _"without restriction of any kind, 
provided that the above copyright notice and this paragraph are included as 
references to the derived
portions on all such copies and derivative works"_

So the suggestion is to move out the license of the two PDF files from OGF 
to separate files under META-INF (even though those PDF files are not included 
in the distro) -- and then only refer to them from the upper LICENSE. The 
NOTICE can then go back to normal ASF-only.

See discussion on 
[legal-discuss](https://lists.apache.org/thread.html/911ba67907cbca6925851e448ac8a7e73a921cb59efb8ca028e15845@%3Clegal-discuss.apache.org%3E)

Views?

LICENSE.GFD.98.txt from
https://www.ogf.org/documents/GFD.98.pdf

LICENSE.GFD.204.txt from
https://www.ogf.org/documents/GFD.204.pdf

LICENSE.W3C.software.txt from
http://www.w3.org/Consortium/Legal/copyright-software-19980720


You can merge this pull request into a Git repository by running:

$ git pull https://github.com/apache/incubator-taverna-server OGF-LICENSE

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/incubator-taverna-server/pull/5.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #5


commit 89aa2d41ea65779166dce0f95b397b341e2e2bcd
Author: Stian Soiland-Reyes 
Date:   2018-01-16T10:33:39Z

Moved copyright notices to META-INF/LICENSE.*

LICENSE.GFD.98.txt from
https://www.ogf.org/documents/GFD.98.pdf

LICENSE.GFD.204.txt from
https://www.ogf.org/documents/GFD.204.pdf

LICENSE.W3C.software.txt from
http://www.w3.org/Consortium/Legal/copyright-software-19980720

See

https://lists.apache.org/thread.html/911ba67907cbca6925851e448ac8a7e73a921cb59efb8ca028e15845@%3Clegal-discuss.apache.org%3E




---