To be clear, the thing that made me feel weird is the implication that this would be applied retroactively and without explicit consent from you each user (which I assume is not what was meant, but it is how it read to me).
I’m perfectly fine with contributions going forward requiring a specific license as in arXiv (preferably requiring a minimal license that basically allows reproduction in the EA Forum and then having default options for more permissive licenses), as long as this is clearly explained (eg a disclaimer below the publish button, a pop-up, or a menu requiring you to choose a license).
I am also fine applying this change retroactively, as long as authors give their explicit permissions and have a chance before of removing content they do not want to be released this way.
Ah, thanks for the clarification. Yes, I agree that retroactive application raises separate issues. Maybe there are precedents of this that we could copy, or learn from.
The Stack Overflow case [1] that Thomas linked to in another comment seems a good place to learn from.
I think multiple license support on a post-by-post basis is a must. Old posts must be licensed as all-rights-reserved, except for the right of publication on the Forum (which is understood that the authors have granted de facto when they published).
New posts can be required to use a particular license or (even better) users can choose what license to use, with the default being preferably CC-BY per the discussion on other comments.
The license on all posts should be ideally updatable at will, and I would see it as positive to nudge users to update the license in old posts to CC-BY (perhaps sending them an email or a popup next time they log in that gathers their explicit permission to do so).
To be clear, the thing that made me feel weird is the implication that this would be applied retroactively and without explicit consent from you each user (which I assume is not what was meant, but it is how it read to me).
I’m perfectly fine with contributions going forward requiring a specific license as in arXiv (preferably requiring a minimal license that basically allows reproduction in the EA Forum and then having default options for more permissive licenses), as long as this is clearly explained (eg a disclaimer below the publish button, a pop-up, or a menu requiring you to choose a license).
I am also fine applying this change retroactively, as long as authors give their explicit permissions and have a chance before of removing content they do not want to be released this way.
Ah, thanks for the clarification. Yes, I agree that retroactive application raises separate issues. Maybe there are precedents of this that we could copy, or learn from.
The Stack Overflow case [1] that Thomas linked to in another comment seems a good place to learn from.
I think multiple license support on a post-by-post basis is a must. Old posts must be licensed as all-rights-reserved, except for the right of publication on the Forum (which is understood that the authors have granted de facto when they published).
New posts can be required to use a particular license or (even better) users can choose what license to use, with the default being preferably CC-BY per the discussion on other comments.
The license on all posts should be ideally updatable at will, and I would see it as positive to nudge users to update the license in old posts to CC-BY (perhaps sending them an email or a popup next time they log in that gathers their explicit permission to do so).
[1] https://meta.stackexchange.com/questions/333089/stack-exchange-and-stack-overflow-have-moved-to-cc-by-sa-4-0