>>> On Fri, Sep 2, 2005 at 8:31 pm, in message <[EMAIL PROTECTED]>, [EMAIL PROTECTED] wrote: > Thank you guys for the positive feedback! I hadn't realized the complexity > of the process originally but your messages got me thinking about it. >
Yes Pascal's emails are full of great ideas. The yast integration is a splendid idea! I wonder how that could be achieved? Answering to his email seems futile since I concur totally. > We need a simple mechanism that will use potential from the whole world. > Otherwise, if we go directly for a perfect solution, we may never launch it. > Here are the objectives I see and how to accomplish them: > > 1. How to collect a large number of RPMs > We have to allow everyone to create a free account and to upload RPMs. > Everyone? Sure I think that would be OK. I had such an open policy with Yoper, but this brings me to your next point which was ultimately the biggest issue arising from 1.) > 2. How to protect download users from bad RPMs > We have to maintain a download count and user comments for each RPM. That > way download users will know what risk they are taking by installing an RPM > for the first time or without a positive comment. Yes, we'll also rely on > the downloaders' good faith to provide good comments. > There needs to be a signoff model. I cannot imagine to allow 1 without any control mechanism. This would result in chaos. I do speak from experience and maintaining a mess is hard work. Further on I introduced such a test model (with a package being promoted from "staging" into "stable" and that did work better in my opinion. Something like that as a minimum even if a singoff modell is too strict (works for the kernel thoug?) I can remember that Debian and the others all have similar policies. I shall go back and read them as Pascal suggested. > 3. How to protect the host from being flooded > We can have a few people who authorize uploads bigger than a certain size. > To distribute the workload among the authorizers, we can create multiple > brackets, e.g. 1MB, 10MB, 100MB. We can also maintain a quota per user to > avoid flooding through many small files. > Good point. Individual user quota is certainly a minimum req. for that. > All those things are easy to implement through the wiki. If some problems > occur later, we'll act on them as we go. We'll learn how to maintain the > repository while it's growing. > How would you see this implemented though the wiki? Upload, bad rpm protection and so on. Curious ..... . > I also thought of recruiting "trusted builders" but that would be a too > formal yet too slow process and the initiative will lose momentum. > Some sort of check must happen otherwise we will end up in chaos. > Let me know what y'all think. > In principle a totally open upload policy is acceptable and certainly advisable for a seperate repository, let's call it SUPER repository. SUSE and also the OSS release itself needs to stay stable and commercial grade to be able to be be valued as a product in the business community and by a wider audience, which after all is the basis for our future at Novell and SUSE. An addon reposiory around a commnity based 1 CD install could be much more experimental than our mainstream can. Experimental SUPER - Stable SUSE. SUPER compatible with SUSE --> Innovation can happen in both and the repository is really just an OSS addon to a stable distro. Something similar (does not have to be called SUPER ;) .... that would be advisable IMHO to allow as you rightfully say, a fast process and that way I can imagine us growing to a large size quickly. Out of that huge pool distributed with a modified YAST/apt/yum (would it not be great to have all of them supported) in the 1CD installer around SUPER. SUSE.de can then decide which quality rpm's to use in the commercial grade base distro. Every new SUSE release we can recreate the large repository with the help of the previously by suse people mentioned public build servers, which will go online next year some time. I can see this working perfectly with people of your caliber on board and with the support of suse.de. This would satisfy both the commercial need of us at Novell and also the need of the community to have a large amount of packages, even if they are "experimental" and provide with an answer to other distro's like Ubuntu, which have a similar model (I call it the Yoper model ;) - 1 CD - experimental stuff - user friendly) This would be a very exciting distro indeed with low entry barriers. Not elitist and open to the public satsfying both the need of the community and the commercial reality. I like your ideas and I hope I could somehow gather them together into this email. Let me know what you think. Andreas --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
