33

Personally I don't think it's our place to be policing supposed use of unlicensed anything unless the question is about how to get the fonts illegally or circumvent the licence in some way. I especially don't think we should be making assumptions about where people got their fonts from if they are asking an otherwise legitimate question. So questions ...


29

They can be reported on Meta Stack Overflow - ZQNA was already added by @doncherry: Report sites that use SE content without following attribution rules here


18

I think the site is clear that you retain copyright, so as Joseph has already said, you are free to do anything with your own codes, including using them or making them available to others at a different location under a different (or same) licence. It's worth noting that option 1 is not really available: even if you edit or delete the text anyone with a ...


17

The site license says that when you post code, the material is available to others under the CC-SA conditions. That means that for example you can't simply 'pull' all of the content: important so that the material remains available for others, and particularly reflects the fact that as others can edit, it's hard to say content is '100% yours'. However, you ...


13

Any code of mine that I publish on https://tex.stackexchange.com/ I hereby relicense under the LPPL, version 1.3 or later (not author maintained). Enrico Gregorio


12

We have a couple of methods for dealing with the problem: commenting; editing. A comment could be something like Please edit your question, because, as it's formulated now, it can raise some doubts about copyright issues. On the other hand, how the questioner came in possession of the fonts is usually not relevant for solving the problem, so an edit ...


10

Any code of mine that I publish on https://tex.stackexchange.com/ I hereby place in the public domain to the extent governable by law. Explicitly, I place it under the CC0.


10

Any code of mine that I publish or have published previously on the TeX.SE main site I hereby relicense under the WTFPL.


7

Any code of mine that I publish on https://tex.stackexchange.com/ I hereby place under the LPPL, version 1.3 or later.


6

Any TeX code of mine that I publish on https://tex.stackexchange.com/ I hereby place in the public domain to the extent governable by law. Explicitly, I place it under the CC0. Note Regarding Attribution Code that is placed in the public domain does not require attribution. However, if you have found this site useful, the best way to say "Thank you" is to ...


6

Any code of mine that I publish on https://tex.stackexchange.com/ I hereby place in the public domain to the extent governable by law. Explicitly, I place it under the CC0.


6

Any code of mine (TeX, LaTeX, bash, ImageMagick or any other) that I publish on https://tex.stackexchange.com/ or https://tex.meta.stackexchange.com/ or in chat rooms associated with the site I hereby give permission for it to be used and released under either LPPL license in version 1.3 or higher. The works itself, if applicable, fall into the category "...


6

Any code (or any stuff for more general) of mine that I publish or have published previously on https://tex.stackexchange.com/ is free as in "free of charge" and "freedom". You can claim it as yours. No attribution or permission is needed.


6

Do not do option one. The code will not be destroyed, but there are no good automated systems to repair the damage. This means SE employees, site moderators, and high rep users will have to do a lot of work to repair the vandalism. As for legal trouble, I don't think you need to worry. In countries in which there is a presumption of innocence, in order to ...


5

The issue with showing it in your profile is that there is no public history of it. If you post your license statement in the thread Relicensing code from answers , the information is there forever, with precise dating and timing, which allows to backtrace the correct license for each piece of code you published here.


5

Any code of mine that I publish on https://tex.stackexchange.com/ I hereby relicense under the WTFPL.


5

Any code of mine that I publish on TeX.SX I hereby relicense under the LPPL. Claudio


4

Any code of mine that I publish on https://tex.stackexchange.com/ I hereby relicense under the LPPL. JB


4

Any code of mine that I publish on https://tex.stackexchange.com/ I hereby place in the public domain to the extent governable by law. Explicitly, I place it under the CC0.


4

Any code of mine that I publish or have published previously on https://tex.stackexchange.com/ I hereby relicense under the LPPL. Mikko Korpela


4

Any TeX code of mine I publish and published on https://tex.stackexchange.com/ I hereby license as Beer-Ware. If you reuse it it should contain the following comment: % ---------------------------------------------------------------------------- % "THE BEER-WARE LICENSE" (Revision 42): % Jonathan P. Spratte wrote this code. As long as you retain this ...


4

Perhaps StackExchange should consider offering text under CC and code under e.g. BSD/MIT license (this would automatically include LaTeX snippets, and make them LLPL-compatible). (Yes, that opens a can of worms full to the rim with "what is text, what is code", and "can I use the question/answer/comment in the documentation", so that is only a partial ...


4

Any code of mine that I publish on https://tex.stackexchange.com/ I hereby place in the public domain to the extent governable by law. Explicitly, I place it under the CC0.


4

First of all it should be noted that since you are the author of your codes, you will retain the full copyright under any normal jurisdiction (except maybe Cuba or North Korea). At this point it is completely irrelevant what the TeX.SX FAQ or whatever says, because they are not above the law. This is also a common misconception and people think it is ...


3

Any code of mine that I publish on https://tex.stackexchange.com/ I hereby place under the LPPL, version 1.3 or later.


3

Any code or in general anything of mine that I publish or have published previously on https://tex.stackexchange.com/ is free as in "free of charge" and "freedom". You can claim it as yours. No attribution or permission is needed. May the source be with you. RGS


2

Any code of mine that I have published or will publish on https://tex.stackexchange.com/ can be used under the terms of the LaTeX Project Public License either version 1.2 or, at your option, any later version. This license is granted in addition to the terms that apply by default to contents published on https://tex.stackexchange.com/. Florent Rougon


2

Any strings of characters, that I posted previously or I will post in the future to this site, automatically belong to you and are not mine. I am not responsible for any gain or loss of using them. Please refrain from contacting me for granting royalty or attribution. I am not collecting money let alone popularity. :-)


2

Any code of mine that is published on https://tex.stackexchange.com/ I hereby place in the public domain to the extent governable by law, except when stated otherwise in the corresponding answer. Explicitly, I place such code under the CC0.


Only top voted, non community-wiki answers of a minimum length are eligible