[hackerspaces] Wiki license
Matthew Senate
mattsenate at gmail.com
Thu Apr 24 01:11:27 CEST 2014
Providing no license leaves me with the old-school "copyleft, all wrongs
reversed" sentiment which I like to use sometimes:
https://gist.github.com/wrought/5890620#file-copyleft_all_wrongs_reversed-html
this of course has dubious legal bearing, so licenses are still an
interesting set of options.
this is an important question since hackerspaces.org (to my knowledge) is
the primary shared knowledge base for hackerspaces globally, plus one of
the (if not *the*) largest implementations of semantic mediawiki, making
much wiki content stored as structured data. Rad, huh?
So what should be used?
My first inclination is to support a Wikipedia-compatible license (meaning
for example CC-BY or CC-BY-SA).
My second thought would be to question if hackerspaces.org content should
be thought of in a similar way folks are thinking about "open data",
(meaning for example CC-0 or CC-SA)
CC-SA is pretty interesting, it came out in the first CC license draft and
has been discontinued since, but still remains a usable license
https://creativecommons.org/licenses/sa/1.0/ This enables very easy
data-reuse (no attribution necessary), so long as your work has a
compatible license, but I imagine would make merging data sets difficult as
other data licenses will likely not be "share-alike" or have the "copyleft"
mechanism. Basically, it may be the GPL of open data, without the baggage
of caring who exactly is named. Provenance can then be dealt with using a
least path.
// Matt
On Wed, Apr 23, 2014 at 1:18 PM, Christie Dudley
<christie at hackcounsel.com>wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> You'd likely to come across the same in the US. "Engaged in commerce"
> is not the same as "for-profit".
>
> Christie
>
> On 4/21/14, 17:57, hellekin wrote:
> > On 04/21/2014 09:26 PM, Mike Dupont wrote:
> >> This was a non profit radio station, according to the german
> >> judge all public use is commercial use.
> >>
> > *** Wow! That seems to be abusive. That's the ultimate step into
> > commoditization of the public space.
> >
> > == hk
> >
> > _______________________________________________ Discuss mailing
> > list Discuss at lists.hackerspaces.org
> > http://lists.hackerspaces.org/mailman/listinfo/discuss
> >
>
> - --
> Quis custodiet ipsos custodes?
>
> Class C poetic license in the land of broken memes.
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG/MacGPG2 v2.0.22 (Darwin)
> Comment: GPGTools - http://gpgtools.org
>
> iQEcBAEBAgAGBQJTWCAaAAoJEINTCJXtxRQuNXEH+wU7Mrj1YE+x02CBSgZxm0tT
> 8ZeAjWFSNeiz4SrrLWuE1cgVihofABq5ZOeR8aHoadhbWGqDgGosAEcJpa0ra3oK
> fHLJ6h5nzzeJkp/ukXROj1Dcj/m0I3mUrKE/bTPKCBsRMzjeke/DRUlLHfZn7IZm
> a0//xAb0hri8KhHAXVSJpLV0V+I2TfSXWfkGHqWdaD2AMrUPaMAnqYMNCD5EUO/1
> jNlQ2SOhS5TtU8XMNIU9+E6uw2wu9BoHon+jTGZEeTefIErbkAVOAFgQZOo1NVPl
> DekBmkNgbbmkzaloJVtHjmHBl7MKUjW+3/CuqjTODdurU1cvWc+V11DjdQA72Ds=
> =RyQW
> -----END PGP SIGNATURE-----
> _______________________________________________
> Discuss mailing list
> Discuss at lists.hackerspaces.org
> http://lists.hackerspaces.org/mailman/listinfo/discuss
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.hackerspaces.org/pipermail/discuss/attachments/20140423/4e8bc5e9/attachment.html>
More information about the Discuss
mailing list