Am Montag 28 Juli 2008 11:29:00 schrieb Alexey Eremenko: ...

...

The thing is that only a very small group has write access to Factory and they need to review the submissions for security reasons.

To be able to scale with this setup, we have the maintainers in the "devel projects" which are responsible for the packages and do a first review of submitted changes. So when you like to update a package, you need to submit to these places. Or ask for write access there.

There was no real discussion yet how to handle new packages btw ...

Seriously, I understand the need for maintaining integrity for openSUSE.

Actually I think that a good idea would be to build a "multi-level" introduction of packages into factory,

Actually, this is what we have.

like: 1. community "home" projects on Build Service - experimental packages go here.

basically any project inside and outside of home: has this level.

2. Pre-Factory tree project (place where evaluations will take place on both quality, stability and license, ...) This repository will contain the "candidate" packages, that are aimed at future inclusion into factory.

These are the "devel projects" I spoke before. run osc meta pkg openSUSE:Factory $SOME_PACKAGE to see, which project is used for this package.

3. Factory itself - Novell employees will take packages, from "pre-factory" tree. Packages, that are qualified will be put into factory.

Everybody, independend of Novell Employee or not, can submit packages. However, a small group, the autobuild team is reviewing the submission and accepts or declines it (with a reason). But these submissions should come from a "devel project" to be sure that the experts for these packages have seen and accepted the change.

After all, moving openSUSE distro construction to openly-viewed build service, is made exactly for purpose of external contributions...

Write commits to pre-factory tree should be made upon request for community members.

Layered approach is a good way to make things moving...

I think we have this kind of system already. And we do not make a difference between Novell Employee or not btw. Novell Employees have also not direct write access to Factory and need the review and acceptance from the autobuild group as well. -- Adrian Schroeter SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) email: adrian@suse.de --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org

On Mon, 28 Jul 2008, Alexey Eremenko wrote:

...

...

Now: May I get commit access ?

No ;)

Well, a bit sad :(

No. It's a good thing, that I can rely on the Factory variant. I do want to trust the distribution to a certain degree. And the trust level for Factory inclusion should be much higher than for openSUSE.

Seriously, I understand the need for maintaining integrity for openSUSE.

Actually I think that a good idea would be to build a "multi-level" introduction of packages into factory, like: 1. community "home" projects on Build Service - experimental packages go here. 2. Pre-Factory tree project (place where evaluations will take place on both quality, stability and license, ...) This repository will contain the "candidate" packages, that are aimed at future inclusion into factory. 3. Factory itself - Novell employees will take packages, from "pre-factory" tree. Packages, that are qualified will be put into factory.

After all, moving openSUSE distro construction to openly-viewed build service, is made exactly for purpose of external contributions...

Write commits to pre-factory tree should be made upon request for community members.

Layered approach is a good way to make things moving...

Well, why don't you take the path we currently have: a) Build your stuff in home. b) If it is stable search for a toplevel project, where you can get it moved into and apply for inclusion of your package into that top-level directory. c) If that worked reliable for some time, ask the Novell people (e.g. one providing packages in the same field of software) to think about Factory inclusion. If the statistics are back and working fine, then c) can also be done automatically based on download counts. Ciao -- http://www.dstoecker.eu/ (PGP key available) --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org

On Tue, Jul 29, 2008 at 3:19 AM, Cristian Rodríguez wrote:

Adrian Schröter escribió: Or ask for write access there.

...

There was no real discussion yet how to handle new packages btw ...

I think we should estabilish something like the Fedora package review guidelines.

http://fedoraproject.org/wiki/Package_Review_Process

Well, yes, it makes sense. How do we proceed from here? -- -Alexey Eromenko "Technologov"

On Tue, Jul 29, 2008 at 1:15 PM, Michal Marek wrote:

Cristian Rodríguez wrote:

...

Adrian Schröter escribió: Or ask for write access there.

...

There was no real discussion yet how to handle new packages btw ...

I think we should estabilish something like the Fedora package review guidelines.

http://fedoraproject.org/wiki/Package_Review_Process

Fedora's Package Review Guidelines are a nice checklist for measuring quality of packages, however, in our case, the most important question IMHO should be: "Does this package *need* to be part of the core distribution?". For many packages a home in the buildservice repositories is actually the better option: * Buildservice packages can be updated after distro release quite easily (and without wasting space in you repositories) * Can be provided for released distributions * For the end-user, using buildservice packages is IMO as easy as using distribution packages.

There are plenty of small useful packages on the net. And yes, I believe that they need to become part of the core distro. Especially for offliners among us, that download whole repository and use it locally. And looking at 100 different repositories (Build Service Home projects) is not the same thing as looking into 1 main repository. I prefer to have 1 place to look for packages. -- -Alexey Eromenko "Technologov"

Full ACK here. Also if something gets into the core distro, then it is tested to work with the rest of the distro. Right now even popular repositories are mutually exclusive. Devel versions could still maintained in the BS. Bye,

Not to mention inter-dependencies. If I make a new package that has a dependency on core distro then all is fine, but if my packages have a dependency on third-party packages, and his packages in turn has dependency on some other repository we are returning back into dependency hell. Good example: -iperf and iperfQt - IP performance test. -iperf is not my package, but I need to copy it into my home project because I developing iperfQt which is a Qt GUI for iperf, which is not core package. I don't want to have a dependency on some one else's home project. Thankfully Qt is :) -- -Alexey Eromenko "Technologov" --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org

