Re: [eGroupWare-core] How to move on? (second try)

[Ralf B. <Ral...@di...>]

Hi Weiwu, hi Frank,

my thoughts about branches:

- they are fine for a custom development, ment for later merging (eg. 
it's based on the stable branch, but cant be commited there, because of 
the feature freece).
- they are not ok for custom developments never ment to be published, as 
sf.net requires everything to be under an open source license.
- I also disagree putting custom logos there, or UI modifications for a 
single customer. Better use the time to make the concerned part of the 
UI configurable. That way it can easyly be integrated in the main 
codeline (in HEAD of cause).

About the Incubator: If I understand it right, it should be for 
contributed applications, which are (not yet) in the regular eGroupWare 
release. Please correct me if that's wrong.

 From a release point of view, we would not need an Incubator, as our 
release is atm. the cvs alias "all", so additional apps (directories in 
your cvsroot) dont matter. It might help to have a cleaner cvsroot, if 
the Incubator is a single directory under the cvsroot, with different 
apps in it (like atm. the old directory).

For porting your changes back to the main eGW codeline, an Incubator (as 
I understood and describt it above) does not help. We would need a 
branch on the concerned directories (eg. the phpgwapi), else we are not 
able to merge.

Last but not least: Do we really want a vote for each new app to be 
included. My understanding so far is: it need to be announced on the 
list and if noone objects in a reasonable time, it can be imported 
without a vote. I would prefer to leave it that way.

Ralf

Frank Alcantara schrieb:
>>>Should i take care of the project management? Seems like no one else seem to
>>>care.
>>> 
>>>
>>Well, I currently care about one idea when I talked about one month ago: 
>>I wish each developer has the right to branch without explicit 
>>permission. Now do we have this right? (sorry again I didn't read 
>>through all the 60+ emails in last two weeks.) If it is okay, I think I 
>>am going to branch right now. Now I have several customers using several 
>>slightly modified versions of egroupware (mostly UI modifications) that 
>>is done by contract, currently we maintain it on svn server inside our 
>>company, and keeping them a seperate branch on the main cvs repository 
>>may save management trouble. I think many people like me have the same 
>>feeling: they possibily have other versions of slightly modified 
>>egroupware, and the modification is too perticular (e.g. insert client 
>>company logo) to go to HEAD.
>>
> 
> Hi Wiewu, Lars... 
> 
> I still believe in incubator idea. Sorry, but I totally disagree about
> the freedom to branch... it will bring us a total mess of projects,
> inside our project and we should avoid it. 
> 
> We should have the Incubator, with rules. 
> 
> This is a draft for the rules I think could be great to project.
> 
> 1 Each branch should have his own page in egw incubator site
> 2. All project in incubator must have the brand eGroupWare Incubated
> Project, in his logo and pages.
> 3. To be in incubator the project must be approved by developers vote.
> 4. The incubator projects can have his own developers list and
> structure.
> 5. Each incubated project must have at least one Egw developer as leader
> 
> Frank Alcantara
> 
>>
>>
>>-------------------------------------------------------
>>This SF.Net email is sponsored by: New Crystal Reports XI.
>>Version 11 adds new functionality designed to reduce time involved in
>>creating, integrating, and deploying reporting solutions. Free runtime info,
>>new features, or free trial, at: http://www.businessobjects.com/devxi/728
>>_______________________________________________
>>eGroupWare-core mailing list
>>eGr...@li...
>>https://lists.sourceforge.net/lists/listinfo/egroupware-core
>>
> 
> 
> 
> -------------------------------------------------------
> This SF.Net email is sponsored by: New Crystal Reports XI.
> Version 11 adds new functionality designed to reduce time involved in
> creating, integrating, and deploying reporting solutions. Free runtime info,
> new features, or free trial, at: http://www.businessobjects.com/devxi/728
> _______________________________________________
> eGroupWare-core mailing list
> eGr...@li...
> https://lists.sourceforge.net/lists/listinfo/egroupware-core

-- 
eGroupWare Training ==> http://www.outdoor-training.de/egroupware