Hi Charles, On Tue, Dec 20, 2011 at 2:53 AM, Charles Parnot <[email protected]> wrote: > > Hi everybody, > > Finally! I am sorry it took so long, but here is a more official email > introducing Mekentosj, Papers and myself to the CSL developer community. I > will assume this is the right mailing list / outlet to do that, but let me > know if that's not the case.
This is the right place. Welcome. ... > Note that in Papers 2.1, we introduced some Papers2-specific CSL variables to > deal with some user requests. Inspired by CSS and vendor-specific extensions, > I prefixed those variables with 'papers2_', and thus named those > `papers2_pmid`, `papers2_pmcid` and `papers2_notes`. They are quite > self-explanatory. Please let me know if you have any questions, or comments > on that. We certainly don't want to 'fork' CSL or go crazy with new variables > or other modifications of the CSL. On the contrary, we think a strong and > consistent CSL implementation across multiple platforms and sofwtare packages > is also in Mekentosj's best interest. I think if you come across what you think is a missing variable or some such, you should post a feature request ASAP at: https://github.com/citation-style-language/schema/issues Can you check through the existing ones, and add whatever you think is missing? > At this stage, we thus have a good Objective C processor, with still a few > holes, as well also a nice harness app to keep fixing bugs without breaking > existing behavior, and with the ability to leverage present and future CSL > fixtures. In the back of our mind, we have the idea of open-sourcing all that > stuff maybe one day, but at the moment, it still has too many dependencies > shared with the rest of Papers2. Also, it's not clear we can do a good job at > managing an open-source project in an acceptable way for others (our poor > records in communicating with the CSL devs so far is not a good indication!). > Also, I am not even sure that it would be very useful to many people other > than us. Let us know what you think. I would encourage you to evolve it to the state (WRT dependencies) that you could open source it. Putting a project on github, for example, is an easy way to get the benefits of open source, without substantial costs in terms of community management (it has a good issue tracker, code merging, wiki, and messaging infrastructure). Put it up, issue an announcement, and see what happens. The only labor you really need to do is to be responsive to pull requests and issues. ... > I also have a handful of styles contributed by some users, that I'd like to > push to the main CSL repository. I'd be happy to have direct commit access, > but then I also don't know what the process is to get commit access. Maybe > getting commit access would be counterproductive for you, so I'm just as > happy to submit them through the normal submission process (I have read the > instructions, etc… so no worry, I don't need them, and I know it's not the > right place to ask questions about this). Whatever minimizes the amount of > work on your end. Same for the fixtures. If you'd like commit rights, just send me your github user name and I'll add you to the "Style Editors" org team. I'll let Frank (or Rintze?) respond on the test fixtures. Bruce ------------------------------------------------------------------------------ Write once. Port to many. Get the SDK and tools to simplify cross-platform app development. Create new or port existing apps to sell to consumers worldwide. Explore the Intel AppUpSM program developer opportunity. appdeveloper.intel.com/join http://p.sf.net/sfu/intel-appdev _______________________________________________ xbiblio-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/xbiblio-devel
