+1 - Agreed - nothing fancy, just one mega-scroll should do, like the
big-name apps do.  :)

Added it as a new task to Jira:

https://issues.apache.org/jira/browse/TAVERNA-1012



On 21 September 2016 at 16:19, Gale Naylor <ga...@noventussolutions.com> wrote:
> That sounds good!
>
> On Wed, Sep 21, 2016 at 8:02 AM Rajan Maurya <rajanmaurya...@gmail.com>
> wrote:
>
>> Yes, We can show opensource licences of all the library in the menu action
>> button.
>>
>> For an example : open google gmail app -> click navigation home button ->
>> scroll to botton -> click on Settings -> open settings action menu -> click
>> on Help & feedback ->
>> open Help & feedback action menu -> click on "Open-source liceneces".
>>
>> I think this is sufficient.
>>
>>
>>
>> On Wed, Sep 21, 2016 at 2:01 PM, Ian Dunlop <ianwdun...@gmail.com> wrote:
>>
>> > Hello,
>> >
>> > I agree with Gale that we can add it to the play read more but we also
>> need
>> > to think about people who will just download the apk. So maybe we do need
>> > to add some details to the "about" section within the app. It's not a big
>> > deal to do. I guess we will discover what to do when we release. We could
>> > ask these questions on general@incubator, I wonder what they do for iOS.
>> >
>> > Cheers,
>> >
>> > Ian
>> >
>> > On 20 September 2016 at 18:44, Stian Soiland-Reyes <st...@apache.org>
>> > wrote:
>> >
>> > > 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" <ga...@noventussolutions.com>
>> > > 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 <st...@apache.org>
>> > > > 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/0000-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)
>>



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

Reply via email to