Introduction

The goal of this section is to collaboratively draft ideas that can enhance U+1 performance as a team. Our main goals are:

• Recruiting more members;
• Retaining members;
• Getting members involved into team activities (technical, organisational);
• Improving our communication to other Ubuntu teams, groups and users;
• Improving our current resources (wiki, FAQ, forum, IRC, tools, Launchpad, etc);
• Improving our technical processes (testing methods: Procedures, tools, automation, etc);
• Improving our management processes;

Mostly any coherent idea fits one of these goals. Idealy, as Blueprints are added to this section, other users can edit and improve them, turning thoughts and ambitions into mature projects.

Blueprints

Blueprint #1: The U+1 "You+1" Project

• Goal: Getting more people involved

• Description: Select one Ubuntu user that is not a current member but shows interest in technical aspects of Ubuntu (there are plenty of them on IRC, UbuntuForums, your university, etc). Invite them for an event in IRC in which current members will present the team, its activities, goals, relevance of the work, examples, etc. A portion of these users may potentially develop some interest in joining the team.

Blueprint #2: New Role - Marketing and Communication Manager

• Goal: Publicise the team; Getting more people involved

• Description: A member will email blogs, forums managers and admins, groups of users, publicising the U+1 Team and the easy procedures for joining it.

Blueprint #3: U+1 Tools

• Goal: Making work of team members easier

• Description: Take advantage of currently existing QATeam tools, develop and customise other tools aimed at performing boring tasks faster and automatically: From download / sync and burn of daily ISO, to Testing Automation. Pre-requisite: Identify members technical skills.

Blueprint #4: Map members hardware profiles and testing preferences

• Goal: Assess our infrastructure and define our testing capacity

• Description: Create table on wiki where registered members can fill in the hardware specs they will make available for testing. Not all members will accept to do all types of tests (i.e. Ubuntu Flavors). Identify what members are willing to test, their preferences and interest.

Blueprint #5: Ask members what we can do to trigger their motivation to get involved. Evaluate this regularly

• Goal: Improve members commitment

• Description: Communities fail for lack of interest and involvement of their members. But they also never ask what are these users needs, problems, expectations, frustrations, what triggers them, what they love to do, what they hate to do. New Role: Team Staff Manager

Blueprint #6: Ask members what we can do to trigger their motivation to get involved. Evaluate this regularly

• Goal: Improve members commitment

• Description: Communities fail for lack of interest and involvement of their members. But they also never ask what are these users needs, problems, expectations, frustrations, what triggers them, what they love to do, what they hate to do. New Role: Team Staff Manager

Blueprint #7: Open Blueprint for members and the larger Ubuntu community

• Goal: Improve members commitment; Recruit new members; Assign blueprints development to members

• Description: People like to brainstorm, have ideas, discuss their point of views, feel as a part of it. Let's use our current resources (Forum, IRC) to ask them to come here and insert their own Blueprints.

Blueprint #8:Make testers wiki easy

• Goal: Making it easier for new members to understand technical concepts, retain members

• Description: Ventrical made a good point with this Blueprint. We should always review our work to make sure it can be used and understood by any team member and user. It might be impossible to make it accessible to all users (some have absolutely no skills, interest or will to read and learn, but we must focus on the people, no matter their skill level, that *are* interested.

Blueprint #9:Insert name here

• Goal: Insert goal(s) here

• Description: Insert description here

Blueprint #10:Insert name here

• Goal: Insert goal(s) here

• Description: Insert description here

Blueprint #11:Insert name here

• Goal: Insert goal(s) here

• Description: Insert description here

Blueprint #12:Insert name here

• Goal: Insert goal(s) here

• Description: Insert description here

Blueprint #13:Insert name here

• Goal: Insert goal(s) here

• Description: Insert description here

Blueprint #14:Insert name here

• Goal: Insert goal(s) here

• Description: Insert description here