50,000 Foot Overview This article describes the source code management and deployment process for SharePoint 2010 initaitives and provides the current-state of SharePoint 2007 deployment analysis as well as listing the various options and associated best practices for SharePoint 2010
no search term matches found in comments.
Well pretty much for the same reasons that competing companies use the same open source frameworks: because you can cut development costs and benefit from a widely used code base. One of the best examples of commercial companies competing on products but using the same code base is the WebKit project
Traditionally, the largest area of contribution has been developers writing and contributing code...Again, this has worked well for open-source infrastructure where technology is coded for developers, by developers
With open code, anybody can become a reviewer, suggest improvements, find bugs, contribute documentation or even fork it to build something different or better
I am particularly excited as companies start to make the transition to take these applications and deploy them in the Cloud
It is also getting much easier to maintenance and deploy new versions of enterprise software, which makes it possible for in-house solutions to stay up to date with the latest technologies and features (such as mobile access)
Again, it makes a lot of sense to share code at the infrastructure level, since competition may still happen at the higher levels of the software, while the infrastructure code may be expensive to maintain on your own
Is it possible to have an Enterprise 2.0 deployment in a small company?
As coders, bug reporters, beta testers, translators or proofreaders