10 tips on how to prevent business value risk
One category of risk that project teams need to ensure they address is business value failure – delivering a product that fails to provide value for the business investor.
The content has been bookmarked!
There was an error bookmarking this content! Please retry.
How would you like to view the presentation?
Fair Trade Software Licensing - A Guide to Neo4j Licensing Options
Getting Started with Stratos - an Open Source Cloud Platform
Agile Practices to Improve Project Management Organization (PMO) Effectiveness
They are aware that GPL forces the users of the package to also GPL their product, and so ... you need to provide a dual license model if you want to get any users that wouldn't want to publish their code ? And I'm pretty sure that this is the case with a very big percent of the users.
IANAL, but AFAIK the GPL doesn't force you to give your source code to your client, unless you deliver binaries to them. Ie. if you only create a website, or your service is exposed trough HTTP (HTTPS hopefully), you don't need to give your clients the source code. This is true for both GPLv2 and GPLv3.
There is a variation of the GPL called the AGPL (AGPLv2 and AGPLv3 more precisely), which does make it obligatory to deliver source code, even if you only expose your software trough a network service, but it is not as widely used as GPL.
There is another similar project called Apache Cassandra. Its still in the incubator. It offers the same BigTable like data model and uses the same Eventually Consistent model from Amazon's Dynamo. It is Apache licensed, which makes life much simpler for most people consuming it.
Here is a presentation from OSCON by Jonathan Ellis:
bit.ly/1tujuf
Paul
One category of risk that project teams need to ensure they address is business value failure – delivering a product that fails to provide value for the business investor.
InfoQ spoke to the authors of Software Systems Architecture on a couple of new topics, the System Context viewpoint and Agile, which have been added to the second edition.
Alex Papadimoulis discusses ugly code, where it comes from, how to avoid it, and how to get rid of it.
John Davies examines Visa’s architecture and shows how enterprises have architected complex integrations incorporating Hadoop, memcached, Ruby on Rails, and others to deliver innovative solutions.
Sean Comerford unveils ESPN.com’s architecture, what components are used and why, and the current changes the website goes through.
Are there repeated patterns of failure on Enterprise Agile Enablement efforts? Sanjiv and Arlen discuss Seven Deadly Sins to avoid when adopting Agile in an enterprise.
Erik Dörnenburg answers: What is Enterprise and Evolutionary Architecture?, discussing 4 issues: Turning strategy into execution, Ensuring conformance, Where do the architects sit? Buying or building?
Sean Cribbs explains what Map-Reduce and Riak are, why and how to use Map-Reduce with Riak, and how to convert SQL queries into their Map-Reduce equivalents.
3 comments
Watch Thread Reply