Community Integrated Version

[Ammler]

Honestly I'd rather wait for an invitation to use project resources like the wiki and possibly version control. However all this is personal opinion, so don't let that stop you from doing it if you are so inclined.

I only spoke about WIKI, nothing more.. (wiki is already for community, you don't need invitation from someone, from who?)
Well, just thought, it would be easier to make a list with all patches included etc., maybe also to track which patches to update for next Build 2.). Instead of making new Thread... and copy everything over...
(isn't that in the sense of CIV?)

Edit: Marked the wiki as draft.

Greets
Ammler

[Vikthor]

Speaking of the wiki, if anybody could write a short howto about desync debugging I would be very thankful. I know there is --enable-desync-debugging configure option but if somebody who knows how to use it could write short article it could help not only CIV but all other desync ridden patches. And as Ammler pointed out you probably won't get any official invitation to wiki, AFAIK WWOTTDGD did not get any invitation too.

[wleader]

After much pressure (ok, just a little pressure), I am ready to embrace using the wiki for Community IV stuff. I still feel that because of the unofficial nature of this project we ought to play nice with the rest of the wiki, so I've made a template that can be quickly added to any of the pages related to this project. Putting the text {{CIV}} into the wiki code will add a warning, and include the page in the Community IV category, This way should the powers that be decide that the wiki is the wrong place for this information, all related pages can be found and copied out and removed.

On another note I was starting to notice a great deal of deference to my opinions on this project. While it is flattering, I don't want to create the precedent that I am the De facto leader of this project. It is named Community Integrated Version, and not wleader IN. I also recognize that I can be very seasonal about my interest in various projects as my amount of free time waxes and wanes throughout the year. When the time comes that I get too busy to contribute regularly, I want Community IV to be able to continue without me. With that in mind, I propose that we regularly elect a new Integrator who will perform those duties. I see no reason to prohibit someone from serving more than once, but I would like to truly establish that this is not just my project.

Any thoughts?

[sulai]

What about letting the patch submitters do Integration?

Then we need no leader and no single person has to do all the integration work.

For example, a new CIV thread is created:

phase one: new patches are allowed. (about one week)
- First guy who transmits a patch has easy work: He just updates his patch A to the current trunk and submits it to the CIV thread.
- Second guy takes this first patch A and add his own patch B. He is only allowed to submit a patch file that includes both his own and the first guy's patch (A+B).
- Third guy adds his patch C and submitts a diff containing (A+B+C).
- During this first week, the first guy may update his patch, but must commit (A'+B+C) in a new post.

phase two: testing and bugfixing. (open end)
- no further new submissions are allowed
- the patch maintainers (and other developers too) may work freely on the latest submission and post their debugged CIV diffs.
- This debugging phase is open end, no deadline defined.

start new cylce
A new cycle may be started 2 weeks after the previous CIV thread at the earliest. This is to give the patch submitters of the previous CIV a little time for testing and bugfixing.
Reasons for starting a new CIV cycle:
* Someone missed the deadline of the previous CIV and wants to submit his patch.
* In the debugging phase, the "trunk is running away": The CIV diff doesn't really fit any more to the latest trunk revision, and patch developers stop updating their patches.