 | Start a set with this search |
 | Include this search in one of my sets |
 | Exclude this search from one of my sets |
 | Permalink to these results Paste this link in email or IM: |
 | Atom feed for tracking future search results Paste this URL into your reader: |
14 messages in org.apache.legal-discussRe: Maven repository issues [Was: Cre...| From | Sent On | Attachments |
|---|---|---|
| Henri Yandell | May 29, 2008 1:06 am | |
| Stefano Bagnara | May 29, 2008 1:17 am | |
| Assaf Arkin | May 29, 2008 10:53 am | |
| Henri Yandell | May 29, 2008 12:10 pm | |
| Stefano Bagnara | May 29, 2008 12:35 pm | |
| David Jencks | May 29, 2008 12:47 pm | |
| Craig L Russell | May 29, 2008 2:38 pm | |
| Gilles Scokart | May 30, 2008 1:04 am | |
| Stefano Bagnara | May 30, 2008 1:47 am | |
| Assaf Arkin | May 30, 2008 2:50 am | |
| sebb | May 30, 2008 2:51 am | |
| Stefano Bagnara | May 30, 2008 3:33 am | |
| Assaf Arkin | May 30, 2008 4:33 am | |
| Gilles Scokart | May 30, 2008 4:35 am |
| Permalink for this message Paste this link in email or IM: |
| Permalink for this thread Paste this link in email or IM: |
| Atom feed for this thread Paste this URL into your reader: |
| Subject: | Re: Maven repository issues [Was: Creative Commons Attribution License] | Actions... |
|---|---|---|
| From: | Assaf Arkin (ark...@intalio.com) | |
| Date: | May 29, 2008 10:53:08 am | |
| List: | org.apache.legal-discuss | |
On Thu, May 29, 2008 at 1:18 AM, Stefano Bagnara <apa...@bago.org> wrote:
Henri Yandell ha scritto:
On Thu, May 29, 2008 at 12:58 AM, Stefano Bagnara <apa...@bago.org> wrote:
Craig L Russell ha scritto:
I don't have any problem with depending on a CC licensed artifact, but I'm troubled by the notion that an artifact would be installed into a Maven repository by "not the author".
I had big issues with the fact that pom.xml in maven repository have no license headers. Our PMC voted down redistributing some of them because of this.
It should be enforced that any uploaded pom.xml include a license header to specify the license for the pom itself.
Unfortunately most pom.xml in the current repository do not have the license header and we don't even know who hold the copyright for that files, AFAIK.
Apart from the description of the project, which is usually copied from the project website if it's even there, I wonder how much copyright there is in a pom.xml. All of the xml tags and attributes are a standard enforced by the Maven tool, so that leaves the data in between the xml - namely urls, people's names, project name/versions and some small level of configuration (ie: numbers and file paths).
A different world than even a build.xml where basic building blocks are used as a set of instructions.
Hen
An official statement from the ASF that says that we can safely include pom.xml with no license headers (from the maven central repository or even any repository) in our redistributable would really help our next releases (Apache JAMES PMC). Some of our PMC member are convinced (and I don't have knowledge to say they are wrong) that even the most simple pom automatically generated by maven when installing an artifact with no pom (so that it only contains the artifactId, groupId and version) is copyrightable.
A lot of people trip on that. You don't have to file for copyright on a work, you get it by merely creating the work, which almost sounds like everything you create would be protected by copyright.
Except, not everything is copyrightable, it has to have some creativity in it.
This particular case is not copyrightable, and slapping a copyright statement on it won't change that.
But there's a separate issue to consider. If I'm serving you a large collection of files, how would you know all the files there are either under an agreeable license or not copyrighted to being with? Manually checking every file is tedious, and automated tools don't have good judgment call as to what is or is not copyrighted.
So the issue is not just legal but also technical.
Assaf
Stefano
--------------------------------------------------------------------- DISCLAIMER: Discussions on this list are informational and educational only. Statements made on this list are not privileged, do not constitute legal advice, and do not necessarily reflect the opinions and policies of the ASF. See <http://www.apache.org/licenses/> for official ASF policies and documents.