Project process

This section of the site describes the various roles and actions around the OVP project.

Current project committee members

  • Will Law:  Developer/Committer/Administrator (Flash)
  • Charles Newman:  Developer/Committer/Administrator (Flash)
  • Nick Brookins:  Developer/Committer/Administrator (Silverlight, HTML5)
  • James Mutton:  Developer/Committer/Administrator (Silverlight, HTML5)
  • Pankaj Chaudhari:  Developer/Committer (Silverlight)
  • Tommy Petrovic:  Developer/Committer (iPhone)
  • Adam Greenbaum:  Administrator

Roles

OVP participation is categorized into one of several roles. The roles and responsibilities are defined below.

User
An individual using OVP for player deployment. Users have access to the configuration tool, player, and documentation, and may identify bugs, request feature enhancements, and open and contribute to discussions on the forums.

Developer
An individual using OVP for player development and deployment. Developers have access to source code and documentation, and may identify bugs, request feature enhancements, and open and contribute to discussions on the forums. Developers may also contribute documentation and source code. For more information on making contributions, please refer to the submission process described in this section.

Committer
An individual that reviews code contributions to ensure that it conforms to the overall OVP project vision. Committers demonstrate a continued dedication to the project, including frequent contributions to the project as a Developer. For more information on becoming a Committer for OVP, please refer to the role nomination process described in this section.

Administrator
An individual that monitors the OVP project and acts as a final authority in making decisions. For more information on becoming an Administrator for OVP, please refer to the role nomination process described in this section.

Submissions

Feature Requests
Participants in any role may submit feature enhancements. OVP currently uses the Feature Requests tracker on SourceForge for all communication around features. You can access it here. Please be thorough when submitting feature requests. You are required to include details about “what” and “why” as well as which format of OVP.

Feature requests require unanimous approval from the Project Committee (Committers and Administrators), and can be influenced by Developers. For more information on the approval process for OVP, please refer to ‘Approvals and appeals’ section.

Bugs
Participants in any role may submit bug reports. OVP currently uses the Bug tracker on SourceForge. You can access it here.

Please be thorough when submitting bugs. A bug must be an issue that can be reproduced and it is ideal to include information about your operating system, browser, and computer as well as OVP specifics such as format and version.

Code contributions (Patches)
Only Developers may contribute code. OVP currently uses the Bug tracker on SourceForge. You can access it here.

Please be thorough when submitting code. You should provide at a minimum:

  • A description of what problem the contribution solves
  • Modification to existing files in the form of a diff (svn diff)
  • Unit tests for any code
  • Documentation changes for any new or modified behavior

All submissions will be confirmed.  Submissions that are added will include recognition of the contributor as an author and include a message of appreciation for the submission.

Role nominating and revoking

Committers
Any Committer may nominate a Developer to receive Committer status. Approval of a nominee is accomplished by the Project Committee, must be unanimous, and follows the process as that for the inclusion of a feature request. Appeals are not allowed but a Committer may re-nominate a Developer.

Committers can have their status revoked. If a Committer does not contribute actively and positively to the project, then any Committer or Administrator may recommend to the Project Committee to revoke commit privileges. Revoking is accomplished by the Project Committee, must be unanimous, and follows the process as that for the inclusion of a feature request, and a response will include reasoning. Revoking should only be considered in extreme situations.

Administrators
Any Administrator may nominate any Committer to receive Administrator status. A unanimous decision is required by the OVP Project Committee to grant Administrative privileges.

Approvals and appeals

Approvals
An approval includes decisions from each individual as follows:

  • Yes. Indicates a desire for the request to be implemented and will help with the implementation.
  • None. Indicates a waive of rights to contribute to the approval decision.
  • No. Indicates a desire for the request to be denied, with an explanation of why included.

Appeals
Appeals are welcome by any individual and will be handled by the Project Committee. All decisions during the approval process will be considered, as well as consideration for the overall vision of the OVP project. A reply to the appeal will be provided including a reason is final.