On Wed, 29 Nov 2017, Aris Merchant wrote:

What would people think of a proposal actually specifying that Agorans
all share copyright over the rules (and the gamestate in general) and
that they are licensed under X licence? I don't think this would ever
actually be a problem, but it's probably better to make it clear so
that it can't be. Also, what license would be appropriate (public
domain is a pretty strong contender, because that's basically the
situation now)?

Although I'm working only from impression myself, I don't think copyright law works that way. Any actual copyright reassignement or licensing requires the explicit permission of every person who's contributed nontrivially to the current rules.

If it actually _is_ a problem, it's terribly complicated to fix, possibly impossible (we might not be able to _find_ every contributor). Agora was created during a time when no one cared about copyright for stuff like this. Barn doors and horses.

Greetings,
Ørjan.

-Aris

On Wed, Nov 29, 2017 at 8:59 PM, Owen Jacobson <[email protected]> wrote:

On Nov 24, 2017, at 2:24 AM, Kerim Aydin <[email protected]> wrote:



I don't recall who drew that particular image.  But the heraldic description was
mandated by a proposal by GreyKnight adopted in 2007 (it was later made into
a rule):

Proposal 4898 by Greyknight, AI=1, Ordinary
Agoran Arms

The coat of arms of Agora is defined by the following blazon:

     Tierced palewise sable, argent, and sable, charged with a quill and an
axe in saltire, proper, and in the chief a capital letter A, gules.

When any Player requires an image that e may use to represent Agora or
the interests thereof, e must use an image which accurately depicts the
blazon presented here.

Thanks.

I ended up using it, with some hesitation, for the app icon for 
https://github.com/ojacobson/cadastre/ 
<https://github.com/ojacobson/cadastre/>. To see it in action you have to have 
a Heroku account - it’s only displayed during setup, when you click the “Deploy to 
Heroku” button in the README.

-o


Reply via email to