I've been prompted to think about CSL development process again, but two things:
1) Rintze issued a pull request and I accepted it too quickly. But what should be the proper process? What's the appropriate time-frame? How do we deal with dissent? Also, I think in general Rintze has been a little frustrated with the not-entirely fluid process. 2) some tension in the Sakai world around OAE development process, in which Ian Boston advocated for the Apache model So I looked at the Apache model: <https://blogs.apache.org/comdev/entry/how_apache_projects_use_consensus> ... and want to ask what we should do? I floated one idea (which is basically to use github pull requests + Apache model for spec or schema change proposals) here: <https://github.com/citation-style-language/documentation/pull/18#issuecomment-1493667> So in other words, pull requests require concrete proposals (though we have the problem they may be split across two projects, unfortunately), and the Apache process (essentially, any member has a veto right, and we have an explicit focus on consensus) makes sure we're on the same page. Bruce ------------------------------------------------------------------------------ All of the data generated in your IT infrastructure is seriously valuable. Why? It contains a definitive record of application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-d2d-c2 _______________________________________________ xbiblio-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/xbiblio-devel
