Quality Community Growth

Registered by Nicholas Skaggs on 2013-03-04

More and more users are willing and able to run what was historical the "development" release. The potential quality members has increased with the changes. Let's talk about how to reach these potential members as well as encourage, retain, and grow our current community

Blueprint information

Status:
Not started
Approver:
Jono Bacon
Priority:
Undefined
Drafter:
None
Direction:
Needs approval
Assignee:
None
Definition:
New
Series goal:
Accepted for raring
Implementation:
Unknown
Milestone target:
None

Related branches

Sprints

Whiteboard

eHost:
Topic: Quality community Growth. UDS Day 2 03/06/2013 14:00 UTC
Questions:
How will changes in the release cyle effect what is refered to now as "Beta, Alpha" releases?
Measuring Growth. How is it measured, how it compares to prior measurements.
Prior Survey:
https://docs.google.com/spreadsheet/ccc?key=0As1YvmKT_zzbdG5ucGNRN2dFdElCSktHM0xTcU91c2c&usp=sharing
Prior Survey:
http://www.theorangenotebook.com/2012/08/quality-perceptions-survey-results.html
What can we do to reach more people?
    Classroom Sessions/UDW/Ubuntu Global
    Outreach beyond ubuntu community
        social networks
        publishing articles outside of ubuntu planet / ubuntu blogs
        partnering with other teams?
            loco teams?
            dev teams?
            bug squad?
        hackathons
        irc meeting / hangouts
        askubuntu
upstream - Debian?
Current Member
    how easy is it to contribute?
        test results
        test contributions
        new tool
    are things existing for all skill levels?
Beta version:
    how to get feedback?
        ubuntu accomplishments?

Attempts to drive people via sklls by asking a few questions:
    https://qa.ubuntu.com/getting-involved/
    could we create something like: http://www.whatcanidoformozilla.org/?

    Have targetted outreach drives?
        target communities with skills that would be useful for testing
Define the purpose of those involved. <<
IDEA:
would a good idea be to approach upstreams with things such as "you know, you got five bad reviews in USC because your app crash when you do foo"
 you can also approach upstream and relay a thanks from the users as given on USC reviews
Bullet Points/recap:

(?)

Work Items

Work items for ubuntu-13.04-month-6:
[nskaggs] Update manual test repository with ubuntu touch tests: DONE
[nskaggs] Re-do contribution screencast for iso testing: DONE
[nskaggs] Encourage projects to utlize ubuntu-manual-tests for manual testcases, and the call for testing options (send email to ml): DONE
[nskaggs] Work with hexr and checkbox team to launch the open hw db: DONE
[nskaggs] Ubuntu touch info -- how to test, make sure we capture people interested in new platforms: DONE
[nskaggs] Engage with app dev community to instill best practices. Work with dplanella: DONE

Work items:
[nskaggs] Publish article to omg, et la, announcing and explaining the team, mission, and goals: DONE
[nskaggs] work with pitti to engage with upstreams -- talk about tests we've written, incorporate them: DONE
[philipballew] Help push out info to lo-co's to encourage them to test beta's: TODO
[philipballew] Ubuntu accomplishments for betas: TODO