Engagement/Developer Engagement/Event request workflow: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
 
(39 intermediate revisions by the same user not shown)
Line 1: Line 1:
== Workflow overview ==
== Workflow overview ==


Lorem ipsum dolor sit amet, consectetur adipiscing elit. Nulla est quam, pretium at sagittis ac, dignissim id neque. Suspendisse potenti. Etiam eu efficitur justo. Sed eget lacinia ante! Fusce enim dolor, maximus sollicitudin placerat id, laoreet et justo. Class aptent taciti sociosqu ad litora torquent per conubia nostra, per inceptos himenaeos. Nullam consectetur quam at lorem congue mattis.
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 ==


=== Understanding status keywords ===
=== Keywords ===
 
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]]
<div style="clear: both"></div>
 
==== Available keywords ====
 
===== Requests =====
 
The following keywords can be used with event requests:
 
<dl>
    <dt>event-request-under-review</dt>
    <dd>Meaning: The request is being reviewed</dd>
 
    <dt>event-request-pending-fulfilment</dt>
    <dd>Meaning: The request has been discussed and is nearly ready to be fulfilled</dd>
 
    <dt>event-request-no-further-action</dt>
    <dd>Meaning: The request requires no further action</dd>
</dl>
 
===== Discussions =====
 
The following keywords can be used with event discussions:
 
<dl>
    <dt>event-discussion-needs-review</dt>
    <dd>Meaning: The discussion hasn't started</dd>
 
    <dt>event-discussion-pending-additional-information</dt>
    <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>
    <dd>Meaning: A decision has been reached. It has been pre-approved but needs final approval.</dd>
 
    <dt>event-request-pending-fulfilment</dt>
    <dd>Meaning: The event being discussed is nearly ready to be fulfilled</dd>


Lorem ipsum dolor sit amet, consectetur adipiscing elit. Nulla est quam, pretium at sagittis ac, dignissim id neque. Suspendisse potenti. Etiam eu efficitur justo. Sed eget lacinia ante! Fusce enim dolor, maximus sollicitudin placerat id, laoreet et justo. Class aptent taciti sociosqu ad litora torquent per conubia nostra, per inceptos himenaeos. Nullam consectetur quam at lorem congue mattis.
    <dt>event-request-no-further-action</dt>
    <dd>Meaning: No further discussion is needed</dd>
</dl>


=== Enabling and disabling notifications ===
=== Notifications ===


==== Request bugs ====
==== Request bugs ====


To receive notifications about all changes made to request bugs... consectetur adipiscing elit. Nulla est quam, pretium at sagittis ac, dignissim id neque. Suspendisse potenti. Etiam eu efficitur justo. Sed eget lacinia ante! Fusce enim dolor, maximus sollicitudin placerat id, laoreet et justo. Class aptent taciti sociosqu ad litora torquent per conubia nostra, per inceptos himenaeos. Nullam consectetur quam at lorem congue mattis.
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 all changes made to discussion bugs... consectetur adipiscing elit. Nulla est quam, pretium at sagittis ac, dignissim id neque. Suspendisse potenti. Etiam eu efficitur justo. Sed eget lacinia ante! Fusce enim dolor, maximus sollicitudin placerat id, laoreet et justo. Class aptent taciti sociosqu ad litora torquent per conubia nostra, per inceptos himenaeos. Nullam consectetur quam at lorem congue mattis.
To receive email notifications about changes to event discussions, follow these steps:


=== Using listings ===
<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''.


Lorem ipsum dolor sit amet, consectetur adipiscing elit. Nulla est quam, pretium at sagittis ac, dignissim id neque. Suspendisse potenti. Etiam eu efficitur justo. Sed eget lacinia ante! Fusce enim dolor, maximus sollicitudin placerat id, laoreet et justo. Class aptent taciti sociosqu ad litora torquent per conubia nostra, per inceptos himenaeos. Nullam consectetur quam at lorem congue mattis.
To disable notifications, follow these steps:


==== Drilling down on listings ====
# 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''


After navigating to a listing, use <i>Edit search</i> feature to  further filter the bugs that appear. To do this... consectetur adipiscing elit. Nulla est quam, pretium at sagittis ac, dignissim id neque. Suspendisse potenti. Etiam eu efficitur justo. Sed eget lacinia ante! Fusce enim dolor, maximus sollicitudin placerat id, laoreet et justo. Class aptent taciti sociosqu ad litora torquent per conubia nostra, per inceptos himenaeos. Nullam consectetur quam at lorem congue mattis.
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 ==
Below are links to open requests and discussions that meet certain criteria.
 
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 ===


