i've sent email to brent (contentlicensing author). he's ok with it ...
i'll let you know when i migrate repository to github ... then merge
would be needed. i guess person to do this is the one who did changes on
contentlicesing branch.


lp rok



On 12/09/11 21:16, Brent Lambert wrote:
> Hello Rok,
>
> All this sounds great. I have not yet looked at the Plumi branch, but
assuming that their additional features work well with the eduCommons
community I would be very happy to combine the two. Do you know what
features they have added or what functionality they have changed?
>
> Also very interesting to hear about Plone and GitHub. If we move it
there, what would be the implications? Presumably I would have to join
the github plone collective, and assuming that this is easy enough, and
that Mr. Developer plugin would have no problems finding the code base
there and downloading it through buildout, I think it would be a good idea.
>
> Is there some resource somewhere I can read about to get up to speed
on this?
>
> Thanks,
>
> Brent
>
>
> ----- Original Message -----
>> From: [email protected]
>> To: [email protected]
>> Sent: Saturday, September 10, 2011 9:05:02 AM
>> Subject: request for new release of collective.contentlicensing
>>
>>
>> hey,
>>
>> i've been working with Plumi lately and they've been using their own
>> branch (plone4_compatibility). sadly they didn't notify you about it
>> and they started working on it more then a year ago.
>>
>> now by looking at the changes i saw that this would not be a trivial
>> merge, since you and they added some features. what i'm proposing is
>> to merge and then work on it together and make new release of
>> contentlicensing with new release of plumi.
>>
>> i guess they can always fork it and rename it, but having 2 packages
>> doing almost the same thing, just a little different would only add
>> confusion to users of plone.
>>
>> my motivation behind this is that i just dont want to run plumi
>> installation and require subversion, thats why i'm helping them. :)
>>
>>
>> a little bit out of topic: would you be interested in migrating code
>> to github. i'm migrating plone to github and would mean 5min of
>> additional work to migrate your package as well.
>>
>> please reply on [email protected] or contact me on IRC (garbas at
>> freenode.org)
>>
>> saludos.
>>


_______________________________________________
Discuss mailing list
[email protected]
http://lists.plumi.org/listinfo/discuss

Reply via email to