On Tue, 29 Jul 2008, Michal Marek wrote:

* For the end-user, using buildservice packages is IMO as easy as using distribution packages.

Not. it is not. But openSUSE 11.0 is going good steps into the right direction. Some Buildservice search and repository integration in the yast package search would be a final step. For example the package search in yast could have the option to also search the buildservice and allow (easier than now) to register a new project as data source. Ciao -- http://www.dstoecker.eu/ (PGP key available) --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org

Now, what about offliners, that keep everything locally ? Having too many repositories makes things difficult. -- -Alexey Eromenko "Technologov" --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org

On 2008-07-29 14:07:35 +0000, Alexey Eremenko wrote:

Now, what about offliners, that keep everything locally ?

Having too many repositories makes things difficult.

Having one big repository would make things difficult too. I don't want to imagine how much disk space would be needed... Marcus --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org

On Tue, Jul 29, 2008 at 2:28 PM, Alexey Eremenko wrote:

On Tue, Jul 29, 2008 at 2:18 PM, Marcus Hüwe wrote:

...

On 2008-07-29 14:07:35 +0000, Alexey Eremenko wrote:

...

Now, what about offliners, that keep everything locally ?

Having too many repositories makes things difficult.

Having one big repository would make things difficult too. I don't want to imagine how much disk space would be needed...

Actually about disk space: Debian 4.0 takes 13 GB of space per 1 architecture (i386+noarch) for 18000 packages. openSUSE 10.3 takes 8 GB of space per 1 arch for 6000 packages. Which means: openSUSE already has all the big packages, what is lacking are utilities and "helper" packages. Adding many useful utilities (many of whom are CLI) won't make the core distro even 2x bigger than we are now. If we count the fact that we are not going to add 10000+ utilities overnight, rather it will be a long process lasting several years, then I see no problem at all, since both hard disks becoming big, 50mbps VDSL becoming reality and blu-ray discs of course.... -- -Alexey Eromenko "Technologov"

On Fri, 1 Aug 2008, Vincent Untz wrote:

What would be bad about having an openSUSE:Community repository where we can put everything that is not in the core repository (after some review, of course)?

Go back in the archives of this list (probably a year or more) and search for the Packman effect (for sure Packman is mentioned in the thread). There was a lengthy discussion, why such a large repository would create more problems, than it solves. Also this thread showed some of the resulting problems. Ciao -- http://www.dstoecker.eu/ (PGP key available) --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org