Project Status? about cl-cairo2

[tpapp]

Hi Ryan,

I have not been using this library for a while (switched to cl-pdf for
vector image generation). Ideally, it would be best if someone took
over. I am happy to hand it to you if you want to work on it, or I
can just ask people in a blogpost.

Regarding the license: I am happy to change it to LLGPL, but I think
(IANAL) I would have to ask the contributors (most notably Kei Suzuki)
for approval. Or the new maintainer can do it.

Best,

Tamas

On Mon, 23 Jan 2012, Ryan Pavlik wrote:

What is the status of this project? I would like to add cl-freetype2 compatibility and bring this up-to-date with current Cairo, but I have not seen updates in quite some time.

The licensing is also a bit unclear; some systems are marked LLGPL, and others merely GPL. Is it possible for this entire project to be LLGPL?

thanks,

---

Reply to this email directly or view it on GitHub:
https://github.com/tpapp/cl-cairo2/issues/10

[rpav]

I am definitely be willing to take over; I'm working on a project
which uses this heavily and have a rather vested interest, and
rewriting bindings from scratch is less than ideal to say the least.

If I take over maintenance I can do this if there is contact info. I
only see commits on github from a few people so this should hopefully
not be that big an issue, if Kei Suzuki is willing.

thanks,

[tpapp]

On Mon, 23 Jan 2012, Ryan Pavlik wrote:

On Mon, Jan 23, 2012 at 09:50, tpapp
[email protected]
wrote:

Hi Ryan,

I have not been using this library for a while (switched to cl-pdf for
vector image generation).  Ideally, it would be best if someone took
over.  I am happy to hand it to you if you want to work on it, or I
can just ask people in a blogpost.

I am definitely be willing to take over; I'm working on a project
which uses this heavily and have a rather vested interest, and
rewriting bindings from scratch is less than ideal to say the least.

Great! There are a few forks which you could also integrate, I will
make a list for you.

Regarding the license: I am happy to change it to LLGPL, but I think
(IANAL) I would have to ask the contributors (most notably Kei Suzuki)
for approval.  Or the new maintainer can do it.

If I take over maintenance I can do this if there is contact info. I
only see commits on github from a few people so this should hopefully
not be that big an issue, if Kei Suzuki is willing.

OK, I will dig out all the contact info and contact them.

What's your preferred license? Once we are changing it, we might as
well go for something you find optimal (if that's not LLGPL). I like
Boost [1] very much (basically a liberal MIT/BSD type license), but
you can pick the one you like best.

Best,

Tamas

[1] http://www.boost.org/users/license.html

Best,

Tamas

thanks,

[rpav]

Beyond "compatible and lisp-friendly" I have no particular preference... many things are LLGPL and BSD-ish, so getting along with those is useful IMHO.

[tpapp]

I have obtained permission from all contributors and changed the license to BOOST 1.0.