One of the goals of Apache Nuvem is to provide a API and then component implementations for different cloud providers. I'd like to suggest that we follow a pattern for components that we have identified as part of the Nuvem Cloud API, where we would have a top level jira that would describe the Service being supported, and sub-tasks that would help us identify that the proper API has been discussed and agreed upon and what cloud providers already have a implementation available :
- Support for Mail Services (main JIRA) - Define a common API (sub-task) (this is true even we are going to agree to use a well established standard) - Provide Mail services implementation for Standalone (sub-task) (this would be used when the cloud provider does not support the service) - Provide Mail Services implementation for GAE (sub-task) - Provide Mail Services implementation for EC2 (sub-task) - etc Thoughts ? -- Luciano Resende http://people.apache.org/~lresende http://twitter.com/lresende1975 http://lresende.blogspot.com/
