Jump to: navigation, search

Difference between revisions of "How to request new APIs for eRCP"

(New page: # Create a bug report with enhancement severity with the proposed specification. Meaning the exact javadoc (which is something solid and community can comment ) # Send an email to dsdp-erc...)
 
 
Line 2: Line 2:
 
# Send an email to dsdp-ercp-dev mailing list with a link to the bug report and the needs, and clients(or use cases) for the new API.  
 
# Send an email to dsdp-ercp-dev mailing list with a link to the bug report and the needs, and clients(or use cases) for the new API.  
 
# We keep the new API proposal open for discussion at least 1 week. If in this period there are no objections to it and everyone is content with the new API, Our PMC member (Mark Rogalski) and  eRCP project lead( Gorkem Ercan) approves the inclusion of the new API in the bugzilla. If there are objections and community can not agree on the API we reject it.
 
# We keep the new API proposal open for discussion at least 1 week. If in this period there are no objections to it and everyone is content with the new API, Our PMC member (Mark Rogalski) and  eRCP project lead( Gorkem Ercan) approves the inclusion of the new API in the bugzilla. If there are objections and community can not agree on the API we reject it.
 +
[[Category:eRCP]]

Latest revision as of 11:26, 24 March 2008

  1. Create a bug report with enhancement severity with the proposed specification. Meaning the exact javadoc (which is something solid and community can comment )
  2. Send an email to dsdp-ercp-dev mailing list with a link to the bug report and the needs, and clients(or use cases) for the new API.
  3. We keep the new API proposal open for discussion at least 1 week. If in this period there are no objections to it and everyone is content with the new API, Our PMC member (Mark Rogalski) and eRCP project lead( Gorkem Ercan) approves the inclusion of the new API in the bugzilla. If there are objections and community can not agree on the API we reject it.