I wanted to share my experience as a TL4 on many technical (and a few non-technical) Discourse instances.
I share a lot of reservations about editing other folks’ content. I was surprised to find that most of my “edits” were:
- changing the category or tag to a more appropriate one (for instance, for the product or team in question, so the correct people read their messages)
- fixing code snippets, which means tracking down and closing the code brackets
- I’m the first to notice someone asks their content be edited for a reason (sharing file paths in a code snippet, where they’d rather not, for instance)
- broken links because of extra characters (example.com,)
All these communities I was on teams with other volunteers, and we are all present and aware of each other’s edits; it’s a nice practice to double-check. And what I noticed is no one edited to fix language, per se. Rather than copywriting, it is a kind of standard to “quote and clarify”.
I believe it’s standard because that’s what all of us can do, for our entire “career” in Discourse, if we see something amiss: quote and clarify. And if the conversation is contemporaneous, the original poster is normally able to edit their topic (per site configuration, so it’s different for diff sites). That’s a great feature of Discourse, and takes off a lot of potential work for TL4s.
Finally, I wanted to share a tip that I think kinda speaks to a few concerns expressed here, but indirectly: the Discourse Solved plugin.
It may be configured for trust levels to be able to mark any topic as solved, and useful for TL4. For really long discussions, decisions get made, great arguments are had, and possibly more conversations have spun off. So rather than creating a digest with links and all and editing the topic, a TL4 may post a reply (or choose a suitable one) and mark it as the “solution” for that topic, which will show prominently at the top of the discussion. You get the benefit of annotation, with all the history intact.
(I’m not sure how a lot of this site is configured, as I mostly read it via RSS.)