The Practical cloud computing proposal is starting to gain momentum, given the number of followers.
There's bound to be discussions around the scope of such a site, so let's get things going...
There have previously been proposals for vendor-specific cloud sites:
- AWS: Proposed Q&A site for Developers, IT Professionals and Enterprise/Solution/Domain Architects working on the Amazon Web Services (AWS) Cloud platform
- Azure: Proposed Q&A site for developers , IT Pro's, Enterprise/Solution/Domain Architects, DevOps working on the Azure Cloud platform
While each of these could gain sufficient support individually, there are some benefits to having a multi-technology "Cloud Computing" site:
- The various clouds (AWS, Azure, Eucalyptus, OpenStack, Apache CloudStack, Joyent) have many similarities
- Participants may be able to answer questions across multiple technologies, thus building up their reputation rather than spreading it across multiple sites
- The site will attract more activity, making it easier to pass hurdles for new StackExchange sites
- The StackExchange overlords will have a larger pool of participants to attract advertising, thus increasing longevity of the site
- Participants might ask multi-cloud questions (eg "Which cloud technology can do this?") that would normally be out-of-scope for a single technology, but would be in-scope for a general Cloud Computing site
While I'm pretty active on StackOverflow answering AWS questions, I can see the benefit of having a wider Cloud Computing site, even if only for concentrating reputation on fewer sites. Given appropriate use of tags, I don't see a problem with combining technologies -- it happens already on StackOverflow.
So, some questions:
- Do any followers of this proposal have any problem with it being a multi-technology / multi-vendor site?
- Are there any clarifications we should add to the Scope to help differentiate it from other sites (eg StackOverflow, UserFault, SuperUser)?
- Is there enough general understanding around the term "Cloud Computing" to consider it to be a sufficient scope definition, or do we need a better definition to define the extent of the site?
- Would it also be a venue to discuss third-party solutions (eg RightScale, Cloudberry products, Orbitera) that manage cloud resources or work in-conjunction with cloud services?