[tei-council] code vs. wiki licensing
john.m.unsworth at gmail.com
Mon Sep 12 12:42:04 EDT 2011
If the council is thinking about moving off of the current wiki, you might consider GitHub:
are there council members who already use it for other projects?
On Sep 12, 2011, at 11:34 AM, Piotr Bański wrote:
> Speaking of sensible licensing, let me point out (with thanks to Syd
> Bauman, who has raised this issue on another mailing list), that the
> current system, whereby XSLT/XQuery code submitted to the wiki ends up
> obligatorily licensed under an early version of the GNU Free
> *Documentation* License, makes very little sense.
> I admit I feel partially responsible for this, because I was among those
> who promoted the use of the TEIWiki for the purpose of storing code, a
> few years ago, but some issues have become very obvious since then:
> * wiki is not a revision-control system for code;
> * wiki is not even a good display system for code (some stuff has to be
> escaped because of wiki requirements, there is no syntax highlighting);
> * whether the submitter specifies the license or not, the code ends up
> licensed under GFDL.
> A way out could be to provide SVN space for the code, and restrict the
> wiki to document that, as it does for the other tools.
> tei-council mailing list
> tei-council at lists.village.Virginia.EDU
> PLEASE NOTE: postings to this list are publicly archived
More information about the tei-council