Hi all,
We often get contributions for adding custom filetypes to Geany, and we even have some in the source tree already. We tend to not want to add them to Geany repo, usually due to limited functionality, or limited popularity.
I would like to propose that we add a new repository to Github, similar to geany-themes, where we add any custom filetypes that are useful, but perhaps aren't up to par or popular enough to add to Geany proper. This would give a single place to get them all at once (via Git or Github Zip file download), and also a repo for packagers to use should they want to provide a package.
Inside the repo we could have the README or some other file cataloging all the filetypes, along with who contributed them, their status, like whether tag parsing works, syntax lexing, and such meta info. As a start, we could add all of the filetypes from the Wiki[0], any useful ones from pull requests, and even any questionable ones already in Geany (if there are any). We could also add some shell script or something to install them into a user's home dir all at once, if that's useful.
What do you think?
Cheers, Matthew Brush
Sounds like a reasonable idea, but it triggered me to ask about licenses and copyright. Imagine my feigned horror when I discovered none of Geany's filetypes has a copyright notice or license for its use.
So I am claiming copyright and Enrico and Colomban, the invoice is in the mail :)
The wiki has a blanket "cc share alike" license notice in the footer, so thats better than nothing, though with no copyright owners identified just who is giving this license is questionable. But its better than Geany.
We need to make sure that the license is transferred to the new repo as well, and then I think its a good idea.
Cheers Lex (IANAL, nothing in the above constitutes legal advice :)
On 20 December 2015 at 12:11, Matthew Brush mbrush@codebrainz.ca wrote:
Hi all,
We often get contributions for adding custom filetypes to Geany, and we even have some in the source tree already. We tend to not want to add them to Geany repo, usually due to limited functionality, or limited popularity.
I would like to propose that we add a new repository to Github, similar to geany-themes, where we add any custom filetypes that are useful, but perhaps aren't up to par or popular enough to add to Geany proper. This would give a single place to get them all at once (via Git or Github Zip file download), and also a repo for packagers to use should they want to provide a package.
Inside the repo we could have the README or some other file cataloging all the filetypes, along with who contributed them, their status, like whether tag parsing works, syntax lexing, and such meta info. As a start, we could add all of the filetypes from the Wiki[0], any useful ones from pull requests, and even any questionable ones already in Geany (if there are any). We could also add some shell script or something to install them into a user's home dir all at once, if that's useful.
What do you think?
Cheers, Matthew Brush
Devel mailing list Devel@lists.geany.org https://lists.geany.org/cgi-bin/mailman/listinfo/devel
On 2015-12-19 09:04 PM, Lex Trotman wrote:
Sounds like a reasonable idea, but it triggered me to ask about licenses and copyright. [...]
As a lesson learned from geany-themes project, I suggest we use a single license for all files. I'm pretty sure there isn't much IP issues with filetype configurations, but just in case, having a single permissive license removes all doubt and makes it easier for packagers.
Cheers, Matthew Brush
Agreed.
On 20 December 2015 at 15:10, Matthew Brush mbrush@codebrainz.ca wrote:
On 2015-12-19 09:04 PM, Lex Trotman wrote:
Sounds like a reasonable idea, but it triggered me to ask about licenses and copyright. [...]
As a lesson learned from geany-themes project, I suggest we use a single license for all files. I'm pretty sure there isn't much IP issues with filetype configurations, but just in case, having a single permissive license removes all doubt and makes it easier for packagers.
Cheers, Matthew Brush
Devel mailing list Devel@lists.geany.org https://lists.geany.org/cgi-bin/mailman/listinfo/devel
On 20.12.2015 06:10, Matthew Brush wrote:
On 2015-12-19 09:04 PM, Lex Trotman wrote:
Sounds like a reasonable idea, but it triggered me to ask about licenses and copyright. [...]
As a lesson learned from geany-themes project, I suggest we use a single license for all files. I'm pretty sure there isn't much IP issues with filetype configurations, but just in case, having a single permissive license removes all doubt and makes it easier for packagers.
Yes. Even GPL is not the best idea for configs I think as all other things for Geany is GPLv2+, this files could be too.
Cheers, Frank
On 20.12.2015 06:04, Lex Trotman wrote:
Sounds like a reasonable idea, but it triggered me to ask about licenses and copyright. Imagine my feigned horror when I discovered none of Geany's filetypes has a copyright notice or license for its use.
So I am claiming copyright and Enrico and Colomban, the invoice is in the mail :)
The wiki has a blanket "cc share alike" license notice in the footer, so thats better than nothing, though with no copyright owners identified just who is giving this license is questionable. But its better than Geany.
We need to make sure that the license is transferred to the new repo as well, and then I think its a good idea.
We put the complete repo to GPL2+ and all PR automatic have that license.
Cheers, Frank
On 20 December 2015 at 19:43, Frank Lanitz frank@frank.uvena.de wrote:
On 20.12.2015 06:04, Lex Trotman wrote:
Sounds like a reasonable idea, but it triggered me to ask about licenses and copyright. Imagine my feigned horror when I discovered none of Geany's filetypes has a copyright notice or license for its use.
So I am claiming copyright and Enrico and Colomban, the invoice is in the mail :)
The wiki has a blanket "cc share alike" license notice in the footer, so thats better than nothing, though with no copyright owners identified just who is giving this license is questionable. But its better than Geany.
We need to make sure that the license is transferred to the new repo as well, and then I think its a good idea.
We put the complete repo to GPL2+ and all PR automatic have that license.
Hi Frank,
"The repository" is not useful, as soon as I clone or download a tarball its no longer part of "the repository".
As for PRs, anything submitted that can be reasonably understood to be intended to be incorporated into Geany code is also understood to be licensed by the Geany license for the file it is incorporated in.
But these filetypes files are whole files, that have no copyright notice or reference to a license. Some useful information from the FSF:
"You should put a notice at the start of each source file, stating what license it carries, in order to avoid risk of the code's getting disconnected from its license. If your repository's README says that source file is under the GNU GPL, what happens if someone copies that file to another program? That other context may not show what the file's license is. It may appear to have some other license, or no license at all (which would make the code nonfree).
Adding a copyright notice and a license notice at the start of each source file is easy and makes such confusion unlikely.
This has nothing to do with the specifics of the GNU GPL. It is true for any free license."
In particular note that no license means it cannot be used, not that it is public domain.
Since conf files accept comments there should be no problem with putting the usual header in the filetypes files, just a quick Python script away :)
Will look at it if I get bored soon.
As for changing the license of stuff off the wiki, unless it has a license that says we can do so, or we know who owns it and get their approval we can't legally change it.
Cheers Lex
Cheers, Frank
Devel mailing list Devel@lists.geany.org https://lists.geany.org/cgi-bin/mailman/listinfo/devel
On 20.12.2015 11:22, Lex Trotman wrote:
"The repository" is not useful, as soon as I clone or download a tarball its no longer part of "the repository".
If the tarball is including a LICENCE it should be clear.
As for PRs, anything submitted that can be reasonably understood to be intended to be incorporated into Geany code is also understood to be licensed by the Geany license for the file it is incorporated in.
But these filetypes files are whole files, that have no copyright notice or reference to a license. Some useful information from the FSF:
"You should put a notice at the start of each source file, stating what license it carries, in order to avoid risk of the code's getting disconnected from its license. If your repository's README says that source file is under the GNU GPL, what happens if someone copies that file to another program? That other context may not show what the file's license is. It may appear to have some other license, or no license at all (which would make the code nonfree).
Yes. Best practice. If somebody is copying it and doesn't keep it under terms of GPL he is doing a break of GPL so this is something for legal. Theoretically.
Adding a copyright notice and a license notice at the start of each source file is easy and makes such confusion unlikely.
Yes. A one liner should be enough.
This has nothing to do with the specifics of the GNU GPL. It is true for any free license."
In particular note that no license means it cannot be used, not that it is public domain.
It depends. From my understanding in US if nobody claims Copyright, its actually nearly PD (It's not, but feels similar to it) In Europe you don't have to claim copyright as e.g. German Urheberrecht is having the implicit.
Since conf files accept comments there should be no problem with putting the usual header in the filetypes files, just a quick Python script away :)
Will look at it if I get bored soon.
As for changing the license of stuff off the wiki, unless it has a license that says we can do so, or we know who owns it and get their approval we can't legally change it.
Well... This can be hard. CC-SA is not including re-licensing IIRC.
Cheers, Frank
On 20.12.2015 03:11, Matthew Brush wrote:
Hi all,
We often get contributions for adding custom filetypes to Geany, and we even have some in the source tree already. We tend to not want to add them to Geany repo, usually due to limited functionality, or limited popularity.
I would like to propose that we add a new repository to Github, similar to geany-themes, where we add any custom filetypes that are useful, but perhaps aren't up to par or popular enough to add to Geany proper. This would give a single place to get them all at once (via Git or Github Zip file download), and also a repo for packagers to use should they want to provide a package.
Inside the repo we could have the README or some other file cataloging all the filetypes, along with who contributed them, their status, like whether tag parsing works, syntax lexing, and such meta info. As a start, we could add all of the filetypes from the Wiki[0], any useful ones from pull requests, and even any questionable ones already in Geany (if there are any). We could also add some shell script or something to install them into a user's home dir all at once, if that's useful.
What do you think?
I like that idea.
On 12/19/2015 09:11 PM, Matthew Brush wrote:
Hi all,
We often get contributions for adding custom filetypes to Geany, and we even have some in the source tree already. We tend to not want to add them to Geany repo, usually due to limited functionality, or limited popularity.
I would like to propose that we add a new repository to Github, similar to geany-themes, where we add any custom filetypes that are useful, but perhaps aren't up to par or popular enough to add to Geany proper. This would give a single place to get them all at once (via Git or Github Zip file download), and also a repo for packagers to use should they want to provide a package.
Inside the repo we could have the README or some other file cataloging all the filetypes, along with who contributed them, their status, like whether tag parsing works, syntax lexing, and such meta info. As a start, we could add all of the filetypes from the Wiki[0], any useful ones from pull requests, and even any questionable ones already in Geany (if there are any). We could also add some shell script or something to install them into a user's home dir all at once, if that's useful.
What do you think?
Cheers, Matthew Brush
Devel mailing list Devel@lists.geany.org https://lists.geany.org/cgi-bin/mailman/listinfo/devel
I love your idea Matthew Brush.
Thanks, Devyn Collier Johnson
Hi Matt and all,
On 20/12/15 17:58, Devyn Collier Johnson wrote:
On 12/19/2015 09:11 PM, Matthew Brush wrote:
Hi all,
We often get contributions for adding custom filetypes to Geany, and we even have some in the source tree already. We tend to not want to add them to Geany repo, usually due to limited functionality, or limited popularity.
I would like to propose that we add a new repository to Github, similar to geany-themes, where we add any custom filetypes that are useful, but perhaps aren't up to par or popular enough to add to Geany proper. This would give a single place to get them all at once (via Git or Github Zip file download), and also a repo for packagers to use should they want to provide a package.
Inside the repo we could have the README or some other file cataloging all the filetypes, along with who contributed them, their status, like whether tag parsing works, syntax lexing, and such meta info. As a start, we could add all of the filetypes from the Wiki[0], any useful ones from pull requests, and even any questionable ones already in Geany (if there are any). We could also add some shell script or something to install them into a user's home dir all at once, if that's useful.
What do you think?
Cheers, Matthew Brush
I love your idea Matthew Brush.
Me too! This should ease handling additional filetype configurations, enable more people to easily to contribute to them and finally make changes more visible and traceable.
For the license topic: as the rest of us, I'm not a lawyer as well. In my opinion, it should suffice to put configuration files under GPLv2+ (as Geany itself) and as Lex stated, put a short license header in each config file to make this obvious.
Regards, Enrico