On Tue, Nov 15, 2011 at 11:00 AM, Robert Knight <[email protected]> wrote: >> The other thing to make it easier to incorporate experimental >> features is just to make sure to document use cases and requirements, >> so that we leave room for other solutions to the same problems > > Indeed, preferably in the same place that code changes and issues are > tracked.
Just to clarify, are you suggesting these get tracked at the main csl github project? And to be really clear, I'm almost going so far as to suggest a common template for feature requests going forward; in Markdown: # Use Cases [insert examples of what people need to be able to do that they cannot now, in the most clear way possible] # Requirements [deriving some higher-level processing principles that allows us to quickly understand the different design issues and tradeoffs] # Proposal [Not sure, but in some cases this might come in the form of a schema patch] I think too many of the issues in the tracker result in long threads, and hence, wasted time. Bruce ------------------------------------------------------------------------------ RSA(R) Conference 2012 Save $700 by Nov 18 Register now http://p.sf.net/sfu/rsa-sfdev2dev1 _______________________________________________ xbiblio-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/xbiblio-devel