* [http://mzl.la/1sRJdv8 Discussions that are ready to begin]
* [http://mzl.la/1y0szOB Discussions that are ready to begin]
* [http://mzl.la/1wC9Z04 Discussions that are underway]
* [http://mzl.la/1wC9Z04 Discussions that are underway]


Line 38: Line 123:


* Requests
* Requests
** [http://mzl.la/1E4pKBO Requests under review]
** [http://mzl.la/1IzdPc6 Requests under review]
** [http://mzl.la/1CxAUKL Requests pending fulfillment]
** [http://mzl.la/1y0tm1R Requests pending fulfillment]
** [http://mzl.la/1Hs0x0t Requests with no further action needed]
** [http://mzl.la/1Hs0x0t Requests with no further action needed]
* Discussions
* Discussions
** [http://mzl.la/1x4DA0O Discussions needing review]
** [http://mzl.la/1FAW3Jp Discussions needing review]
** [http://mzl.la/1wXJgL5 Discussions pending additional information]
** [http://mzl.la/1y0tCOw Discussions pending additional information]
** [http://mzl.la/16KBavS Discussions that are pre-approved, but need final approval]
** [http://mzl.la/1FAWmnz Discussions that are pre-approved, but need final approval]
** [http://mzl.la/13WLqjs Discussions pending fulfillment]
** [http://mzl.la/1y0tOxa Discussions pending fulfillment]
** [http://mzl.la/1x4D3fj Discussions with no further action needed]
** [http://mzl.la/1y0tLl5 Discussions with no further action needed]


=== Further information needed ===
=== Further information needed ===


* [http://mzl.la/1CxDy3k All requests and discussions that need further information]
* [http://mzl.la/1FAX6Jg All requests and discussions that need further information]
* By person
* [http://mzl.la/1FAXmbc More information needed from Sandra Persing]
** [http://mzl.la/1zdbXAM More information needed from Dave Camp]
** [http://mzl.la/1GQQl3n More information needed from Janet Swisher]
** [http://mzl.la/1vhXSkr More information needed from Robyn Chau]
** [http://mzl.la/1xc5DP3 More information needed from Sandra Persing]
** [http://mzl.la/1xFHiAG More information needed from Stormy Peters]


=== Speakers ===
=== Speakers ===


* [http://example.com All events that need a speaker]
* [http://mzl.la/1xc9J9T All events that need a speaker]
* By continent
* By continent
** [http://example.com Events in Africa that need a speaker]
** [http://mzl.la/1yrh97Q Events in Africa that need a speaker]
** [http://example.com Events in Asia that need a speaker]
** [http://mzl.la/1yrh5Vy Events in Asia that need a speaker]
** [http://example.com Events in Australia that need a speaker]
** [http://mzl.la/1yrhvvf Events in Australia that need a speaker]
** [http://example.com Events in Europe that need a speaker]
** [http://mzl.la/15tEdYp Events in Europe that need a speaker]
** [http://example.com Events in North America that need a speaker]
** [http://mzl.la/1yrhLuf Events in North America that need a speaker]
** [http://example.com Events in South America that need a speaker]
** [http://mzl.la/15tEPx8 Events in Central / South America that need a speaker]
** [http://example.com Events online that need a speaker]
** [http://mzl.la/15tEXg6 Online-only events that need a speaker]


=== Other details ===
=== Other details ===
Line 79: Line 159:
** [http://mzl.la/1xc8ozO Other]
** [http://mzl.la/1xc8ozO Other]
* Mozilla product represented
* Mozilla product represented
** [http://example.com Firefox OS]
** [http://mzl.la/1v9wggi Firefox OS]
** [http://example.com Firefox Web Browser]
** [http://mzl.la/1xc8NlQ Firefox Web Browser]
** [http://example.com Webmaker]
** [http://mzl.la/1xc8SpN Webmaker]
** [http://example.com Persona]
** [http://mzl.la/1xc8TtK Persona]
** [http://example.com Marketplace]
** [http://mzl.la/1xc8XcV Marketplace]
** [http://example.com Thunderbird]
** [http://mzl.la/1xc8YgT Thunderbird]
** [http://example.com The Free and Open Web]
** [http://mzl.la/1xc8ZS4 The Free and Open Web]
* Requestor type
** [http://mzl.la/1xc93RR Developer Tools]
** [http://example.com Vouched Mozillian]
* Requester type
** [http://example.com Not a vouched Mozillian]
** [http://mzl.la/1xc9bRc Vouched Mozillian]
* Former sponsorship
** [http://mzl.la/1xc9awF Not a vouched Mozillian]
** [http://example.com Events that have been sponsored before]
* Past sponsorship
** [http://example.com Events that have not been sponsored before]
** [http://mzl.la/1v9wqEh Events that have been sponsored before]
** [http://mzl.la/1xc9qf7 Events that have not been sponsored before]
* Speaker
* Speaker
** [http://example.com Events that need a speaker]
** [http://mzl.la/1xc9s6U Events that need a speaker]
** [http://example.com Events that do not need a speaker]
** [http://mzl.la/1xc9taK Events that do not need a speaker]
* Booth
* Booth
** [http://example.com Events that have an option to sponsor a booth]
** [http://mzl.la/1v9wrrY Events that have an option to sponsor a booth]
** [http://example.com Events that do not have an option to sponsor a booth]
** [http://mzl.la/1v9wtzZ Events that do not have an option to sponsor a booth]
* Continent
* Continent
** [http://mzl.la/1xc6UFF Events in Africa]
** [http://mzl.la/1xc6UFF Events in Africa]
Line 105: 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 Online-only events]
* Prospectus
* Prospectus
** [http://example.com Events that have a prospectus]
** [http://mzl.la/1xc9zz6 Events that have a prospectus]
** [http://example.com Events that do not have a prospectus]
** [http://mzl.la/1v9wu70 Events that do not have a prospectus]
* Open Web
** [http://example.com Event that include a session about developing with HTML, CSS, or JavaScript]
** [http://example.com Event that do not include a session about developing with HTML, CSS, or JavaScript]

Latest revision as of 15:32, 26 January 2015

Workflow overview

The 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 Developer Events form. Bugzilla processes the answers and opens a request bug to summarize the request and a discussion bug for the Developer Events team to discuss the request privately. The team discusses the request and updates 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

Keywords

Requests and discussions can be tagged with special keywords that indicate state. Requests and discussions are automatically organized based on their keywords (see 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.

A screenshot of an event request with the Keywords field highlighted

Available keywords

Requests

The following keywords can be used with event requests:

event-request-under-review
Meaning: The request is being reviewed
event-request-pending-fulfilment
Meaning: The request has been discussed and is nearly ready to be fulfilled
event-request-no-further-action
Meaning: The request requires no further action
Discussions

The following keywords can be used with event discussions:

event-discussion-needs-review
Meaning: The discussion hasn't started
event-discussion-pending-additional-information
Meaning: The discussion can't continue until more information is provided
event-discussion-needs-final-approval
Meaning: A decision has been reached. It needs final approval and has not been pre-approved.
event-discussion-pre-approved-needs-final-approval
Meaning: A decision has been reached. It has been pre-approved but needs final approval.
event-request-pending-fulfilment
Meaning: The event being discussed is nearly ready to be fulfilled
event-request-no-further-action
Meaning: No further discussion is needed

Notifications

Request bugs

To receive email notifications about changes to event requests, follow these steps:

  1. Log into Bugzilla
  2. Visit the Component Watching page
  3. Choose the product Developer Engagement and the component Events Request. Click Add.
  4. Visit the Email Preferences page
  5. 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:

  1. Visit the Component Watching page
  2. Near the bottom of the page, check the Events Request component and click Remove Selected

To re-enable notifications, follow steps 2-3 of the first list.

Discussion bugs

To receive email notifications about changes to event discussions, follow these steps:

  1. Log into Bugzilla
  2. Visit the Component Watching page
  3. Choose the product Developer Engagement and the component Events Request Discussion. Click Add.
  4. Visit the Email Preferences page
  5. 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:

  1. Visit the Component Watching page
  2. 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 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 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 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

Status

Further information needed

Speakers

Other details

Retrieved from "https://dev.wikimo.nonprod.webservices.mozgcp.net/index.php?title=Engagement/Developer_Engagement/Event_request_workflow&oldid=1050360"