You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@marmotta.apache.org by Sebastian Schaffert <ss...@apache.org> on 2013/02/19 14:14:50 UTC
Marmotta Code Import
Dear all,
after last Friday's LMF 2.6 release, we have now done the initial code
import into the GIT repository at
Re: Marmotta Code Import
Posted by Sergio Fernández <se...@salzburgresearch.at>.
For keeping the track with the base code imported, we've created a tag
in git:
object ee17ab4ba362ef87cf30e227561273bae787bf01
type commit
tag import
tagger Sergio Fernández <wi...@apache.org> 1361280393 +0100
code imported from lmf
Cheers,
On 19/02/13 14:21, Sebastian Schaffert wrote:
> Dear all,
>
> (sorry, GMail send the mail when I pressed enter for newline...)
>
>
> after last Friday's LMF 2.6 release, we have now done the initial code
> import into the GIT repository at
>
> https://git-wip-us.apache.org/repos/asf/incubator-marmotta.git
>
> We will now start restructuring the directory layout according to the
> decision we had on the mailinglist. Next tasks:
> - update directory layout
> - update to the Apache Parent POM
> - update group IDs (to org.apache.marmotta) and artifact IDs
> - rename the Java packages to org.apache.marmotta
> - update the headers, notices, ...
> - update the LMF 3.0 snapshot on Google Code to represent the code split
> and depend on the new artifacts
>
> We will finish these tasks during the next days. :-)
>
> Mentors: Is there any other process we need to follow to conclude the code
> import? We already signed and submitted the contributor agreement.
>
> Greetings,
>
> Sebastian
>
--
Sergio Fernández
Salzburg Research
+43 662 2288 318
Jakob-Haringer Strasse 5/II
A-5020 Salzburg (Austria)
http://www.salzburgresearch.at
Re: Marmotta Code Import
Posted by Peter Ansell <an...@gmail.com>.
On 22 February 2013 19:29, Andy Seaborne <an...@apache.org> wrote:
> On 22/02/13 09:08, Sebastian Schaffert wrote:
>>
>> Hi Andy,
>>
>> we had some patches from Peter Ansell in the parsing components for
>> JSON-LD
>> and RDF/JSON.
>
>
> You can use them anyway (with the right copyright handling) but I'm sure
> Peter will be willing to grant them to Apache, then you can treat them like
> everything else which is easier in the long run (no extra NOTICE or LICENSE
> entries). If it's recent, it may even be covered by his current Apache iCLA
> which would be perfect.
I opened the fairly small (mostly rearranging maven modules) pull
requests on Bitbucket in November 2012 [1][2]. I am definitely happy
to grant the contributions to Apache.
[1] https://bitbucket.org/srfgkmt/sesame-tools/pull-request/3/extract-rdfformat-instances-into-a-new/diff
[2] https://bitbucket.org/srfgkmt/sesame-tools/pull-request/2/make-java-files-compile-and-cleanup/diff
Cheers,
Peter
Re: Marmotta Code Import
Posted by Andy Seaborne <an...@apache.org>.
On 22/02/13 09:08, Sebastian Schaffert wrote:
> Hi Andy,
>
> we had some patches from Peter Ansell in the parsing components for JSON-LD
> and RDF/JSON.
You can use them anyway (with the right copyright handling) but I'm sure
Peter will be willing to grant them to Apache, then you can treat them
like everything else which is easier in the long run (no extra NOTICE or
LICENSE entries). If it's recent, it may even be covered by his current
Apache iCLA which would be perfect.
As often with legal stuff, a small amount of work now can save a lot of
work later.
(With Jena we had about 10 significant items to chase up - the previous
environment at HP made it hard to take large contributions as one large
org does not like "giving" things to another - everyone was very helpful
and we were only left with one item where the company no longer existed
and we stuck with the BSD license terms it arrived under)
> Some of the code originates from old projects (e.g. the
> parser for the reasoning language) and has been written by persons
> currently not associated with the project. I'll check with them on the
> license (but all code was either BSD or APL).
Usually the terms and conditions of someone's employment says the
employer owns the copyright. If so, and if it was Salzburg Research,
then it may well already be covered by the existing grant. For once, no
extra legal work to do!
> Otherwise I think there have not been any major third-party contributions.
Andy
Re: Marmotta Code Import
Posted by Sebastian Schaffert <ss...@apache.org>.
Hi Andy,
we had some patches from Peter Ansell in the parsing components for JSON-LD
and RDF/JSON. Some of the code originates from old projects (e.g. the
parser for the reasoning language) and has been written by persons
currently not associated with the project. I'll check with them on the
license (but all code was either BSD or APL).
Otherwise I think there have not been any major third-party contributions.
Greetings,
Sebastian
2013/2/22 Andy Seaborne <an...@apache.org>
> On 22/02/13 08:42, Sergio Fernández wrote:
>
>> Andy,
>>
>> we know it. Once we finished the package renaming we'll run the licence
>> maven plugin to fix that.
>>
>> Thanks to remember it to us.
>>
>
> Cool - seeing all the clearup going on, I thought I'd mention it early.
>
> Have you had code, patches, etc from anyone else?
>
> Andy
>
>
>
>> Cheers,
>>
>> On 22/02/13 09:34, Andy Seaborne wrote:
>>
>>> I had a quick scan of the code repository. I didn't look at every files
>>> but the ones I did have a copyright statement on them.
>>>
>>> e.g.
>>> Copyright (c) 2013 The Apache Software Foundation
>>> Copyright (C) 2013 Salzburg Research.
>>>
>>> You don't put those on granted files - you only leave existing copyright
>>> statements on files from other sources. Where the files are covered by
>>> the grant from your organisation, you can remove the (c) lines and put a
>>> copyright statement in NOTICE.
>>>
>>> (Don't move or remove someone else's copyright statement - only the
>>> copyright holder should do that.)
>>>
>>> http://www.apache.org/legal/**src-headers.html<http://www.apache.org/legal/src-headers.html>
>>>
>>> Andy
>>>
>>
>>
>
Re: Marmotta Code Import
Posted by Andy Seaborne <an...@apache.org>.
On 22/02/13 08:42, Sergio Fernández wrote:
> Andy,
>
> we know it. Once we finished the package renaming we'll run the licence
> maven plugin to fix that.
>
> Thanks to remember it to us.
Cool - seeing all the clearup going on, I thought I'd mention it early.
Have you had code, patches, etc from anyone else?
Andy
>
> Cheers,
>
> On 22/02/13 09:34, Andy Seaborne wrote:
>> I had a quick scan of the code repository. I didn't look at every files
>> but the ones I did have a copyright statement on them.
>>
>> e.g.
>> Copyright (c) 2013 The Apache Software Foundation
>> Copyright (C) 2013 Salzburg Research.
>>
>> You don't put those on granted files - you only leave existing copyright
>> statements on files from other sources. Where the files are covered by
>> the grant from your organisation, you can remove the (c) lines and put a
>> copyright statement in NOTICE.
>>
>> (Don't move or remove someone else's copyright statement - only the
>> copyright holder should do that.)
>>
>> http://www.apache.org/legal/src-headers.html
>>
>> Andy
>
Re: Marmotta Code Import
Posted by Sergio Fernández <wi...@apache.org>.
Andy,
we know it. Once we finished the package renaming we'll run the licence
maven plugin to fix that.
Thanks to remember it to us.
Cheers,
On 22/02/13 09:34, Andy Seaborne wrote:
> I had a quick scan of the code repository. I didn't look at every files
> but the ones I did have a copyright statement on them.
>
> e.g.
> Copyright (c) 2013 The Apache Software Foundation
> Copyright (C) 2013 Salzburg Research.
>
> You don't put those on granted files - you only leave existing copyright
> statements on files from other sources. Where the files are covered by
> the grant from your organisation, you can remove the (c) lines and put a
> copyright statement in NOTICE.
>
> (Don't move or remove someone else's copyright statement - only the
> copyright holder should do that.)
>
> http://www.apache.org/legal/src-headers.html
>
> Andy
--
Sergio Fernández
Re: Marmotta Code Import
Posted by Andy Seaborne <an...@apache.org>.
I had a quick scan of the code repository. I didn't look at every files
but the ones I did have a copyright statement on them.
e.g.
Copyright (c) 2013 The Apache Software Foundation
Copyright (C) 2013 Salzburg Research.
You don't put those on granted files - you only leave existing copyright
statements on files from other sources. Where the files are covered by
the grant from your organisation, you can remove the (c) lines and put a
copyright statement in NOTICE.
(Don't move or remove someone else's copyright statement - only the
copyright holder should do that.)
http://www.apache.org/legal/src-headers.html
Andy
Re: Marmotta Code Import
Posted by Andy Seaborne <an...@apache.org>.
On 19/02/13 13:21, Sebastian Schaffert wrote:
> Dear all,
>
> (sorry, GMail send the mail when I pressed enter for newline...)
>
>
> after last Friday's LMF 2.6 release, we have now done the initial code
> import into the GIT repository at
>
> https://git-wip-us.apache.org/repos/asf/incubator-marmotta.git
Yipee!
>
> We will now start restructuring the directory layout according to the
> decision we had on the mailinglist. Next tasks:
> - update directory layout
> - update to the Apache Parent POM
> - update group IDs (to org.apache.marmotta) and artifact IDs
> - rename the Java packages to org.apache.marmotta
> - update the headers, notices, ...
> - update the LMF 3.0 snapshot on Google Code to represent the code split
> and depend on the new artifacts
>
> We will finish these tasks during the next days. :-)
>
> Mentors: Is there any other process we need to follow to conclude the code
> import? We already signed and submitted the contributor agreement.
Not that I know of.
> Greetings,
>
> Sebastian
Andy
Re: Marmotta Code Import
Posted by Sebastian Schaffert <ss...@apache.org>.
Dear all,
(sorry, GMail send the mail when I pressed enter for newline...)
after last Friday's LMF 2.6 release, we have now done the initial code
import into the GIT repository at
https://git-wip-us.apache.org/repos/asf/incubator-marmotta.git
We will now start restructuring the directory layout according to the
decision we had on the mailinglist. Next tasks:
- update directory layout
- update to the Apache Parent POM
- update group IDs (to org.apache.marmotta) and artifact IDs
- rename the Java packages to org.apache.marmotta
- update the headers, notices, ...
- update the LMF 3.0 snapshot on Google Code to represent the code split
and depend on the new artifacts
We will finish these tasks during the next days. :-)
Mentors: Is there any other process we need to follow to conclude the code
import? We already signed and submitted the contributor agreement.
Greetings,
Sebastian