688063 - Attachment flags for Websites > www.mozilla.org

Status: VERIFIED FIXED

(bugzilla.mozilla.org :: Administration, task)

Description

[Gordon P. Hemsley [:GPHemsley]]

Is there any chance we can get the following flags for attachments in Websites > www.mozilla.org?

in-staging
Patch has been committed to projects/mozilla.org/branches/staging/

in-trunk
Patch has been committed to projects/mozilla.org/trunk/

I'm not sure how the choices/settings work, but I'm not sure if we need the full ?/+/- complement, though I suppose the extra options wouldn't hurt. (I'm open to suggestions of the pros and cons of having more than just '+' and null, if anyone cares.) 

I'm probably not the one to sort out the actual permissions for setting the flag, but I would imagine that it should be constrained to just people who have commit access to projects/mozilla.org/. And requests are probably not necessary. (I guess that would be the '?' option?)

These are fairly simple flags, and I believe they'd be temporary—at some point I think we're supposed to have the regular automatically-merge-stage-to-trunk architecture, but right now it's a little hard to keep track of where patches have been applied (if anywhere). Folks have a tendency to bypass staging and commit directly to trunk.

Thanks!

Comment 1

[:glob ✱]

i've added the flags with + and - only.

restricting the permissions based on commit access isn't easy as there's no bridge between commit access and bmo.  i've made it so you need editbugs on bmo to set the flag, which should be enough to avoid drive-by spamming.

Comment 2

[Gordon P. Hemsley [:GPHemsley]]

(In reply to Byron Jones ‹:glob› from comment #1)
> i've added the flags with + and - only.
> 
> restricting the permissions based on commit access isn't easy as there's no
> bridge between commit access and bmo.  i've made it so you need editbugs on
> bmo to set the flag, which should be enough to avoid drive-by spamming.

Sounds good. Thanks again!