Discord/RfC

The following discussion is closed. Please do not modify it. Subsequent comments should be made in a new section.

Proposals 1.1, 1.5, 2.2, 2.3.1 and 2.4 have passed. Proposal 2.1 for a FAQ has not passed but instead there is support for an #server-info channel which has passed. Regarding proposal 1.6 which calls for establishing an audio channel, there is mixed support so a channel will be created on an experimental basis and if it is not used it will be removed. Reception123 (talk) (C) 05:52, 27 August 2019 (UTC)

---

Anything not covered will remain in line with status quo.

The following page is a voting section to determine the changes to the discord server following a consultation.

Any user is free to add their own questions within reason and may adapt the existing question up until the RfC starts. Sections should only be closed after that point by someone with the ability to implement the changes (even if it is against) unless the discussion gets out of hand. Threaded discussion is permitted but if it gets long may be moved to the comments section or Talk Page.

• Opened: ~ RhinosF1 - _(chat) ^{· CA · contribs · Rights} - on) 12:05, 16 August 2019 (UTC)

New channels

Should a rules channel be created?

Support

1.  Support Discord rules should be clear on a specific page. Reception123 (talk) (C) 14:11, 16 August 2019 (UTC)
2.  Strong support We need a on server area for rules. ~ RhinosF1 - _(chat) ^{· CA · contribs · Rights} - on) 14:59, 16 August 2019 (UTC)
3.  Support Something basic for the coexistence of people on a server is always the rules. --Dark Dragoon (talk) 11:22, 18 August 2019 (UTC)
4.  Strong support Always good to have guidelines for the server. -- Elaeagnifolia (talk) 20:26, 22 August 2019 (UTC)

Should a read-only FAQ channel be created?

Support

1.  Support as long as it's kept up to date. ~ RhinosF1 - _(chat) ^{· CA · contribs · Rights} - on) 14:59, 16 August 2019 (UTC)

Oppose

1.  Oppose I think linking the on-wiki FAQ is enough. Reception123 (talk) (C) 14:56, 16 August 2019 (UTC)
2.  Oppose This section (and probably others) proposes that the same information be available in multiple formats. Some questions come to mind: Who's going to keep the Discord copy aligned with future changes to FAQ? If the versions differ, which is authoritative? What do we do with a good-faith user acting in accordance with an out-of-date duplicate? Anyone should be free to write his own summary of Miraheze essentials, with links to the official ones. But the official ones should continue to be wiki pages on Meta, Miraheze being a wiki farm and not a chat farm. Spıke (talk)20:54 22-Aug-2019

Comments

1. I think a #info channel for basic information and some useful links is more productive than a #faq channel. --Dark Dragoon (talk) 11:27, 18 August 2019 (UTC)

   I think this is a solid idea. Other Discord servers I'm in have this type of "info" channel, often called #server-info, which provides a brief overview of the server as well as links to helpful related resources. Something like this, perhaps? -- Elaeagnifolia (talk) 20:26, 22 August 2019 (UTC)

   I  Support having a #info channel and think that would work if we used Elaeagnifolia's draft. Shall we add it properly to the RfC? ~ RhinosF1 - _(chat) ^{· CA · contribs · Rights} - on) 08:50, 23 August 2019 (UTC)

fix ping ~ RhinosF1 - _(chat) ^{· CA · contribs · Rights} - on) 08:51, 23 August 2019 (UTC)

Should a separate help channel be created?

Support

1.  Weak support I personally support the idea of splitting #general and #help chatter, but I can also see the arguments for opposing the split due to not enough traffic. -- Elaeagnifolia (talk) 20:26, 22 August 2019 (UTC)

Oppose

1.  Oppose Was not sure about this but finally have decided to vote against, because currently #general is mostly concentrated on helping people, and #irc-relay is more useful for getting help at this time. Reception123 (talk) (C) 14:11, 16 August 2019 (UTC)
2.  Weak oppose No need, not enough traffic. Asking between #general and #irc-relay is confusing enough. ~ RhinosF1 - _(chat) ^{· CA · contribs · Rights} - on) 14:59, 16 August 2019 (UTC)

Abstain

1.  Abstain Meh, if there will be a #general and a #offtopic I think it is unnecessary, but if a #offtopic is not created, yes, because maybe the #general some users want to use it for offtopic things. --Dark Dragoon (talk) 11:31, 18 August 2019 (UTC)

Should a feedback channel be created?

Oppose

1.  Oppose I'm not sure about this, but personally I think a feedback channel would be used very little currently. Reception123 (talk) (C) 14:11, 16 August 2019 (UTC)
2.  Oppose Not going to work logistically. ~ RhinosF1 - _(chat) ^{· CA · contribs · Rights} - on) 14:59, 16 August 2019 (UTC)

Abstain

1.  Abstain Seems like it could be useful, but I'm unfamiliar with how the technical logistics would work and would rather just use Phabricator for reporting. -- Elaeagnifolia (talk) 20:26, 22 August 2019 (UTC)

Should an off-topic channel be created?

Support

