(separated from the meetings thread because this is important)
On 13/03/13 09:23, Sergio Fernández wrote:
> So, from my point of view, we'd be ready to prepare our first incubating
> release :-)
>
> Mentors?
Build one and we can review it. It's easier to refer to a concrete thing.
Andy
Just seen this (buried in a JIRA!)
"""
I think now we already have a proper NOTICE file for Marmotta.
Please mentors, if you could check it and tell us any feedback about it,
because this is quite important for the release.
"""
Quick scan - I hope Fabian and Nandana can take a look because we
different experiences (and different opinions probably!) of this.
1/ there aren't the associated details in LICENSE (important).
2/ it's a bit long and likely to get "feedback" (style)
3/ Code tree and distribution N&L are likely to be different (important)
1/ ==>
BSD requires
"""
1. Redistributions of source code must retain the above copyright
notice, this list of conditions and the following disclaimer.
"""
so for BSD, mention in NOTICE, put the full license text in LICENSE. If
the license requires reproducing, put it in LICENSE.
And for BSD, it is each use of BSD is different strictly "BSD-like"
because each statement has editted the template to put the owners name
in it so it is different text each time.
2/ ==>
A shorter
"""
This product includes software developed by
X under a Y license.
"""
is enough for NOTICE - don't need to say where it occurs.
[Especially as a down side of the GIT UI is URLs links to files aren't
easily hackable]
e.g.
"""
Contains software based on Dracula Graph Library licensed under
the MIT License.
"""
3/ ==>
It is likely the N&L that go at the top of the source code tree is
different to the N&L at the top of the distribution.
The source code tree one just covers the tree, not the included material
pulled into the distribution.
(assuming a formal release is one big thing)
[[
The module marmotta-webapp packages together all dependencies, including
transitive ones. For copyright details please refer to the dependencies
declared at build configuration files.
]]
You need to pull out the transitive ones for N&L for the binary here.
NOTICE+LICENSE for more details, should be the only place a downstream
repackager or a careful user needs to look before needing to examine the
code itself.
Don't forget to put the appropriate N&L in the jar files under META_INF.
Sorry it's rushed ....
Andy
