947
edits
Auto-tools/Goals/2012Q1: Difference between revisions
add community involvement goals
No edit summary |
(add community involvement goals) |
||
| Line 248: | Line 248: | ||
* '''Depends On''' | * '''Depends On''' | ||
** Releng for Deployment - will likely require side-by-side deployment | ** Releng for Deployment - will likely require side-by-side deployment | ||
= Community Involvement Goals = | |||
* Identify all stakeholders and audience for each project in 2012 Q1. (ctalbert + project leads) | |||
** Ensure we have docs and good feature pages for each project to detail our phases, our plans and how to get involved (check out code, setup etc) (ctalbert to work with dria on making us easy-to-write feature page style wikis for this) | |||
* Integrate yourself with the teams that you're designing/implementing tools for (live in their IRC channel, go to their meetings, post to their newsgroup (as well as the tools newsgroup) (all of us will need to do this) | |||
* Ensure there are clear requirements for each phase of the project, including the polish/test/deployment phase - (ctalbert + project leads will work on this) | |||
* Increase visibility | |||
** Use Twitter with #mozauto and newsgroups to help build visibility | |||
** Use yammer if you want, we decided it doesn't seem that useful | |||
** put "auto-tools" or "a*team" in the title of your blog post if appropriate | |||
** don't rely on blog posts for interaction, use them more for resources to have reference material for our projects, cross post to newsgroups where/when appropriate (usually when you want/expect discussion). | |||
** we are hard to find (as a group) on social networks. Optionally, you're encouraged to put your twitter/other-social-group-info-you're-comfortable-with-sharing into your A*team members entry: https://wiki.mozilla.org/Auto-tools/The_Ateam | |||
** Feel free to think about proposing talks for conferences and community events if that's something you're interested in. It's an excellent way to bring in more contributors. OpenSourceBridge is coming up in May/June in Portland if people want to start thinking about presenting there. | |||