On Mar 31, 2013, at 3:57 AM, Rintze Zelle wrote:

> On Wed, Mar 27, 2013 at 11:37 PM, Rintze Zelle <[email protected]> wrote:
>> Going forward, I would like to become a bit more strict about the
>> dependent styles that go into the repository. I plan to write an
>> extension to the CSL schema so that we can use Travis CI to check for
>> additional requirements. I would like to require each dependent style
>> to have a default-locale (possible exceptions for multilingual
>> styles), a documentation link, and a self link. I also would like to
>> disallow having two (or more) instances of cs:issn, since generally
>> one should be a cs:eissn.
> 
> I added "csl-repository.csl" to the schema repository
> (https://github.com/citation-style-language/schema/blob/master/csl-repository.rnc).
> It can be called instead of csl.rnc. It is dependent on the normal
> schema, but changes a few things. So far, it:
> 
> - forbids more than one cs:issn element
> - forbids some attributes on cs:style in dependent styles ("class",
> global options, and inheritable name options)
> - forbids affixes on cs:et-al ("prefix" and "suffix")
> - requires cs:rights, set as <rights
> license="http://creativecommons.org/licenses/by-sa/3.0/";>This work is
> licensed under a Creative Commons Attribution-ShareAlike 3.0
> License</rights>
> - requires at least one cs:link element.

Why don't we just add the requirements (as well as those you mentioned below: 
ordering, self-link etc.) to the tests? We can add a description and a link to 
the schema to the Readme stating these as mandatory requirements for 
pull-requests. GitHub will send each pull request and subsequent changes to 
Travis-CI. We could even go further, by adding a Hook that auto-responds to bad 
pull requests with a message reiterating the rules or something along those 
lines.

I have committed to many open source projects and typically, the more 
established they are, the more burden is placed on the person making the 
commit/pull request. Ideally, it should not be necessary for you (or other 
maintainers) to have to respond to every pull request that leaves a style in a 
bad shape, but only review those which pass all the repository rules.

If I remember correctly, the tests validate each style against the schema; if 
you can express the conditions, I can adapt some styles to be validated against 
the new schema, as well.

Sylvester


------------------------------------------------------------------------------
Own the Future-Intel(R) Level Up Game Demo Contest 2013
Rise to greatness in Intel's independent game demo contest. Compete 
for recognition, cash, and the chance to get your game on Steam. 
$5K grand prize plus 10 genre and skill prizes. Submit your demo 
by 6/6/13. http://altfarm.mediaplex.com/ad/ck/12124-176961-30367-2
_______________________________________________
xbiblio-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/xbiblio-devel

Reply via email to