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

Engagement/Developer Engagement/Event request workflow (view source)

375 bytes added , 20 January 2015

Confirmed users

1,193

edits

@@ Line 1: / Line 1: @@
 == 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 ==