Talk:IRC: Difference between revisions
(channel 'structure') |
|||
| Line 2: | Line 2: | ||
I agree, the description of #olpc was too broad and the (current) use as support for core-development is so—which raises the question: wouldn't it be more logical to move #olpc to #olpc-devel (or similar) and thus 'liberate' #olpc as the 'information desk'? |
I agree, the description of #olpc was too broad and the (current) use as support for core-development is so—which raises the question: wouldn't it be more logical to move #olpc to #olpc-devel (or similar) and thus 'liberate' #olpc as the 'information desk'? |
||
:Yes, more logical. But the change would require altering many peoples' behavior. And the expertise in #olpc is useful in triaging questions. As long as there is somewhere else to talk, and the user experience of bouncing through #olpc doesn't get too bad, then perhaps we should defer the issue, and let increasing visitors eventually drive devel elsewhere. [[User:MitchellNCharity|MitchellNCharity]] 13:02, 4 June 2007 (EDT) |
|||
Also, have something like #olpc-chat, for general chatter or talk could be something to explore. |
Also, have something like #olpc-chat, for general chatter or talk could be something to explore. |
||
: #olpc-talk? I think that's the mailing-list convention. [[User:MitchellNCharity|MitchellNCharity]] 13:02, 4 June 2007 (EDT) |
|||
There are a series of ad-hoc channels too (ie: #olpc-es (spanish), #olpc-ro (Romania), #olpc-brasil, etc) that could be included. Or set up a simple way.... like #olpc-country, #olpc-xx (xx being language code). --[[User:Xavi|Xavi]] 09:14, 4 June 2007 (EDT) |
There are a series of ad-hoc channels too (ie: #olpc-es (spanish), #olpc-ro (Romania), #olpc-brasil, etc) that could be included. Or set up a simple way.... like #olpc-country, #olpc-xx (xx being language code). --[[User:Xavi|Xavi]] 09:14, 4 June 2007 (EDT) |
||
:I added #olpc-es/-ro/-brazil. But not etc. :) Also mentioned -country/-xx convention. [[User:MitchellNCharity|MitchellNCharity]] 13:02, 4 June 2007 (EDT) |
|||
This morning I tried to add/get added mention of #olpc-content in the #olpc /topic, but the /topic is locked down, and the request met by silence. Sigh. [[User:MitchellNCharity|MitchellNCharity]] 13:02, 4 June 2007 (EDT) |
|||
Revision as of 17:02, 4 June 2007
Channels for Chatter
I agree, the description of #olpc was too broad and the (current) use as support for core-development is so—which raises the question: wouldn't it be more logical to move #olpc to #olpc-devel (or similar) and thus 'liberate' #olpc as the 'information desk'?
- Yes, more logical. But the change would require altering many peoples' behavior. And the expertise in #olpc is useful in triaging questions. As long as there is somewhere else to talk, and the user experience of bouncing through #olpc doesn't get too bad, then perhaps we should defer the issue, and let increasing visitors eventually drive devel elsewhere. MitchellNCharity 13:02, 4 June 2007 (EDT)
Also, have something like #olpc-chat, for general chatter or talk could be something to explore.
- #olpc-talk? I think that's the mailing-list convention. MitchellNCharity 13:02, 4 June 2007 (EDT)
There are a series of ad-hoc channels too (ie: #olpc-es (spanish), #olpc-ro (Romania), #olpc-brasil, etc) that could be included. Or set up a simple way.... like #olpc-country, #olpc-xx (xx being language code). --Xavi 09:14, 4 June 2007 (EDT)
- I added #olpc-es/-ro/-brazil. But not etc. :) Also mentioned -country/-xx convention. MitchellNCharity 13:02, 4 June 2007 (EDT)
This morning I tried to add/get added mention of #olpc-content in the #olpc /topic, but the /topic is locked down, and the request met by silence. Sigh. MitchellNCharity 13:02, 4 June 2007 (EDT)