Grievance: Cease and Desist Request: Standard Resolution Procedure:
1) The Project Coordinator Should attempt to make decisions according to the consensus of the Project Members. Mr. Bragin is making procedural changes with out the full consensus of all Project Members.
2) The Repository Coordinator Should make decisions which are fair and reasonable, and preferably consistent with the consensus of the Project Members. Due to the unfilled Repository Coordinator position, Mr. Bragin has assumed full control of that position and making decisions with out the full consensus of all Project Members.
3) General rules: a) Violation of first rule: Project Coordinator issued change orders, Project Members began working on the changes. These changes are against the general consensus among the Project Members. Reference: http://www.reactos.org/archives/public/ros-dev/2008-June/010394.html
b) Violation of second rule: Project Coordinator banned Project Member with out the ability to rejoin the Project at any time.
c) Violation of third rule: Project Coordinator assumed full control of Repository Coordinator position and used that position to remove access to a Project Member.
Adhering to: Standard Resolution Procedure: The procedure: The procedure begins when a draft General Resolution is announced on a public Project mailing list. Which no other rule can apply, I hereby request a Cease and Desist until this Grievance is heard by all Project Members. Project Members have a contractual agreement and must abide by it.
PS: This is a very serious mater and not at all a joke. If this project has any merit, it needs to resolve these issues in the open.
Hi,
Maybe you guys can use a distributed version control system such as Mercurial and git to avoid such problems in the future... =)
[ simon.cpu ]
Oops, I didn't read the whole thread. I guess someone proposed it already. Anyway, here's a good wiki on the subject:
http://wiki.freebsd.org/VersionControl
[ simon.cpu ]
"ReactOS Roadmap A short sum-up of the ReactOS roadmap, for more information visit our ReactOS roadmap page. Short-term plan The next release will be 0.3.5, with an earliest projected release date being May, 2008."
Another grievance. Please have this updated. ReactOS is now part of our campaign here in India.
Rgds, CK Raju
hehe, i have it updated in the spanish version :-P
Date: Wed, 25 Jun 2008 09:59:40 +0530 From: ck.thrissur@gmail.com To: ros-general@reactos.org Subject: Re: [ros-general] Grievance
"ReactOS Roadmap A short sum-up of the ReactOS roadmap, for more information visit our ReactOS roadmap page. Short-term plan The next release will be 0.3.5, with an earliest projected release date being May, 2008."
Another grievance. Please have this updated. ReactOS is now part of our campaign here in India.
Rgds, CK Raju _______________________________________________ Ros-general mailing list Ros-general@reactos.org http://www.reactos.org/mailman/listinfo/ros-general
_________________________________________________________________ MSN Video. http://video.msn.com/?mkt=es-es
Have a heart for the english version too...
On 6/25/08, Javier Fernández Arroyo jfarroyo82@hotmail.com wrote:
hehe, i have it updated in the spanish version :-P
Date: Wed, 25 Jun 2008 09:59:40 +0530 From: ck.thrissur@gmail.com To: ros-general@reactos.org Subject: Re: [ros-general] Grievance
"ReactOS Roadmap A short sum-up of the ReactOS roadmap, for more information visit our ReactOS roadmap page. Short-term plan The next release will be 0.3.5, with an earliest projected release date being May, 2008."
Another grievance. Please have this updated. ReactOS is now part of our campaign here in India.
Rgds, CK Raju _______________________________________________ Ros-general mailing list Ros-general@reactos.org http://www.reactos.org/mailman/listinfo/ros-general
MSN Video. http://video.msn.com/?mkt=es-es
Well, this is serious... I would like to hear from the Project Coordinator what is officialy his position about this acusations. And them I propose a voting about revoking the made decisions and another about revoking his position. The ideal would be a virtual assembly (have a date marked and every member enters a channel and discuss, make other propositions and vote. I undertand that a "Cease and Desist" is legitim, but it doesn't help to resolve the issue, unless it is used as a preassure mechanism.
Farewell
2008/6/23 James Tabor jimtabor@adsl-64-217-116-74.dsl.hstntx.swbell.net:
Grievance: Cease and Desist Request: Standard Resolution Procedure:
- The Project Coordinator Should attempt to make decisions according
to the consensus of the Project Members. Mr. Bragin is making procedural changes with out the full consensus of all Project Members.
- The Repository Coordinator Should make decisions which are fair and
reasonable, and preferably consistent with the consensus of the Project Members. Due to the unfilled Repository Coordinator position, Mr. Bragin has assumed full control of that position and making decisions with out the full consensus of all Project Members.
- General rules:
a) Violation of first rule: Project Coordinator issued change orders, Project Members began working on the changes. These changes are against the general consensus among the Project Members. Reference: http://www.reactos.org/archives/public/ros-dev/2008-June/010394.html
b) Violation of second rule: Project Coordinator banned Project Member with out the ability to rejoin the Project at any time.
c) Violation of third rule: Project Coordinator assumed full control of Repository Coordinator position and used that position to remove access to a Project Member.
Adhering to: Standard Resolution Procedure: The procedure: The procedure begins when a draft General Resolution is announced on a public Project mailing list. Which no other rule can apply, I hereby request a Cease and Desist until this Grievance is heard by all Project Members. Project Members have a contractual agreement and must abide by it.
PS: This is a very serious mater and not at all a joke. If this project has any merit, it needs to resolve these issues in the open. _______________________________________________ Ros-general mailing list Ros-general@reactos.org http://www.reactos.org/mailman/listinfo/ros-general
Dear Eduardo, first of all, who are you that *I* have to give explanations to you, or listen to your proposals of succesfully destroying the project?
Since I know absolutely nothing about you, and, probably, you know nearly nothing about me and the project (yes, of course we held an assembly already), I doubt you are entitled to judge me or anyone else of ReactOS.
If you would give me some background info about yourself, I could care more.
Anyway, closer to the facts, it was a test of our team, how strong it is, and what if a teamkiller exists. There were some misunderstandings, problems, which are (hopefully) resolved now. Also, James proposed a good way to officially solve this kind of problems in future, however, we agreed on discussing it more with all team members to ensure it's good, which would be a must when reactos development team grows over a certain limit.
Right now, in case of *any* problem, people should talk directly to me first. Lots of problems could go away with just talking first. If that doesn't help, then official procedure applies.
The same could have been applied to me (talking first), but I decided to take blaming to myself and push Magnus decision myself, without involving team members in a process of "Magnus punishment" (since this is anti-social behavior). I realized the magnitude of this problem, but I didn't think Magnus will go as far as making false claims and lie about me. But, again, this happens in big projects, and I have experience in that already.
If there is anything else, just ask, but in future, use a more polite way of obtaining information.
With the best regards, Aleksey Bragin ReactOS Foundation President and Project Coordinator.
On Jun 25, 2008, at 6:45 PM, Eduardo Menezes wrote:
Well, this is serious... I would like to hear from the Project Coordinator what is officialy his position about this acusations. And them I propose a voting about revoking the made decisions and another about revoking his position. The ideal would be a virtual assembly (have a date marked and every member enters a channel and discuss, make other propositions and vote. I undertand that a "Cease and Desist" is legitim, but it doesn't help to resolve the issue, unless it is used as a preassure mechanism.
Farewell
-
Aleksey Bragin -
CK Raju, Thrissur -
Eduardo Menezes -
James Tabor -
Javier Fernández Arroyo -
Simon Cornelius P. Umacob