32

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


19

Yes, I'm very much in the wrong here. Touchstack was originally intended to be a smartphone web client for Stack Exchange sites (using the API), but I ended up rushing it out so I could show it to a few people. I posted it on Stack Apps as a work in progress, intending to update it over the next few days and bring in a lot of features that were missing. It ...


17

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 ...


16

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 ...


11

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


11

Any LaTeX/TeX code of mine that I publish on https://tex.stackexchange.com/ or https://tex.meta.stackexchange.com/ I hereby relicense under the LPPL (version 1.3c or later). Any Perl, Bash or other software programming language code of mine (with the explicit exception of LaTeX/TeX code) that I publish on https://tex.stackexchange.com/ or https://tex.meta....


11

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.


9

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.


7

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


7

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


7

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


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

Any LaTeX/TeX code of mine that I publish on https://tex.stackexchange.com/ or https://tex.meta.stackexchange.com/ I hereby relicense under the LPPL (version 1.3c or later). Any Perl, Bash or other software programming language code of mine (with the explicit exception of LaTeX/TeX code) that I publish on https://tex.stackexchange.com/ or https://tex.meta....


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 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

You can certainly already do this by indicating your license preference is for your posts in your "About Me" field, which is prominently displayed on your user page. I know I've seen several users do this on a few different Stack Exchange sites.


6

It looks pretty much legal to me, have a look at who's behind TouchStack. At least, it has been created through the SX web app system, and it looks ok with the moderators. One should also note that it does not seem to be importing the actual questions – more like, it seems to access them through Stack Exchange. Regarding what is legal or not, all ...


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


5

All posts on all stackexchange sites are under the CC license, originally v2.something, now v3.0. This license allows to share and adapt the content freely. You accepting this license when posting things here. I don't think the stackexchange people have anything against this. They actually provide an API to access all posts and touchstack seems to use it. ...


5

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 ...


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


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