canmove, Confirmed users
1,953
edits
(Replaced mailing list ilnks with links to Discourse) |
|||
Line 209: | Line 209: | ||
* The MDN Taiga project is set as a "public project". | * The MDN Taiga project is set as a "public project". | ||
* The MDN roadmap and other related planning and outcome documents are publicly visible, by being linked from the [[Engagement/MDN_Durable_Team|MDN Durable Team's wiki page]], and set with access "anyone with the link can view". | * The MDN roadmap and other related planning and outcome documents are publicly visible, by being linked from the [[Engagement/MDN_Durable_Team|MDN Durable Team's wiki page]], and set with access "anyone with the link can view". | ||
* The User Stories planned for each Sprint are announced on the [ | * The User Stories planned for each Sprint are announced on the [https://discourse.mozilla-community.org/c/mdn MDN discussion forum], once they have been decided upon. Volunteers are encouraged to share their plans for MDN-related work as part of the thread. | ||
* The work accomplished during a Sprint is shared on the [ | * The work accomplished during a Sprint is shared on the [https://discourse.mozilla-community.org/c/mdn MDN discussion forum], along with a link to the MDN team's "demo package" (note that the Marketing-wide Sprint Demo meeting is not public, because some durable teams may share confidential information). | ||
* MDN Durable Team meetings (except Retrospectives) are public, and are marked in the [https://www.google.com/calendar/embed?src=mozilla.com_2d35383434313235392d323530%40resource.calendar.google.com Public MDN Events calendar], along with video conference connection information for video meetings. | * MDN Durable Team meetings (except Retrospectives) are public, and are marked in the [https://www.google.com/calendar/embed?src=mozilla.com_2d35383434313235392d323530%40resource.calendar.google.com Public MDN Events calendar], along with video conference connection information for video meetings. | ||
* Team members are encouraged to seek help from volunteers for day-to-day tasks and reviews of work, by posting on the [ | * Team members are encouraged to seek help from volunteers for day-to-day tasks and reviews of work, by posting on the [https://discourse.mozilla-community.org/c/mdn MDN discussion forum]. | ||
* Due to the distributed nature of the MDN team and community, asynchronous communication (email) is preferred over ad-hoc synchronous meetings. Whenever possible, hold | * Due to the distributed nature of the MDN team and community, asynchronous communication (email) is preferred over ad-hoc synchronous meetings. Whenever possible, hold discussions in public, such as on the [https://discourse.mozilla-community.org/c/mdn MDN discussion forum]. | ||
* When meetings are needed (especially for planning and prioritization), invite all team members, using mandatory and optional attendee settings in Google Calendar to indicate who is required, vs. informed. If possible, add meetings to the MDN public calendar to enable community members to attend. ''Make sure there is a guest Vidyo link in the calendar event.'' | * When meetings are needed (especially for planning and prioritization), invite all team members, using mandatory and optional attendee settings in Google Calendar to indicate who is required, vs. informed. If possible, add meetings to the MDN public calendar to enable community members to attend. ''Make sure there is a guest Vidyo link in the calendar event.'' | ||
* Take and share notes of meetings to communicate decisions made, actions assigned, etc. | * Take and share notes of meetings to communicate decisions made, actions assigned, etc. |