Introduce Discord rights guideline#4
Conversation
There was a problem hiding this comment.
Thank you for the sketch @energyLS! I think it great as the first iteration, and probably only a few points may need some polishing before we'll be able to incorporate this part. Have added a few comments which would be also perfect to discuss with @hazemakhalek and @davide-f since they relate to some implications for the existing practices
| | Contributor | Contributor | Normal chat rights; all but "moderator only" | | ||
| | Coordinator | Stream Coordinator | Moderation in own stream, private coordinator channel (?), all but "moderator only" | | ||
| | Steering Committee | Steering Committee | Server-wide moderation, strategic channels, manage channels, access to "moderator only" | | ||
| | Admin (technical) | Server Admin | Technical admin only, no governance authority | |
There was a problem hiding this comment.
To my understanding, administration rights are more or less equivalent to server-wide moderation for a Discord server. Agree however that it could be good to have someone who is taking care about the technical part but it would be good to agree on having a clean split between the technical part and moderation
| | Participant | @everyone | Normal chat rights; all but "moderator only" | | ||
| | Contributor | Contributor | Normal chat rights; all but "moderator only" | |
There was a problem hiding this comment.
Could it be a good idea to incorporate also the rules we have in readme-rules channel?
|
|
||
| ## Rationale | ||
| This table defines how the governance roles of PyPSA meets Earth map to Discord roles and which permissions are associated with them. | ||
| It is intended as a practical reference for configuring and maintaining the Discord server while ensuring transparency, minimal privilege, and role‑aligned decision structures. |
There was a problem hiding this comment.
We need also a short code of conduct since there is quite a usual issues with people using the server to post advertisements of their services which have nothing to do neither with energy not with open source
There was a problem hiding this comment.
Agree, we can take inspiration from the readme in discord too
| | --- | --- | --- | | ||
| | Participant | @everyone | Normal chat rights; all but "moderator only" | | ||
| | Contributor | Contributor | Normal chat rights; all but "moderator only" | | ||
| | Coordinator | Stream Coordinator | Moderation in own stream, private coordinator channel (?), all but "moderator only" | |
There was a problem hiding this comment.
As discussed previously, there is a balance between keeping the communication as open as possible and as closed as necessary. Not sure it makes sense to have too many private channels but a few maintainance-related seem to be quite effective. Let's probably try to stay flexible? E.g. revising into something like that:
| | Coordinator | Stream Coordinator | Moderation in own stream, private coordinator channel (?), all but "moderator only" | | |
| | Coordinator | Stream Coordinator | Moderation in own stream, private coordinator channel (if applicable), all but "moderator only" | |
| | **Participant** | @everyone | Standard chat rights; access to all public channels; no moderation permissions; excluded from moderator‑only and maintenance channels. | | ||
| | **Contributor** | Contributor | Standard chat rights; access to contributor-only channels; no moderation rights; excluded from moderator‑only and maintenance channels; project/stream‑specific access may be granted case‑by‑case. | | ||
| | **Coordinator** | Stream Coordinator | Moderation rights within own stream; access to coordinator‑only channels (if applicable); no server‑wide moderation; extended permissions in project/stream‑specific channels possible; no access to moderator‑only or maintenance channels unless explicitly granted. | | ||
| | **Steering Committee** | Steering Committee | Server‑wide moderation rights; access to moderator‑only channel; may manage channels where needed; access to maintenance channels. No newline at end of file |
There was a problem hiding this comment.
In the moderator-only channel, the permissions are currently adjusted in a way that we have a lot of participants here. I fear it won't be very polite to withdraw the permissions abruptly
davide-f
left a comment
davide-f
left a comment
There was a problem hiding this comment.
Thanks for the draft! Added a few comments.
Good for me too
|
|
||
| ## Rationale | ||
| This table defines how the governance roles of PyPSA meets Earth map to Discord roles and which permissions are associated with them. | ||
| It is intended as a practical reference for configuring and maintaining the Discord server while ensuring transparency, minimal privilege, and role‑aligned decision structures. |
There was a problem hiding this comment.
Agree, we can take inspiration from the readme in discord too
| | Participant | @everyone | Normal chat rights; all but "moderator only" | | ||
| | Contributor | Contributor | Normal chat rights; all but "moderator only" | |
| | Governance Role | Discord Role | Permissions Summary | | ||
| |---------------------|----------------------|----------------------| | ||
| | **Participant** | @everyone | Standard chat rights; access to all public channels; no moderation permissions; excluded from moderator‑only and maintenance channels. | | ||
| | **Contributor** | Contributor | Standard chat rights; access to contributor-only channels; no moderation rights; excluded from moderator‑only and maintenance channels; project/stream‑specific access may be granted case‑by‑case. | | ||
| | **Coordinator** | Stream Coordinator | Moderation rights within own stream; access to coordinator‑only channels (if applicable); no server‑wide moderation; extended permissions in project/stream‑specific channels possible; no access to moderator‑only or maintenance channels unless explicitly granted. | | ||
| | **Steering Committee** | Steering Committee | Server‑wide moderation rights; access to moderator‑only channel; may manage channels where needed; access to maintenance channels. No newline at end of file |
There was a problem hiding this comment.
This appears duplicated, best to have a single table in my opinion
|
Note: It is also possible to have the status quo of people on the server/rights, then we just would need to write it in the governance |
3 participants
This PR introduces a Discord rights guideline, closely linked to the governance itself.