← Back to team overview

launchpad-dev team mailing list archive

Re: Quick'n'dirty solution sought: Locking down certain bugs even further

 

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Martin Pool wrote on 25/03/11 22:49:
>
> On 26 March 2011 05:56, Jonathan Lange <jml@xxxxxxxxxxxxx> wrote:
>...
>> They have bugs that they must keep public, for reasons of both
>> principle and practicality. However, they don't really want anyone
>> outside of an authorized set of people actually *doing* anything to
>> those bugs. Outsiders change tags, statuses and add unhelpful comments
>> and the Ubuntu developers would like to stop that from happening.
>...
> I think it would be interesting and perhaps reasonably cheap to add
> two checkboxes per bug: "lock status" and "lock comments".  They can
> be changed by bug supervisors of any task.  If the former is set, task
> fields (status, importance, etc) can't be changed and new tasks can't
> be created, except by bug supervisors.  If the latter is set, comments
> and attachments can't be added, again except by bug supervisors.
> (Perhaps s/bug supervisors/some other role/; the intention being that
> only developers can change it.)
>
> I don't anticipate this would be set on many bugs but there are some
> very hot bugs where it could be useful.
>...

There are a few similar ideas in <http://launchpad.net/bugs/73122>.

- -- 
mpt
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk2QYXYACgkQ6PUxNfU6ecooggCfVHCpb7sU5pvt2NnNOUj19nXj
NlwAoMVCEAaD3QKoRVj8Qn//fdz6rMWN
=Trd+
-----END PGP SIGNATURE-----



References