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

Jump to navigation Jump to search
Line 1: Line 1:
== Workflow overview ==
== Workflow overview ==


The [http://files.openjck.com/developer-events-workflow.html workflow flow chart] provides a visual overview of this workflow.
The [http://files.openjck.com/developer-events-workflow.html Developer Events flow chart] offers 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.
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.


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


== Using this workflow ==
== Using this workflow ==
Confirmed users
1,193

edits

Navigation menu