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 google it.

-Joe


2010/6/10 Pacho Ramos <pacho@gentoo.org>:
> 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 when their reports get stalled due maintainer not being
> available.
>
> My suggestion (until http://bugs.gentoo.org/show_bug.cgi?id=256934 is
> solved) is to add a new step to "how to use the Devaway System"
> instructions asking people to also change their bugzilla name appending
> "(Devaway)", for example:
>
> "Pacho Ramos" would be changed to "Pacho Ramos (Deavaway)"
>
> Then, people could simply search "devaway" in google and would get
> proper information (gentoo devway page is the first shown)
>
> Thanks
>

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,
>> and I don't agree that people will know what "devaway" means - i.e.
>> they may not even google it.
>
> It's what bug 256934 is about but, until it's solved... :-/

sounds like a huge pita for people. better to spend cycles getting
things upgraded and integrated properly.
-mike