The community dashboard is a research and analysis project. The goal is to help the team bring rigor to its goal-setting and also to give us a means of measuring success over time.
There are many successful communities within Red Hat, Fedora, and JBoss, and those communities have been built by many different people. The Community Architecture team wants to understand how these communities are created, and how we ensure that every member of Red Hat, Fedora, and JBoss is capable of creating and leading a successful community.
Community Biology 101
Community serves as a catalyst in everything that Red Hat, Fedora, and JBoss does.
Reaction: The progress of any task from idea to reality. The task can be as simple as a one-page summary of Fedora 10 for the press, or as complicated as the feature planning process for Fedora 11. The task can be code, leadership, process documentation, testing, writing, artwork, etc.
For any reaction to complete requires some amount of energy. From a business point of view, energy, time, and money are all synonymous.
The blue curve represents a reaction that does not operate with a community-building mindset. Perhaps this is a proprietary software project, and community isn't even an option. Perhaps it is an open source upstream that is so focused on coding, it doesn't have the time to properly build a community. Either way, the amount of energy required to reach a successful end state is high.
The red curve represents a reaction that does operate with a strong community. Whether it is a Fedora sub-project, Fedora as a whole, the RPM upstream, OLPC, or an emerging technology like Cobbler or Func is irrelevant.
Note that both reactions ultimately reach the same end state. The difference is the energy required to get there. Microsoft and Red Hat can both produce an operating system. Our job is to ensure that Red Hat does so more efficiently, and community is the mechanism by which we achieve that.
Incremental vs. Continuous
We still need to define the end state of a successful community-catalyzed reaction. The end state has two characteristics:
- The community has a clearly identified critical path and roadmap for the future.
- The community has a clearly defined leadership structure that does not depend on any of the catalysts.
In short, the reaction will have reached critical mass. The Community Architecture team can disengage from day-to-day operations in the community, but the community will continue to grow and thrive. Perhaps certain members of the team still participate in the community because they choose to, but the community is self-sustaining. We have made ourselves redundant, and therefore free to choose a new community to catalyze.
If we have done our job correctly, the activation energy needed to reach critical mass will be lower than in an equivalent reaction that did not focus on community building.
EKG is a community health scanner.
Its goal is to mine and present statistics about the health of various communities. Currently, its focus is on mailing lists but it has the potential to expand to other forms of contributions. Mailing lists are a proper first step because they represent the common denominator that every community must have. Furthermore, the depth (number of messages) and breadth (number of unique authors) are a decent indicator of the community's size and velocity.
EKG can process the entire history of a project, so different communities can be inserted or removed from the EKG analysis at any point in time, without the risk of data loss. Because EKG can look backward in time, it can quickly show a community's entire growth history.
Finally, EKG represents a means of processing a huge amount of raw data that is available. Our dashboard will focus on a (changing) subset of this data, but is important to know that there is an always-flowing and always-increasing river of data underneath the dashboard.
There are four main types of communities that we must track:
- Fedora communities
- RHEL communities (Emerging Technologies, Red Hat upstream projects, etc.)
- JBoss communities
- Other upstreams and other distributions (to serve as a point-of-comparison)
Determine the initial subset of communities to include in the dashboard.
- Poll Red Hat stakeholders (Brian Stevens) for communities that are of particular strategic importance, and ensure that EKG is tracking them.
- Create a subset of Fedora communities that Community Architecture has engaged with over the past year, or that we consider of specific importance to the overall health of Fedora. Make sure that EKG is tracking them.
Conduct a time-based analysis of these communities, looking back as far as possible.
- New action items will fall out of this analysis.
- In the case that certain communities that have been identified as strategic appear that they could use some community-building assistance, reach out to the leadership of those communities. Begin a constructive (not critical) conversation, and see if they are interested in working with us.
- When we discover thriving communities that we have not previously engaged with directly, speak to their leaders and perhaps learn some new tricks, and build relationships.
It is critical to recognize that the end state of every community is not the same, and therefore the engagement model is not necessarily the same for each community. It is also worth noting that some communities will neither need nor want to work with the Community Architecture team.
- Track everything that a person has done within a project (emails, commits, irc logs, wiki edits, etc.)
- Leverage index (discussing resource allocation, tends to be more quantitative)
- Effectiveness index (getting stuff done, tends to be more qualitative)
- Associated with other timeline events (releases) and over one year.
- Where are contributions coming from? (domains)
- How many contributions are being made? (numbers)
- Is the community happy? (face)
- Welcoming to exclusionary.
- Is the community productive? (face)
- Social to effectual.
- Newbies versus old-timers in the community.
- What is the rate of change of contributions over time?
- How large is the (active) community?
- How easy is it to join the community?
- What is the barrier to making an initial contribution?
- Are community members in places of leadership?
- Are community members distinguishing themselves as potential Red Hat
- Are community members distinguishing themselves as potential hires for us/customers/partners?
- Are community members coming from customers/partners?
- Does the community have an opportunity to meet in person?
- Is someone tasked with addressing the community's concerns?
- Does the community have a public roadmap with milestones?
- How often does the community meet its milestones?
- Does the community have public discussions?
- How easy is it to get a product/project installed?
- Number of bugs submitted by email@example.com
- Bugs addressed by firstname.lastname@example.org (comments, etc.)
- Who logs the bug, who fixes, who closes
- How many users does something have?
- Fedora yum connection tracking
- Fedora MirrorManager
- Fedora downloaded package count
- Size of a project's IRC channel and mailing lists.
- @redhat.com vs. email@example.com breakdown on IRC and mailing lists.
- New wiki pages from firstname.lastname@example.org
- Wiki pages edited by email@example.com
- Number of commits from firstname.lastname@example.org
- Total commits to the project.