Developer Advisory Team Plans for Q

Registered by Daniel Holbach on 2012-04-18

Started during the P cycle, the Developer Advisory Team has been reaching to development contributors and while things have worked out quite well, there are surely things we can improve. https://wiki.ubuntu.com/DeveloperAdvisoryTeam

Agenda:
 - team meetings
 - outreach
 - improve feedback collection process
 - get notified about contributor status changes (active→inactive, new→experienced)
 - following up with contributors who don't reply
 - avoiding trello craziness

Blueprint information

Status:
Not started
Approver:
Jono Bacon
Priority:
Undefined
Drafter:
Daniel Holbach
Direction:
Approved
Assignee:
Daniel Holbach
Definition:
Approved
Series goal:
Accepted for quantal
Implementation:
Unknown
Milestone target:
milestone icon ubuntu-12.10

Related branches

Sprints

Whiteboard

Agenda:
 * team meetings
  * Andrea set up a doodle poll
 * outreach
 * improve feedback collection process
 * get notified about contributor status changes (active→inactive, new→experienced)
  * analysis: merges, syncs, SRUs, etc
 * following up with contributors who don't reply
 * avoiding trello craziness

We plan to do a better job in our communications with contributors (better feedback collation and try to offer more advice going forward) and start reaching out to experienced contributors (mid-way in their process) as well. Also will we try to improve how we organise our lists to have more visibility and be able to act more quickly.

(?)

Work Items

Work items for quantal-alpha-1:
[broder] start discussion about interaction plan (optimising response rate): TODO
[dholbach] extend email templates to ask if new contributors need advice in figuring out what they want to work on: DONE
[christophe.sauthier] start discussion about better information sharing between overview and trello board (get people off the list if necessary): TODO

Work items for quantal-alpha-2:
[dholbach] blog about feedback analysis (we need to learn from other people's experience): DONE
[dholbach] start reaching out to 'experienced' contributors: DONE
[dholbach] agree on criteria of experienced contributors: DONE

Work items:
[dholbach] look into 'status changes view': POSTPONED
[bhavi] give a session at UDW/UOW about the supporting factors when you start with Ubuntu development: DONE