: New feature! MozillaWiki is now mobile-friendly. Visit from a mobile device to see new mobile theme + try editing. Release details.

User:Ckoehler/Open Planning Checklist

From MozillaWiki
Jump to: navigation, search
Request for Comments
date created 2014-05-07
author Christie Koehler
status draft
To make comments: Edit this page, putting your comments in the #Comments section. Include ~~~~ to include your signature.

Background

The purpose of this document is to help those leading projects have an open planning processes in order to enable community participation.

This checklist started with content from Community Event Planning.

Best Practices

  • Announce your planning kick-off meeting and all other planning meetings through relevant mailinglists and other channels (blogs, yammer, mopo/moco meetings.
  • Specifically invite key paid and volunteer contributors.
  • Identify asynchronous and synchronous channels for planning and encourage people to participate.
  • Assign a note taker at each meeting, post notes as soon as possible afterward.
  • Keep track of open tasks, deadlines and other reminders in a way that that will enable participants to just jump in and get work done.
  • Set up a place on the wiki to document all aspects of your project. Be sure to archive all meeting notes there.
  • Use a collaborative editing tool like Etherpad to take meeting notes and draft communications about the project.

Checklist

  • name and short summary of project?
  • wiki page for project
  • how can contributors get involved?
  • location for asynchronous communication?
    • is this open to everyone? mozillians only? staff only?
    • is this friendly to those connecting via a low-bandwidth connection?
    • is this friendly to those who are not native english speakers?
  • location for synchronous communication?
    • is this open to everyone? mozillians only? staff only?
    • is this friendly to those connecting via a low-bandwidth connection?
    • is this friendly to those who are not native english speakers?
  • location for meeting and project notes and updates?
    • is this open to everyone? mozillians only? staff only?
    • is this friendly to those connecting via a low-bandwidth connection?
    • is this friendly to those who are not native english speakers?

Comments

Tips for adding comments:

  • Include ~~~~ as the last text of your comment to include your signature.
  • Indent text to reply with a colon :

Examples:

This is is the first comment! Christie Koehler (ckoehler) (talk) 12:53, 7 May 2014 (PDT)

this is the first reply! Christie Koehler (ckoehler) (talk) 12:53, 7 May 2014 (PDT)

Add your comments and suggestions here:

  • What is the purpose of the document? To whom is it geared? The background section should be augmented. ~~~~
  • Provide information around the WHY and HOW they would include people in the planning. MichelleMarovich (talk) 09:53, 8 May 2014 (PDT)
  • The question: "How can this include Contributors?" is too broad-- for people who do not know how to do this, we need to break this down into a smaller subset of questions that leads them to being able to answer this question. MichelleMarovich (talk) 09:53, 8 May 2014 (PDT)
  • I wonder if adding recommendations would be useful? For instance, I've had experiences where people are receptive to having discussions in a public way, but they don't know what options to use to do that. One way to fold in recommendations could look like: "Is this open to everyone? Consider a discussion forum. Is it for mozillians only? Consider Yammer." -- David