[BangPypers] Suggestion for GUI
Narendra Sisodiya
narendra at narendrasisodiya.com
Mon Jan 10 16:41:03 CET 2011
On Mon, Jan 10, 2011 at 1:03 PM, Anand Balachandran Pillai <
abpillai at gmail.com> wrote:
> On Mon, Jan 10, 2011 at 10:56 AM, Narendra Sisodiya <
> narendra at narendrasisodiya.com> wrote:
>
> > code to run.
> > >
> >
> > I am just typing some random string , it comes out to be a PyQT code.
>
>
> How ? This is some skill if you ask me.
>
>
> > some
> > fellows are interested to buy it, I never tested using PyQT nor i am
> > giving
> > them suggestion to install PyQT. Client are doing by their own. How come
> I
> > am making any violation ....
> >
>
> Are you kidding ? You might have typed the code in your sleep, but as long
> as it is using library "X" and X stipulates a licensing scheme, which is
> non-free,
> you and your customers are bound by X's licensing terms.
>
> If you want a rough and dirty guide to open source licensing, here it is.
>
> 1. Using public domain/free licenses (BSD, MPL etc) - You are free to
> choose
> whatever licensing you want to. Typically people re-license code using
> BSD*
> libraries in BSD or compatible licenses.
> 2. Throw-away/free/utility code which you don't care - Put in public domain
> or
> use some arbit license. I suggest WTFL.
> 3. Code under LGPL - You can relicense in LGPL or stricter licenses such
> as GPL*. Can't re-licenses typically under a much freer license such as
> BSD.
> 4. Code under GPLv2/GPLv3 - Typically provides a lot of restrictions on
> commercial
> use of the source code. People re-license under same licenses.
>
> I suggest spending some time on
> http://www.opensource.org/licenses/index.html
> whenever you got time. It is worth your while.
>
>
Thanks, people are funny.. I am well aware of concept of license and
copyright,
More information about the BangPypers
mailing list