From bhargab.analytics at gmail.com Tue Sep 5 10:51:04 2023 From: bhargab.analytics at gmail.com (CS with BHARGAB) Date: Tue, 5 Sep 2023 16:21:04 +0530 Subject: [License-discuss] Asking Eligibility to apply license for Python Package Message-ID: Hello, I have written a python package which is globally accessible from pypi.org. you can visit the python package by the following link: https://pypi.org/project/chi-final/ I want to know if I can apply for an Open Source License? Note: I am using the MIT license for initial upload purposes. But can I have a separate license for this package? Regards, Bhargab Ganguli -------------- next part -------------- An HTML attachment was scrubbed... URL: From forums at david-woolley.me.uk Wed Sep 6 14:37:28 2023 From: forums at david-woolley.me.uk (David Woolley) Date: Wed, 6 Sep 2023 15:37:28 +0100 Subject: [License-discuss] Asking Eligibility to apply license for Python Package In-Reply-To: References: Message-ID: On 05/09/2023 11:51, CS with BHARGAB wrote: > Hello, > I have written a python package which is globally accessible from > pypi.org . you can visit the python package by the > following link: > https://pypi.org/project/chi-final/ > I want to know if I can apply for an Open Source License? > Note: I am using the MIT license for initial upload purposes. But can I > have a separate?license for this package? > I'm not clear what you are asking. Are you saying you want to create a new set of licence conditions, or are you saying can you apply a different, existing set to the software? (Although one talks about the MIT licence one really means the MIT licence conditions; the actual licence is the statement that those conditions apply.) If you mean a new set of conditions, that is very unlikely unless you can demonstrate that they fill a hole not covered by existing sets of conditions. There is a problem of licence condition proliferation, and new sets of conditions are difficult to get approved. If you are saying can you relicense the software under a new set of conditions, the answer is, if you own all the copyrights, and the new licence is otherwise compatible, yes you can. If you don't own all the copyrights, you would need to consult a lawyer, although, if everything uses the MIT terms, that may be straightforward. From tenorgil at gmail.com Wed Sep 6 15:32:46 2023 From: tenorgil at gmail.com (Tenorgil) Date: Wed, 6 Sep 2023 11:32:46 -0400 Subject: [License-discuss] Asking Eligibility to apply license for Python Package In-Reply-To: References: Message-ID: <8C3CECDB-4AC5-4559-A5A3-AD5FB22ADD0E@edison.tech> If it?s your code, (looks like it from the link) you can license it as you see fit. The confusion here (and it?s common) is that the term ?license? is used in two different ways. 1. In plain meaning, a license is a statement of permission. If you put a license on your code, you are granting permission to others to use your code - thank you for that. 2. However, in commercial licensing contexts, people purchase or request licenses since they are viewed as limited tokens that you pay for and get. Since this is an open source context, licensing means something you, the author, can give us, not something you get. Gil Yehuda > > On Sep 6, 2023 at 10:25 AM, wrote: > > > > Hello, > I have written a python package which is globally accessible from pypi.org (http://pypi.org/). you can visit the python package by the following link: > https://pypi.org/project/chi-final/ > > I want to know if I can apply for an Open Source License? > > Note: I am using the MIT license for initial upload purposes. But can I have a separate license for this package? > > > > Regards, > > Bhargab Ganguli > > _______________________________________________ The opinions expressed in this email are those of the sender and not necessarily those of the Open Source Initiative. Official statements by the Open Source Initiative will be sent from an opensource.org email address. License-discuss mailing list License-discuss at lists.opensource.org http://lists.opensource.org/mailman/listinfo/license-discuss_lists.opensource.org > -------------- next part -------------- An HTML attachment was scrubbed... URL: