Confirmed users
1,193
edits
(24 intermediate revisions by the same user not shown) | |||
Line 1: | Line 1: | ||
== Workflow overview == | == Workflow overview == | ||
The [http://files.openjck.com/developer-events-workflow.html Developer Events flow chart] offers a visual overview of this workflow. | |||
As a summary, anyone who would like Mozilla to participate in an event completes the [https://bugzilla.mozilla.org/form.dev-engagement-event Developer Events form]. Bugzilla processes the answers and opens a <strong>request bug</strong> to summarize the request and a <strong>discussion bug</strong> for the Developer Events team to discuss the request privately. The team discusses the request and updates [[#Keywords|keywords]] and other bug metadata along the way. When a decision is reached, the team shares the decision in the request bug where the requester can see it. | |||
More detail is provided in further sections. | |||
== Using this workflow == | == Using this workflow == | ||
=== | === Keywords === | ||
Requests and discussions can be tagged with special keywords that | Requests and discussions can be tagged with special keywords that indicate state. Requests and discussions are automatically organized based on their keywords (see [[#Listings|Listings]] below) so it's important that keywords are manually updated when requests and discussions change. | ||
In the example below, a request is tagged with the keyword ''event-request-under-review''. | |||
[[File:Developer_event_keyword_example.png|900px|left|A screenshot of an event request with the ''Keywords'' field highlighted]] | [[File:Developer_event_keyword_example.png|900px|left|A screenshot of an event request with the ''Keywords'' field highlighted]] | ||
<div style="clear: both"></div> | <div style="clear: both"></div> | ||
==== | ==== Available keywords ==== | ||
===== Requests ===== | ===== Requests ===== | ||
The following keywords can be used | The following keywords can be used with event requests: | ||
<dl> | <dl> | ||
<dt>event-request-under-review</dt> | <dt>event-request-under-review</dt> | ||
<dd>The | <dd>Meaning: The request is being reviewed</dd> | ||
<dt>event-request-pending-fulfilment</dt> | <dt>event-request-pending-fulfilment</dt> | ||
<dd>The | <dd>Meaning: The request has been discussed and is nearly ready to be fulfilled</dd> | ||
<dt>event-request-no-further-action</dt> | <dt>event-request-no-further-action</dt> | ||
<dd>The | <dd>Meaning: The request requires no further action</dd> | ||
</dl> | </dl> | ||
===== Discussions ===== | ===== Discussions ===== | ||
The following keywords can be used | The following keywords can be used with event discussions: | ||
<dl> | <dl> | ||
<dt>event-discussion-needs-review</dt> | <dt>event-discussion-needs-review</dt> | ||
<dd>The discussion | <dd>Meaning: The discussion hasn't started</dd> | ||
<dt>event-discussion-pending-additional-information</dt> | <dt>event-discussion-pending-additional-information</dt> | ||
<dd>The discussion | <dd>Meaning: The discussion can't continue until more information is provided</dd> | ||
<dt>event-discussion-needs-final-approval</dt> | |||
<dd>Meaning: A decision has been reached. It needs final approval and has not been pre-approved.</dd> | |||
<dt>event-discussion-pre-approved-needs-final-approval</dt> | <dt>event-discussion-pre-approved-needs-final-approval</dt> | ||
<dd>A decision | <dd>Meaning: A decision has been reached. It has been pre-approved but needs final approval.</dd> | ||
<dt>event-request-pending-fulfilment</dt> | <dt>event-request-pending-fulfilment</dt> | ||
<dd>The event being discussed is nearly ready to be fulfilled</dd> | <dd>Meaning: The event being discussed is nearly ready to be fulfilled</dd> | ||
<dt>event-request-no-further-action</dt> | <dt>event-request-no-further-action</dt> | ||
<dd>No further discussion is needed</dd> | <dd>Meaning: No further discussion is needed</dd> | ||
</dl> | </dl> | ||
=== | === Notifications === | ||
==== Request bugs ==== | ==== Request bugs ==== | ||
To receive notifications about | To receive email notifications about changes to event requests, follow these steps: | ||
<div id="notifications-request-enable"></div> | |||
# Log into [https://bugzilla.mozilla.org/ Bugzilla] | |||
# Visit the [https://bugzilla.mozilla.org/userprefs.cgi?tab=component_watch Component Watching] page | |||
# Choose the product ''Developer Engagement'' and the component ''Events Request''. Click ''Add''. | |||
# Visit the [https://bugzilla.mozilla.org/userprefs.cgi?tab=email Email Preferences] page | |||
# Check one box in the ''Component'' column for each type of notification you would like to receive. Click ''Submit Changes''. | |||
To disable notifications, follow these steps: | |||
# Visit the [https://bugzilla.mozilla.org/userprefs.cgi?tab=component_watch Component Watching] page | |||
# Near the bottom of the page, check the ''Events Request'' component and click ''Remove Selected'' | |||
To re-enable notifications, follow steps 2-3 of [[#notifications-request-enable|the first list]]. | |||
==== Discussion bugs ==== | ==== Discussion bugs ==== | ||
To receive notifications about | To receive email notifications about changes to event discussions, follow these steps: | ||
<div id="notifications-discussion-enable"></div> | |||
# Log into [https://bugzilla.mozilla.org/ Bugzilla] | |||
# Visit the [https://bugzilla.mozilla.org/userprefs.cgi?tab=component_watch Component Watching] page | |||
# Choose the product ''Developer Engagement'' and the component ''Events Request Discussion''. Click ''Add''. | |||
# Visit the [https://bugzilla.mozilla.org/userprefs.cgi?tab=email Email Preferences] page | |||
# Check one box in the ''Component'' column for each type of notification you would like to receive. Click ''Submit Changes''. | |||
To disable notifications, follow these steps: | |||
# Visit the [https://bugzilla.mozilla.org/userprefs.cgi?tab=component_watch Component Watching] page | |||
# Near the bottom of the page, check the ''Events Request Discussion'' component and click ''Remove Selected'' | |||
To re-enable notifications, follow steps 2-3 of [[#notifications-discussion-enable|the first list]]. | |||
=== Using Listings === | |||
Listings are collections of requests and discussions that meet certain criteria. To browse Listings, follow the links in the [[#Listings|Listings section]]. | |||
==== Drilling down through Listings ==== | |||
When searching through requests and discussions, it can sometimes be helpful to start with a published Listing and then further narrow the criteria of that Listing. To do this, open a Listing and click ''Edit Search'' near the bottom of the page. Add additional criteria and click ''Search''. | |||
==== Making a request or discussion appear in a different Listing ==== | |||
If a request or discussion is appearing in the wrong Listing, open that specific request or discussion be sure that the ''Keyword'' is set correctly. Also ensure that the information in the ''Whiteboard'' is accurate. Make any changes that are needed and click ''Save Changes''. | |||
== Listings == | == Listings == | ||
Listings are requests and discussions that meet certain criteria. With few exceptions, closed | Listings are collections of requests and discussions that meet certain criteria. | ||
Because requests and discussions are only visible to Mozilla staff, Listings will be empty unless you are logged into Bugzilla with a Mozilla email address. With a few exceptions, Listings do not include closed requests/discussions or requests/discussions filed before late January 2015. | |||
=== Discussion === | === Discussion === | ||
Line 102: | Line 136: | ||
* [http://mzl.la/1FAX6Jg All requests and discussions that need further information] | * [http://mzl.la/1FAX6Jg All requests and discussions that need further information] | ||
* [http://mzl.la/1FAXmbc More information needed from Sandra Persing] | |||
=== Speakers === | === Speakers === | ||
Line 113: | Line 142: | ||
* [http://mzl.la/1xc9J9T All events that need a speaker] | * [http://mzl.la/1xc9J9T All events that need a speaker] | ||
* By continent | * By continent | ||
** [http://mzl.la/ | ** [http://mzl.la/1yrh97Q Events in Africa that need a speaker] | ||
** [http://mzl.la/ | ** [http://mzl.la/1yrh5Vy Events in Asia that need a speaker] | ||
** [http://mzl.la/ | ** [http://mzl.la/1yrhvvf Events in Australia that need a speaker] | ||
** [http://mzl.la/ | ** [http://mzl.la/15tEdYp Events in Europe that need a speaker] | ||
** [http://mzl.la/ | ** [http://mzl.la/1yrhLuf Events in North America that need a speaker] | ||
** [http://mzl.la/ | ** [http://mzl.la/15tEPx8 Events in Central / South America that need a speaker] | ||
** [http://mzl.la/ | ** [http://mzl.la/15tEXg6 Online-only events that need a speaker] | ||
=== Other details === | === Other details === | ||
Line 157: | Line 186: | ||
** [http://mzl.la/1xc79Rf Events in North America] | ** [http://mzl.la/1xc79Rf Events in North America] | ||
** [http://mzl.la/1xc7djQ Events in Central / South America] | ** [http://mzl.la/1xc7djQ Events in Central / South America] | ||
** [http://mzl.la/1v9whko | ** [http://mzl.la/1v9whko Online-only events] | ||
* Prospectus | * Prospectus | ||
** [http://mzl.la/1xc9zz6 Events that have a prospectus] | ** [http://mzl.la/1xc9zz6 Events that have a prospectus] | ||
** [http://mzl.la/1v9wu70 Events that do not have a prospectus] | ** [http://mzl.la/1v9wu70 Events that do not have a prospectus] |