Hi,

what I'm worried is also exactly the same. because we need to launch a
product which is closed source. and our client doesn't want the public to
know the technology we are using. so that why i thought that having a
commercial license where we can modify the code to match unique business
processes will be great. because re-inventing the wheel should be the last
option in development.

Regards,

Praveen

On Fri, Aug 22, 2008 at 1:51 PM, Tabrez Iqbal <[EMAIL PROTECTED]>wrote:

> Well, what is the definition of 'commercial' use here? AGPL doesn't prevent
> someone from selling the software for money but I think if the intention is
> to take laconi.ca code, make your modifications and then make it
> closed-source("without mentioning base framework"), then I think Evan and
> most of the laconi.ca community members would be dead-against such
> licensing.
>
> tabrez
> On Thu, Aug 21, 2008 at 11:02 PM, Steve Ivy <[EMAIL PROTECTED]> wrote:
>
>> Hi Praveen,
>>
>> While I appreciate the sometime usefulness of multi-licensing, knowing
>> Evan just a little (and his dedication to Free and Open software and
>> services) I think I can say that the likelyhood of there being a
>> commercial version of laconica is pretty slim. But Evan would have to
>> answer that question definitively.
>>
>> --Steve
>>
>> On Thu, Aug 21, 2008 at 10:29 AM, Praveen Gunasekara
>> <[EMAIL PROTECTED]> wrote:
>> > Hi All,
>> >
>> > Well what if someone want to use laconica in a commercial project
>> > without mentioning about the base framework they use...
>> >
>> > have you guys had a thought before about releasing laconica under a
>> > commercial license ?
>> >
>> > if not isn't it the best time to decide the pricing strategy for such
>> now... :)
>> >
>> > waiting for everyone's comments...
>> >
>> > Regards,
>> >
>> > Praveen Gunasekara
>>
>> --
>> Steve Ivy
>> http://redmonk.net // http://diso-project.org
>> This email is: [ ] bloggable [x] ask first [ ] private
>>
>>
>
_______________________________________________
Laconica-dev mailing list
[email protected]
http://mail.laconi.ca/mailman/listinfo/laconica-dev

Reply via email to