From Fedora Project Wiki

Line 1: Line 1:
 
[[Category:Community Architecture]]
 
[[Category:Community Architecture]]
  
== Bugzilla ==
+
Is the community diverse and passionate?
 +
* Where are contributions coming from?
 +
* How many contributions are being made?
 +
* Does the community have an opportunity to meet in person?
 +
* Is someone tasked with addressing the community's concerns?
  
* Number of bugs submitted by not-@redhat.com  
+
What is the progress compared to investment?
 +
* Does the community have a public roadmap?
 +
* Does the community have public meetings?
 +
* How quickly is the community achieving its stated goals?
 +
* How much “leveraged engineering value” is the community providing?
 +
 
 +
Is community participation and leadership growing?
 +
* 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
 +
hires?
 +
 
 +
BUG TRACKING
 +
* Number of bugs submitted by not-@redhat.com
 
* Bugs addressed by non-@redhat.com (comments, etc.)
 
* Bugs addressed by non-@redhat.com (comments, etc.)
 
* Who logs the bug, who fixes, who closes
 
* Who logs the bug, who fixes, who closes
  
== Downloads ==
+
DOWNLOADS
  
* Smart scripts
+
* Integrate Sacha's JBoss metrics
 +
* Fedora yum connection tracking
 
* Fedora MirrorManager
 
* Fedora MirrorManager
* Fedora downloaded package count -- why are we not even asking Fedora mirrors for this info, even in aggregate?
+
* Fedora downloaded package count
 
 
== IRC ==
 
 
 
* Number of IRC channel users who are non-Red Hat Employees
 
* % of chat not-@redhat.com
 
  
== Mailing Lists ==
+
COMMUNICATION
  
* Number of emails to *-devel by not-@redhat.com
+
* Size of a project's IRC channel and mailing lists.
* Number of emails to *-users by not-@redhat.com
+
* @redhat.com vs. non-@redhat.com breakdown on IRC and mailing lists.
  
== Wiki ==
+
COMMITS
  
* New pages from non-@redhat.com
+
* New wiki pages from non-@redhat.com
* Pages edited by non-@redhat.com
+
* Wiki pages edited by non-@redhat.com
 +
* Number of commits from non-@redhat.com
 +
* Total commits to the project.

Revision as of 12:58, 23 February 2009


Is the community diverse and passionate?

  • Where are contributions coming from?
  • How many contributions are being made?
  • Does the community have an opportunity to meet in person?
  • Is someone tasked with addressing the community's concerns?

What is the progress compared to investment?

  • Does the community have a public roadmap?
  • Does the community have public meetings?
  • How quickly is the community achieving its stated goals?
  • How much “leveraged engineering value” is the community providing?

Is community participation and leadership growing?

  • 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

hires?

BUG TRACKING

  • Number of bugs submitted by not-@redhat.com
  • Bugs addressed by non-@redhat.com (comments, etc.)
  • Who logs the bug, who fixes, who closes

DOWNLOADS

  • Integrate Sacha's JBoss metrics
  • Fedora yum connection tracking
  • Fedora MirrorManager
  • Fedora downloaded package count

COMMUNICATION

  • Size of a project's IRC channel and mailing lists.
  • @redhat.com vs. non-@redhat.com breakdown on IRC and mailing lists.

COMMITS

  • New wiki pages from non-@redhat.com
  • Wiki pages edited by non-@redhat.com
  • Number of commits from non-@redhat.com
  • Total commits to the project.