1.  Support I think it's good to be able to also have off-topic conversations not related to Miraheze, but they should definitely be held somewhere else (not in #general). Reception123 (talk) (C) 14:11, 16 August 2019 (UTC)
2.  Support meh, might be useful and will do no harm. ~ RhinosF1 - _(chat) ^{· CA · contribs · Rights} - on) 14:59, 16 August 2019 (UTC)
3.  Support I think a #offtopic channel on a Discord server is always good. --Dark Dragoon (talk) 11:34, 18 August 2019 (UTC)
4.  Support As mentioned, somewhere to separate off-topic chatter unrelated to Miraheze. -- Elaeagnifolia (talk) 20:26, 22 August 2019 (UTC)

Should an audio channel be established?

NB: This would include an accompanying text channel for links/pictures relating to the conversation

Support

1.  Support It may not be a frequent occurrence, but there are people who like to speak in Discord, so I think it's good to create it. I also agree with the text channel to be able to publish things (text or multimedia) during a conversation. --Dark Dragoon (talk) 11:39, 18 August 2019 (UTC)
2.  Support I see no harm in creating one just in case for the users who do prefer to use Discord's audio features. -- Elaeagnifolia (talk) 20:26, 22 August 2019 (UTC)

Abstain

1.  Abstain Don't know what to say here, because I don't know if there's a demand, if there is sure. Reception123 (talk) (C) 14:11, 16 August 2019 (UTC)
2.  Abstain can't see me using it but if people want it then no reason why not. ~ RhinosF1 - _(chat) ^{· CA · contribs · Rights} - on) 14:59, 16 August 2019 (UTC)

Should a channel alerting users how to report vandalism to CVT be created?

Oppose

1.  Oppose I think this can be grouped in with the rules channel or be in the topic of a CVT channel. Reception123 (talk) (C) 14:11, 16 August 2019 (UTC)

Abstain

1.  Abstain Could we add it somewhere else? ~ RhinosF1 - _(chat) ^{· CA · contribs · Rights} - on) 14:59, 16 August 2019 (UTC)

Comments

• Could have this as a pinned post in #cvt rather than its own channel. -- Elaeagnifolia (talk) 20:26, 22 August 2019 (UTC)

Structure

Should Discord/Verification be moved to its own channel?

Support

1.  Support I think a channel where the information on how to get verified is pinned would be useful. Personally when I went through the verification process, I also found it helpful looking at how other users formatted their posts to make sure I did things right; however, I had to do that via the Discord search function because there was so much other bot spam in the channel. I agree with the opposed opinions that the channel wouldn't get much traffic, but I see the benefit of it as more separating it from the current traffic of the bot channel. -- Elaeagnifolia (talk) 20:26, 22 August 2019 (UTC)

Oppose

1.  Oppose Low traffic so no need in my opinion. Can be kept on the bot channel. Reception123 (talk) (C) 14:11, 16 August 2019 (UTC)
2.  Oppose No need to separate it when it's so low traffic. ~ RhinosF1 - _(chat) ^{· CA · contribs · Rights} - on) 14:59, 16 August 2019 (UTC)

Should read-only channels be grouped together?

Support

1.  Support I believe it's best if all read-only channels are separate in one place, to make it easier to see them. Reception123 (talk) (C) 14:11, 16 August 2019 (UTC)
2.  Strong support to help people know where to find them. ~ RhinosF1 - _(chat) ^{· CA · contribs · Rights} - on) 14:59, 16 August 2019 (UTC)
3.  Support For aforementioned reasons. -- Elaeagnifolia (talk) 20:26, 22 August 2019 (UTC)

Where Should #wiki-feed be placed?

Miscellaneous

1.  Support fits with those channels. ~ RhinosF1 - _(chat) ^{· CA · contribs · Rights} - on) 14:59, 16 August 2019 (UTC)
2.  Support For aforementioned reasons. -- Elaeagnifolia (talk) 20:26, 22 August 2019 (UTC)

CVT

1.  Oppose definitely not. Reception123 (talk) (C) 14:11, 16 August 2019 (UTC)
2.  Weak oppose might discourage non-CVTs from watching. ~ RhinosF1 - _(chat) ^{· CA · contribs · Rights} - on) 14:59, 16 August 2019 (UTC)

Comments

• Added this question as it currently resides in 'General' and moving per some suggestions would need discussion ~ RhinosF1 - _(chat) ^{· CA · contribs · Rights} - on) 09:15, 15 August 2019 (UTC)
• @Reception123: but where should it go? ~ RhinosF1 - _(chat) ^{· CA · contribs · Rights} - on) 14:59, 16 August 2019 (UTC)

Not sure, can't decide between Misc and General, but CVT would imply that it's only for CVT. Reception123 (talk) (C) 15:12, 16 August 2019 (UTC)

Should #Bot-Trolling and #Verification be moved to a 'miscellaneous' section?

Support

1.  Support - should be in their own area. ~ RhinosF1 - _(chat) ^{· CA · contribs · Rights} - on) 14:59, 16 August 2019 (UTC)
2.  Support Falls under the #miscellaneous category better than the current #general chat section. -- Elaeagnifolia (talk) 20:26, 22 August 2019 (UTC)

Comments

• Again added this as it would be new to the discord server if accepted ~ RhinosF1 - _(chat) ^{· CA · contribs · Rights} - on) 09:15, 15 August 2019 (UTC)
• # verification being moved here obviously requires the earlier question on whether it should exist to  pass ~ RhinosF1 - _(chat) ^{· CA · contribs · Rights} - on) 09:16, 15 August 2019 (UTC)

---

The above discussion is preserved as an archive. Please do not modify it. Subsequent comments should be made in a new section.