Hi Stephan, Le vendredi 25 septembre 2009, Stephan Kulow a écrit :
Am Freitag 25 September 2009 schrieb Johannes Meixner:
Hello,
On Sep 24 17:31 Stephan Kulow wrote (shortened):
* We create openSUSE:Factory:Devel as a pool of packages with single maintainers, maintainers can move their packages their if they do not feel they belong in any specific group. In there you only maintain your package, not the rest.
First of all, I agree with your initial analysis that the current model doesn't make sense for all packages.
What exactly is meant with "you only maintain"?
Is it meant as a kind of habit, i.e. "in openSUSE:Factory:Devel you are obliged to maintain only your package, not any other packages in openSUSE:Factory:Devel" or is it meant as something which is enforced by the Build Service, i.e. "only you can maintain your package(s) (i.e. accept submit requests and so on) not other people in openSUSE:Factory:Devel can do this" ?
If you mean the latter, what happens when there is a severe issue with a package but its "single maintainer" is not available for some time (e.g. is on vacation or whatever)?
Right now devel projects are setup all or nothing. If you have a package in it, you became maintainer for all other packages. For many projects this works very fine (Publishing, Base:System, GNOME, KDE, perl - just to name a few). For others it doesn't (devel:libraries:c_c++ is my favorite "no group feeling" project).
I beg to disagree for Base:System. It was the first example that came to my mind as a "no group feeling" project. I have 3 packages I maintain in Base:System (dmidecode, sensors, i2c-tools) and I was forcibly subscribed to a list where I receive submit requests and answers for all other packages of Base:System. The fact is that Base:System is big and I don't care about what happens to all the other packages there. I do not have any interest in following them _and_ I definitely do not have the time either. I believe it would have been saner to let people ask for separate devel projects where they felt the need, rather than forcing all packages to belong to a group as was done. If you think there really is room for a Base:System project with a group feeling, then maybe this means that it should be shrunk to a much smaller project only containing the real base system, rather than being a default container with packages with no other obvious home, as it the case right now IMHO.
So what I'm proposing is to create a place where you can put your package if you don't feel connected to any group - technically for that package. And this group I would setup so that everyone decides for his package, who maintains it (this doesn't mean it's a single person).
Sounds like a very good idea to me. -- Jean Delvare Suse L3 -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org