incubator-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Daniel Dekany <ddek...@freemail.hu>
Subject Re: Donating freemarker-online as part of the FreeMarker project, how?
Date Fri, 10 Mar 2017 18:27:28 GMT
To be clear, the ASF has confirmed receiving the CCLA, also I have
checked the contents of the CCLA (company name and persons match
reality). But because we are only a poddling project, I'm not sure if
we can now proceed with the pull request and merging, or we should
wait for confirmation from the IPMC.


Wednesday, March 8, 2017, 7:18:10 AM, Daniel Dekany wrote:

> Yesterday the ASF has received the CCLA. Does the IPMC accept it, can
> we go ahead with the pull request?
>
> Thursday, February 23, 2017, 7:15:29 AM, Craig Russell wrote:
>
>> Hi Daniel,
>>
>>> On Feb 22, 2017, at 9:24 PM, Daniel Dekany <ddekany@freemail.hu> wrote:
>>> 
>>> Wednesday, February 22, 2017, 8:12:32 PM, Craig Russell wrote:
>>> 
>>>> Hi,
>>>> 
>>>> Sounds like the easiest way to handle this is as you described. 
>>> 
>>> If we can do that, that's great! I will wait a few days to see if
>>> someone else has anything to add, then I will assume that the
>>> Incubator PMC has agreed and I will go ahead.
>>> 
>>>> Get a CCLA from Kenshoo with
>>>> https://github.com/kenshoo/freemarker-online describing the code being contributed
>>>> Add any current Kenshoo employees 
>>>> Get an ICLA from non-Kenshoo folks
>>> 
>>> I'm a bit confused regarding the last point above. We already got
>>> ICLA-s from the non-Kenshoo folks at the ASF, but they have
>>> contributed code to a non-ASF project back then. (Do we rather need an
>>> SGA from them maybe?)
>>
>> If you have ICLAs from all of the non-Kenshoo folks then nothing
>> else is needed from them. The ICLA is not project specific.
>>
>> Craig
>>> 
>>>> Create a git repo for the new content
>>>> After we accept the CCLA, generate a pull request and take in the code
>>>> Change package names
>>>> Change license headers
>>>> 
>>>> Craig
>>>> 
>>>>> On Feb 22, 2017, at 10:39 AM, Daniel Dekany <ddekany@freemail.hu>
wrote:
>>>>> 
>>>>> Hello,
>>>>> 
>>>>> This is related to the incubating FreeMarker project.
>>>>> 
>>>>> A company called Kenshoo has developed a simple but handy online
>>>>> evaluator service for FreeMarker, some 3 years ago, and they are still
>>>>> hosting it. Because they don't develop this service anymore, and
>>>>> because timely pull request merging and deployment seems to become an
>>>>> issue, we would like to bring the source code over to be part of the
>>>>> FreeMarker project. They are willing to donate the source code to the
>>>>> ASF.
>>>>> 
>>>>> As of the more technical aspect of this, the FreeMarker project has
>>>>> multiple Git repos, one for each "product" (one product is the engine
>>>>> itself, another is the documentation/website generator Ant task, and
>>>>> yet another is the website content). These are separate products,
>>>>> because their versioning/releasing is independent. We would like to
>>>>> add one more such Git repo and product, for freemarker-online.
>>>>> 
>>>>> We are trying to find out what's the most efficient yet legally
>>>>> acceptable way of doing this. Just as an example, after the repo was
>>>>> created and we add LICENSE and such, we could, technically, accept a
>>>>> pull request from Kenshoo if they sign a Corporate CLA. I know it's an
>>>>> extreme approach as they contribute to an almost empty repo, OTOH we
>>>>> are talking about only 31 classes and some build files (~160 KB source
>>>>> code). Anyway, how should we do it?
>>>>> 
>>>>> The source code we want to bring over:
>>>>> https://github.com/kenshoo/freemarker-online
>>>>> 
>>>>> Note that the 2 contributors from outside Kenshoo are also FreeMarker
>>>>> contributors, so we can get any papers needed from them (as there was
>>>>> no CLA signed at Kenshoo).
>>>>> 
>>>>> -- 
>>>>> Thanks,
>>>>> Daniel Dekany
>>>>> 
>>>>> 
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>>>>> For additional commands, e-mail: general-help@incubator.apache.org
>>>>> 
>>>> 
>>>> Craig L Russell
>>>> clr@apache.org
>>>> 
>>>> 
>>>> 
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>>>> For additional commands, e-mail: general-help@incubator.apache.org
>>>> 
>>>> 
>>> 
>>> -- 
>>> Thanks,
>>> Daniel Dekany
>>> 
>>> 
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>>> For additional commands, e-mail: general-help@incubator.apache.org
>>
>> Craig L Russell
>> Architect
>> craig.russell@oracle.com
>> P.S. A good JDO? O, Gasp!
>>
>>
>>
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>> For additional commands, e-mail: general-help@incubator.apache.org
>>
>>
>

-- 
Thanks,
 Daniel Dekany


---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org


Mime
View raw message