Timeline for We're switching to CommonMark
Current License: CC BY-SA 4.0
13 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 11, 2021 at 8:09 | review | Suggested edits | |||
| Oct 11, 2021 at 8:23 | |||||
| Jun 16, 2020 at 8:07 | history | edited | GlorfindelMod | CC BY-SA 4.0 |
added 52 characters in body
|
| Jun 16, 2020 at 7:57 | comment | added | TheLethalCarrot | This appears to be fixed. | |
| Jun 11, 2020 at 14:37 | comment | added | Roland | @YaakovEllis Retroactive fixes are not enough for license changes. This essentially means you can't trust the license displayed on Stack Exchange sites since you can't assume that the correct license is shown. Personally, I don't care because I don't reuse content in a commercial setting but others do that ... | |
| Jun 3, 2020 at 14:38 | comment | added | Yaakov Ellis StaffMod | For the initial test sites, these edits will show up as being licensed. A fix in is being worked on right now, and will be retroactive when it goes up. See here for more information. | |
| Jun 3, 2020 at 14:09 | comment | added | Catija Staff | From what I understand, the fix encompasses things like the change to HTTPS, so it's going to be retroactive by default since most of the changes are years-old. | |
| Jun 3, 2020 at 14:06 | history | edited | GlorfindelMod | CC BY-SA 4.0 |
added 276 characters in body
|
| Jun 1, 2020 at 20:57 | comment | added | NoDataDumpNoContribution | The edits cannot really cause a license change because they may be inserted in the timeline, and you don't want to jump to a higher CC version and then down again. It could become tricky if someone inserted a space after a leading # by him/herself and changed other things in an edit. Not sure, what the community bot wants to do in that case so enable earlier revisions to be in commonmark. | |
| Jun 1, 2020 at 19:59 | review | Suggested edits | |||
| Jun 1, 2020 at 20:21 | |||||
| Jun 1, 2020 at 15:04 | comment | added | Yaakov Ellis StaffMod | These edits will not cause a license change (I am working on a bunch of follow-up items for licensing, this will be included) | |
| Jun 1, 2020 at 14:52 | comment | added | Thomas Owens | This is key. I think it's already problematic that all edits, including minor edits and the automatic HTTP->HTTPS edits changed the license. This would affect even more posts than those, I would suspect. Handling the license needs to be thought through very carefully. | |
| Jun 1, 2020 at 14:11 | comment | added | ilkkachu | You could read that version history as saying the edits made by Community are licensed under CC BY-SA 3.0... But the text on top, "Current License: CC BY-SA 3.0" is obviously wrong. And worse, if the last edit changes the license shown for the whole post, it'll change not only for automated modifications, but even if some other human user than the author makes some minor edit. It's not that rare for a user to write a substantial answer, which is then then copy-edited/clarified/expanded by another. Usually close to the original posting, sure, but sometimes much later. | |
| Jun 1, 2020 at 12:15 | history | answered | GlorfindelMod | CC BY-SA 4.0 |