Skip to content

Encourage using this repo for meta discussion#62

Merged
MadaraUchiha merged 1 commit intoJavaScriptRoom:masterfrom
kendfrey:master
Apr 30, 2018
Merged

Encourage using this repo for meta discussion#62
MadaraUchiha merged 1 commit intoJavaScriptRoom:masterfrom
kendfrey:master

Conversation

@kendfrey
Copy link
Copy Markdown
Contributor

I think we need to be more helpful in guiding users to this repo for any complaints about the topics, conversations, people, and especially room owners of Room 17. To this end I've edited the readme and added some clarifying information.

We should avoid discussing these issues extensively in chat itself, as that tends to stir up emotions very quickly, and ROs that aren't present at the time don't get to contribute. If someone complains about being kicked or some other RO action, we should gently point them here, and only kick if they continue to make a disturbance in the room proper.

Thoughts?

If we agree that this is what we want, my next proposal will be to change Caprica's welcome message to include a link to this repo, so new users know where to go when they want to report a problem.

@oliversalzburg
Copy link
Copy Markdown

Someone remind me why we aren't directing people to https://meta.stackoverflow.com/questions/ask?tags=discussion,chat,javascript-room and ask ROs to subscribe to that javascript-room tag or whatever.

That's where everyone already has an account and it's the designated place for meta discussion on the network. Why was GitHub selected as the platform of choice for this in the first place?

@ssube
Copy link
Copy Markdown

ssube commented Apr 29, 2018

@oliversalzburg at least in part, because meta doesn't have threaded conversation. It might be a better place than Github for taking votes on a Q and some As, but we need a side channel to discuss those conclusions.

@benjamingr
Copy link
Copy Markdown
Contributor

Also because we don't want every single user in StackOverflow having to go through our stuff in order to decide on our policy and it would be rude of us to ask for their time whenever any user has an issue.

Copy link
Copy Markdown
Contributor

@benjamingr benjamingr left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm 100% behind this change

@benjamingr
Copy link
Copy Markdown
Contributor

Given the 9 +1s and 2 approvals and the fact we don't have an official policy for these sort of PRs - I think this is safe to land.

@MadaraUchiha MadaraUchiha merged commit ecec0ce into JavaScriptRoom:master Apr 30, 2018
@kendfrey
Copy link
Copy Markdown
Contributor Author

I've created a Caprica PR including linking to this repo in the welcome message: Zirak/SO-ChatBot#301. Comments welcome.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants