Difference between revisions of "Philosophy"

m
Line 34: Line 34:
 
ImageJ subscribes to the [https://en.wikipedia.org/wiki/Release_early,_release_often release early, release often] mantra often cited in software engineering circles. In particular—and especially because there is a small core development team—the project is driven by [http://blog.codinghorror.com/boyds-law-of-iteration/ Boyd's Law of Iteration]: '''speed of iteration beats quality of iteration'''. That is not to say that we do not strive for quality—we do. But we have found through experience that more releases, together with guiding user feedback, push a project forward more efficiently than a slower release cycle does.
 
ImageJ subscribes to the [https://en.wikipedia.org/wiki/Release_early,_release_often release early, release often] mantra often cited in software engineering circles. In particular—and especially because there is a small core development team—the project is driven by [http://blog.codinghorror.com/boyds-law-of-iteration/ Boyd's Law of Iteration]: '''speed of iteration beats quality of iteration'''. That is not to say that we do not strive for quality—we do. But we have found through experience that more releases, together with guiding user feedback, push a project forward more efficiently than a slower release cycle does.
  
To ensure releases can happen quickly, the SciJava components strive for [[reproducible builds]] with a "release ready" <code>master</code> branch. This allows individual SciJava components to be released with the [[Architecture#Jenkins|push of a button]], in a ''timespan less than a five minutes''. This puts bug-fixes into the hands of users as quickly as possible.  
+
To ensure releases can happen quickly, the SciJava components strive for [[reproducible builds]] with a "release ready" <code>master</code> branch. This allows individual SciJava components to be released with the [[Architecture#Jenkins|push of a button]], in a ''timespan less than five minutes''. This puts bug-fixes into the hands of users as quickly as possible.  
  
 
== Do it in public ==
 
== Do it in public ==
  
 
ImageJ and SciJava are not [[open source]] software ''products''—they are [[open source]] software ''projects'' following an [[open source]] development ''process''. ImageJ is funded by taxpayer money, so the project strives to be as transparent as possible, by [http://blog.codinghorror.com/how-to-stop-sucking-and-be-awesome-instead/ doing it in public]!
 
ImageJ and SciJava are not [[open source]] software ''products''—they are [[open source]] software ''projects'' following an [[open source]] development ''process''. ImageJ is funded by taxpayer money, so the project strives to be as transparent as possible, by [http://blog.codinghorror.com/how-to-stop-sucking-and-be-awesome-instead/ doing it in public]!

Revision as of 14:15, 28 October 2014

Template:DevelopmentImageJ, and the SciJava software stack in general, is developed according to certain biases, which we describe here. This philosophy has evolved over a very long development history, reflecting many lessons learned over a course of decades.Template:Sidebox== Release early, release often ==

ImageJ subscribes to the release early, release often mantra often cited in software engineering circles. In particular—and especially because there is a small core development team—the project is driven by Boyd's Law of Iteration: speed of iteration beats quality of iteration. That is not to say that we do not strive for quality—we do. But we have found through experience that more releases, together with guiding user feedback, push a project forward more efficiently than a slower release cycle does.

To ensure releases can happen quickly, the SciJava components strive for reproducible builds with a "release ready" master branch. This allows individual SciJava components to be released with the push of a button, in a timespan less than five minutes. This puts bug-fixes into the hands of users as quickly as possible.

Do it in public

ImageJ and SciJava are not open source software products—they are open source software projects following an open source development process. ImageJ is funded by taxpayer money, so the project strives to be as transparent as possible, by doing it in public!