On 26 March 2015 at 15:41, Sergio Fernández <[email protected]> wrote: > I've just created our first issue COMMONSRDF-1 [1] for managing such > process, where:
Hurray! > * I can easily prepare a bundle with the current repository +1. Would you then also do a git signed tag and then include the commit in the IP clearance? It could provide a useful marker for later. For Taverna I used a tag name like apache-import-20150223 https://git-wip-us.apache.org/repos/asf?p=incubator-taverna-language.git;a=tag;h=3f43e2023ddc1b4cff0e98f446afd7e7928487a7 > * If the contribution by an external developer (commit > 2ff2c6be5415295943c3131625695be1f5415c5a [3]) would represent an issue, we > can easily skipped from the code donation given its minor importance. I can't see how Ian's contribution [3] is copyrightable or included under "sufficient rights", and anyway it is covered by Apache License section 5 contributions. (See also current discussion on general@incubator for Groovy software grant) I could always ask Ian - but he's pretty busy with a brand new baby these days... > [1] https://issues.apache.org/jira/browse/COMMONSRDF-1 BTW, where do email notifications on Jira go..? I didn't see anything here or on commits. -- Stian Soiland-Reyes Apache Taverna (incubating), Apache Commons RDF (incubating) http://orcid.org/0000-0001-9842-9718
