Confirmed users
360
edits
DOM/IRC: Difference between revisions
m
office hours editing
(irc first try) |
m (office hours editing) |
||
| Line 2: | Line 2: | ||
There are 2 DOM-related IRC channels: | There are 2 DOM-related IRC channels: | ||
* #content: For DOM-related technical discussion, questions, and general discussion by those interested in the DOM. Most Mozilla Corporation DOM team engineers maintain a presence in this channel so that they can answer questions, | * #content: For DOM-related technical discussion, questions, and general discussion by those interested in the DOM. Most Mozilla Corporation DOM team engineers maintain a presence in this channel so that they can answer questions, engage in and be aware of technical discussion, and informally chat. Note: You do not need to a be a MoCo engineer to hang out in this channel; the channel is open to everyone! | ||
* #content-watercooler: A strictly optional channel created out of recognition that for potential, new, and even experienced contributors, it can be intimidating to ask questions on #content where there are so many people. The expectation is that those reading the channel are doing so because they want to chat and/or would like to help answer questions. | * #content-watercooler: A strictly optional channel created out of recognition that for potential, new, and even experienced contributors, it can be intimidating to ask questions on #content where there are so many people. The expectation is that those reading the channel are doing so because they want to chat and/or would like to help answer questions. | ||
** Any topic that is okay here is also okay in #content. The intent of this channel is to be less intimidating, not as a place to send off-topic discussion. (It is okay to discuss the movie you just saw in #content!) | ** Any topic that is okay here is also okay in #content. The intent of this channel is to be less intimidating, not as a place to send off-topic discussion. (It is okay to discuss the movie you just saw in #content!) | ||
** When discussion in this channel touches on DOM-related technical topics that are of broad interest or involve implementation discussion, participants may say "let's take this to #content" | ** When discussion in this channel touches on DOM-related technical topics that are of broad interest or involve implementation discussion, participants may say "let's take this to #content" to avoid #content-watercooler becoming a second #content where everyone has to monitor both channels. | ||
If you need info on how to connect to Mozilla's IRC service to access these great channels, please see https://wiki.mozilla.org/IRC. | If you need info on how to connect to Mozilla's IRC service to access these great channels, please see https://wiki.mozilla.org/IRC. | ||
| Line 15: | Line 15: | ||
* A person who feels comfortable answering questions about parts of the DOM code base decides they have some time (~1hr) where they can answer questions on IRC and possibly in a videoconferencing hangout at the same time. | * A person who feels comfortable answering questions about parts of the DOM code base decides they have some time (~1hr) where they can answer questions on IRC and possibly in a videoconferencing hangout at the same time. | ||
* The person will update the IRC topic for #content to indicate: | * The person will update the IRC topic for #content to indicate: | ||
** Who is answering questions and when. | |||
** Any specific topics they feel proficient in. (No one knows everything!) | |||
** Any videoconferencing link to use as a supplement to IRC. (Frequently it's easier to reach a shared understanding over videoconferencing, especially when screen-sharing is available.) | |||
* When the office hours are over, the person will reset the IRC topic. | * When the office hours are over, the person will reset the IRC topic. | ||
| Line 43: | Line 43: | ||
** Combining the two, that gives us something like: | ** Combining the two, that gives us something like: | ||
*** <code>DOM Office Hours with :asuth here and WebRTC via https://appear.in/asutherland | https://wiki.mozilla.org/DOM/IRC | Logged: https://mozilla.logbot.info/content | Triage https://mzl.la/2JtE4IH</code> | *** <code>DOM Office Hours with :asuth here and WebRTC via https://appear.in/asutherland | https://wiki.mozilla.org/DOM/IRC | Logged: https://mozilla.logbot.info/content | Triage https://mzl.la/2JtE4IH</code> | ||
* Setting the channel topic message. | |||
** An op or other fancy IRC person needs to set the topic. | |||
*** If you are an established member of the IRC channel and can commit to not abusing IRC powers, you can ask :smaug on #content to make you an op. Note that your IRC login will need to be password-protected. | |||
*** If you aren't quite there yet, you can ask one of the ops in the channel to set the topic for you. | |||
** The IRC command to set the topic is <code>/topic #content ...</code> | |||
*** So to set the topic to "No, this is not the right topic to use", you'd type: <code>/topic #content No, this is not the right topic to use</code> | |||