2010/6/10 Pacho Ramos:
El jue, 10-06-2010 a las 12:23 -0600, Joe Peterson escribió:
I think a better solution, if we need to indicate this, is to have
bugzilla grab the status from devaway and display it next to the dev's
name in bug reports. Changing the user's name seems a bit cumbersome,
El vie, 11-06-2010 a las 00:38 +0200, Christian Ruppert escribió:
On 06/10/2010 07:07 PM, Pacho Ramos wrote:
Hello
Currently, we only need to set a proper message in ~/.away (as talked in
http://www.gentoo.org/proj/en/devrel/roll-call/devaway.xml ) when
becoming devaway. The problem is
Hello
Currently, we only need to set a proper message in ~/.away (as talked in
http://www.gentoo.org/proj/en/devrel/roll-call/devaway.xml ) when
becoming devaway. The problem is that a lot of our users don't know
about that devaway list and, then, they will still open bug reports and
complaint
I think a better solution, if we need to indicate this, is to have
bugzilla grab the status from devaway and display it next to the dev's
name in bug reports. Changing the user's name seems a bit cumbersome,
and I don't agree that people will know what devaway means - i.e.
they may not even
El jue, 10-06-2010 a las 12:23 -0600, Joe Peterson escribió:
I think a better solution, if we need to indicate this, is to have
bugzilla grab the status from devaway and display it next to the dev's
name in bug reports. Changing the user's name seems a bit cumbersome,
and I don't agree that
On 06/10/2010 07:07 PM, Pacho Ramos wrote:
Hello
Currently, we only need to set a proper message in ~/.away (as talked in
http://www.gentoo.org/proj/en/devrel/roll-call/devaway.xml ) when
becoming devaway. The problem is that a lot of our users don't know
about that devaway list and, then,
