m (1 revision(s)) |
m (moved JesseKeating/PackageACLOpening to User:JesseKeating/PackageACLOpening: Moved this user page to the User: namespace. Sorry for the noise!) |
||
| (One intermediate revision by one other user not shown) | |||
| Line 6: | Line 6: | ||
--> | --> | ||
= | == Overview == | ||
= | === Problem Space === | ||
== Problem Space == | |||
<!-- Describe the problem this proposal seeks to solve | <!-- Describe the problem this proposal seeks to solve | ||
--> | --> | ||
A good number of previously core packages still have default locked down ACLs. This prevents a culture of fixing each others packages and can delay important changes being done or timely rebuilds done for broken deps. | A good number of previously core packages still have default locked down ACLs. This prevents a culture of fixing each others packages and can delay important changes being done or timely rebuilds done for broken deps. | ||
== Solution Overview == | === Solution Overview === | ||
<!-- Describe in brief the solution proposed | <!-- Describe in brief the solution proposed | ||
--> | --> | ||
Having an automated "opening" of all ACLs (that is allowing cvsextras commit access) that a maintainer can opt /out/ of should they choose. | Having an automated "opening" of all ACLs (that is allowing cvsextras commit access) that a maintainer can opt /out/ of should they choose. | ||
== Scope == | === Scope === | ||
<!-- Describe the scope of what all things will be effected by the proposal | <!-- Describe the scope of what all things will be effected by the proposal | ||
--> | --> | ||
This change would mostly deal with pkgdb, however depending on the method decided to use for opting out of ACL opening it could touch on cvs or bugzilla. | This change would mostly deal with pkgdb, however depending on the method decided to use for opting out of ACL opening it could touch on cvs or bugzilla. | ||
== Active Ingredients == | === Active Ingredients === | ||
<!-- Optional, describe the main action of the proposal | <!-- Optional, describe the main action of the proposal | ||
--> | --> | ||
The active ingredient would be a script that is used to identify packages that currently do not allow cvsextras commit access. This script would mark these packages in some way as being targetted by an automated opening. An appropriate wait time will be observed allowing maintainers to opt out, and then another script would identify all the packages still marked for opening and open them using pkgdb. | The active ingredient would be a script that is used to identify packages that currently do not allow cvsextras commit access. This script would mark these packages in some way as being targetted by an automated opening. An appropriate wait time will be observed allowing maintainers to opt out, and then another script would identify all the packages still marked for opening and open them using pkgdb. | ||
=== Sub Component === | ==== Sub Component ==== | ||
<!-- Describe how other components will be effected by the active ingredient. | <!-- Describe how other components will be effected by the active ingredient. | ||
--> | --> | ||
CVS could potentially be used to mark a package for opening and allow for a maintainer to opt-out. | CVS could potentially be used to mark a package for opening and allow for a maintainer to opt-out. | ||
= Discussion Points = | == Discussion Points == | ||
<!-- Describe things which should be discussed regarding the proposal. Specifics that need narrowing down, or contentions parts of the proposal. | <!-- Describe things which should be discussed regarding the proposal. Specifics that need narrowing down, or contentions parts of the proposal. | ||
--> | --> | ||
| Line 43: | Line 40: | ||
* What is a reasonable delay between marking and opening? | * What is a reasonable delay between marking and opening? | ||
== Comments ? == | === Comments ? === | ||
<!-- A section provided for comments | <!-- A section provided for comments | ||
--> | --> | ||
We should probably make it a requirement to provide a good rationale and store it along with the packages in the package database for maintainers who wish to retain ACL's in their packages - RahulSundaram | We should probably make it a requirement to provide a good rationale and store it along with the packages in the package database for maintainers who wish to retain ACL's in their packages - RahulSundaram | ||
Latest revision as of 23:17, 5 July 2010
Overview
Problem Space
A good number of previously core packages still have default locked down ACLs. This prevents a culture of fixing each others packages and can delay important changes being done or timely rebuilds done for broken deps.
Solution Overview
Having an automated "opening" of all ACLs (that is allowing cvsextras commit access) that a maintainer can opt /out/ of should they choose.
Scope
This change would mostly deal with pkgdb, however depending on the method decided to use for opting out of ACL opening it could touch on cvs or bugzilla.
Active Ingredients
The active ingredient would be a script that is used to identify packages that currently do not allow cvsextras commit access. This script would mark these packages in some way as being targetted by an automated opening. An appropriate wait time will be observed allowing maintainers to opt out, and then another script would identify all the packages still marked for opening and open them using pkgdb.
Sub Component
CVS could potentially be used to mark a package for opening and allow for a maintainer to opt-out.
Discussion Points
- How to mark packages for opening?
- How maintainers can opt-out?
- What is a reasonable delay between marking and opening?
Comments ?
We should probably make it a requirement to provide a good rationale and store it along with the packages in the package database for maintainers who wish to retain ACL's in their packages - RahulSundaram