Need official editbugs doc on devmo
Aaron Leventhal
fairly unofficial:
http://www.gerv.net/hacking/before-you-mail-gerv.html
Maybe there should be something that explains
editbugs better and has a more official-seeming
procedure?
- Aaron
Axel Hecht
I personally don't follow any kind of policy, but gutt feeling. That
used to serve me well. Then again, most of my changes are for
localization people, so I know what they're doing or what we want them
to do, in case of localization owners.
Axel
Simon Paquet
wrote:
Do you want a document, which details how to get editbugs, or one,
which details what can/should (or cannot and should not) be done with
these privileges.
http://developer.mozilla.org/en/docs/What_to_do_and_what_not_to_do_in_Bugzilla
exists for the second case.
Cya
Simon
L. David Baron
I think this is something we don't want too much policy around.
There are a bunch of people who have the power to grant canconfirm
and editbugs. I think if there's a significant part of the
community that doesn't have somebody with this power then we should
fix that. Essentially, we want to give these privileges to people
who (a) want to help and (b) we have some reason to trust (e.g.,
they've made useful comments or they're working on patches).
It might be good to have a list of those of the people who have the
power to grant these privileges who are willing to take requests for
granting them. But not all of the people who grant them are
necessarily willing to take requests from other parts of the
community. For example, I can grant them so I can grant them to new
layout developers or people I noticed being helpful on layout bugs,
but I don't want to deal with requests. There are people who are
willing to deal with requests (such as Gerv).
Probably we should ask people to read the Bugzilla etiquette page
when giving these as well...
-David
--
L. David Baron <URL: http://dbaron.org/ >
Technical Lead, Layout & CSS, Mozilla Corporation
Simon Paquet
> Probably we should ask people to read the Bugzilla etiquette page
> when giving these as well...
Good idea. At the moment I just ask people to read
http://developer.mozilla.org/en/docs/What_to_do_and_what_not_to_do_in_Bugzilla
when I grant them editbugs or canconfirm privileges (which I do mostly
for people
doing QA in Calendar land).
Cya
Simon
Aaron Leventhal
How do I get editbugs?
There should be a page just on that. When I go to
gerv's current page it has that "out of date" feel
and contains all kinds of other info, like stuff
about the Christianity page. I don't have an issue
with that but just pointing out it's a strange mix
which leads to the feeling it's not the right
place to find out how to get editbugs.
- Aaron
Aaron Leventhal
have on a personal page. The email listed on that
page that I found wasn't the email Gerv wants you
to use.
I want to be able to do a search for "Mozilla
editbugs" or something like that, and be led to an
official webpage which explains what it is, how to
get it, and that's all.
- Aaron
Myk Melez
> I think this is something we don't want too much policy around.
> There are a bunch of people who have the power to grant canconfirm
> and editbugs. I think if there's a significant part of the
> community that doesn't have somebody with this power then we should
> fix that. Essentially, we want to give these privileges to people
> who (a) want to help and (b) we have some reason to trust (e.g.,
> they've made useful comments or they're working on patches).
Right. Hypothetically speaking, if there was a Mozilla social network
that linked Mozilla community members to each other the way Facebook
links "friends," then I'd suggest our policy be to grant editbugs
privileges to everyone in the network who is connected via some chain of
trust to a large set of community principals.
-myk
Gervase Markham
> Right now I'm going off of this, but it seems fairly unofficial:
>
> http://www.gerv.net/hacking/before-you-mail-gerv.html
It is fairly unofficial. I don't have the power to set project-wide
editbugs-granting policy. That's just the standard I use. It's on my
page because it's my policy, and people who want to email me for the
first time get routed via there. It's sort of a FAQ - and the editbugs
thing is Frequently Asked.
If we want to set project-wide editbugs policy, I can contribute my
opinion. But I don't think it's necessary. As dbaron and myk says, it's
kind of a fluid thing.
For example, I set certain requirements. Yet merely seeking out the
instructions and being able to meet the requirements tells me a lot,
even before I look at the bugs concerned.
Gerv
Gervase Markham
> I should add that it's just a strange thing to have on a personal page.
> The email listed on that page that I found wasn't the email Gerv wants
> you to use.
Just as a factual correction, that's not right. There's a big link on
the third line which says "Mozilla stuff". Click it, and you get the
right email.
Gerv
Aaron Leventhal
It seemed confusing to me, since I'm coming from a
point of view of not knowing much about it at all.
- Aaron