COIN-OR: Open-source software for Operations Research


		<trim>
		Documentation
		- Tends to be nonexistent, sparse and embedded in the code.
		- Repository is for other people that like to code, not read about code...not newbies.
		- Most other OS s/w early is of this nature.
		- Community sees values as code, not documentation.
		- It’s as good as the community provides – improve it! Sample programs, sleazy tricks using CLP, etc.
		Ease of Use
		- not for novices. typically not even for window users.
		- people like Frontline come along and make it easy.
		Recognition
		- OR/Math community doesn't yet have a way to evaluate and recognize contributions to os, as in the T&P process. In some communities (e.g., CS) they've been thinking about this.
		Testing
		- Testing is the writers responsibility.
		- Provide mechanism they release, and testing modification by others.
		- Not a way we as a community think (or are trained).
		Intellectual Property
		- What are you giving away? There's a sense that something may have monetary value and you're reducing it.
		- Most people over estimate monetary value in this case.
		- There's a heck of a lot of work to market.
		- The original author can re-license.
		- The money is in the consulting and application space, not in the solver software.
		Maintenance
		- Order of magnitude work to maintain than to create.
		- Design for maintainable is different than a one-off for a research paper.