On Fri, Dec 30, 2011 at 6:07 PM, jdd <jdd@dodin.org> wrote:
Le 30/12/2011 23:52, Greg Freemyer a écrit :
On the technical side, vetos definitely exist, and they exist now.
The Release Manager (Coolo) ultimately decides what goes into openSUSE. ie. The Release Manager has veto power.
I challenge this. yet Coolo have some power on paid suse people.
eg. If I decided I wanted to submit a patch to change grub to grub2, it has to be accepted. And in the current setup that basically means Coolo has to accept it. (or veto it).
if you where the only maintainer of grub and decided to stop it, I don't see what coolo could do.
Let me switch to an area I know more about, filesystems. At some point I assume btrfs will be the default filesystem on a new opensuse install. ext4, xfs, etc. will still be supported at that point. ie. There will not be a shortage of choices nor a shortage of maintainers for the options. I don't know exactly how the decision to make btrfs the default will be made. But it should not be made by only the btrfs maintainers, nor should it be made only by the ext4 maintainers. It is a project decision. With the current setup Coolo and/or Andreas I assume would come up with an adhoc method for making that decision. Probably they would talk to the SUSE filesystems experts, etc. Once a decision along those lines is made, the project will be steered in that direction. But if today, I apply to be a zypper maintainer, then I submit changes to make btrfs be the default there is no guarantee those SRs will be accepted. And they shouldn't be until there is a "project" decision that we are ready for btrfs to be the default. ie. Coolo can simply reject SRs that implement changes for direction he does not want to see happen. I call that veto power. Greg -- To unsubscribe, e-mail: opensuse-project+unsubscribe@opensuse.org To contact the owner, email: opensuse-project+owner@opensuse.org