Community Architecture goals

This page is a draft only
It is still under construction and content may change. Do not rely on the information on this page.

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

As our goals change throughout the year, this page will be updated as warranted.

Leading Red Hat's education strategy

The Community Architecture team is accountable for Red Hat's strategy in the intersection of The Open Source Way and educators, educational institutions. Our multi-year goal is to build a community of practice in this space, establishing Red Hat as a thought leader and facilitator. Furthermore, we should demonstrate a force-multiplied return on our investments, as professors and institutions with whom we work have the ability to impact multiple students over the course of many semesters and school years.

Professors' Open Source Summer Experience

POSSE will continue into its second year, with the following goals and metrics:

• Be on a pace to have a public-facing POSSE Alumni list containing at least 400 professors after 5 years of POSSE.
  • For tracking purposes, a reasonable metric is 50 after this year's POSSEs conclude, 125 after year 3, 250 after year 4, 400 after year 5.
• Solidify the Computer Science POSSE curriculum with 2010 POSSEs, and facilitate at least one inter-disciplinary POSSE as well.
• Establish metrics that can be tracked over time.
  • Conversion rate -- how many POSSE graduates go on to organize and/or teach a POSSE in the future?
  • Attrition rate -- how many POSSE graduates are still teaching after X years, and how many are still teaching open source?
• Build a roadmap for a POSSE Alumni reunion, which encourages further POSSE development, and is critical to the leveraged, yet managed, expansion of POSSE.
  • Given the long time cycle of academia, planning for this may occur during FY11 for an event during FY12.
• Continue to work with Red Hat Legal in determining whether or not it is appropriate to pursue any trademarks.

Teaching Open Source community

• Step up Red Hat's participation here, with two aims:
  • Make it clear that Red Hat is a driving force in this community, and a thought leader in catalyzing projects and growing the community.
  • Inject some corporate urgency and speed into the slower-moving academic world.
• 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.
• Re-focus the community as a place where open-source engaged professors come to gain efficient visibility and to collaborate with their peers.
• Convert at least 5 new opensource.com/education contributors from the TOS community.
• Implement a TOS Ambassadors program, which allows professors who find value in TOS to represent TOS and grow the TOS brand.
• Treat our university investments like a financial portfolio and track returns and prospects over time.
• Establish some guidelines for future investments. Formalize and expand the professor grants idea.

Practical Open Source Software Engineering textbook

• Textbook
  • Alpha is complete by end of FY11 Q1.
  • Beta is complete by end of FY11 Q2.
  • Textbook being used in at least 3 live courses when 2010 school year starts (FY11 Q3).
• RH007 opened, updated, localized, and being used.

Thought leadership

• http://opensource.com/education
  • 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, CommArch 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.

Red Hat summer coding

• 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, with an eye to passing leadership into the community with CommArch oversight.
• Summer Coding --> EXPAND ME.

Open Source evangelism, both external and internal

• External evangelism
  • The Open Source Way as a growing, living best practices manual that is referenced in all things Red Hat participates in, and as a hook for public speaking engagements.
  • CORP: Provide a voice for project marketing, which complements the product and sales messages that Red Hat sends, especially around cloud and virtualization, and that is well-aligned with engineering and brand.
  • CORP: What to do with RHCE Loopback?
• Internal evangelism
  • Orientation
  • The Open Source Way applied internally

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. 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.
• Data driven benchmarking: include metrics of participation, statistical analysis, and deltas over time.
• Work with (and contribute to) the EKG project and lookatgit project, which are upstream tools for analyzing mailing lists and git repositories of projects.
• Provide the team with a tool that can demonstrate the improvements in the communities in which we engage directly, as well as internal advocacy and exposure to the team's work.

Working with Fedora contributors, provide vision and high-level management to create and track the next generation of statistics for the Fedora community.

• Integrate this work into the aforementioned dashboard.

Continue development and promotion of The Open Source Way.

• FIXME -- What's the expansion roadmap?
• FIXME -- How do we incorporate video or audio, like a podcast on community best practices?
• FIXME -- Integration with RHU, as an excuse to refresh some old RHU content and make it CommArch owned?

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.

• FIXME -- Project Marketing for virtualization, cloud, management?
• FIXME -- Cloud and Fedora. Amazon and deltacloud.
• FIXME -- Spacewalk, as a "for instance" of two birds with one stone.
• Expand and institutionalize an "open sourcing process" for use across Red Hat.

FIXME -- Become a recognized expert on the impact that other Linux distributions have on Red Hat's business. Do we still want this as a goal?

Fedora Project stewardship

The Community Architecture team contributes to the success of the Fedora Project, and ensures that the Fedora community is healthy. The team's efforts within the Fedora Project are spent less on the technical aspects of the Fedora distribution, and more on supporting the inclusive infrastructure of participation that the Fedora Project aspires to, encouraging minimal Red Hat touch in community leadership.

Sub-project leadership

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

Marketing

The Fedora Marketing team should be community-led early in the Fedora 14 release cycle.

Ambassadors

Make Fedora Ambassadors as self-sufficient as posible. When Fedora holds its 2011 elections for the Fedora Ambassadors Steering Committee, the only Community Architecture team members who should run for election are those who are (if applicable) specifically tasked with community leadership in specific regions of the world.

• Work with the Fedora Ambassadors Steering Committee to manage a global events budget.
• Cultivate and support local leadership communities worldwide.
• Identify, encourage, develop, and engage with local community leaders.

Premier Fedora Events

Be a catalyst for Premier Fedora Events, while encouraging community leadership, ownership, and accountability.

• Ensure that at least 3 FUDCons are held in various regions, in which primary organizational responsibility is driven by local community members with financial support from Community Architecture.
  • Have a plan in place, with Red Hat resources, that will allow for 4 FUDCons in FY12+.
• Ensure that at least 20 Fedora Activity Days are held around the world, with specific goals and deliverables.
  • Analyze the past two years of FADs, and make recommendations regarding what kinds of FADs are more or less successful, and how we can improve our success rate, and total number of FADs, over the course of 2 years.
• Establish standard operating procedures around Premier Fedora Events, so that community members worldwide feel that they are empowered to organize events, attend events, make use of resources, and proactively provide value to different parts of the Fedora Project.

Visibility

Team members maintain a presence in the Fedora community, since it is a focal lens for many projects that are important to Red Hat.

• Keep up with Fedora Weekly News, 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.

Other

There are several other goals that are general, and don't fit into any of the previously discussed buckets.

Blogging

Each team member authors a blog (with at least 50 substantive posts this year) that is aggregated on Planet Fedora and other appropriate aggregators (such as Planet TOS).

General management

The team's manager is accountable for the budget, meetings, and Community Architecture general team leadership.