← Revision 46 as of 2005-12-05 19:30:44
1237
Comment:
|
← Revision 47 as of 2005-12-05 19:32:12 →
1265
|
Deletions are marked like this. | Additions are marked like this. |
Line 27: | Line 27: |
== 1. Adopt a Formal RFC Process for Each New Feature in Cytoscape 2.3 == | == 1. Adopt a Formal RFC Process for Each New Feature / Refactoring in Cytoscape 2.3 == |
Line 29: | Line 29: |
Each new feature slated for Cytoscape 2.3 will go through a public review process via an RFC posted to the Cytoscape Wiki. | Each new feature / refactoring slated for Cytoscape 2.3 will go through a public review process via an RFC posted to the Cytoscape Wiki. |
About this Document
This is an official Request for Comment (RFC) for "improving the quality of the Cytoscape 2.3 release."
RFC 2 is divided in three parts:
- Part I consists of Ethan's interviews with six Cytoscapers (Trey, Gary, Ben, Allan, Aditya, and Rowan).
- Part II consists of ideas generated at the 2005 Cytoscape retreat.
- Part III consists of final, concreate ideas, which are being proposed to the Cytoscape group.
Status
This document is under construction.
Part I: The Interviews
["/Part 1"]
Part II: Results from 2005 Cytoscape Retreat
["/Part 2"]
Part III: Final Proposals
1. Adopt a Formal RFC Process for Each New Feature / Refactoring in Cytoscape 2.3
Each new feature / refactoring slated for Cytoscape 2.3 will go through a public review process via an RFC posted to the Cytoscape Wiki.
["RFC_1"] will serve as a starting template for all RFCs.
Depending on the feature, the RFC should include the following:
- Use case addressed.
- Proposed user interface.
- Proposed API.
Once posted to the wiki, the RFC owner should announce it via the cytostaff emailing list, and provide a specific deadline for public discussion.