-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Alexey Eremenko wrote:
On Sun, Aug 17, 2008 at 2:56 AM, Pascal Bleser <pascal.bleser@opensuse.org> wrote:
Posting from Alexey's "Requesting to create a top level project "Contrib"" post:
Pascal Bleser wrote:
Either you want a coordinated effort with several contributors or you just rush something badly thought out on your own. If you want the former, then we're not done discussing it. For example, I have some doubts about your list of candidates on the wiki page [1]. To be more specific, dynagen/dynamips? Who the hell cares about those ? You and 5 other people ? Does that make it a good candidate for being in the contrib repository ? (playing devil's advocate here)
Well, those 2 specific packages are needed by me, but I agree, that those may be poor candidates, at least for first stage.
I have removed them from candidates list for now.
Well I just meant that maybe we should think a bit about which packages we want to be in contrib :)
+1
I think that, indeed, starting with the smaller things that are missing in Factory is a good idea. They're usually not very invasive, and easier to package.
+1
About release cycle: "Contrib" will be in sync with Factory release cycles. It will BETA-test during openSUSE 11.1 BETA cycle, together with it
Yes, that's one way of doing it, and it sounds like a good plan -- at least it does to you and me. But maybe someone else sees a problem with doing that, and has a better idea.
+1
e.g.: what do we think is an appropriate size for the repository to be ? - - just shove anything into it and possibly end up with a huge repository; - - keep it small and well tested ? Ideally it should be both reasonably stable and have large number of packages. Specific packages are to be reviewed on case-by-case basis.
Ok. So how do we want to do those reviews ? Do we need a release management team for contrib ? (people who decide what gets in, what doesn't, which versions are OK after doing a bit of research on upstream)
I think that approval needs to be done by aleast 2 other members of the community. I think having 2 peer reviews should be required as a starting point.
It might be organizational overkill... but on the other hand, we need something to handle it, because once we start the project, we might end up with 50 or 100 requests of people who want this, and that, etc...
+1
Maybe later on we will revisit the idea, and add separation. (stable/unstable) But if anyone thinks we need unstable repository now, let discuss it.
But only for staging.
An example: - - someone requests a package of "foo" - - the release management team reviews the request, - -- has a look at upstream: - --- is the software actively developed or is it dead since 2004 ? - --- does it comply with legal ? - -- checks whether we have someone who wants to maintain that package in contrib - - the release management says "ok, let's have it in contrib" - - packager X builds RPMs of it
and then, at that point.. how do we determine whether it's stable or not? I think that the next item should be "test":
- - the packages go into "contrib-testing" and is announced somewhere - - testers install the package and give it a run, reporting whether it has bugs or whether it works - - once we have a critical mass of positive reviews and no show-stopper bugs (whatever that critical mass is.. 5 positive reviews and no blockers ?), the package is moved from "contrib-testing" to "contrib"
It's just an idea...
+1 - -- Boyd Gerber <gerberb@zenez.com> ZENEZ 1042 East Fort Union #135, Midvale Utah 84047 -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) Comment: For info see http://quantumlab.net/pine_privacy_guard/ iEYEARECAAYFAkioS7AACgkQVtBjDid73eZLdQCdHcQxRHw0SVoWYU8hstKFIqGV 5CcAnjNyB6bfavuf+BMyl6wngJLK+A6t =UON/ -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org