-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments #48
Comments
Alternatively, someone could set up diqus 😄 |
eh i'm busy today. gotta defend |
👎 I dislike comments on things like this. Put a link to the issues instead and point people here. |
Judging by the process on this issue, I would say that a "comments section" is a bad idea for one reason: needing active moderation. From simple spam to harassment or abuse, it could be a lot of work to maintain and need that work promptly. Who wants to maintain something else right now? |
Perhaps these are discussions best left to current students :)
…On Thu, Aug 3, 2017, 9:13 PM Thomas Russell Murphy ***@***.***> wrote:
Judging by the process on this issue, I would say that a "comments
section" is a bad idea for one reason: needing active moderation. From
simple spam to harassment or abuse, it could be a lot of work to maintain
and need that work promptly. Who wants to maintain something *else* right
now?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#48 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AFa1U7sFvfdnmZ_jsvs4EojrhoGMCVC-ks5sUppdgaJpZM4Nvje8>
.
|
If possible, it might be useful to implement a comment system where people can (anonymously or not) write a comment on a page, maybe regarding the page's readability and usefulness, or even mentioning information that was left out.
Or just have a friendly note on each page pointing readers to this repo if they have any issues with the wiki. That would be simpler, although the Issues tab might get a bit flooded with comments on multiple different pages. Additionally, it would slightly raise the "barrier to entry" for HacSoc / CS newcomers who are unfamiliar with this site, repo, etc.
The text was updated successfully, but these errors were encountered: