The Sakai Community Practice Work Group: Progress Statement - PowerPoint PPT Presentation

the sakai community practice work group progress statement n.
Skip this Video
Loading SlideShow in 5 Seconds..
The Sakai Community Practice Work Group: Progress Statement PowerPoint Presentation
Download Presentation
The Sakai Community Practice Work Group: Progress Statement

play fullscreen
1 / 20
The Sakai Community Practice Work Group: Progress Statement
Download Presentation
Download Presentation

The Sakai Community Practice Work Group: Progress Statement

- - - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript

  1. The Sakai Community Practice Work Group:Progress Statement Mark J. Norton, Chairman

  2. Formed in Dec. of 2005 to document Sakai Community practices at the request of the Sakai Board of Directors. Originally co-chaired by Chris Coppola and Mara Hancock. First project was a group charter. SCP Formation

  3. Members Mark Norton –chairman. Chris Coppola Mara HancockAnthony Whyte Charles Severance Peter KnoopTom LewisClay FenlasonDuff GillmanRuth Sabean

  4. A permanent working group that serves the Sakai community by collecting and documenting it’s processes. While it may author some of these, the group encourages people who are currently managing a process to submit it for approval and wider distribution. Definition

  5. Coordinate the development, documentation, communication, and maintenance of a consistent set of community practices. Minimize the barrier to community participation. Maximize the effectiveness of our community Objectives

  6. Specific Practical matters of day to day work. Consistent Allows people to participate more easily. Transparent Clearly communicated and easy to find. Document Characteristics More …

  7. Maintained Evolve as the community evolves. Comprehensive Describe all areas of the work. Sustainable SCP is committed to sustaining the community practices. More Characteristics

  8. Process

  9. Proposals can come from several places and be in many forms: Suggested by the community Documentation submitted by a stakeholder Descriptions from a work group leader Revisions to existing practices Proposals

  10. The proposal is used to create a draft practice document. SCP document templates exist for Word and Confluence. Draft is worked for consistency and clarity. Where possible, this work is done in close cooperation with the proposal author. Draft Created

  11. Proposed practice is distributed widely through out the Sakai community for comments and feedback. Typically, a two week comment period is used, longer for more complex documents. All comments are reviewed and addressed by the SCP-WG and the proposal author. Public Comment

  12. Finished practices are submitted to the Sakai BOD for final approval. This is done in to be inclusive of their direction and leadership and to make sure that any legal issues are considered. Approval doesn’t require a BOD meeting Approval is assumed unless there is an objection by a BOD member. Final Approval

  13. SCP documents will be published on the project website ( PDF formatted documents allow easy viewing on-line and clean prints to be made. SCP documents are numbered consecutively as they are approved. Publishing

  14. Four Documents have been finished: 001: License Management 002: Criteria for Provisional Status * 003: Sakai Software Organization * 004: Group Management Process * Work Status * Waiting on BOD approval.

  15. Educational Community License Our distribution license. Contribution Agreements All contributors must agree to Sakai IP. Using code from third party releases Allows code to be used with permission and allow original party to retain rights. License Management SCP-001

  16. Defines provisional status for tools in Sakai. These are distributed, but hidden. Allows new tools to be tested in production without fully recommending them. Describes technical, design, documentation and desired elements. Criteria for Provisional Status SCP-002

  17. Describes how Sakai software is developed and released. Defines roles in the process. Code committers control the process. People become committers based on the merits of their contributions to the project. Creating projects and how to join them. Software Organization SCP-003

  18. Defines Sakai working groups. How to create and run them. Guiding principles. Intended to be compatible with the Sakai Software Organization practice. Group Management Process SCP-004

  19. The following documents are still being developed at this time: Sakai Requirements Process Sakai Fellow Selection Process Documents in Progress

  20. Submit proposals for Sakai processes that should be documented. Read and use the published practice documents. Please respond to request for comments – this is your say into how Sakai runs! Call to Action