Hi all,
I just went through my first new package under the new process (aka package no 100, so I'm experienced in this). The mail below may seem flamebate but it is mean't very seriously, so please take it seriously.
And the new process SUCKS!
First of all as discussed earlier the new review with flags is both unclear / not very well documented and much more work then it used to be, without any clear arguments why we needed a new process in the first place -> SUCKS
Then I wanted todo an import an it failed as I first needed to be in owners.list and that requires manual intervention by an CVS admin, so now I have the feeling that I need a CVS admin for any fart I want todo -> SUCKS
The new ACL design is broken, the ACL's shouldn't work by owners.list, but instead by putting the owner in the acl in the initial import and then owners.list would "just" be used for bugzilla and not for CVS access / ACL, which in turn means that then anyone could be given rights to owners.list as things were -> problem solved. I know things are probably not that easy. But the current solution is not a solution its a cure worse then the disease! IOW it SUCKS!
Regards,
Hans
On Mon, 05 Feb 2007 17:19:20 +0100, Hans de Goede wrote:
Hi all,
I just went through my first new package under the new process (aka package no 100, so I'm experienced in this). The mail below may seem flamebate but it is mean't very seriously, so please take it seriously.
What?!
Do you say there is a new process also for Extras package submissions and not just for the Merge reviews?
How many lists do contributors have to follow these days? I've seen a huge "RFC" thread on maintainers-list, but no official announcement of a change in policies or processes.
And the new process SUCKS!
The mails that come in via fedora-package-review list confuse my a lot, but so far I haven't found the time to look into any new package review process, so my comment ends here.
On 2/5/07, Michael Schwendt mschwendt.tmp0701.nospam@arcor.de wrote:
On Mon, 05 Feb 2007 17:19:20 +0100, Hans de Goede wrote:
I just went through my first new package under the new process (aka package no 100, so I'm experienced in this). The mail below may seem flamebate but it is mean't very seriously, so please take it seriously.
What?!
Do you say there is a new process also for Extras package submissions and not just for the Merge reviews?
Just to push this point (since I haven't seen anything one way or the other), is this new process applicable to all new package submissions/reviews going forward, or just the Core-merge reviews?
-Chris
Hans de Goede (j.w.r.degoede@hhs.nl) said:
Then I wanted todo an import an it failed as I first needed to be in owners.list and that requires manual intervention by an CVS admin, so now I have the feeling that I need a CVS admin for any fart I want todo -> SUCKS
Mmm, hyperbole. Right now, the initial set up of a package needs done by the admin; currently this is adding an entry to the owners.list/ making the directory in CVS. In future it might be 'adding the entry to the package database and setting it up in the build system'. The step will still be needed, even though parts of it may change.
Heck, I'd love to get it where the CVS branching stuff isn't a separate step. But that takes time and infrastructure, and there seems to be a dearth of people who want to touch the CVS stuff.
The new ACL design is broken, the ACL's shouldn't work by owners.list, but instead by putting the owner in the acl in the initial import and then owners.list would "just" be used for bugzilla and not for CVS access / ACL, which in turn means that then anyone could be given rights to owners.list as things were -> problem solved. I know things are probably not that easy. But the current solution is not a solution its a cure worse then the disease! IOW it SUCKS!
owner in acl == anyone in acl can remove all the other owners.
Bill
On Mon, 2007-02-05 at 16:02 -0500, Bill Nottingham wrote:
Hans de Goede (j.w.r.degoede@hhs.nl) said:
The new ACL design is broken, the ACL's shouldn't work by owners.list, but instead by putting the owner in the acl in the initial import and then owners.list would "just" be used for bugzilla and not for CVS access / ACL, which in turn means that then anyone could be given rights to owners.list as things were -> problem solved. I know things are probably not that easy. But the current solution is not a solution its a cure worse then the disease! IOW it SUCKS!
owner in acl == anyone in acl can remove all the other owners.
And where is the problem?
Spell: Trust Spell: VCS
Ralf
-
Bill Nottingham -
Chris Weyl -
Hans de Goede -
Michael Schwendt -
Ralf Corsepius