caGrid Community Projects Process

The Community Project process involves the efforts of the caGrid Knowledge Center and the development team of the contributed component. There are several required steps to prepare a project for inclusion. However, we have created the process to allow both new and established projects to use existing infrastructure and migrate to Community Project infrastructure as needed.

This page is a synopsis of the caGrid Community Projects Governance document.

Development Teams wishing to propose a new Community Project must initiate the process by performing the following steps:

Download the caGrid Community Projects Governance document.
Download the Community Project Proposal document.
Follow the instructions in the Governance document to complete the Project Proposal document.
Email the completed Project Proposal to knowledge@osu-citih.org

Process Diagram

Process Overview

In order to establish a project, the Project Owner must submit a project proposal so that the Knowledge Center can work with the project owner to establish necessary project resources.

Project Proposal (Project Owner)
1. Download the Community Project Proposal document.
2. Complete the requested background and documentation.
3. Complete self-assessment of current state of compliance with Community Projects best practices.
4. Provide Project Infrastructure Requirements.
5. If project will use Community Projects repository
  1. Create repository accounts
  2. Request commit permissions
6. Submit Proposal to caGrid Knowledge Center via email at knowledge@osu-citih.org.
Project Proposal Review (KC)
1. Archival of Proposal documents.
2. Work with Project Owner to clarify Proposal, if needed.
3. Verify projects infrastructure requirements.
Project Inception
1. The Knowledge Center will perform actions based upon the information provided in the finalized Project Proposal (KC)
  1. (Optional) Create caGrid.org Wiki account for Project Owner and Committer(s).
  2. (Optional) Create private cagrid.org WIKI space for Project using the project "key" and project name provided in the proposal.
  3. (Optional) Approve committer access to the Community Projects repository.
  4. Generate a "Welcome Kit" containing instructions for steps to complete inception of the project based upon information provided in the Project Proposal and email to the Project team.
2. Project Team will receive a "Welcome Kit" with next steps based upon the information that was provided in the Project Proposal. The kit will specify steps from the following list.
  1. Create publicly available project documentation on cagrid.org WIKI or separate location. (Project Owner and Committer(s))
  2. (Optional) If using the Community Projects repository, extract the Community Projects example zip and setup for code within this template. This will allow the Community Projects master build to build your project.
  3. Commit of project code to Community Projects SVN or other publicly accessible source code repository.
  4. Verify Access to the caGrid Knowledge Center Forums.
  5. Email caGrid Knowledge Center at knowledge@osu-citih.org to inform them that you have completed the Welcome Kit.
3. Upon receipt of notification that the Project Team has completed the Welcome Kit the following steps will be performed (KC)
  1. Review the project WIKI space.
  2. (Optional) Create project specific forum for project.
  3. (Optional) Set public access to cagrid.org WIKI space.
  4. Update KC and cagrid.org WIKI Community Project list to include links to the newly public project.
  5. Announce new project to caGrid Users mailing list, caGrid.org, and KC wiki.
  6. Schedule Project Owner to present the project on the next available caGrid Users Community conference call.
Active Community Projects
1. Support community by answering user questions and fixing reported bugs. (Project Owner)
2. Complete self-assessment of current state of compliance with Community Projects best practices. Recommended at each new version of the project. (Project Owner)
3. Contact Project Owner periodically to ensure that the Community Projects process and infrastructure are meeting their needs. Verify that the posted documentation is in sync with the project code. (KC)
4. Verify that Forum questions are being answered in a timely manner. (KC)