Is rendering Markdown to HTML considered an &quot;adaptation&quot; under CC BY-SA 3.0? Title pretty much sums it up. Are the rights given to adaptations granted if someone renders Markdown?
Usually not, usually Translating literary works is generally regarded as an adaptation, but I don't think translation programs—and HTML and Markdown, two markup languages with similar principles—are adaptations. According to the description on Creative Commons, Merely changing the format never creates a derivative. So changing WAV to MP3 is not considered an adaptation, nor is changing DOC to PDF. As for HTML and Markdown, it seems a bit vague, but it can be said that although their encoding methods are different, the results presented are very similar. According to https://creativecommons.org/faq/#when-is-my-use-considered-an-adaptation, a modification rises to the level of an adaptation under copyright law when the modified work is based on the prior work but manifests sufficient new creativity to be copyrightable Adaptation produces a derivative. A derivative contains both the will of the original author and the adapter. Creation involves choice, the painter chooses the colors to use, and the translator chooses the words to translate. There are inherently fewer options to create a program. Rendering markdown to html can be done directly through other programs, and it is difficult to see the shadow of the adapter. Editorial originality is very import. Yet one more thing is important: legal definitions. This is what it says in the https://creativecommons.org/faq/#what-is-an-adaptation FQA page What constitutes an adaptation depends on applicable law So, the laws of where you live still matter. We all know that there is a large gray area in copyright law, which often makes everything depend on the actual situation. This is just a little bit of my personal thoughts for your reference :)
What happened is that you created a legal mess. You are obviously on the hook for copyright infringement. The maintainers of the project will scramble to replace your code with newly written code. They will likely ask your company which code they are complaining about - that puts your company into the problematic situation that they shouldn't identify code that isn't theirs, that it will be hard to sue for infringing code when they didn't give the project maintainers a chance to fix it, and that everything they identify will be replaced. Since it is your actions that caused the trouble, anyone suffering damages from your actions can sue you.
You can read it, you can examine it to the point where you understand it, and then you can get inspired by the code and write your own code, without copying the code on the website, which does the same thing. If there is no license, then you can do what copyright law allows you to do. You are not allowed to copy the code, or create derived works by taking the code and modifying it.
You can't Under clause 7(b) of the CC-SA-BY 3.0 the licence is irrevocable providing that the licensee complies with its terms. However, ... It appears that your work is part of a Collection (as defined and under clause 4(a), the licensee has this obligation: If You create a Collection, upon notice from any Licensor You must, to the extent practicable, remove from the Collection any credit as required by Section 4(c), as requested. While you cannot have your work removed, you can have the attribution removed so that no one knows that it is your work - this would seem to meet your desire of having no association with the website. "To the extent practicable" should include anonymising you. As a bonus, if they don't do this "to the extent practicable" then they are in breach of the licence and it's automatically revoked - you can then proceed with DCMA takedown notices and/or sue for copyright breach.
The terms transfer IP rights only for the New IP, meaning that Customer would own the new stuff. Developer will still own their old stuff, but Customer will have the right to use the old stuff, depending on the license terms. If the license is as in your link, then it is forever (but this is a stub, so I assume that the license will be more specific and possibly restrictive). You retain all your rights to old stuff, customer will not pay royalties for the old stuff, and they can transfer or extend the license, or part of the license, to others.
The first thing that people need to do is to quit over thinking it. That being said, I'm going to see if I can tackle your problems one by one, before summarizing and providing my own opinion: Many users don't care if their code is copied. I'm like that. I left a couple comments on Shog9's post that read this: Good point: Licensing does not prevent careless or malicious use. I'm surprised about how many people are thinking that this license will let them steal their code, because it's already happening right now. I don't want to sound pessimistic, but when thousands of people break a license/law/contract, it's a bit of a lost cause. You're not significantly damaged in a direct way, so honestly, let it go. All I want is to make sure that no one can come up to me if something of mine screwed something on there side. Aside from that, I don't care about people who don't attribute me: chances are, they have no moral sanity, and I will appreciate the people who do, and help me out. As it is, I'm 16, I share what I know with a good heart, and in a well-spirited manner, and at the end of the day, knowing that I was able to help someone out makes my day. I don't mind if my code is copied. I know that people will copy my code whether I like it or not, but I also know that there will be people in the world who will say "thanks", and will try to attribute me where possible. I feel good about that. That being said, I don't care. But the person who uses my code does. The license that affects all Stack Exchange posts are licensed under the Creative Commons Attribution Share-Alike license, or CC BY-SA. Code contributions don't fit well with this. This excellent post on Open Source explains why it's discouraged for code. What these people want is a code-friendly license, so that they can stay in the clear when it comes to copyright issues. The next thing they want, is for someone to come after them over some licensing issue. You may think that people are good, but you never know the world around you. They can be evil. For other users, they don't mind their code being copied to another post, as long as there is a link to the post and a mention of the original author. Most people post with good intention. There's not that much of an issue from a legal perspective either: The license allows people to copy and paste into answers of their own, and since the license remains the same, there's no issue to get into. The license allows it, and contributors kind of have to acknowledge it. I don't think anyone cares what happens to code that is less than 3-4 lines at least. I can probably agree. Such code probably wouldn't be eligible for copyright anyway, since it's so trivial. Many jurisdictions have a "Threshold of Originality," which means that simple things can't be under copyright. Stack Exchange does not probably want people to own the code they submit. For example, Stack Exchange has (and probably wishes to retain) the right to keep even deleted posts in the visibility of the high rep users (even if the author is against it). Wait what? You may be right that it is in Stack Exchange's interest to host content. After all, they get hits, which helps them as a business. It is illegal for companies to host illegal content. If somebody sees objectionable, copyrighted content hosted on Stack Exchange that they would like removed, then they need to file a DMCA Takedown Request. This is also why moderators, like myself, cannot process legal requests. The reason why Stack Exchange doesn't act themselves, even if they see something that is copyrighted and objectionable, is because it's a form of liability. When YouTube began removing copyrighted content themselves, they received a wave of lawsuits (If you remove some, you need to remove all. Why didn't you remove mine? being the argument). The plaintiff's won those, and when YouTube did nothing, they weren't liable at all. If a user wants to have their content taken down, it's tricky. You need to look at the Terms of Service for Stack Exchange: (quoting Section 3) You agree that all Subscriber Content that You contribute to the Network is perpetually and irrevocably licensed to Stack Exchange When Stack Exchanges gets your content, you grant them an irrevocable license to your contribution. This is pretty standard across a lot of sites: it's just a way to secure data and stay in the clear of licensing issues. At the same time, it doesn't seem fair for SE to acquire complete ownership of the content. The user must still have the final say, if the content is to be used for purposes not already agreed upon in the licence. They don't. What users have done is that they have provided a license of their content to Stack Exchange. This is done, again, through their Terms of Service: You grant Stack Exchange the perpetual and irrevocable right and license to use, copy, cache, publish, display, distribute, modify, create derivative works and store such Subscriber Content and to allow others to do so in any medium now known or hereinafter developed (“Content License”) in order to provide the Services, even if such Subscriber Content has been contributed and subsequently removed by You. The user grants a license to their content to Stack Exchange, but they do not assign or relinquish copyright. The code still belongs to them. It's important not to conflate the user contribution policy, with copyright assignment. You are still free to add an additional license to your content (known as dual or multi-licensing), and have a copy for your own use. Stack Exchange will always host a copy licensed under the CC BY-SA license. Stack Exchange can expect a high level of decorum and respect for laws from its users. At the same time, it cannot expect redundant attributions anywhere and everywhere, because one of its main aims is to not waste the users' time. Not only Stack Exchange expects it, but many copyright laws in various jurisdictions require it too. There's a concept known in many jurisdictions known as moral rights. These are rights that are irrevocable, whether you like it or not. Generally, these include attributions, disclaimer of liability, and other rights as well. Even if your work is in the public domain, you still retain these moral rights. If memory serves me right, the right to be attributed is revokable under United States copyright law. Therefore, attribution becomes more a courtesy, when the right is revoked. Licenses such as CC BY, and CC BY-SA still require attribution as a part of their licensing terms. What defines attribution is generally up to the person who uses the content. If memory serves right again, one can not demand how to attribute. There should be a clear-cut way to determine what is code and what isn't. The code formatting indicators on SE may not be adequate because some users simply use backticks, or 4-space indented text for other not-so-codey text. Personally, I feel like making the entirety of a post under both the Creative Commons license and whatever proposed code license they use is the best option, and allow people to use moral judgement to determine the most appropriate license. The concern comes about people who lack such judgment. I bet these same people don't follow the existing license anyway - and are a lost cause. We made it through! There will always be debate on the license of choice. Some people want the GPL, a license that's apparently closer to the status quo of Creative Commons license (I disagree that it's a good match), while other's want permissive licenses, such as the MIT or the Apache licenses. I'd prefer the permissive type, since it allows use in closed-source applications, and grant more rights (i.e. less restrictions) to the people that use them. I'm not going to right much because my hands are tired, but I'm sure if you've got more questions about the open source licenses themselves, you can probably ask on Open Source Stack Exchange.
You automatically have copyright protection for what you create. A collection of numeric answers to math equations probably would not qualify (lack of requisite creativity), but certainly anything that counts as a "paper" is protected.
Ideas (methods of playing, game mechanics, strategy, goals) cannot be protected by copyright. But any part of a creative work can. So, no copying of drawings, patterns, images, sounds, or the element. I suppose copying the software code is not an issue here, but it can, obviously, also not be copied. And nothing in your game can look like someone's else trademark.