In thinking of this some more, I realized that I only added to the mass of confusion and complaints. So, I will try to be more clear with the issues, and a possible set of solutions.
There are three distribution and contribution points. These are the cooker, the contrib., and the club. There does not seem to be a clear definition of the difference between these or what the relationship should be. A second set of issues is around the contributions themselves. Where should something be contributed, and who has permission, and if access is needed, who can grant that access. So, here is a recommended solution for this: The contrib. are should allow anyone to upload suggested packages that they have constructed. These would be considered the lowest level of contribution. To be allowed to move to the second level, and include a binary RPM, they must be mentored by someone. This gets them to the club level. Once again, they should be able to upload packages as they are able. To post something for cooker, they once again must be mentored. When they are able to produce packages that meet a well-documented set of requirements, then they will be elevated to cooker level. Now, to really make this work, each of the mentor levels must have the capability to increase access to the next level. If this is not done, the process no matter which one is followed will NEVER scale and we will miss out on a lot of opportunity. While I realize this may not be the best possible fit, it is however a suggested route that could ease the burden on the few that control all the access and make this more a larger project and potential success for all of us. Richard -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Jean-Michel Dault Sent: Sunday, January 26, 2003 12:04 PM To: [EMAIL PROTECTED] Cc: Stefan van der Eijk Subject: Re: [Cooker] the line between cooker and contrib Le dim 26/01/2003 � 09:00, Stefan van der Eijk a �crit : > php-dba_bundle currently BuildRequires db4-devel > ADVX-build is needed by apache-1.3.27-5mdk > db4-devel is needed by php-dba_bundle-4.3.0-2mdk > libjs1 >= 1.5 is needed by php-xslt-4.3.0-2mdk > Can we please be a bit more carefull with these? The problem here, is that Cooker is always in constant evolution, but at the same time, you are not allowed to upload new packages into Cooker. You have to e-mail QA all the time, and these changes are manual, unfortunately. So instead of having to wait for a week for the package to be accepted manually into Cooker, and not being able to work on my packages during that time, the solution is to *temporarily* put packages into Contribs. In the case of db4, I'm still waiting for the decision from my manager to include it into Cooker main. In the case of php-xslt, it is due to the fact that Mozilla used to provide libjs1, but no longer does, for an unknown reason. So I had to manually create an RPM. Maybe the Mozilla packager will re-put libjs1 into Mozilla, I don't know, I'm still waiting for the answer. In the case of ADVX-build, Apache 1.3 will be moved to Contribs, while Apache 2.0 will be moved to Cooker. This should be complete within a week. In conclusion, as a general rule, the final distrib must not depend on any contribs packages, but as Cooker is the *development* version, I think we should be a bit more flexible, as packages can move from one tree to the other, depending on the available space on the final CDs. If it were only me, I would put *all* Apache modules and their Requires and BuildRequires into the Main distro, but I don't think this can be acceptable, since we would have to remove some packages to make some room. Jean-Michel
