Tuesday, March 6, 2018, 9:54:08 PM, Nick Boldt wrote: > What's involved in performing a code contribution to ASF? Are > lawyers involved? Do I just send an email to someone saying "here's > the repo, it's EPL, fork it as you want" ? I'm not a lawyer, so take it like that... The simplest version I find likely to work is like this: First of all I discuss this at FreeMarker/ASF, and see if we want this contribution (because it's not up to me). If yes, then "you" (RedHat) fill and sing a Software Grant and Corporate Contributor License Agreement (https://www.apache.org/licenses/cla-corporate.txt), scan and e-mail it to the ASF office, then we create an almost empty repo for the plugin at the ASF, and then you create a PR on Github with which you contribute the whole source code. And that's the end of it on you side; the contributed code is now owned by the ASF, and we will replace the license headers, re-brands stuff, etc. But again, it's just my educated guess. But you can expect something like this. Anyway, I take that you prefer moving the plugin to the ASF, and that there are certainly no legal obstacles on your side. Is that correct? If yes, then I start discussion on my side. > Nick > > On Tue, Mar 6, 2018 at 2:44 PM, Daniel Dekany <ddekany(a)freemail.hu&gt; wrote: > Tuesday, March 6, 2018, 3:35:02 PM, Nick Boldt wrote: > >> I'm no lawyer but afaik you should easily be able to just fork the >> github repo at push that new fork up to apache.org. > > Certainly that would be my last commit at the ASF... (: It's more > paper work. "You" (RedHat) had to contribute the code to the ASF > first. Then the EPL licenses will be replaced by ASL, the product is > rebranded to be "Apache", packages names change, etc. > > If you think that a such transfer is doable, and is preferred over me > managing the plug-in here, then I will bring it up at the ASF, and see > what they think. > >> The code's currently under EPL so moving it to ASL should be easily >> done -- or just leave it as-is, if it's OK to have ASF-hosted code >> under an EPL license. >> >> The project should be easy enough to build as long as you keep it >> current against the latest JBoss Tools parent pom [1] version. If >> you prefer to not have cross-org dependencies, or are not allowed >> to, you will probably have to implement your own parent pom (copy >> from ours into the freemarker plugin project's root pom). >> >> [1] >> https://github.com/jbosstools/jbosstools-build/blob/master/ parent/pom.xml >> >> If you need to rebrand it (change namespace from org.jboss to >> org.apache) there's a way to ensure that old versions can still be >> updated through the namespace change. I can provide you with a PR or >> sample code for the p2.inf instructions you need in your feature(s) to support such a name change. >> >> It's really not that much work to move to another foundation -- >> we've often contributed org.jboss plugins/features to Eclipse so I know it's doable. >> >> Once you have it hosted at apache, building and publishing an >> update site (and/or zip) should be fairly easy too. Do you have a >> Jenkins or Hudson instance you can use there? > > Yes. > >> Nick >> >> >> >> >> On Tue, Mar 6, 2018 at 5:43 AM, Daniel Dekany <ddekany(a)freemail.hu&gt; wrote: >> Monday, March 5, 2018, 10:46:59 PM, Nick Boldt wrote: >> >>> Great question. See reply in >>> https://stackoverflow.com/questions/49072160/why-is- freemarker-ide-in-eclipse-oxygen-jboss-tools-4-5-2- final-deprecated/49119784#49119784 >> >> Thanks! >> >>> Turns out we JUST removed Freemarker tooling from the forthcoming >>> JBoss Tools 4.5.3.AM2 build (to be released tomorrow), after deprecating it in July 2017. >>> >>> So, it could come back if you're willing to take ownership of the >>> tooling builds & publication. >> >> Sure, I'm willing to (assuming there's no crazy administrative >> overhead). In fact, I have asked about this earlier (like years ago), >> as it was difficult to get my PR-s merged. >> >> Or, just my quick idea, but you can perhaps donate the code to the >> ASF, where the FreeMarker project is anyway. Haven't looked into how >> messy that would be legally though... >> >>> Do you have any stats to demonstrate the size of its user base? >> >> Nope. >> >> People who need this plugin need it because of FreeMarker, and they >> have no "relationship" with the other JBoss IDE products, so... as the >> installation instructions on apache.freemarker.org say, they only >> install the FreeMarker plugin. Then no statistics are collected, as >> far as I understand from your answer on StackOverflow. >> >>> Nick >>> >>> >>> >>> On Sat, Mar 3, 2018 at 3:05 AM, Daniel Dekany <ddekany(a)freemail.hu&gt; wrote: >>> I have noticed months ago that the FreeMarker plugin was deprecated. >>> As a current maintainer of FreeMarker, I would like to know what will >>> it practically mean in the future, such as, will PR-s be still >>> integrated, will the artifacts be still hosted, and for how long? What >>> steps should we (at FreeMarker) take to ensure that the plugin remains >>> available for users (if any)? >>> >>> Also, can someone answer this user question about the deprecation (as >>> I'm not entirely sure about the answer either)?: >>> https://stackoverflow.com/questions/49072160/why-is- freemarker-ide-in-eclipse-oxygen-jboss-tools-4-5-2-final-deprecated >>> >>> -- >>> Thanks, >>> Daniel Dekany >>> >>> _______________________________________________ >>> jbosstools-dev mailing list >>> jbosstools-dev(a)lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev >>> >>> >>> >> >> -- >> Thanks, >> Daniel Dekany >> >> >> >> > > -- > Thanks, > Daniel Dekany > > > > -- Thanks, Daniel Dekany