I like the idea of client-specific forks. In fact, I have styles that I could already host on such a fork, which require the PMID variable (and which for now, rely on a Papers2-specific CSL variable).
Forking could have been perceived as a bit aggressive, so I never really considered it (and to be honest, I don't think I ever realized it could be a nice way to handle the few edge cases like Papers2-specific styles). Now, there is one potential risk of further confusion for the end user: instead of just 1 repo, there are now a bunch of them. That will require to make it very clear what's going on. Though, to be honest, if the end user has to go on github to get a style, we already failed ;-) (and in fact, that's currently something that sometimes confuse the few brave souls that try to get a style from the web). All in all, I'd say the benefits outweigh the potential problems. Charles On Jun 6, 2012, at 9:12 AM, Bruce D'Arcus wrote: > Actually, an idea: > > On Wed, Jun 6, 2012 at 11:46 AM, Bruce D'Arcus <[email protected]> wrote: > > > Per Rintze's earlier comments, I think it ought to be possible. Maybe upon > > editing a style, for example, there's a "submit to public repository" link > > that has a small description field, and which creates a patch and pull > > request on the giithub repository? > > Each project has their own github fork of the main CSL styles repo. > > Users get styles from their respective forks, and if they edit and submit, > they do so to that fork, on branches. > > Project-specific maintainers merge those branches as they see fit, and issue > a pull request on the main csl repo. > > A script could automate this, so that the amount of work in curating the > edits is minor. > > Seem reasonable? > > If yes, then it ought to be a small step from what Steve has now to that, and > it shouldn't matter where the editor lives: in client apps, on the web, or > more likely, both. > > Right? > > Bruce > ------------------------------------------------------------------------------ > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. Discussions > will include endpoint security, mobile security and the latest in malware > threats. > http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/_______________________________________________ > xbiblio-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/xbiblio-devel -- Charles Parnot [email protected] twitter: @cparnot http://mekentosj.com ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ xbiblio-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/xbiblio-devel
