This repository has been archived by the owner on Jun 6, 2021. It is now read-only.
Clarify policy on keeping primary channels open #522
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
I don't know if this is the exact policy, but this seems to describe better what was explained to me on #freenode-services: ``` 17:58 <pinkieval> Someone closed a # channel I was in, can you make it forward to the ## channel with the same name, like https://freenode.net/policies#channel-ownership says? 18:01 <@tabmow> pinkieval: what channel? 18:01 <pinkieval> Tabmow: #freenode-policy-feedback 18:02 <@tabmow> pinkieval: umm, no. Those are used by freenode staff when needed. 18:02 <pinkieval> So freenode channels are excluded from the policy? 18:05 <@tabmow> pinkieval: they are part of the freenode group which staff own. Read the policy again. 18:06 <pinkieval> I get it, but the policy says "Primary channels are required to stay open.". #freenode-policy-feedback is a primary channel, right? 18:09 <@tabmow> pinkieval: there are many freenode primary channels, like this one. 18:10 <pinkieval> So only one primary channel per project needs to stay open? 18:19 <-- Tabmow (~tabmow@freenode/staff/tabmow) a quitté (Quit: ZNC 1.8.2 - https://znc.in) 18:20 --> Tabmow (~tabmow@freenode/staff/tabmow) a rejoint #freenode-services 18:20 -- Mode #freenode-services [+o Tabmow] par ChanServ 18:21 <pinkieval> Tabmow: (in case you missed the question: ) So only one primary channel per project needs to stay open? 18:29 <@tabmow> pinkieval: not exactly, but sure. ``` (I removed unrelated messages from the log)
|
I don't think #freenode has any open primary channels. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I don't know if this is the exact policy, but this seems to describe better
what was explained to me on #freenode-services:
(I removed unrelated messages from the log)
Suggestions are welcome to make this closer to the actual policy.