Confirmed users
266
edits
AllHands: Difference between revisions
Jump to navigation
Jump to search
no edit summary
No edit summary |
|||
| Line 122: | Line 122: | ||
</div> | </div> | ||
</onlyinclude> | </onlyinclude> | ||
===Documentation and process: How we support our engagement work === | |||
<b>Time</b>: Tuesday morning<br | |||
/> | |||
<b>Lead</b>: Erika Owens, Leah Gilliam<br | |||
/><b>Collaborators</b>: <br | |||
/><b>Local SF contact</b>: <br | |||
/><b>Goal</b>We're all doing a lot of great work. How do we document it and share our learnings within our teams, between our projects, with our stakeholders, and beyond? Thinking through the followthrough and documentation process is also critical in keeping contributors engaged. Let's sketch out some of the key elements of documentation and follow-through and share tactics about how to make sure it actually happens. | |||
Etherpad: https://etherpad.mozilla.org/allhands2014-community-docs We're going to loop back with Matt's working MoFo session.<br | |||
/>'''Length''':? <br | |||
/> | |||
'''Tags''': [allhands][newcommunities][documentation] | |||
<div style="align:left;"> | |||
<bugzilla> | |||
{ | |||
"whiteboard": "[allhands][newcommunities][documentation]", | |||
"include_fields": "id, summary, whiteboard, assigned_to, status", | |||
"maxrows":"50", | |||
"order": "bug_id" | |||
} | |||
</bugzilla> | |||
</div> | |||
</onlyinclude> | |||
===Maker Party: Driving Mozilla-wide participation === | ===Maker Party: Driving Mozilla-wide participation === | ||
| Line 397: | Line 422: | ||
}</bugzilla><div style="align:left;"></onlyinclude> | }</bugzilla><div style="align:left;"></onlyinclude> | ||
==Anytime / Unscheduled== | ==Anytime / Unscheduled== | ||