# CSL Agenda 2016

**URL:** <https://discourse.citationstyles.org/t/csl-agenda-2016/1430>\
**Category:** CSL Development\
**Created:** [November 15, 2015, 3:54am UTC](https://discourse.citationstyles.org/t/csl-agenda-2016/1430 "2015-11-15T03:54:10Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Rintze\_Zelle](https://yyz1.discourse-cdn.com/flex029/user_avatar/discourse.citationstyles.org/rintze_zelle/32/175_2.png) [@Rintze\_Zelle](https://discourse.citationstyles.org/u/Rintze_Zelle)\
**Post date:** [November 15, 2015, 3:54am UTC](https://discourse.citationstyles.org/t/csl-agenda-2016/1430/1 "2015-11-15T03:54:10Z")

</div>

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](https://github.com/citation-style-language/governance/blob/master/governance.md)),  
so this is the start of that effort)

In addition to what Sebastian said:

> 1. Moving style hosting to [www.citationstyles.org](http://www.citationstyles.org)  
> We’d like to transition from [zotero.org](http://zotero.org) style ids, and offer both a GUI  
> version of the style repository on [citationstyles.org](http://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](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](https://github.com/citation-style-language/styles/issues/2)

Unless anybody raises concerns, I think the way to go is to first  
start hosting the current styles (with unchanged  
“[Zotero Style Repository](http://www.zotero.org/styles/)_" style IDs and “self” links) via the  
 [citationstyles.org](http://citationstyles.org) domain with their proper CSL style MIME type  
([https://www.iana.org/assignments/media-types/application/vnd.citationstyles.style+xml](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](http://www.zotero.org/styles/)_” URL scheme to something  
like “[http://styles.citationstyles.org/](http://styles.citationstyles.org/)_" or  
"[http://repository.citationstyles.org/](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).

> 1. 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](http://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](http://nabble.com)

With all the bad news surrounding SourceForge  
([DHI Group plans to sell off Slashdot and Sourceforge | Ars Technica](http://arstechnica.com/information-technology/2015/07/dhi-group-plans-to-sell-off-slashdot-and-sourceforge/)),  
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](http://sourceforge.net/p/forge/documentation/Mailing%20List%20Archives/)).  
We could either try our luck with another Mailman hosting service  
([COM/Mailman hosting services - Mailman Wiki](http://wiki.list.org/COM/Mailman%20hosting%20services), 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](http://blog.discourse.org/2014/04/install-discourse-in-under-30-minutes/)),  
or we could purchase hosting for $200 per year  
([https://www.discoursehosting.com/](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](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

---

<div class="post-metadata">

**Author:** ![Matej\_Cepl](https://avatars.discourse-cdn.com/v4/letter/m/e480ec/32.png) [@Matej\_Cepl](https://discourse.citationstyles.org/u/Matej_Cepl)\
**Post date:** [November 15, 2015, 5:21pm UTC](https://discourse.citationstyles.org/t/csl-agenda-2016/1430/2 "2015-11-15T17:21:50Z")

</div>

I mean if the list is moved somewhere else, somebody should let  
[gmane.org](http://gmane.org) people know so they can retarget their server from  
reading the new list. Just that nobody forgets and reminder that  
there are people (like me ;)) who prefer NNTP for reading their  
lists.

Matěj

---

<div class="post-metadata">

**Author:** ![Matej\_Cepl](https://avatars.discourse-cdn.com/v4/letter/m/e480ec/32.png) [@Matej\_Cepl](https://discourse.citationstyles.org/u/Matej_Cepl)\
**Post date:** [November 15, 2015, 5:32pm UTC](https://discourse.citationstyles.org/t/csl-agenda-2016/1430/3 "2015-11-15T17:32:15Z")

</div>

Also, I am not attached to the gmane as archive per se (although  
it would be probably worthy to include into [gmane.org](http://gmane.org) the rest  
of the archive as well … [http://gmane.org/import.php](http://gmane.org/import.php) ; is it  
possible to export whole archive from [nabble.com](http://nabble.com)?) but I really  
prefer NNTP client for processing tons of messages I read every  
day (see the User-Agent header of this message). Does nabble  
provide NNTP bidirectional gateway as well?

Best,

Matěj

---

<div class="post-metadata">

**Author:** ![Rintze\_Zelle](https://yyz1.discourse-cdn.com/flex029/user_avatar/discourse.citationstyles.org/rintze_zelle/32/175_2.png) [@Rintze\_Zelle](https://discourse.citationstyles.org/u/Rintze_Zelle)\
**Post date:** [November 15, 2015, 11:56pm UTC](https://discourse.citationstyles.org/t/csl-agenda-2016/1430/4 "2015-11-15T23:56:30Z")

</div>

Ah, okay. We’ll keep it in mind if we start hosting the mailing list  
elsewhere, although if we switch to a more forum-based platform like  
Discourse that most probably wouldn’t work.

I’ll also contact Gmane regarding importing the pre-2011 emails (we  
can grab those directly from SourceForge as an mbox file).

Rintze