Communities

Writing
Writing
Codidact Meta
Codidact Meta
The Great Outdoors
The Great Outdoors
Photography & Video
Photography & Video
Scientific Speculation
Scientific Speculation
Cooking
Cooking
Electrical Engineering
Electrical Engineering
Judaism
Judaism
Languages & Linguistics
Languages & Linguistics
Software Development
Software Development
Mathematics
Mathematics
Christianity
Christianity
Code Golf
Code Golf
Music
Music
Physics
Physics
Linux Systems
Linux Systems
Power Users
Power Users
Tabletop RPGs
Tabletop RPGs
Community Proposals
Community Proposals
tag:snake search within a tag
answers:0 unanswered questions
user:xxxx search by author id
score:0.5 posts with 0.5+ score
"snake oil" exact phrase
votes:4 posts with 4+ votes
created:<1w created < 1 week ago
post_type:xxxx type of post
Search help
Notifications
Mark all as read See all your notifications »
Q&A

Welcome to Codidact Meta!

Codidact Meta is the meta-discussion site for the Codidact community network and the Codidact software. Whether you have bug reports or feature requests, support questions or rule discussions that touch the whole network – this is the site for you.

Comments on Please allow specifying license for answers

Parent

Please allow specifying license for answers

+3
−0

While one can specify a license when making a question, when writing an answer there doesn't seem to be any place to specify and it just ends up saying "CC BY-SA 4.0" once posted.

While asking a good question can be a lot of work, so can writing a good answer and it'd be nice to be able to specify a license. This may be even more important for technical sites where answers could include code, but I suspect it'd be useful on a lot of sites.

(I'd also like a way to edit a license once something's been posted, but that's probably more complicated, especially if there are multiple editors of the text. It could be a little weird that the original author picking a license ends up selecting the license that any editors of that post are forced to contribute their changes under, though, especially if the editor isn't expecting that.)

History
Why does this post require attention from curators or moderators?
You might want to add some details to your flag.
Why should this post be closed?

1 comment thread

General comments (5 comments)
Post
+3
−0

I'm... surprised nobody noticed this earlier. I've added the license picker to the answer form now, pending deploy.

Changing a license after a post has been created is [status-declined] for now at least - there's very real chance of creating confusion or legal ambiguity that way, which we'd rather avoid. We might be able to revisit this down the line once we have time to look and design in more detail, but I'm not going to make any promises.

History
Why does this post require attention from curators or moderators?
You might want to add some details to your flag.

1 comment thread

General comments (2 comments)
General comments
Peter Cooper Jr.‭ wrote over 4 years ago

Thank you. And yes, editing licenses definitely opens a can of legal worms.

ArtOfCode‭ wrote over 4 years ago

Legal worms... worms in wigs and robes... there's a thought.