Return to Answer

First, let's start by understanding which problems with the current licensing exist (if any). Each of these could be a Meta question, spaced out over time.

1. What is wrong with the status quo? What is the threat, if we do nothing? (Does your company limit your use of Stack Exchange due to legal concerns, for example?)
2. What are some specific or hypothetical use cases of code taken from Stack Exchange that we as a community consider abusive and worthy of legal action? (One example per answer, please. Let's vote.)
3. What are some specific concrete use cases of code taken from Stack Exchange that we as a community want to allow, no strings attached? (Cite one real post per answer.)
4. What are some specific concrete use cases of code, if any, taken from Stack Exchange that we as a community want to allow, but requiring some attribution at the point of use in a code comment?
5. What are some specific concrete use cases of code, if any, taken from Stack Exchange that we as a community want to allow, but requiring some attribution in the product's documentation?
6. Are the problems above solvable through code licensing? Can those goals be achieved within the CC-BY-SA framework, or by adjusting the site's Terms of Use?

Then, depending on the results of those discussions, we may be able to proceed with further discussions, each focusing on a logical next step.

First, let's start by understanding which problems with the current licensing exist (if any). Each of these could be a Meta question, spaced out over time.

1. What is wrong with the status quo? What is the threat, if we do nothing? (Does your company limit your use of Stack Exchange due to legal concerns, for example?)
2. What is right with the status quo? How have you (personally or as a member of the Stack Exchange community) benefitted from CC BY-SA 3.0?
3. What are some specific or hypothetical use cases of code taken from Stack Exchange that we as a community consider abusive and worthy of legal action? (One example per answer, please. Let's vote.)
4. What are some specific concrete use cases of code taken from Stack Exchange that we as a community want to allow, no strings attached? (Cite one real post per answer.)
5. What are some specific concrete use cases of code, if any, taken from Stack Exchange that we as a community want to allow, but requiring some attribution at the point of use in a code comment?
6. What are some specific concrete use cases of code, if any, taken from Stack Exchange that we as a community want to allow, but requiring some attribution in the product's documentation?
7. Are the problems above solvable through code licensing? Can those goals be achieved within the CC-BY-SA framework, or by adjusting the site's Terms of Use?

Then, depending on the results of those discussions, we may be able to proceed with further discussions, each focusing on a logical next step.

First, let's start by understanding the problem. Each of these could be a Meta question, spaced out over time.

1. What is wrong with the status quo? What is the threat, if we do nothing? (Does your company limit your use of Stack Exchange due to legal concerns, for example?)
2. What are some specific or hypothetical use cases of code taken from Stack Exchange that we as a community consider abusive and worthy of legal action? (One example per answer, please. Let's vote.)
3. What are some specific concrete use cases of code taken from Stack Exchange that we as a community want to allow, no strings attached? (Cite one real post per answer.)
4. What are some specific concrete use cases of code, if any, taken from Stack Exchange that we as a community want to allow, but requiring some attribution at the point of use in a code comment?
5. What are some specific concrete use cases of code, if any, taken from Stack Exchange that we as a community want to allow, but requiring some attribution in the product's documentation?
6. Are the problems above solvable through code licensing? Can those goals be achieved within the CC-BY-SA framework, or by adjusting the site's Terms of Use?

Then, depending on the results of those discussions, we may be able to proceed with further discussions, each focusing on a logical next step.

First, let's start by understanding which problems with the current licensing exist (if any). Each of these could be a Meta question, spaced out over time.

1. What is wrong with the status quo? What is the threat, if we do nothing? (Does your company limit your use of Stack Exchange due to legal concerns, for example?)
2. What are some specific or hypothetical use cases of code taken from Stack Exchange that we as a community consider abusive and worthy of legal action? (One example per answer, please. Let's vote.)
3. What are some specific concrete use cases of code taken from Stack Exchange that we as a community want to allow, no strings attached? (Cite one real post per answer.)
4. What are some specific concrete use cases of code, if any, taken from Stack Exchange that we as a community want to allow, but requiring some attribution at the point of use in a code comment?
5. What are some specific concrete use cases of code, if any, taken from Stack Exchange that we as a community want to allow, but requiring some attribution in the product's documentation?
6. Are the problems above solvable through code licensing? Can those goals be achieved within the CC-BY-SA framework, or by adjusting the site's Terms of Use?

Then, depending on the results of those discussions, we may be able to proceed with further discussions, each focusing on a logical next step.

First, let's start by understanding the problem. Each of these could be a Meta question, spaced out over time.

1. What is the threat, if we do nothing?
2. What are some specific or hypothetical use cases of code taken from Stack Exchange that we as a community consider abusive and worthy of legal action? (One example per answer, please. Let's vote.)
3. What are some specific concrete use cases of code taken from Stack Exchange that we as a community want to allow, no strings attached? (Cite one real post per answer.)
4. What are some specific concrete use cases of code, if any, taken from Stack Exchange that we as a community want to allow, but requiring some attribution at the point of use in a code comment?
5. What are some specific concrete use cases of code, if any, taken from Stack Exchange that we as a community want to allow, but requiring some attribution in the product's documentation?
6. Are the problems above solvable through code licensing? Can those goals be achieved within the CC-BY-SA framework, or by adjusting the site's Terms of Use?

Then, depending on the results of those discussions, we may be able to proceed with further discussions, each focusing on a logical next step.

First, let's start by understanding the problem. Each of these could be a Meta question, spaced out over time.

1. What is wrong with the status quo? What is the threat, if we do nothing? (Does your company limit your use of Stack Exchange due to legal concerns, for example?)
2. What are some specific or hypothetical use cases of code taken from Stack Exchange that we as a community consider abusive and worthy of legal action? (One example per answer, please. Let's vote.)
3. What are some specific concrete use cases of code taken from Stack Exchange that we as a community want to allow, no strings attached? (Cite one real post per answer.)
4. What are some specific concrete use cases of code, if any, taken from Stack Exchange that we as a community want to allow, but requiring some attribution at the point of use in a code comment?
5. What are some specific concrete use cases of code, if any, taken from Stack Exchange that we as a community want to allow, but requiring some attribution in the product's documentation?
6. Are the problems above solvable through code licensing? Can those goals be achieved within the CC-BY-SA framework, or by adjusting the site's Terms of Use?

Then, depending on the results of those discussions, we may be able to proceed with further discussions, each focusing on a logical next step.