Skip to content

Ohcount4J Open Source Management Plan

Jump to bottom
William Cox edited this page Jun 23, 2016 · 1 revision

Purpose of this Plan

This document defines how the management team of the Ohcount4J Open Source project – the Ohcount4J Fab Five – will release, monitor, and maintain Ohcount4J as an Open Source Software (OSS) project.

The plan for releasing Ohcount4J as OSS is to complete this task by the end of January 2016.

Participants

The following are participants in the Ohcount4J OSS project. Order is alphabetical by last name.

Key Stakeholders

The member of the Ohcount4J Fab Five are:

Open Sourcing Plans

This section discusses how the Ohcount4J project will be released as OSS, how it will be monitored, how Pull Requests will be resolved, etc.

Supporting Ohcount4J

The following points are guidelines for how the Ohcount4J Fab Five will monitor and support the Ohcount4J OSS community.

  • Ohcount4J repository will be on GitHub
  • We will use GitHub Issues to track issues and defects.
    • Note that all existing JIRA tickets related to Ohcount4J language support or defects will be reproduced as a GitHub Issue.
    • Do we reproduce any feature requests? (Are there any?)
    • Fab Five responsible for monitoring GitHub Issues
  • Fab Five responsible for monitoring GitHub Pull Requests

Ohcount4J Languages

Adding New Languages to Ohcount4J

There are some 50 new languages that need to be added to Ohcount4J in order for it to support Open Hub. There are tickets in the Ohcount JIRA project. Support for these languages is not a blocker for OSS release.

Additionally, there are some 9 languages proposed as pull requests in Ohcount (https://github.com/blackducksoftware/ohcount/pulls). The authors need to be contacted about reproducing their work on Ohcount4j. It would be ideal if we could get them to reproduce their PR. However, it should not be surprising that, after over a year without contact, they are unenthusiastic about such a prospect. Especially if they are not as comfortable working in Java.

Resolving Ohcount4J Pull Requests

The following criteria will be used to assess any pull requests to Ohcount4J

  1. Is the language being proposed sufficiently important to be added to Ohcount4J
  2. Does the code being proposed actually perform the intended work?
  3. Is the code readable and maintainable?

Open Questions

  1. Add test suite to Ohcount4J repository
  2. Will one person act as a liason to the OSS community?
Clone this wiki locally