9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Bernd R. Fix" <Bernd.Fix@aspector.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] J9P/StyxLib
Date: Fri,  3 Apr 2009 03:09:51 +0200	[thread overview]
Message-ID: <49D561DF.4060507@aspector.com> (raw)
In-Reply-To: <1238608248.22573.19384.camel@work>

Roman V Shaposhnik schrieb:
> Not implying anything, just a question: what made you pick GPL in the
> first place?

Thanks to everyone for sharing their views on the licensing issue. Quite
a few statements and arguments to think about... Choosing an appropriate
license for a project is even trickier than I thought. So I started from
scratch again:

I consider J9P to be a framework for developers; "end-users" have no
need for such thing. As a "normal" developer you might risk a look at
the framework sources, but your main focus is to use the libraries
(APIs) and technical design of the framework to create your own killer
application.

I published the framework not because I was looking for developers to
join the project (although everybody is welcome), but for developers to
use the framework to realize their own ideas.

It's fine with me if these developers distribute their own work under
other OSI certified licenses or even commercially as long as the
underlying framework is kept open-source. If you modify the framework,
you must publish that modifications, but not your own work that is based
on the framework. I think that is fair enough for everyone.

So I had a look at a few of the mentioned licenses, and finally ended up
with what I had considered before publishing the project - LGPL. I think
this is a good compromise between a very strict GPL and a somewhat
relaxed BSD. The next build will include the changed license references.

Regards, Bernd.
--
gpg fp: F722 2826 40C2 B3C4 E136 6DE5 1DC0 7A20 513B C8F4



  parent reply	other threads:[~2009-04-03  1:09 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-01 11:43 Bernd R. Fix
2009-04-01 13:20 ` hiro
2009-04-01 14:48 ` David Leimbach
2009-04-01 15:05   ` Bernd R. Fix
2009-04-01 16:20     ` David Leimbach
2009-04-01 16:49       ` Bernd R. Fix
2009-04-01 17:28         ` David Leimbach
2009-04-01 17:50         ` Roman V Shaposhnik
2009-04-01 20:02           ` Bernd R. Fix
2009-04-01 20:19             ` Alex Efros
2009-04-01 20:42               ` J.R. Mauro
2009-04-01 20:46                 ` J.R. Mauro
2009-04-01 21:11                   ` Uriel
2009-04-01 21:33                     ` J.R. Mauro
2009-04-01 22:01                       ` hiro
2009-04-01 20:47                 ` Latchesar Ionkov
2009-04-01 21:30                   ` J.R. Mauro
2009-04-01 21:22                 ` hiro
2009-04-01 21:06               ` Wes Kussmaul
2009-04-01 21:12                 ` David Leimbach
2009-04-02 18:04             ` Roman V Shaposhnik
2009-04-03  1:09           ` Bernd R. Fix [this message]
2009-04-01 15:06 ` Roman V Shaposhnik

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=49D561DF.4060507@aspector.com \
    --to=bernd.fix@aspector.com \
    --cc=9fans@9fans.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).