Hi Matt, Bjorn, Maarten, In general, I agree with the points raised by Maarten. But I also see, and can relate to, the contributor agreements that Matt is talking about.
It seems to me that Maarten, and to some extent Bjorn, aren't necessarily contesting the contributor agreement as such, but see it only as one of the obstacles to contributing to Creative Commons, and where other work is needed before even getting to the issue of a contributor agreement. So what we're saying is that rather than first posting the question of the contributor agreement, you may want to consider how to increase the communication between CC and its community, and how to get that initial collaboration going. Once you have an actual contribution, you can use that opportunity to review the contributor agreement. Sincerely, Jonas On 10 December 2014 at 17:21, Matt Lee <[email protected]> wrote: > Thanks to Maarten and to Bjorn for your feedback. > > Just a follow up on some things I've been working on in response to this > thread. > > * Firstly, I am working on bringing back the labs blog. Later today > it'll be up with a new look and a Jekyll site, that'll be public. I'm > going to be updating it three times a week with news and giving more > transparency for some of the work I'm doing, and others are doing. > > * As you may know, we already have a non-CC developer working on The > List app, and we expect to get many more. In the last few months, I > have been traveling around, talking about The List, and we are > currently working toward an alpha release in the coming weeks. > > If you're interested in hacking on The List, we have an Android app in > development, which is mostly Java, and a web app which is mostly PHP. > We also have an early version of our website about The List, which I'm > going to hope we can launch in the next few days, but it's all up > there in GitHub, if you're interested. > > https://github.com/creativecommons/list > > Regarding the contributor agreement: > > As we're already dealing with outside contributions on this app, and > given my limited resources at CC, I don't want to worry about being > unable to release the app, or worse, being unable to release the app > under a free license. > > I signed a very similar document with the Free Software Foundation > about 8 years ago and it has been extremely easy to contribute to a > lot of free software since then. In fact, it has been my job for most > of that time. > > As a small team with few resources, we need to be able to keep all our > work public and freely licensed, and this is a legal hack to do just > that. > > Projects that don't have such an agreement in place are effectively > stuck on a particular license for the rest of time. That's a situation > I'd like to avoid. > _______________________________________________ > cc-devel mailing list > [email protected] > http://lists.ibiblio.org/mailman/listinfo/cc-devel _______________________________________________ cc-devel mailing list [email protected] http://lists.ibiblio.org/mailman/listinfo/cc-devel
