On 27/2/03 8:12 am, "Carsten Ziegeler" <[EMAIL PROTECTED]> wrote:
> So, we really should come back to the usual open source handling
> of things: first a proposal, than a vote, than the action.
> And not: making a proposal and during the proposal doing the
> action only because one committer that "great". All the other
> committers had even no chance to say their opinion.
Ok, soory, my bad...
Maybe I should have pointed out that the change is backward compatible? Did
you try doing "cvs co xml-cocoon2"? It still works...
Mine _is_ a proposal: if you want to propose something related to code,
usually you stop sitting on your ass and send out a patch to the mailing
list, how can you do the same when what you wanted to propose is the CVS
repository itself?
My vision is pretty simple, you do it, and you keep it backward compatible,
exactly as I did. All the old repositories, with all the old branches, with
all the old names, are _still_ there (the only "unrevertable" change is the
fact that now they're owned by the "cocoon" group, and not by the XML), but
there's no difference between yesterday and today, from your point of view,
if you want to ignore my proposal, just go ahead and do as you always did
using the old xml-cocoon2 name...
> Sorry Pier that this time it hits you, but I hope you feel better
> when you know that you are not the only one doing things in cocoon
> this way. Even I do it sometimes...but it really depends on the
> impact of the change. If the change can be simply reverted it might
> be seen as "ok".
It's not that things can be "reverted", it's that things, for the eyes who
doesn't want to see the change, does not exist... The repository name,
LITERALLY is still there, with the old name and the whole thing... The only
thing you see now are also few new "repositories" which are my proposal to
this list (it's an infrastructure "diff" with a lot of + and no - lines) :-)
Sorry if I wasn't clear from the beginning...
Pier
