Project

Summary

Activity Overview

Four categories of data are collected. Shown here is the state of the project in each of the categories as of Sept. 11, 2017.

  • Infrastructure (score: , weight: )
    • Does it have a website? (score: , weight: )
    • Does it have a mailing list? (score: , weight: )
    • Does it have a project definition statement on website? (score: , weight: )
    • Does it not need a contributor licensing statement or agreement? (score: , weight: )
    • Does it have an OSI approved open source license? (score: , weight: )
    • Does it have a bugzilla/bug tracking system? (score: , weight: )
    • Does it have a governance model identified on the website? (score: , weight: )
    • Does it have a source code repository like git/svn? (score: , weight: )
    • Does it have a project blog? (score: , weight: )
  • Activity (score: , weight: )
    • Release Activity (score: , weight: )
      • Age of most recent release (score: , weight: )
    • Commits Activity (score: , weight: )
      • Percentage of committers by dominant domain name (score: , weight: )
      • Percentage of commits by dominant domain name (score: , weight: )
      • Unique email address domains (score: , weight: )
      • Unique committers (score: , weight: )
    • Bug Reports Activity (score: , weight: )
      • Percentage of bug reporters by dominant domain name (score: , weight: )
      • Percentage of bug reports by dominant domain name (score: , weight: )
      • Unique bug reporter domains (score: , weight: )
    • Events and Meeting Activity (score: , weight: )
      • Events per month (score: , weight: )
      • Longest interval between events (score: , weight: )
    • Mailing Lists Activity (score: , weight: )
      • Percentage of mailing list posts by dominant domain name (score: , weight: )
      • Percentage of mailing list threads by dominant domain name (score: , weight: )
      • Unique email address domains (score: , weight: )
    • Blog Posts (score: , weight: )
      • Number of posts per month (score: , weight: )
      • Shortest interval between blog posts (score: , weight: )
      • Longest interval between blog posts (score: , weight: )
  • Code Quality (score: , weight: )
    • General Quality (score: , weight: )
      • Bugs per KLOC (score: , weight: )
      • Ratio of bugs opened to bugs closed (score: , weight: )
  • Publicity (score: , weight: )
    • Downloads (score: , weight: )
      • Download Frequency (score: , weight: )
    • Blogs (score: , weight: )
      • Number of posts per month (score: , weight: )
      • Shortest interval between blog posts (score: , weight: )
      • Longest interval between blog posts (score: , weight: )
    • Events (score: , weight: )
      • Events per month (score: , weight: )

Infrastructure

Metric datapoints: Back to top

Activity

Release Activity

Metric datapoints:
  • Age of most recent release: N/A

    Rule: New project releases within the last 6 months, Green, within the last 12 months, Yellow, beyond that Red.

Back to top

Commits Activity

Metric datapoints:
  • Percentage of committers by dominant domain name: 26.06%

    Rationale: If more than 50% of COMMITTERS are from one domain (via email ID) it is dominated by one set of people. Suggested target is to have it less than 35%.

  • Percentage of commits by dominant domain name: 53.65%

    Rule: If more than 50% of CODE COMMITS are from one domain (via email ID) it is dominated by one set of people. Suggested target is to have it less than 35%.

  • Unique email address domains: 78 domains

    How many unique domains are represented?

  • Unique committers: 168 committers

    How many UNIQUE COMMITERS are represented?

Number of commits over last:

  • 3 months: 0 commits from 0 contributors
  • 6 months: 99 commits from 7 contributors
  • 9 months: 263 commits from 19 contributors
  • 12 months: 490 commits from 25 contributors
  • 24 months: 1,110 commits from 56 contributors

Top email address domains committing:

Back to top

Bug Reports Activity

Metric datapoints:
  • Percentage of bug reporters by dominant domain name: 7.69%

    Rule: If more than 50% of BUG REPORTERS are from one domain (via email ID) it is dominated by one set of people. Suggested target is to have it less than 35%.

  • Percentage of bug reports by dominant domain name: 19.69%

    Rule: If more than 50% of BUG REPORTS are from one domain (via email ID) it is dominated by one set of people. Suggested target is to have it less than 35%.

  • Unique bug reporter domains: 28 domains

    How many unique domains are represented?

Top email address domains reporting bugs:

Back to top

Events and Meeting Activity

Metric datapoints:
  • Events per month: N/A

    Rationale: At least 2 meetings in person per month is preferred.

  • Longest interval between events: N/A

    Rationale: The interval of meeting should be less than 4 weeks.

Back to top

Mailing Lists Activity

Metric datapoints:
  • Percentage of mailing list posts by dominant domain name: 30.45%

    Rationale: If more than 50% of MAILING LIST POSTERS are from one domain (via email ID) it is dominated by one set of people. Suggested target is to have it less than 35%.

  • Percentage of mailing list threads by dominant domain name: 68.21%

    Rationale: If more than 50% of MAILING LIST POSTS are from one domain (via email ID) it is dominated by one set of people. Suggested target is to have it less than 35%.

  • Unique email address domains: 226 domains

    How many unique domains are represented?

Number of emails over last:

  • 3 months: 0 posts from 0 posters
  • 6 months: 170 posts from 6 posters
  • 9 months: 881 posts from 21 posters
  • 12 months: 1,244 posts from 30 posters
  • 24 months: 2,256 posts from 72 posters

Top email address domains posting:

Back to top

Blog Posts

Metric datapoints:
  • Number of posts per month: N/A

    Rationale: Posts by developers are indication of activity and at least 4 per month is good.

  • Shortest interval between blog posts: N/A

    Rationale: Weekly posts are preferred.

  • Longest interval between blog posts: N/A

    Rationale: At least one post per week is preferred.

Back to top

Code Quality

General Quality

Metric datapoints:
  • Bugs per KLOC: N/A

    Rationale: The lesser the number of bugs reported per 1 KLOC the better.

  • Ratio of bugs opened to bugs closed: 0.77

    Rationale: Fixing code/time indicates a level of developer focus and project activity score.

Reliability

  • Number of bugs reported over last:
    • 3 months: 0
    • 6 months: 21
    • 9 months: 109
    • 12 months: 169
    • 24 months: 265
  • Number of bugs closed over last:
    • 3 months: 0
    • 6 months: 12
    • 9 months: 88
    • 12 months: 123
    • 24 months: 198
  • Number of severe bugs reported over last:
    • 3 months: 0
    • 6 months: 0
    • 9 months: 0
    • 12 months: 0
    • 24 months: 0

Size:

  • Lines of code over last:
    • 3 months: 0
    • 6 months: 0
    • 9 months: 0
    • 12 months: 0
    • 24 months: 0
Back to top

Publicity

Downloads

Metric datapoints:
  • Download Frequency: N/A

    This could be zero depending on if the metric can be gathered.

Back to top

Blogs

Metric datapoints:
  • Number of posts per month: N/A

    Rationale: Posts by developers are indication of activity and at least 4 per month is good.

  • Shortest interval between blog posts: N/A

    Rationale: Weekly posts are preferred.

  • Longest interval between blog posts: N/A

    Rationale: At least one post per week is preferred.

Back to top

Events

Metric datapoints:
  • Events per month: N/A

    Rationale: At least 2 meetings in person per month is preferred.

Back to top

Downloads

Not currently determined

Back to top