Re: [PROPOSAL] JSNodeTypes contribution :: IP clearance needed?
Hi Bertrand, thanks for your feedback, that sounds good! If there are no objections I would commit it with SLING-4364 in the folder /contrib/commons/js/nodetypes with the Sling parent pom, the ArtifactId org.apache.sling.commons.js.nodetypes and the version 1.0.SNAPSHOT. Does that fit in the general structure? Best, Sandro Am 27.01.15 um 17:29 schrieb Bertrand Delacretaz: Hi Sandro, On Tue, Jan 27, 2015 at 4:51 PM, Sandro Boehme sandro.boe...@gmx.de wrote: ...Now that I'm a Committer in the meantime and I have written the JSNodeTypes library solely on my own the question is if the IP clearance process is still needed IMO it's not needed in this case, committing code that you wrote yourself is covered by your iCLA. I suggest that you wait 24 hours for possible objections, and if there's none go ahead and commit. -Bertrand
Re: [PROPOSAL] JSNodeTypes contribution :: IP clearance needed?
Hi Sandro, On Wed, Jan 28, 2015 at 5:37 PM, Sandro Boehme sandro.boe...@gmx.de wrote: ...If there are no objections I would commit it with SLING-4364 in the folder /contrib/commons/js/nodetypes with the Sling parent pom, the ArtifactId org.apache.sling.commons.js.nodetypes and the version 1.0.SNAPSHOT Works for me but maybe use 0.1.0-SNAPSHOT so that the first release can be 1.0.0 We use alternating odd/even versions so after 1.0.0 it's 1.0.1-SNAPSHOT and the next release is 1.0.2. -Bertrand
Re: [PROPOSAL] JSNodeTypes contribution :: IP clearance needed?
Hello again, while I think the JSNodeTypes contribution is useful I would also like to have it in Sling to not need an OBR to install the Resource Editor. Now that I'm a Committer in the meantime and I have written the JSNodeTypes library solely on my own the question is if the IP clearance process is still needed. What do you think? Best, Sandro Am 18.12.14 um 14:02 schrieb Bertrand Delacretaz: Hi Sandro, On Thu, Dec 11, 2014 at 4:25 PM, Sandro Boehme sandro.boe...@gmx.de wrote: ...Here you find a demo of the full API and all background information: http://www.jcrbrowser.org/sling/libs/jsnodetypes/content/documentation.html I think it's interesting, I support accepting this donation as it is used in your editor. Thanks for this! Note that we'd need to go via the IP clearance process as we did for the editor. -Bertrand
Re: [PROPOSAL] JSNodeTypes contribution :: IP clearance needed?
Hi Sandro, On Tue, Jan 27, 2015 at 4:51 PM, Sandro Boehme sandro.boe...@gmx.de wrote: ...Now that I'm a Committer in the meantime and I have written the JSNodeTypes library solely on my own the question is if the IP clearance process is still needed IMO it's not needed in this case, committing code that you wrote yourself is covered by your iCLA. I suggest that you wait 24 hours for possible objections, and if there's none go ahead and commit. -Bertrand
Re: [PROPOSAL] JSNodeTypes contribution
Hi Sandro, On Thu, Dec 11, 2014 at 4:25 PM, Sandro Boehme sandro.boe...@gmx.de wrote: ...Here you find a demo of the full API and all background information: http://www.jcrbrowser.org/sling/libs/jsnodetypes/content/documentation.html I think it's interesting, I support accepting this donation as it is used in your editor. Thanks for this! Note that we'd need to go via the IP clearance process as we did for the editor. -Bertrand
Re: [PROPOSAL] JSNodeTypes contribution
Am 18.12.14 14:02, schrieb Bertrand Delacretaz: Hi Sandro, On Thu, Dec 11, 2014 at 4:25 PM, Sandro Boehme sandro.boe...@gmx.de wrote: ...Here you find a demo of the full API and all background information: http://www.jcrbrowser.org/sling/libs/jsnodetypes/content/documentation.html I think it's interesting, I support accepting this donation as it is used in your editor. Thanks for this! Note that we'd need to go via the IP clearance process as we did for the editor. -Bertrand Hi Bertrand, I'm glad to read that. The IP clearance should be simpler as the iCLA is already there and there are no runtime dependencies external to Sling including no external frontend libraries (no JQuery, no images,...). I will be on vacation to pursue my hobby from the 27'th of december until the 10th of january. Thanks, Sandro
[PROPOSAL] JSNodeTypes contribution
Hello, I would like to offer the JSNodeTypes library to Apache Sling as a contribution. It provides a JavaScript API for JCR node types. I use it in the new code update of the Sling Resource Editor at the Add Node dialog to provide: o the applicable node names o the applicable node types o the applicable node name / node type combinations and o a warning if a resource type is entered even though the chosen node type does not allow for it. Here you find a demo of the full API and all background information: http://www.jcrbrowser.org/sling/libs/jsnodetypes/content/documentation.html This library is Apache 2 licensed and plain JavaScript and Java. It is 39kB and does not contain dependencies external to Sling. To replace the Gson dependency with oa.sling.commons.json most of the Java runtime code has been rewritten. Of course I'm committed to maintain this library. What do you think? Best, Sandro
