Timeline for Help us identify new roles for community members
Current License: CC BY-SA 4.0
7 events
when toggle format | what | by | license | comment | |
---|---|---|---|---|---|
Dec 4, 2022 at 12:27 | comment | added | Braiam | @starball that process was created to introduce as much friction as possible in the system because it's usually thought out as a general waste of time. But I see it more as a lack of appropriated tooling that will make those actions painless. | |
Dec 1, 2022 at 13:41 | history | edited | This_is_NOT_a_forum | CC BY-SA 4.0 |
Active reading [<https://en.wikipedia.org/wiki/Q%26A_software> <https://en.wiktionary.org/wiki/ongoing#Adjective> <https://en.wikipedia.org/wiki/Sentence_clause_structure#Run-on_sentences>].
|
S Dec 1, 2022 at 9:49 | history | suggested | janw | CC BY-SA 4.0 |
Add brackets around "basic" to clarify that it is the name of an actual tag; slight punctuation fixes
|
Dec 1, 2022 at 9:22 | review | Suggested edits | |||
S Dec 1, 2022 at 9:49 | |||||
Dec 1, 2022 at 3:02 | comment | added | starball | It feel weird to me that there's such carefully thought out criteria for whether a tag should be burninated (such as being non-ambiguous), and formal procedure with community dialogue and SME consultation, but that I've never heard of any such formality for tag creation (granted, I don't know much about tag creation having never done it myself). Maybe the tag creation process could learn a thing or two from the burnination process or the area51 process (which I also know next to nothing about, but in my mind, somehow the creation of a tag has some conceptual likeness to creation of a site). | |
Dec 1, 2022 at 2:56 | history | edited | Henry Ecker | CC BY-SA 4.0 |
Incorrect word; typo;
|
Dec 1, 2022 at 2:51 | history | answered | Henry Ecker | CC BY-SA 4.0 |