[opensuse-factory] "contrib" repository: Further progress
We need to progress this project further. Next stage, I believe is to decide who are the maintainers, that have the final say on what gets in. Maintainers will be grant write access to "contrib" repo, that currently was added to OBS. Currently only Coolo has write commit access, and I believe he will share it with future maintainers. As Yaloki puts it - we need uneven number of leaders, so problematic cases could be solved by voting. Maintainers: Who volunteer ? -I am. (Alexey) -Pascal Bleser (yaloki) ? -Martin Schlander ? -Michal Marek ? -Anyone from Novell ? -Anyone ? Next stage would be asking coolo to give write commit access. I want to have few packages inside contrib by 11.1 BETA1 time-frame (due in 1 month) This is an open discussion so feel free to participate... -- -Alexey Eromenko "Technologov" --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Alexey Eremenko wrote:
We need to progress this project further.
Sure, that's what we're doing now by raising issues and proposing solutions.
Next stage, I believe is to decide who are the maintainers, that have the final say on what gets in. Maintainers will be grant write access to "contrib" repo, that currently was added to OBS. Currently only Coolo has write commit access, and I believe he will share it with future maintainers.
As Yaloki puts it - we need uneven number of leaders, so problematic cases could be solved by voting.
Maintainers: Who volunteer ? -I am. (Alexey) -Pascal Bleser (yaloki) ? -Martin Schlander ? -Michal Marek ? -Anyone from Novell ? -Anyone ?
I'll definitely be available to maintain packages in there. And I think I qualify to do some peer reviews :)
Next stage would be asking coolo to give write commit access.
I want to have few packages inside contrib by 11.1 BETA1 time-frame (due in 1 month)
s/want/would like/
This is an open discussion so feel free to participate...
Well, first of all, please slow down.
We're not there yet.
cheers
- --
-o) Pascal Bleser
I'll definitely be available to maintain packages in there. And I think I qualify to do some peer reviews :)
Well, all maintainers are also peer-reviewers, I think.
I want to have few packages inside contrib by 11.1 BETA1 time-frame (due in 1 month)
s/want/would like/ Yes, correct. My sentence was a bit aggressive.
This is an open discussion so feel free to participate...
Well, first of all, please slow down. We're not there yet.
The question is: why slow down ? Or what slowness will give us ? I think using momentum for acceleration of the project is better than slowing down, especially now, in initial stage of the project. -- -Alexey Eromenko "Technologov" --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Alexey Eremenko wrote:
I'll definitely be available to maintain packages in there. And I think I qualify to do some peer reviews :)
Well, all maintainers are also peer-reviewers, I think.
Yeah, true, most probably. [...]
This is an open discussion so feel free to participate... Well, first of all, please slow down. We're not there yet.
The question is: why slow down ? Or what slowness will give us ?
More opinions, time for more people to read the thread and give feedback. As well as the items I mentioned in my previous posts: - - find enough packagers - - prepare the infrastructure and documentation before putting packages into the repository Did we actually take decisions on the questions we raised in this thread? IMHO we should try to get more feedback/ideas first.
I think using momentum for acceleration of the project is better than slowing down, especially now, in initial stage of the project.
It's a balance between both :)
cheers
- --
-o) Pascal Bleser
Pascal Bleser
Alexey Eremenko wrote:
I'll definitely be available to maintain packages in there. And I think I qualify to do some peer reviews :)
Well, all maintainers are also peer-reviewers, I think.
Yeah, true, most probably.
[...]
This is an open discussion so feel free to participate... Well, first of all, please slow down. We're not there yet.
The question is: why slow down ? Or what slowness will give us ?
More opinions, time for more people to read the thread and give feedback. As well as the items I mentioned in my previous posts: - find enough packagers - prepare the infrastructure and documentation before putting packages into the repository
Did we actually take decisions on the questions we raised in this thread? IMHO we should try to get more feedback/ideas first.
Should we update the wiki page with some of this discussion. I would suggest to list the open questions and also the various proposals made for them. Otherwise ideas get lost.
I think using momentum for acceleration of the project is better than slowing down, especially now, in initial stage of the project.
It's a balance between both :)
;) Note also that we do not need to have everything one hundred per cent perfect. We need a solid base and I expect that we change things over time. I think we have a base but it's not broad enough right now, Andreas -- Andreas Jaeger, Director Platform / openSUSE, aj@suse.de SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) Maxfeldstr. 5, 90409 Nürnberg, Germany GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
Pascal Bleser wrote:
Alexey Eremenko wrote:
The question is: why slow down ? Or what slowness will give us ?
More opinions, time for more people to read the thread and give feedback. As well as the items I mentioned in my previous posts: - - find enough packagers - - prepare the infrastructure and documentation before putting packages into the repository
There is this "release fast and often" thing in the open source world which means that more people can test stuff and you get smaller incremental changes. For this repository it could mean that you start off early with a small set of packages everyone taking part can agree on, and you're able to test infrastructure and build documentation incrementally as you go. That's usually better than trying to have everything perfect before you start, and spend so much time in the design phase that people lose interest once you're ready to get to the implementation. Robert Kaiser --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Alexey Eremenko wrote:
I'll definitely be available to maintain packages in there. And I think I qualify to do some peer reviews :)
Well, all maintainers are also peer-reviewers, I think.
Hmm, I'm not sure if the "who is allowed what" topic is solved then or whether we have the same definitions :-o. Alexey > ... decide who are the maintainers, that have Alexey > the final say on what gets in. vs. Pascal > I'll definitely be available to maintain packages in there. Let's start with the definitions * every package needs a "maintainer", the person who creates the spec file and is responsible for updating the package - there can be "maintainers" with hundred packages as well as "maintainers" with a single package - these people may or may not have direct write access to the package in the Contrib repo, see below * the repository needs a small group that has access rights to review & create packages and review changes (if there's going to be a review of changes) - "maintainer" is taken, call them "reviewers" perhaps? - number of "reviewers" is going to be much lower than the number of "maintainers" in the long term - of course, anyone can help with reviews, but the final decision is up to this group Do we speak the same language? Or does "maintainer" mean something different to you? Now "who is allowed what" * "reviewers" can do anything by definition, they have write access to Contrib * IMO being a "maintainer" does not necessarily mean being a "reviewer" a) "maintainer" only has access to Contrib/mypackage, OR b) "maintainer" only has access to home:maintainer/mypackage and changes are propagated to Contrib/mypackage _somehow_ (_link vs. submitreq) (Replace Contrib above with openSUSE:Factory:Contrib, openSUSE:11.1:Contrib or whatever the final names will be.) Does this make sense to any of you or do you have a different model in mind? thanks, Michal --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Michal Marek
Alexey Eremenko wrote:
I'll definitely be available to maintain packages in there. And I think I qualify to do some peer reviews :)
Well, all maintainers are also peer-reviewers, I think.
Hmm, I'm not sure if the "who is allowed what" topic is solved then or whether we have the same definitions :-o.
Alexey > ... decide who are the maintainers, that have Alexey > the final say on what gets in. vs. Pascal > I'll definitely be available to maintain packages in there.
Let's start with the definitions
* every package needs a "maintainer", the person who creates the spec file and is responsible for updating the package - there can be "maintainers" with hundred packages as well as "maintainers" with a single package - these people may or may not have direct write access to the package in the Contrib repo, see below * the repository needs a small group that has access rights to review & create packages and review changes (if there's going to be a review of changes) - "maintainer" is taken, call them "reviewers" perhaps? - number of "reviewers" is going to be much lower than the number of "maintainers" in the long term - of course, anyone can help with reviews, but the final decision is up to this group
Do we speak the same language? Or does "maintainer" mean something different to you?
Now "who is allowed what"
* "reviewers" can do anything by definition, they have write access to Contrib * IMO being a "maintainer" does not necessarily mean being a "reviewer" a) "maintainer" only has access to Contrib/mypackage, OR b) "maintainer" only has access to home:maintainer/mypackage and changes are propagated to Contrib/mypackage _somehow_ (_link vs. submitreq)
(Replace Contrib above with openSUSE:Factory:Contrib, openSUSE:11.1:Contrib or whatever the final names will be.)
Does this make sense to any of you or do you have a different model in mind?
It makes sense to me and I added it to the wiki as a starting point. If you redefine anything, please adjust the wiki as well, we need to have the final outcome of this discussion documented, Andreas -- Andreas Jaeger, Director Platform / openSUSE, aj@suse.de SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) Maxfeldstr. 5, 90409 Nürnberg, Germany GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
participants (5)
-
Alexey Eremenko -
Andreas Jaeger -
Michal Marek -
Pascal Bleser -
Robert Kaiser