ImprovingCommunication

Revision 3 as of 2010-05-10 11:03:16

Clear message

Summary

A session where we're going to discuss how to improve the communication with our community on Mailing lists, IRC Meetings, events, etc.

Release Note

This section should include a paragraph describing the end-user impact of this change. It is meant to be included in the release notes of the first release in which it is implemented. (Not all of these will actually be included in the release notes, at the release manager's discretion; but writing them is a useful exercise.)

It is mandatory.

Rationale

This should cover the _why_: why is this change being proposed, what justifies it, where we see this justified.

User stories

Assumptions

Design

You can have subsections that better describe specific parts of the issue.

Implementation

This section should describe a plan of action (the "how") to implement the changes discussed. Could include subsections like:

UI Changes

Should cover changes required to the UI, or specific UI that is required to implement this

Code Changes

Code changes should include an overview of what needs to change, and in some cases even the specific details.

Migration

Include:

  • data migration, if any
  • redirects from old URLs to new ones, if any
  • how users will be pointed to the new way of doing things, if necessary.

Test/Demo Plan

It's important that we are able to test new features, and demonstrate them to users. Use this section to describe a short plan that anybody can follow that demonstrates the feature is working. This can then be used during testing, and to show off after release. Please add an entry to http://testcases.qa.ubuntu.com/Coverage/NewFeatures for tracking test coverage.

This need not be added or completed until the specification is nearing beta.

Unresolved issues

This should highlight any issues that should be addressed in further specifications, and not problems with the specification itself; since any specification with problems cannot be approved.

BoF agenda and discussion

Agenda

  • Meetings
    • Small round table
    • Rotation on chairing / sending notes
    • "Featured team"
  • Mailing lists
    • ubuntu-qa
    • ubuntu-bugsquad
  • Blogs
    • QA blog
    • Personal blogs
  • Newsletters
  • Twitter

Discussion

  • Meetings
    • The feel Canonical QA team
    • We don't ask the community (call for topics)
    • LoCo Teams

    • Brainstorming
    • Making decissions
    • Lack of agenda
    • Roundtable per team
    • rotation on chairing / sending notes
    • Suggestion on alternate times - 2 fixed times
      • Set up a doodle poll to ask for times - Paolo
    • Selecting the chair at least 2 weeks in advance
    • We need a way to mesure participation
    • Way to (automatically) send transcript of meeting notes to mailing list
    • "Featured team"
      • Representatives from other teams v.s. QA people only
  • Mailing lists
    • ubuntu-qa
      • Introducing themselves, and then you don't hear from them
      • Pointing people to documentation - Once a cycle.
    • ubuntu-bugsquad
      • A way to communicate ways to help
      • Bug conversation needs to happen here
    • ubuntu-bugcontrol
      • Only for reviewing applications to the bug control
      • apport crashes
  • Mentoring?
    • Having a email template to send to new people
    • A way to help people finding a job
  • Blogs
    • QA blog
    • Personal blogs
    • The design team has a blog that also aggregates their personal blogs.
      • We want that!!!!
  • Newsletters
    • Good for people not that involved
  • Twitter


CategorySpec