Great, thanks! Guys, can we do this like with freemarker-online-tester, i.e., we create a git repo, put LICENSE and NOTICE into it, then Oath Inc. signs a CCLA with the employees involved listed, then they replace the copyright headers and rename the package in their repo, and do a PR, and we accept the PR, and done. I would still ping legal of course (someone else?).
Or, we go down on the heavy handed path, with SGA-s and who knows what? I hope not, as this is young, and small project (there's no much IP clearance work to do, no history to untangle). Ben, on your side (Oath Inc.), it would be good if it's kept track tightly who have contributed to the code, because of the paper work. (Like I hope on Github nobody will pop up with a PR suddenly. (: ) Are they all employees of Oath Inc., and did the work as such? As of the project name, see other mail. (I would add that I prefer a name that is generic enough to be not (easily...) seen as a trademark.) Thursday, September 6, 2018, 6:14:06 PM, Ben Jackson wrote: > Here is the existing codebase for this project. > > https://github.com/yahoo/freemarker-maven-plugin > > It seemed more straightforward to work through our opensource team to > publish the code so that it could be reviewed before continuing this > conversation. Please comment on any remediations you see as needed (if > any) before working towards gifting this code to the apache foundation as a > starting point for this plugin. > > Also, as mentioned in the conversation above, it would be preferable if > this plugin had a unique and easily searchable name. Does anyone have > ideas? > I have no good ideas; here are some uninspired options: > > FreeGenerator > FMGenerator > FMGen > fmg > fmgen > FMarkerGen > MarkerGen > MGen > MGenerator > > > On Mon, Aug 20, 2018 at 10:05 AM Woonsan Ko <[email protected]> wrote: > >> On Mon, Aug 20, 2018 at 10:15 AM, Daniel Dekany <[email protected]> >> wrote: >> ...snip... >> > Without an ASF account the contributors couldn't edit the Wiki page. >> > If *they* open a JIRA issue, then we all can edit it. So that's what I >> > recommend. >> Makes sense to me. We can wait for Ben/Mark to create a JIRA ticket >> and we can edit its description together there. >> >> ...snip... >> > This was my intent from the beginning. A generator file can be a >> > .json, or an .ftl[h|x] (or whatever we come up with later, like an xml >> > that's transformed by a templates/myxmltransformat.ftl). They are >> > totally unrelated, independent generator files. I have never assumed >> > that they come in pairs, hence there was never a such thing as "ftl >> > only generator" in my head either. All generator files are lonely. >> That's clear now. I think I made an unnecessary confusion by using >> 'ftl-only' generator when mentioning .ftl type generator. >> Thanks! >> >> Woonsan >> > > -- Thanks, Daniel Dekany
