We want to try experimenting with making space for more collaborative content gardening here on meta, where users who want to help tidy various parts of the forum can coordinate directly with each other.
Think of this topic as a place to discuss things that are worth tidying, but may be too trivial to deserve their own topic or to be flagged.
We expect this process may evolve into something more sophisticated, but we want to start lean, using a single topic, and learn by doing together.
How it works
This first post as a living document, capturing our guidelines for this activity. As we discover things that feel like they are working (or not working), weāll capture them here for reference.
Kinds of things we want to tidy together
Move topics to the appropriate category
Tag completed feature, bug, or UX topics with appropriate tags[1]
Close topics that are no longer relevant
Mark solutions for topics in the Support category and subcategories
Deduplicate topics by merging them or closing duplicates with links to canonical topic
Delete or unlist obsolete topics
What to post about here
Clarify what or how to tidy
Ask clarifying questions about the above guidelines or specific cases
(Larger discussions can be split out into their own topics)
Suggest things to tidy
Point out topics that you think should be tidied, if you donāt have the power to do it yourself
Share work youāve done if itād help us learn
We donāt need to share all our work, but do share if some action weāve taken is a helpful example for others to learn from
What not to do
Donāt @ people
People who want to participate will follow this topic and engage on their own time
Donāt use for typos
Some things are trivial enough issues to just leave be
Donāt use as a replacement for flags that need moderator attention
Posts that need moderator attention should still be flagged
Wonāt this topic get messy? How do we keep it tidy?
This is a topic for active collaboration among those who choose to participate. Itāll be messy, but thatās OK, as long as the mess isnāt getting in the way of doing the work.
If the mess is getting in our way of doing the work, weāll discuss what to do about it.
Sounds like we may need to revisit the guidelines weāve created for ourselves with those tags in documentation (thatās probably a conversation that deserves its own topic).
Oh, are you not able to add those ones yourself @Moin?
If so, Iād say go ahead and tag them.
You can share changes youāve made here if you want another set of eyes on them, or you can ask first if youāre unclear whether they should be tagged.
Iām also learning my way around what powers different people do and donāt have, so we can make the appropriate adjustments there as well as we figure that part of things out.
If I was able to tag them myself I would have done so. But I donāt have permission to create topics in these categories and because of that edit_all_topics permissions donāt help me.
The author is notified. Users watching the topic would only be notified if it was the first post.
I am curious why you prefer a notification compared to seeing that something was done right where it was posted. If someone was reading this topic now, seeing right at Experiment: Collaborative content gardening hub for meta - #8 by Moin if these were done, could be easier than checking all the replies if someone already added the tags.
Checkboxes are great, Iām just wondering down the road whether people will find an old existing reply and add issues to a list ā and would anyone notice if they did. Maybe I misunderstand the intent.
I thought the intent was that more users could check the checkbox. You need edit permission on the post for that, which the wiki would add for TL2+.
But only TL3 can make their own post a wiki, so I am not sure itās that helpful. Something a TL3 cannot do on their own likely needs a TL4, and those can edit the posts without them being a wiki.
