Community Architecture goals

These are our team goals for FY11 (March 2010 - February 2011).

As our goals change throughout the year, this page will be updated and modified.

Open Source in Education

FIXME

FIXME -- POSSE

• We want to be on a pace to have educated 200 professors after 5 years of POSSEs.
• We want to measure the conversion rate -- how many POSSE graduates go on to organize and/or teach a POSSE in the future?
• We want to measure the attrition rate -- how many POSSE graduates stop being professors?
• We want to measure success by geo.
• At some point, we'd like to facilitate a POSSE Alumni Reunion, in service of other educational goals and in order to encourage further POSSE development. Basically, the same reasons why we hold FUDCon.
• Continue to work with Pam Chestek about TM possibilities.

FIXME -- TOS

• Step up Red Hat's participation here, to speed up the heartbeat.
• Take stock of the endeavors that were proposed and started last year, and prune them, focusing only on the ones that have gained some community buy-in and provide value.
• Try to re-focus some of the conversation as a place where open-source engaged professors come to gain efficient visibility into what else is going on in the space.
• Look for potential osdc/edu contributors from clueful folks in TOS.
• TOS Ambassadors.

FIXME -- Curriculum

• Textbook
  • Alpha is complete by end of FY11 Q1.
  • Parts of textbook being used as basis for live courses when 2010 school year starts (FY11 Q3).
  • Beta is complete by end of FY11 Q4.
• RH007

FIXME -- Comms

• opensource.com/education
  • OSDC/EDU articles should generally rate as among the best, by whatever metrics OSDC uses to judge the success of the different channels.
  • By the end of FY11, Greg should only be producing 50% of the content.
  • Build a writer/contributor portfolio that demonstrates OSDC/edu is a center of thought leadership in the space. Prime targets initially:

FIXME -- University Portfolio

• University portfolio
• Treat our university investments like a financial portfolio and track returns and prospects over time.
• Establish some guidelines for future investments. See Professor grants, which is still very early and rough.
• CMU, RIT have the most promise going into FY11.

FIXME -- Fedora

• Maintain visibility in Fedora, and when we see places where tiny amounts of support from us can reinforce or encourage good ideas, provide those tiny amounts of support. This is a visibility/influence play only.
• Fedora Scholarship continues into its 4th year. Minimal time investment.
• Increase mentor and student presence in GSoC 2010 by 2x; use experience to evaluate with community further mentorship programs; CommArch team to consider moving this project to Education goals.

Project Building

Create, be, and be known for being a center of excellence on the following topics on the use, motivations, and characteristics of:

• Open source community building best practices other than participation in code development as presently done by Red Hat engineering.
• Free distributions, their development communities, and their relationship to Red Hat's paid products and commercial value proposition.

Create a community health dashboard, reflecting the status of the communities that exists around key Red Hat initiatives.

• This project should be done in consultation with both RH and JBoss input.
• Provide internal advocacy and exposure to the team's work.
• Include metrics of participation, statistical analysis, and deltas over time.
• Data driven benchmarking.
• Work on the EKG project, which is an upstream tool for analyzing mailing list and other contributions to projects.
• Highlight projects that have been identified as critical to Red Hat, and provide analysis of the health of the communities around those projects to aid in decision making.
• Provide the Community Architecture team with a tool that can demonstrate the improvements in the communities in which we engage directly.

Develop a handbook around the community building strategies and tactics that have made us successful.

Participate, and when possible, provide leadership and vision in key Red Hat projects, providing valuable services to our "internal customers". Be internal advocates of the Community Architecture vision. Ensure that projects are built to handle new contributors.

• Building an ISV ecosystem, including EPEL.
• FreeIPA.
• Spacewalk and management tools.
• Genome.
• Virtualization and cloud.

Become a recognized expert on the impact that other Linux distributions have on Red Hat's business.

Better understand perceptions of the Fedora brand internally and externally, and recommend/take actions to improve that brand as needed.

Global Community Stewardship

Maintain the overall health status and growth of the Fedora Project, encouraging minimal Red Hat touch in community leadership, except in the communities of greatest importance to Red Hat. Provide leveraged development & marketing, and authentically spread the Red Hat brand worldwide.

Create a "top tier" of Fedora-focused events that exist worldwide.

• Organize FUDCon in various regions. (NA, LATAM, EMEA, India/APAC).
• Organize Fedora Activity Days around the world, with specific focuses and goals.

Make Fedora Ambassadors as self-sufficient as posible.

• Work with the Fedora Ambassadors Steering Committee to manage a global events budget.
• Cultivate and support local leadership communities worldwide.
• Engage with and assist Red Hat community assets worldwide, such as Rodrigo (LATAM), Sankarshan (India), and Harish (APAC).
• Identify, encourage, and develop local community leaders.

Work with other parts of the Fedora Project to create and track metrics of community size, growth, and contributions.

Maximize the value of Red Hat's relationship with OLPC and Sugar Labs, both from an engineering and a marketing point of view.

• Serve as a consultant to OLPC and Sugar Labs.
• Maintain the relationship between OLPC and the Fedora community.
• Advise OLPC management in community matters.
• Ensure that Fedora is viable as an operating system that runs on the XO hardware.

Manage Red Hat's Summer coding initiatives.

As needed, triage Fedora communities. Fill leadership gaps, identify critical path, build up a community of leadership, and ultimately transition leadership to a community member.

• Fedora Marketing.
• Fedora Documentation.

Individual

Individual goals that don't fall into a specific category, but are still important.

Assist and advise the Fedora Project Leader.

Budget, meeting, and Community Architecture team leadership.

Maintain an active blog, with at least 50 substantive posts in FY11.

Maintain a strong level of participation in the Fedora community, since it is a focal lens for many projects that are important to Red Hat.

• Keep up with Fedora mailing lists, Planet Fedora, LWN, etc.
• Participate in community events as members of the Red Hat Community Architecture team, as open source evangelists, and as Fedora Ambassadors. Deliver an appropriately broad or narrow message, depending on our role at each event.