Draft roadmap (feedback requested)

[Christie Koehler]

Hi Everyone,

I've created a first draft of our 2014 roadmap:
https://wiki.mozilla.org/Contribute/Education/Roadmap

Please review it and provide feedback by responding to this email (or
you can find me on IRC).

Guiding questions:

* Do our guiding principles make sense? Are they compelling project-wide?
* Do the main goals make sense? Are they compelling project-wide?
* Have we identified the right subgroups? Is the main goal and purpose
of each subgroup clear?

-Ck

--
Christie Koehler
Education Lead, Community Building Team
https://mozillians.org/u/ckoehler/
ckoe...@mozilla.com
+1 415-317-7603

[Laura Hilliger]

Thanks Christie! <3 the rewrite and thanks for the clarifications. I don’t think you made anything more confusing :)

Laura Hilliger
Training & Curriculum Lead
Mozilla Foundation

Email: la...@mozillafoundation.org
Twitter: @epilepticrabbit

On Mar 20, 2014, at 4:28 PM, Christie Koehler <ckoe...@mozilla.com> wrote:

> Thanks so much for your detailed feedback! Responses inline below...
>
> On 03/20/2014 05:57 AM, Laura Hilliger wrote:
>> Guiding Principles: I find that “honor and support diversity” and
>> “mandate unity” are in direct conflict. It’s probably just semantics,
>> but “mandating” has only negative connotations for me. It’s too strict
>> and authoritative. Is it necessary? What are we trying to say there?
>
> In shortening these, I made them more confusing. Also, I think you're right about the negative connotation.
>
> Here is a re-write with some explanation. Let me know how it works for you all.
>
> 1. Support a diversity of contributors.
> -- Basically what this means is that we want to support diversity in everything that we do. This means designing materials and processes to meet the needs of potential contributors from a range of ethnicities, locations, abilities, socio-economic status, genders, etc.
>
> 2. Strive for simplicity, consistency and clarity.
> -- This is an attempt to counteract the confusion that the many, many communication channels and tools of the project generates. Whenever possible, we'll strive to use an existing solution rather than create a new one.
>
>> “Unify communication touch points” - Is the goal here to have every
>> project fill in a communication template for the wiki? If so, wouldn’t
>> it make sense to merge the first two goals, since both are related to
>> wiki gardening? If not, I’d be interested to hear what exactly you have
>> in mind.
>
> You describe one possible solution, but not the only one. The goal is to make it easy for contributors to communicate with various project teams. Kadir might want to jump in and speak more about this...
>
> It's true that lots of activities could be considered part of the Wiki Working Group. However, the point of having subgroups is to make our work manageable and distribute it among different drivers. Plus, the WWG is primarily concerned with the governance of the wiki as a product, and not generating specific content hosted there.
>
> You can get a better sense of what the WWG will be working on here:
> https://wiki.mozilla.org/Contribute/Education/Wiki_Working_Group/Notes/2014-03-07#Priorities
>
>> Resource Index: whoa! We should talk about how this ties into Webmaker.
>> We’re curating resources from all over the web that align with the web
>> literacy map <http://webmaker.org/literacy>. It would be amazing if as
>> we build out the Mozilla Resource Index, we could be tagging relevant
>> things with the WebLitMap. Then, later, we can use the MakeApi to serve
>> great Mozilla resources to the folks who come to Webmaker looking to
>> learn about the web.
>
> Sounds like a good idea.
>
>> Community Building Curriculum: Your friendly Webmaker TeachTheWeb team
>> is designing a training program that embeds pieces and parts of this.
>> I’d love to coordinate here, and build with our teaching kits so that
>> people can rip, read and remix!
>
> Also a good idea!

[Laura Hilliger]