Differences between revisions 49 and 50

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. RFCs should be open for public comment for at least one week, and should provide a clear mechanism for adding comments.

Add a comment about this idea: ["/RFC_Comment"]

-  ← Revision 49 as of 2005-12-05 19:36:46 →
  Size: 1392
  Editor: mskresolve-b
  Comment:
+  ← Revision 50 as of 2005-12-05 19:37:38 →
  Size: 1450
  Editor: mskresolve-b
  Comment:
-Deletions are marked like this.
+Additions are marked like this.
 Line 39:
-Once posted to the wiki, the RFC owner should announce it via the cytostaff emailing list, and provide a specific deadline for public discussion.  RFCs should be open for public comment for at least one week.
+Once posted to the wiki, the RFC owner should announce it via the cytostaff emailing list, and provide a specific deadline for public discussion.  RFCs should be open for public comment for at least one week, and should provide a clear mechanism for adding comments.