release license?
fossfreedom opened this issue · comments
Hi,
I saw your mailing list email about your plugin. I'm interested in packaging this as a Debian package.
I need two bits of info though - the license that you will be releasing the plugin as, together with your public facing email address - email address should be added to the .plugin file.
You can use this to add a LICENSE file to your project as well.
If you are happy for me to do this, please let me know. Thanks in advance.
I added my email and the github link to the .plugin, but I've never done
a proper licensing of a project, so I'd be grateful if you're up for the
task .
Petko
PS: I'm very happy you're interested in packaging the plugin :)
On 03/01/2014 11:46 AM, David Mohammed wrote:
Hi,
I saw your mailing list email about your plugin. I'm interested in
packaging this as a Debian package.I need two bits of info though - the license that you will be
releasing the plugin as, together with your public facing email
address - email address should be added to the .plugin file.You can use this to add a LICENSE file to your project as well.
If you are happy for me to do this, please let me know. Thanks in advance.
—
Reply to this email directly or view it on GitHub
#1.
I forgot to ask - can you tell me where to add the version of the
plugin, mostly for logging purposes, I couldn't figure it out.
Wow, there've been cases where I forget something in a mail but a third
mail on a row may be a record. I didn't mention that the license should
be some GPL. I don't know the differences between different versions, so
I can't really tell, but AFIK it's the standard for FOSS projects, and
the latest version is 3, so probably GPLv3.
most people who create opensource stuff do so under GPL2 or GPL3. For the majority of plugins I've seen people mostly do GPL3. If you dont care with what people do with the code and dont mind that people dont contribute back then BSD is your license.
If you look at my plugin here:
You can add the Version to the plugin - mine is currently at Version=1.0
I personnally also add a github tag so that you can see easily each official version of your project
e.g.
The link I gave you above for the license stuff - the OP has created a semi official website
just follow the instructions on the website - it will automatically add the LICENSE file to your project depending upon which license you want - click each of the license descriptions on the website and it will describe what they mean.
Ok, I think it's all done. Is it packageable now ?
Petko
On 03/03/2014 05:53 PM, David Mohammed wrote:
most people who create opensource stuff do so under GPL2 or GPL3. For
the majority of plugins I've seen people mostly do GPL3. If you dont
care with what people do with the code and dont mind that people dont
contribute back then BSD is your license.If you look at my plugin here:
You can add the Version to the plugin - mine is currently at |Version=1.0|
I personnally also add a github tag so that you can see easily each
official version of your projecte.g.
The link I gave you above for the license stuff - the OP has created a
semi official websitejust follow the instructions on the website - it will automatically
add the LICENSE file to your project depending upon which license you
want - click each of the license descriptions on the website and it
will describe what they mean.—
Reply to this email directly or view it on GitHub
#1 (comment).
excellent - yes. I'll certainly looking at packaging. There is an issue that will stop packaging - but I'll raise an issue for this.