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

From MozillaWiki
Jump to navigation Jump to search
No edit summary
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 workflow flow chart] provides a visual overview of this workflow.
 
In essence, a person who wants 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 details along the way. When a decision is reached, the team shares the decision in the request bug so that the requester is notified.
 
Further detail about this workflow is provided in the sections below.


== Using this workflow ==
== Using this workflow ==

Revision as of 22:23, 20 January 2015

Workflow overview

The workflow flow chart provides a visual overview of this workflow.

In essence, a person who wants 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 details along the way. When a decision is reached, the team shares the decision in the request bug so that the requester is notified.

Further detail about this workflow is provided in the sections below.

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

Keyword meanings

Requests

The following keywords can be used with event requests:

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

The following keywords can be used with event discussions:

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

Notifications

Request bugs

Follow these steps to receive email notifications about event requests:

  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 boxes in the Component column depending on the types of notifications you want to receive. Click Submit Changes.

Follow these steps to disable notifications:

  1. Visit the Component Watching page
  2. Check the Events Request component and click Remove Selected

Follow steps 2-3 of the first list to re-enable notifications.

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 boxes in the Component column depending on the types of notifications you want to receive. Click Submit Changes.

Follow these steps to disable notifications:

  1. Visit the Component Watching page
  2. Check the Events Request Discussion component and click Remove Selected

Follow steps 2-3 of the first list to re-enable notifications.

Listings

Listings are requests and discussions that meet certain criteria. To browse Listings, follow the links in the Listings section.

Drilling down on 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.

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 requests and discussions that meet certain criteria. With few exceptions, closed bugs are not shown.

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