On Fri, 13 Mar 2009 10:44:06 +0100, [email protected]
wrote:
> Jann Forrer <[email protected]> schrieb am 13.03.2009 08:44:12:
> 
>> Andreas Hartmann wrote:
>> > Hi Lenya devs,
>> >
>> > some modules from the 2.0.2 branch look like they weren't maintained
>> > for quite some time. If noone objects, I'd suggest to remove them –
>> > mainly to avoid wrong anticipations and to keep the codebase clean. If
>> > someone uses them, they can still get them from old releases.
>> >
> I agree to remove them from the branch to keep the codebase handy and
> clean.
> 
> Since a new user or dev interested in one of these modules
> for his own development won't find them in an old release,
> I would prefer to move them to an other location outside the branch.
> What about a new svn branch like contributions as Thorsten proposed
> earlier during the modules discussion ?

If I can add, my "user view" to this discussion,

I'm +10 with the Rudolf idea, with a personal add : If this branch is set
up, a little word on this branch in the "official download page" will be
great.

I think that this new branch is very important in order to "show the power
of Lenya" : for example, blog module is IMO and important end-user function
and this module have to be "easy download".

PS: thanks for the work on 2.2 branch

HAND

> This could also be the place for useful add-on contributions like exmaple
> publications
> or modules, which have to be maintained by the users.
> (e.g. the publications from the design contest)
> 
> Rudolf
> 
>> >
>> > Some candidates (feel free to add more):
>> >
>> > * blog
>> > * migration (lacks documentation, could be moved to sandbox?)
>> > * simplesite
>> > * xopus
>> > * task (legacy)
>> > * jcrsource (optional)
>> >
>> > WDYT?
>> I am relly not very experienced in the 2.0.2 branch but I like
>> spring cleaning ;-) Anyway, from my side: no objection.
>>
>> Jann
>>

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to