nihilist/privacyguides.org
1
0
Fork 0
mirror of https://github.com/privacyguides/privacyguides.org synced 2024-11-10 05:03:34 +01:00
Code Issues Packages Projects Releases Wiki Activity

forum 2

Browse Source
This commit is contained in:
Jonah Aragon 2024-08-07 16:05:22 -05:00
parent 2988454e4e
commit fb38140ab7
No known key found for this signature in database
1 changed files with 13 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

15
docs/about/handbook/community.md
View File

@ -42,7 +42,7 @@ What is *less* important:
2. Every post being perfectly on-topic
3. Removal of duplicate posts
These things are *good*, but they are not critical for our forum to function effectively. You are empowered to fix these things, but if you have any doubt that you are making the right changes it may be better if you hold off on doing so.
These things are *good*, but they are not critical for our forum to function effectively. You are empowered to fix these things, but if you have any doubt that you are making the right changes it may be better if you hold off on doing so, or get a second opinion.
Generally speaking, the forum is divided into two overarching sections:
@ -53,6 +53,17 @@ A good rule of thumb when deciding where a post should go is whether the post wo
General [privacy](https://discuss.privacyguides.net/c/privacy/4) discussions on the other hand can be responded to by *any* experts within the community, and may be more open-ended.
### Low Effort Posts
Posts which...
- Duplicate an existing topic
- Ask a vague, open-ended question without adding their own opinion to the discussion
- Don't provide enough information to have a meaningful conversation
- Discuss something completely off-topic for our community
...can generally be [unlisted](#locking--unlisting-topics).
### Where Should Tool Discussions Go?
This is a tricky subject which essentially requires you to use your best judgement. At the end of the day, the [tool suggestion](https://discuss.privacyguides.net/c/site-development/suggestions/6) category is for discussing tools which someone might legitimately argue should be added to the website. Even if the community disagrees and we mark the tool as a "rejected" addition, it serves as a valuable reference point in the future and allows us to re-open discussions if circumstances change.
@ -63,7 +74,7 @@ On the other hand, it is more appropriate to have general discussions about some
For example, a post discussing the privacy problems and benefits of *Google Chrome* would not warrant a *Google Chrome* tool suggestion topic being made to fully evaluate it. Discussing privacy-relevant topics in non-private tools is on-topic for our general community, but does not necessitate any team feedback.
Posts that ask open-ended questions about a tool, like "what do you think about the privacy of x?" can usually be closed, but consider our guidelines on [closing topics](#locking--unlisting-topics) below first. Particularly, keep in mind that if a significant discussion has already occurred, it may be best to leave it as-is. Oftentimes, you should ask the poster to consider posting it to tool suggestions alongside an explanation of why they're personally considering it in the first place, so that it can be properly evaluated by the community.
Posts that ask open-ended questions about a tool without adding any opinions of their own, like simply "what do you think about the privacy of *x*?" can usually be closed as low-effort, but consider our guidelines on [closing topics](#locking--unlisting-topics) below first. Particularly, keep in mind that if a significant discussion has already occurred, it may be best to leave it as-is. Oftentimes, you should ask the poster to consider posting it to tool suggestions alongside an explanation of why they're personally considering it in the first place, so that it can be properly evaluated by the community.
### Question Posts