Created on Jul 28, 2009 11:05 AM by Elijah Lapson
While great to have a file zipped up with or separate from the .nsf package I would love and easy way to put this "license text" with the project. IE if the project template had a page/tab with license information on it. On the page/tab the specific license(s) could be selected by the submitter. ...
Read more...
|
Created on Jul 28, 2009 11:50 AM by John Head/PSCDM
Elijah - I like your approach, but we need to address two items your approach doesn't cover: 1. What about when someone takes the nsf/ntf/files off of OpenNTF.org? How do we make sure the license attributions are included there? They need to be
2. If we put this in the Project section, what ...
Read more...
|
Created on Jul 28, 2009 12:23 PM by Ernie Mercer
For what it's worth here's my suggestion: 1. Attach the license file(s) to the "About this Database" document. This way the information is there when the database is downloaded from OpenNTF (whether as a zip file or not) and is accessible even if the user does not have Domino Designer. 2. Have ...
Read more...
|
Created on Jul 28, 2009 12:56 PM by Karl-Henry Martinsson
I agree that the file should be attached to the About document. And it may not be a bad idea to put it somewhere on the project pages so it can be downloaded/viewsed separate as well. That should be optional, but encouraged.
Read more...
|
Created on Jul 28, 2009 1:32 PM by John Head/PSCDM
Do we want that to come up in the face of ever user every time they open a project from OpenNTF.org? Do we want to go one step further and create a default OpenNTF.org project About Document text - which includes info about OpenNTF.org, info about how to get to the project, and all the license ...
Read more...
|
Created on Jul 28, 2009 2:04 PM by Ernie Mercer
I think we'd only need to set the launch properties to require that the "About" document be displayed the first time the application is opened by a user. I wouldn't want to fill the "About" document with a great deal of text - a very brief note about OpenNTF and a link to the website. I think the ...
Read more...
|
Created on Jul 28, 2009 2:15 PM by John Head/PSCDM
we have to provide the license the nsf/ntf is under AND a license file for each use of external code. Even if they are all of the same license type (all APL for instance). We still have to have a license document for each - and proper attribution to the author, location of the code, and contact ...
Read more...
|
Created on Jul 28, 2009 12:28 PM by Steve Castledine
This way everything stays with the nsf. Once it comes out of the zip - the intended license, attribution is lost otherwise.
Read more...
|
Created on Jul 28, 2009 1:19 PM by John M Turnbow
Additionally I would like a radio button associated with each project about the license type and also a view. It should be clickable to view the license information along with some light "hover info" for each license. I suggest that each of the open source license types be listed along with ...
Read more...
|
Created on Jul 28, 2009 1:31 PM by John Head/PSCDM
John - each release has a license type. We have talked about making that a project creation setting and a release time optional override. But what I am talking about is when a project reuses other projects or code. You have to give proper credit - and in both GPL and APL guidelines, that means ...
Read more...
|
Created on Jul 28, 2009 1:51 PM by Declan Lynch
I think that there are a couple of different audiences that we need to look at to see if they should have access to the license and if so how they should have that access. In my opinion I would divide the audiences into the following groups. Developers : people who will look at the code and maybe ...
Read more...
|
Created on Jul 29, 2009 11:11 AM by John Head/PSCDM
We have talked about file resource, on the release page on the site, in the zip file, and in the About document. I would like to see us narrow that list down to require 1 or 2 and provide the other as options. My only other comment right now is that it seems less than 50% of release files are in ...
Read more...
|
Created on Jul 30, 2009 7:57 AM by mike mcpoyle
It can't be that tough to write something that executes after upload and auto-zips an NTF/NSF, which would include the correct .txt file of the license. You could even write a process to insert at .txt and zip existing projects with the proper license based on the author's selection. This ...
Read more...
|
Created on Jul 30, 2009 10:35 AM by Declan Lynch
That would only work if the code contained within the NTF/NSF is 100% yours. The auto generated notice.txt would be fine. But if you have used somebody else's code you also need to include their license files etc.
Read more...
|
Created on Jul 31, 2009 2:17 AM by Niklas Heidloff/Germany/IBM
There are not only NSFs/NTFs. There are also plugins, C code etc. I think that these projects should be put in a zip and license information is applied in the zip. This is also how Apache does it. For example they require to put license files and a notice file in the root of the zip. It is ...
Read more...
|
Created on Aug 9, 2009 10:58 AM by John Head/PSCDM
I think that we should make our License Documentation within Projects the following: Projects 1. All external licenses will be detailed on the Project page (this will require a change made by the TC). Allow for multiple license documents and/or links to existing OpenNTF.org projects
2. If the ...
Read more...
|
Created on Aug 9, 2009 6:13 PM by Declan Lynch
for licensing on the 'About' page for NTF/NSFs I'd suggest a collapsed section as a starting point. Otherwise this sounds like an excellent proposal.
Read more...
|
Created on Aug 10, 2009 7:49 AM by Peter Tanner
I have edited the proposed Contribution Process document. Check out section 8. Does this capture your discussion here? I have left the GPL section blank for now - so as to permit the GPL Manager to edit according to the GPL requirements. Peter Tanner - IP Manager
Read more...
|
|