Hi all,
(as you all might remember, as the CSL board we promised to annually
propose goals and priorities for the CSL project
(governance/governance.md at master · citation-style-language/governance · GitHub),
so this is the start of that effort)
In addition to what Sebastian said:
- Moving style hosting to www.citationstyles.org
We’d like to transition from zotero.org style ids, and offer both a GUI
version of the style repository on citationstyles.org and serve styles from
there (e.g. for auto-updating). We think this should be the top priority for
2016
We’ll want a proper hosting solution for this and, if clients will want to
rely on our site (rather than pulling from github the way Zotero & Mendeley
currently do) for style updates. We also will want to hire someone to do
this for us. (Elsevier/Mendeley has already announced they’ll again support
us, so we have a budget). Sylvester suggested someone to us, but if anyone
here is interested or has recommendations, that’d be very welcome, too.
Also, for any of the downstream users of the style–will a global change in
style ids cause major headaches? Is there anything we can/should do to make
the transition go smoothly?
We touched on this topic before at
http://xbiblio-devel.2463403.n2.nabble.com/call-for-comments-on-base-URI-issue-td6097469.html
and settle on new base uri for styles, update ids accordingly · Issue #2 · citation-style-language/styles · GitHub
Unless anybody raises concerns, I think the way to go is to first
start hosting the current styles (with unchanged
“Zotero Style Repository" style IDs and “self” links) via the
citationstyles.org domain with their proper CSL style MIME type
(https://www.iana.org/assignments/media-types/application/vnd.citationstyles.style+xml).
Once that is up and running we can hammer out the details on how to
change the "Zotero Style Repository” URL scheme to something
like “http://styles.citationstyles.org/" or
"http://repository.citationstyles.org/” (while keeping these URLs
dereferenceable), and decide what to do about style IDs (my preference
would be to keep style IDs and “self” links in sync, like they are
now).
- Moving away from sourceforge
Rintze has mentioned this before, but we’d like to look at moving away from
sourceforge, which is increasingly spammy, sometimes unreliable, and of an
uncertain future. We’re thinking most likely www.discourse.org, with a paid
hosting solution, but are open to alternatives. Also, we want to make sure
that there’s a way to get data out of Discourse before switching.We won’t be able to transfer the list archive to discourse easily, but it’ll
keep existing on nabble.com
With all the bad news surrounding SourceForge
(DHI Group plans to sell off Slashdot and Sourceforge | Ars Technica),
I think we should at least be prepared that they might stop hosting
mailing lists or shut down altogether.
Fortunately, SourceForge offers mbox downloads
(SourceForge Support / Documentation / Mailing List Archives).
We could either try our luck with another Mailman hosting service
(COM/Mailman hosting services - Mailman Wiki, although I had
a hard time determining which ones are reputable/reliable), or try a
different platform like Discourse (with benefits like editing of
existing posts and syntax highlighting).
It’s relatively easy to set up an instance of Discourse
(Install Discourse in Under 30 Minutes),
or we could purchase hosting for $200 per year
(https://www.discoursehosting.com/). It doesn’t look like it’s
possible to directly import a Mailman archive into Discourse, though
(https://meta.discourse.org/t/import-mailman-archives-into-discourse/18537),
and I’m not sure Discourse can import mbox files. I also couldn’t find
good information on the export options in case we’d later want to
migrate away from Discourse.
Rintze