On Tue, Jun 14, 2011 at 7:49 PM, Bruce D'Arcus <[email protected]> wrote:
> Another issue we need feedback on (though I think Rintze might explain
> a bit more the rationale):
>
> <https://github.com/citation-style-language/schema/issues/53>
>
> My argument is for these sorts of changes, we really need to get
> consensus from the entire implementer community.
>
So basically the question is how we want to organize the process of
designing new CSL features and making modifications to the language.
One of the drawbacks of the existing CSL development workflow is that it's
rather scattered. There is the xbiblio mailing list at SourceForge, several
active repos at GitHub (and inactive archive repos at SourceForge and
Bitbucket), the Zotero forums and the zotero-dev mailing list.
I know that Bruce and Frank follow mostly everything, but it's a lot to keep
up with for outsiders. I was thinking that maybe I should be a bit more
aggressive with committing changes, prepare a changelog before a planned
release (we would need one anyway to document the changes for CSL style
authors and implementors), announce plans for release and have a few weeks
for reflection, and, after polishing things up based on feedback and
dropping problematic proposals, make a release.
Alternatively we could use our original approach of vetting issues
one-at-a-time. But this has proven to be rather slow as it's difficult to
keep everybody's attention to prolonged periods of time.
Rintze
------------------------------------------------------------------------------
EditLive Enterprise is the world's most technically advanced content
authoring tool. Experience the power of Track Changes, Inline Image
Editing and ensure content is compliant with Accessibility Checking.
http://p.sf.net/sfu/ephox-dev2dev
_______________________________________________
xbiblio-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/xbiblio-devel
