Growing a new generation of Ubuntu leaders

Registered by Michael Hall

Identify ways to grow and nurture a new generation of leaders in the Ubuntu community

Blueprint information

Not started
Jono Bacon
Michael Hall
Needs approval
Jono Bacon
Series goal:
Milestone target:

Related branches



Notes from belkinsa:

(DO) Have a Leadership Summit
Maybe focus on the non-natural leaders and maybe explain to the natural leaders that what they doing isn't helpful
From the IRC channel:
[12:15] 18<26rrnwexec> a key distinction is "Leader" (who has vision, can inspire), and "Manager" (who can track progress, unblock obstacles, etc)
[12:15] 18<26rrnwexec> which do we need more of?
[12:15] <rrnwexec> Leaders can be identified by their vision
Jono say we need both, leader and manager
Managers are needed for geting things done and is truey needed (again Jono said that) and is more needed
From IRC:
[12:21] <rrnwexec> perhaps a toolkit to empower managers would be useful. start with a simple event/task and create a punch-list to get that done.
[12:21] <belkinsa> +1
[12:21] <belkinsa> And maybe a wiki page?
ID leaders within the Community and feedback
    Through the leadership training somethings/mentors that could be managed with the active leaders of the Community
    Videos on how to start things and maintain these things
    Required web pages how to be leaders, could be apart of the toolkit
    From IRC:
    [12:33] <rrnwexec> another example is the work that has been done by Jono's team on runnng an Ubuntu SDK event at your LoCo
Break down the barrier of the appoval to make an action
From the IRC:
[12:34] 18<26rrnwexec> there's an idea i've "borrowed" from other local community (face-to-face) volunteer groups: it starts with a promise of time. "I pledge to donate 10 hours of my time to do such and such."
[12:34] 18<26rrnwexec> without that, there's not going to be follow-through
[12:35] 18<26rrnwexec> good Project Management starts with a budget.
[12:35] 18<27mhall119> I've seen it multiple times where people feel they can't do
[12:37] <rrnwexec> with governance in place, especially formal governance, people will always fear a "lack of permission".something without someone's permission
Way to explian what LoCo's are used for what events and what sort of permissions are required
Way to explain that permisson is NOT needed in FOSS
    Maybe through small projects that don't require premission to get people away from it but have some management within the small projects
From IRC:
[12:39] 18<28YoBoY> lot of people are affraid to take decisions, they always search an approval from their "loco/team leader"
Docs are needed to help leaders and have new gen leaders to be lead by the current leaders
    Maybe use of wiki pages but it's a mess (Jono said this)
    Maybe use video but short videos (Jono again)
    Jono will take time to make a list to figure what people are having a hard time to lead via videos
        From IRC:
        [12:44] 18<26rrnwexec> i think the first video or two should be the ones that are widely applicable, to any team
        [12:44] 18<27nxvl> Or share experiences from LoCo's, the problems they faced and how they solved it
    Use of check list of what to do from the video (Nate said that)
    Ref video to a doc (Jono)
    [12:48] 18<28YoBoY> videos, why not, but please do them with subtitles (in english, and with the help of the translation teams)
    Maybe have video/photos from the events in the videos (Mhall)
    Videos with subtitles (Jose)
    Missed someting from Jono!
    From IRC:
    [12:53] 18<27nxvl> having a little "this is how we did it" videos would also help, so, anyone that makes an event, would make a "behind the scenes" kinda clip and share it
    Jono said that five steps in videos and have it comminty.ubuntu and head menu on LoCo
From IRC:
[12:48] 18<26rrnwexec> before telling people how to get involved, a quick "assessment" of their capacity may be useful
[12:48] 18<26rrnwexec> how many hours can they offer?
[12:49] <nxvl> More than doing a "This is what you should do, and how to do it, it should explain a lot WHY to do it"
[12:49] <nxvl> the goals, what should be achieved


Work Items

This blueprint contains Public information 
Everyone can see this information.