GPLv3 The Forums and MIT
Bump
Posts: 592
I was asked to make some changes to the forum guidelines, rules, and whatever else they might be referred to as in regards to licensing and the code snippets posted on these discussion forums. The changes are meant to keep pace with our evolving playground and to not accidentally restrict someone, you nice people, because we failed to be considerate of the changing environment with our verbiage. Soooooooooo
These changes were made:
The OBEX still appears in these changes, but please note this has not yet (2014-08-12) changed the OBEX's license statement which can be read here. We can consider this component up for review, but it may not change. We're not going to try and issue a statement forcing all MIT licensing to be GPLv3, that'd be pretty silly; however in terms of these discussion forums be mindful that you may encounter code from all sorts of licenses, and you should be aware of the licensing provisioned on any code snippet, sample, etc. Practice safe exchange.
I do have it on good account that you may be able to 'git' more of the GPL love you require soon. More on that as it develops.
These changes were made:
Code:
Code listed on the OBEX and web forum may be GPL, MIT, or otherwise licensed; mind the licenses of the software you're using and treat them according to their restrictions.
Code uploaded to OBEX and the web forum, without existing or expressed licensing, should comply with the MIT license.
Code snippets are to be treated as MIT licensed, minus the requirement to include the license text and mandatory attribution, unless under another existing license. We leave it to the good will of the community to resolve other cases amicably and to when applicable note known licenses.
Code listed on the OBEX and web forum may be GPL, MIT, or otherwise licensed; mind the licenses of the software you're using and treat them according to their restrictions.
Code uploaded to OBEX and the web forum, without existing or expressed licensing, should comply with the MIT license.
Code snippets are to be treated as MIT licensed, minus the requirement to include the license text and mandatory attribution, unless under another existing license. We leave it to the good will of the community to resolve other cases amicably and to when applicable note known licenses.
The OBEX still appears in these changes, but please note this has not yet (2014-08-12) changed the OBEX's license statement which can be read here. We can consider this component up for review, but it may not change. We're not going to try and issue a statement forcing all MIT licensing to be GPLv3, that'd be pretty silly; however in terms of these discussion forums be mindful that you may encounter code from all sorts of licenses, and you should be aware of the licensing provisioned on any code snippet, sample, etc. Practice safe exchange.
I do have it on good account that you may be able to 'git' more of the GPL love you require soon. More on that as it develops.
Comments
We are good to go to the next level. Let the code sharing commence!
Ken Gracey
Is it possible for you to organise the ability to upload ".v" files please?
Currently the forum rejects them so they have to be zipped. They are the verilog files used in the fpga.
- I cannot select a zip file for upload in the selection box. I have to manually write (or copy-paste) the name.
- When writing/editing post the cursor often disappears which makes writing very difficult.
Windows 8/8.1, Firefox
But IE11 (latest updates) is even worse - unusable on the forum.
I has to be a Windows 8/8.1 problem. Windows 7 & IE10 is fine.
I think that
should be
Changes indicated as bold, needed as code is not listed on obex, and it clarifies the policy for picky people