Closed Bug 547836 Opened 14 years ago Closed 14 years ago

Create drupal-module drupal-theme drupal-upgrade keywords

Categories

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

x86
Linux
task
Not set
normal

Tracking

()

VERIFIED FIXED

People

(Reporter: paul, Assigned: gerv)

Details

Shall we apply keywords to future bugs (new / edit) so that it is easy for a contributor to find the bugs that he / she would like to work on.

How about we apply the following keywords now ..

theme , module , ux ,  docs , server

Best, 
Paul Booker
Appcoast
At the moment, the buglist is only 47 bugs, and changing pretty fast. Let's wait until things have calmed down a bit more before we spend extra time on bug categorization.

Gerv
@Matt

Would you like me to go through our current list of bugs (87 at the time of writing) and apply keywords so that contributors can easily find something to work on.

I think it would good generally speaking to request the following legal 'keywords' for bugzilla considering the number of drupal sites we now have running at Mozilla ..

drupal-theme , drupal-module , drupal-ux , drupal-docs 
 

Best,
Paul Booker
Appcoast
@Gerv

Do you know to whom the above the question should be directed?

It would be great to be able to pick out quickly all the Drumbeat bugs that are drupal-module related and later to be able to request "all" drupal-module bugs across all sites sorted by "Product:Websites"

Best,
Paul Booker
Appcoast
Paul: file a bug in mozilla.org/Bugzilla: Other Changes (or some similar component name) requesting the creation of the keywords. CC me. Let's make it happen :-)

Gerv
Thanks Gerv , ill get on this ..

Best,
Paul Booker
Appcoast
Can we create the following legal 'keywords' for bugzilla ..

drupal-theme , drupal-module , drupal-ux , drupal-docs 


Best, 
Paul Booker
Appcoast
Assignee: paulbooker → marcia
Component: www.drumbeat.org → Bugzilla: Keywords & Components
Product: Websites → mozilla.org
QA Contact: www-drumbeat-org → timeless
Version: unspecified → other
.. and ..

drupal-security , drupal-upgrade

Best, 
Paul Booker
Appcoast
I've created drupal-theme and drupal-module. 

Keywords like this are useful for when a particular type of bug across multiple products may be fixable by a single individual. So I can see why drupal-theme and drupal-module make sense. But can you explain what each of the other four are for (the keywords list has a Description field, and I need to know what to put) and why they have this property? E.g. I can't see someone being responsible for all drupal-upgrades across multiple websites... Or is that keyword for something else?

Gerv
Gerv,

My undestanding was that these keywords would be understood and applied in a straightforward way ..

Eg.

drupal-theme keyword could be applied to a bug that is connected with "drupal" and is "theme" related

drupal-module keyword could be applied to a bug that is connected with "drupal" and is "module" related

drupal-ux keyword could be applied to a bug that is connected with "drupal" and is related to the "user experience"

drupal-security keyword could be applied to a bug that is connected with "drupal" and is "security" related

drupal-upgrade keyword could be applied to a bug that is connected with "drupal" and the "upgrade" of a contributed module OR theme

Let drop drupal-docs


Thanks 
Paul Booker
Appcoast
(In reply to comment #9)
> drupal-ux keyword could be applied to a bug that is connected with "drupal" and
> is related to the "user experience"

Who would search for such bugs?

> drupal-security keyword could be applied to a bug that is connected with
> "drupal" and is "security" related

Same question...

> drupal-upgrade keyword could be applied to a bug that is connected with
> "drupal" and the "upgrade" of a contributed module OR theme

And again :-)

I can see where people might have cross-site expertise in "drupal module-related problems", but what is special about e.g. the UX of a drupal website (compared to the UX of any other website) that means we need a particular keyword?

I guess my concern here is not to create keywords unless there are definitely people who would find them useful. Because if it exists, people feel they should do the work to add it, and we want to make sure that work is not wasted.

