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

From MozillaWiki
Jump to navigation Jump to search
No edit summary
Line 101: Line 101:
Listings are collections of requests and discussions that meet certain criteria. To browse Listings, follow the links in the [[#Listings|Listings section]].
Listings are collections of requests and discussions that meet certain criteria. To browse Listings, follow the links in the [[#Listings|Listings section]].


==== Drilling down on listings ====
==== Drilling down through listings ====


When searching for specific requests and discussions, it can sometimes be helpful to further narrow the criteria of a given Listing. To do this, open a Listing and click ''Edit Search'' near the bottom of the page. Add additional criteria and click ''Search''.
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 ====
==== Making a request or discussion appear in a different listing ====

Revision as of 14:41, 21 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 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

Follow these steps to receive email notifications about event discussions:

  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.

Follow these steps to disable notifications:

  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.

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, be sure that the Keyword for that item 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. Events filed before December 2014 are not included. With a few exceptions, closed requests and discussions are not included.

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=1049407"