-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
I just trying to open a new bug in bssdb module and assign it to me :-). Seems I have no permissions to do that :-).
The issue is http://bugs.python.org/issue1976
- -- Jesus Cea Avion _/_/ _/_/_/ _/_/_/ jcea@argo.es http://www.argo.es/~jcea/ _/_/ _/_/ _/_/ _/_/ _/_/ jabber / xmpp:jcea@jabber.org _/_/ _/_/ _/_/_/_/_/ ~ _/_/ _/_/ _/_/ _/_/ _/_/ "Things are not so easy" _/_/ _/_/ _/_/ _/_/ _/_/ _/_/ "My name is Dump, Core Dump" _/_/_/ _/_/_/ _/_/ _/_/ "El amor es poner tu felicidad en la felicidad de otro" - Leibniz
On Jan 30, 2008 8:49 AM, Jesus Cea jcea@argo.es wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
I just trying to open a new bug in bssdb module and assign it to me :-). Seems I have no permissions to do that :-).
The issue is http://bugs.python.org/issue1976
We have not worked out any policy on this, but I always assumed we would only assign issues to people with commit privileges. I quick check suggests that you don't have them, Jesus. We can give you the rights to modify issues and set the assignment, but I don't know if you should be able to be assigned a bug yet.
What do other people think?
-Brett
Jesus Cea Avion _/_/ _/_/_/ _/_/_/ jcea@argo.es http://www.argo.es/~jcea/ _/_/ _/_/ _/_/ _/_/ _/_/ jabber / xmpp:jcea@jabber.org _/_/ _/_/ _/_/_/_/_/ ~ _/_/ _/_/ _/_/ _/_/ _/_/ "Things are not so easy" _/_/ _/_/ _/_/ _/_/ _/_/ _/_/ "My name is Dump, Core Dump" _/_/_/ _/_/_/ _/_/ _/_/ "El amor es poner tu felicidad en la felicidad de otro" - Leibniz -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iQCVAwUBR6CqkJlgi5GaxT1NAQJ4VAQAoa7FGC7OxeNiQUDKsjaZ9Q6gtOBXtuJp 0O31VllV82eINCKU2BA/XAHTik/CxvvVRPjLElumln3Lccj++8IVeSgHoPntDZuc 7kJhrD+OZXTPWkV4/g+sgepycF+wNr2ICM2o75ABz2CuyXNYmLum0fH7UPUORi+U V921rj9Kzss= =0Soy -----END PGP SIGNATURE----- _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/brett%40python.org
Brett Cannon wrote:
On Jan 30, 2008 8:49 AM, Jesus Cea jcea@argo.es wrote:
I just trying to open a new bug in bssdb module and assign it to me :-). Seems I have no permissions to do that :-).
We have not worked out any policy on this, but I always assumed we would only assign issues to people with commit privileges. I quick check suggests that you don't have them, Jesus. We can give you the rights to modify issues and set the assignment, but I don't know if you should be able to be assigned a bug yet.
What do other people think?
Given that everyone is free to work on whichever issues are of interest to them (and post comments to the relevant tracker items), I've always seen the assignment field as a way to request that a specific committer either fix the problem themselves, or review a proposed solution and either suggest improvements or check it in.
I think you're right that there isn't really an official policy written down anywhere though - PEP 3 doesn't go into that kind of detail.
Cheers, Nick.
We have not worked out any policy on this, but I always assumed we would only assign issues to people with commit privileges. I quick check suggests that you don't have them, Jesus. We can give you the rights to modify issues and set the assignment, but I don't know if you should be able to be assigned a bug yet.
What do other people think?
That has exactly been the policy that I have been executing, yes.
As for giving additional rights on a per-user basis - that's tricky to implement. We have the User and Developer roles in the tracker, and you get additional rights only with additional roles, normally.
I also agree with Nick as to what the purpose of assignments is. To indicate that you are working on a specific issue, a message saying so is enough (which could also include estimated completion dates, which a mere self-assignment can't).
Regards, Martin
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Martin v. Löwis wrote: | I also agree with Nick as to what the purpose of assignments is. | To indicate that you are working on a specific issue, a message | saying so is enough (which could also include estimated completion | dates, which a mere self-assignment can't).
So, in the concrete case of http://bugs.python.org/issue1976 , patch available, what the next step would be?. Must I contact Greg (previous bsddb maintainer, with python commit access) to review, apply patch (more coming, so no hurry) and tracker update?.
Should I maintain bsddb tracking outside python one, to reduce your burden?.
- -- Jesus Cea Avion _/_/ _/_/_/ _/_/_/ jcea@argo.es http://www.argo.es/~jcea/ _/_/ _/_/ _/_/ _/_/ _/_/ jabber / xmpp:jcea@jabber.org _/_/ _/_/ _/_/_/_/_/ ~ _/_/ _/_/ _/_/ _/_/ _/_/ "Things are not so easy" _/_/ _/_/ _/_/ _/_/ _/_/ _/_/ "My name is Dump, Core Dump" _/_/_/ _/_/_/ _/_/ _/_/ "El amor es poner tu felicidad en la felicidad de otro" - Leibniz
On Jan 31, 2008 1:50 AM, Jesus Cea jcea@argo.es wrote:
Martin v. Löwis wrote: | I also agree with Nick as to what the purpose of assignments is. | To indicate that you are working on a specific issue, a message | saying so is enough (which could also include estimated completion | dates, which a mere self-assignment can't).
So, in the concrete case of http://bugs.python.org/issue1976 , patch available, what the next step would be?. Must I contact Greg (previous bsddb maintainer, with python commit access) to review, apply patch (more coming, so no hurry) and tracker update?.
Yes, that's the typical approach. After a while, if your patches are generally good, Greg will trust you and stop reviewing your code in detail; eventually he will recommend you be granted commit privileges.
Should I maintain bsddb tracking outside python one, to reduce your burden?.
No.
-
"Martin v. Löwis" -
Brett Cannon -
Guido van Rossum -
Jesus Cea -
Nick Coghlan