Gerv
(In reply to comment #10)
> (In reply to comment #9)
> > drupal-ux keyword could be applied to a bug that is connected with "drupal" and
> > is related to the "user experience"
> 
> Who would search for such bugs?

Anyone who contributes to drupal projects like spreadfirefox , spreadthunderbird, QMO etc  and is interested in working improving UX 

> 
> > drupal-security keyword could be applied to a bug that is connected with
> > "drupal" and is "security" related
> 
> Same question...


Anyone who contributes to drupal projects like spreadfirefox , spreadthunderbird, QMO etc  and is interested in proactively monitoring security problems with these sites or just want to check quickly that there are no security problems, ..  
 
> 
> > drupal-upgrade keyword could be applied to a bug that is connected with
> > "drupal" and the "upgrade" of a contributed module OR theme
> 
> And again :-)

Me for one

> 
> I can see where people might have cross-site expertise in "drupal
> module-related problems", but what is special about e.g. the UX of a drupal
> website (compared to the UX of any other website) that means we need a
> particular keyword?
> 

Sorry i didn't see / anticipate a UX keyword so i suppose we could just use UX although my preference would be to differentiate 

> I guess my concern here is not to create keywords unless there are definitely
> people who would find them useful. Because if it exists, people feel they
> should do the work to add it, and we want to make sure that work is not wasted.

Understood
> 
> Gerv
Gerv(In reply to comment #11)
> Anyone who contributes to drupal projects like spreadfirefox ,
> spreadthunderbird, QMO etc  and is interested in working improving UX 

But what I'm asking is, why is UX on Drupal projects different from UX on any other website? Can we use the existing "ue" (user experience) keyword, thereby marking the bugs of interest to general UX/UE experts as well...?

> Anyone who contributes to drupal projects like spreadfirefox ,
> spreadthunderbird, QMO etc  and is interested in proactively monitoring
> security problems with these sites or just want to check quickly that there are
> no security problems, ..  

I'd expect security bugs to be labelled by being in the security group...! 

> Me for one

OK, created "drupal-upgrade" :-)

Gerv
(In reply to comment #12)
> Gerv(In reply to comment #11)
> > Anyone who contributes to drupal projects like spreadfirefox ,
> > spreadthunderbird, QMO etc  and is interested in working improving UX 
> 
> But what I'm asking is, why is UX on Drupal projects different from UX on any
> other website? Can we use the existing "ue" (user experience) keyword, thereby
> marking the bugs of interest to general UX/UE experts as well...?

If we can use multiple keywords like "Drupal" and "ue" to find Drupal UX related bugs then thats fine , any solution that works  

> 
> > Anyone who contributes to drupal projects like spreadfirefox ,
> > spreadthunderbird, QMO etc  and is interested in proactively monitoring
> > security problems with these sites or just want to check quickly that there are
> > no security problems, ..  
> 
> I'd expect security bugs to be labelled by being in the security group...! 

If there is a "security" keyword and we can use multiple keywords like "Drupal" and "security" to find Drupal security related bugs then thats fine .
> 
> > Me for one
> 
> OK, created "drupal-upgrade" :-)

Thanks

> 
> Gerv
Awesome. Done, then :-)

Gerv
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Thanks for your help Gerv , ill update the Drumbeat wiki ..
for bookkeeping purposes, gerv in this bug appears to have created:
drupal-module  	Module-related problem with a Drupal-powered website
drupal-theme 	Theme-related problem with a Drupal-powered website
drupal-upgrade 	Bugs relating to the upgrade of a Drupal module or theme
Assignee: marcia → gerv
Status: RESOLVED → VERIFIED
Summary: Applying keyword to future bugs → Create drupal-module drupal-theme drupal-upgrade keywords
Component: Bugzilla: Keywords & Components → Administration
Product: mozilla.org → bugzilla.mozilla.org
You need to log in before you can comment on or make changes to this bug.