You MUST keep a copy of the license with the program if you choose to distribute it. That goes for both source as well as binary. It does NOT mean that the license has to be EMBEDDED into the binary files -- it means that there must be a FILE WITH it, i.e. "license.txt", included in the archive, installed into the directory with, or similar.
And they MUST be ACCESSIBLE to whoever receives your distributions.... So if, for example, you build a PROTECTED ANDROID APPLICATION using apache licensed (or gpl/etc.) code, then the ONLY WAY that the user will have access to the license text is if you actually provide a FUNCTION IN THE PROGRAM to display the license. One of the BIG REASONS why this is a requirement is in the event that YOU as the distributor, goes out of business or dies or goes to jail, etc., the text of the license MUST be available no matter WHAT happens to you. You will note within android: Settings --> About --> Legal. On Jun 17, 5:18 pm, Onomp <[email protected]> wrote: > Thanks for the link, I have been there and I didn't take in as much as > I did this time. > > I also found this which might be a valuable resource to anyone else > with interest. > > http://mail-archives.apache.org/mod_mbox/www-legal-discuss/ > > On Jun 17, 8:25 am, Daniel Drummond <[email protected]> wrote: > > > On 17 June 2010 13:14, Onomp <[email protected]> wrote: > > > > I am, I was wondering if anyone has found any valuable information in > > > regards to laws surrounding open and closed source code. Or what > > > understandings you have. > > > > I really want or wanted to use some of the features touched on in the > > > API demos but then when I went into the source I noticed the apache > > > license on some of them... I've only begun reading about the apache > > > license but from what I understand I can use them and still have my > > > app closed source but then again I need to leave the license in my > > > source, although its closed( which seems confusing and silly enough to > > > believe I'm in full understanding ) > > > I believe that it actually states that if you distribute in source > > form you need to ensure the copyright notices are there, but a copy of > > the license should be provided seperately even if you distribute in > > binary form. > > This seems usefulhttp://www.oss-watch.ac.uk/resources/apache2.xml > > > The API demos are meant to be examples of how to code different > > features correctly, and are meant as inspiration for building the > > features into your own application. You should be able to use the > > features without just copying the demo code, as you will most likely > > need to tailor it to your needs. > > > Licenses are complex things and your best bet to be completely sure is > > to consult a lawyer that specialises in these things. > > -- You received this message because you are subscribed to the Google Groups "Android Discuss" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/android-discuss?hl=en.
