Re: [Sugar-devel] Activity SoaS Licensing Concerns

2010-02-12 Thread Sebastian Dziallas
Sebastian Dziallas wrote: Sebastian Dziallas wrote: Hi folks, I've lately taken the task of packaging more activities to get us a reasonably user experience for the next iteration of SoaS. The normal review process requires an application to be properly and clearly licensed. I'd like to

Re: [Sugar-devel] Activity SoaS Licensing Concerns

2010-02-12 Thread Tim McNamara
On 13 February 2010 09:15, Sebastian Dziallas sebast...@when.com wrote: If nobody complains by the end of this weekend, I'll just upload the images, put a GPLv2+ license in the archive and make a tarball, as this is what they've been listed under in Strawberry and Blueberry, too. --Sebastian

Re: [Sugar-devel] Activity SoaS Licensing Concerns

2010-02-12 Thread Sebastian Dziallas
Tim McNamara wrote: On 13 February 2010 09:15, Sebastian Dziallas sebast...@when.com mailto:sebast...@when.com wrote: If nobody complains by the end of this weekend, I'll just upload the images, put a GPLv2+ license in the archive and make a tarball, as this is what they've been

Re: [Sugar-devel] Activity SoaS Licensing Concerns

2010-02-12 Thread Luke Faraone
On Fri, Feb 12, 2010 at 16:15, Sebastian Dziallas sebast...@when.com wrote: And I guess from how our logo policy [3] looks like, we might need to have a some more restrictive one there IANAL, but from my understanding, the license of the logo file does not change the trademark license, which

Re: [Sugar-devel] Activity SoaS Licensing Concerns

2010-02-12 Thread Peter Robinson
On Sat, Feb 13, 2010 at 4:15 AM, Sebastian Dziallas sebast...@when.comwrote: Sebastian Dziallas wrote: Sebastian Dziallas wrote: Hi folks, I've lately taken the task of packaging more activities to get us a reasonably user experience for the next iteration of SoaS. The normal review

Re: [Sugar-devel] Activity SoaS Licensing Concerns

2010-02-10 Thread Sebastian Dziallas
Sebastian Dziallas wrote: Hi folks, I've lately taken the task of packaging more activities to get us a reasonably user experience for the next iteration of SoaS. The normal review process requires an application to be properly and clearly licensed. I'd like to encourage activity authors to