m (edit) |
|||
| Line 4: | Line 4: | ||
The [[Irc| IRC]] (Internet relay chat) Support [https://en.wikipedia.org/wiki/Special_Interest_Group SIG] (Special interest group), is a group of people who seek to improve support users get in #fedora and promote a fun social area in #fedora-social. | The [[Irc| IRC]] (Internet relay chat) Support [https://en.wikipedia.org/wiki/Special_Interest_Group SIG] (Special interest group), is a group of people who seek to improve support users get in #fedora and promote a fun social area in #fedora-social. | ||
= Members | = Members = | ||
Anyone can be a member of the SIG. Just start helping others in #fedora, chatting with others in #fedora-social and attend our weekly meetings in #fedora-meeting at 17:00UTC (Noon EST) on Thursdays each week. | Anyone can be a member of the SIG. Just start helping others in #fedora, chatting with others in #fedora-social and attend our weekly meetings in #fedora-meeting at 17:00UTC (Noon EST) on Thursdays each week. | ||
= Channels | = Channels = | ||
Currently the SIG controls/manages the following channels: | Currently the SIG controls/manages the following channels: | ||
| Line 26: | Line 26: | ||
Those not in the above 2 groups are welcome to join and discuss an issue or concern from the other 3 channels, but are asked to then depart after their issue or concern is noted. | Those not in the above 2 groups are welcome to join and discuss an issue or concern from the other 3 channels, but are asked to then depart after their issue or concern is noted. | ||
= Voting Members And Voting | = Voting Members And Voting = | ||
A subset, irc-support-operators [[FAS]] group, of the SIG will be voting members and be able to vote on issues brought up for a vote before the SIG. | A subset, irc-support-operators [[FAS]] group, of the SIG will be voting members and be able to vote on issues brought up for a vote before the SIG. | ||
| Line 34: | Line 34: | ||
* In all cases (aside from promoting/removing members), broad consensus should be attempted first and if no clear consensus can be reached a vote should be taken. All new operator/voting member tickets require a vote. | * In all cases (aside from promoting/removing members), broad consensus should be attempted first and if no clear consensus can be reached a vote should be taken. All new operator/voting member tickets require a vote. | ||
= Items Requiring Votes | = Items Requiring Votes = | ||
All tickets requiring a vote must have 2 meetings: one for discussion, one only for final voting. At the discretion of the nominator and/or the primary chair for the meeting, voting can be extended before or at either of these meetings. The ticket should include the discussion meeting date and voting meeting date. At this time meetings are held on Thursdays, a ticket filed on Tuesday or Wednesday does not have to be discussed at that Thursday's meeting at the discretion of the nominator and/or the primary chair for that week's meeting. Should the primary chair of the discussion or voting meeting feel more time is needed they have the option of extending the discussion period there by changing the vote date, this should be noted in the ticket description. | All tickets requiring a vote must have 2 meetings: one for discussion, one only for final voting. At the discretion of the nominator and/or the primary chair for the meeting, voting can be extended before or at either of these meetings. The ticket should include the discussion meeting date and voting meeting date. At this time meetings are held on Thursdays, a ticket filed on Tuesday or Wednesday does not have to be discussed at that Thursday's meeting at the discretion of the nominator and/or the primary chair for that week's meeting. Should the primary chair of the discussion or voting meeting feel more time is needed they have the option of extending the discussion period there by changing the vote date, this should be noted in the ticket description. | ||
| Line 44: | Line 44: | ||
At the final voting meeting, all votes from the ticket will be tallied and voting members will be queried for votes if they have not or if they would like to change their posted vote on the ticket. These ticket items should be brought up as the last order of business for the final voting meeting before the open floor. Wherein the ticket is either passed or denied based on the majority of +1/-1 votes, abstaining (+0/-0) votes not being counted. In the case of a tie the sig should ask the FPL to either have the final word or appoint a non-voting member to do so for them. The final voting meeting is not a time for discussion, all discussion should be taken care of at the discussion meeting or on the nomination ticket prior to the final voting meeting. | At the final voting meeting, all votes from the ticket will be tallied and voting members will be queried for votes if they have not or if they would like to change their posted vote on the ticket. These ticket items should be brought up as the last order of business for the final voting meeting before the open floor. Wherein the ticket is either passed or denied based on the majority of +1/-1 votes, abstaining (+0/-0) votes not being counted. In the case of a tie the sig should ask the FPL to either have the final word or appoint a non-voting member to do so for them. The final voting meeting is not a time for discussion, all discussion should be taken care of at the discussion meeting or on the nomination ticket prior to the final voting meeting. | ||
= Operator/Voting Member Tickets | = Operator/Voting Member Tickets = | ||
New operators/voting members are nominated by existing operators and/or voting members using the ticketing system. If you are interested in one of these positions please contact an existing member to sponsor and nominate you. Please include the nominee's primary IRC nick and what channels they are being nominated for in the ticket subject. Nominees are encouraged to be active on the ticket for their nomination and to attend the discussion meeting so they can respond to any questions or address any concerns if they are able, this is not required. | New operators/voting members are nominated by existing operators and/or voting members using the ticketing system. If you are interested in one of these positions please contact an existing member to sponsor and nominate you. Please include the nominee's primary IRC nick and what channels they are being nominated for in the ticket subject. Nominees are encouraged to be active on the ticket for their nomination and to attend the discussion meeting so they can respond to any questions or address any concerns if they are able, this is not required. | ||
| Line 52: | Line 52: | ||
When and if other channels wish to join the sig, rules for that can be added for that channel. | When and if other channels wish to join the sig, rules for that can be added for that channel. | ||
= Mailing List | = Mailing List = | ||
The [[IRC_support_sig| IRC Support SIG]] has an open mailing list (subscribe to post) at: [https://lists.fedoraproject.org/mailman/listinfo/irc-support-sig https://lists.fedoraproject.org/mailman/listinfo/irc-support-sig] | The [[IRC_support_sig| IRC Support SIG]] has an open mailing list (subscribe to post) at: [https://lists.fedoraproject.org/mailman/listinfo/irc-support-sig https://lists.fedoraproject.org/mailman/listinfo/irc-support-sig] | ||
| Line 59: | Line 59: | ||
= Trac Instance | = Trac Instance = | ||
The [[IRC_support_sig| IRC Support SIG]] has a trac instance at [https://fedorahosted.org/irc-support-sig/ https://fedorahosted.org/irc-support-sig] | The [[IRC_support_sig| IRC Support SIG]] has a trac instance at [https://fedorahosted.org/irc-support-sig/ https://fedorahosted.org/irc-support-sig] | ||
| Line 66: | Line 66: | ||
= | = FAQ = | ||
'''Q''': I wish to bring up an issue to the sig, how can I do that? | '''Q''': I wish to bring up an issue to the sig, how can I do that? | ||
'''A''': Please file a trac ticket on our trac instance: [https://fedorahosted.org/irc-support-sig/ irc-support-sig] it will be looked at at the next meeting. | '''A''': Please file a trac ticket on our trac instance: [https://fedorahosted.org/irc-support-sig/ irc-support-sig] it will be looked at at the next meeting. | ||
Revision as of 03:24, 12 May 2012
IRC Support SIG
What Is The IRC Support SIG?
The IRC (Internet relay chat) Support SIG (Special interest group), is a group of people who seek to improve support users get in #fedora and promote a fun social area in #fedora-social.
Members
Anyone can be a member of the SIG. Just start helping others in #fedora, chatting with others in #fedora-social and attend our weekly meetings in #fedora-meeting at 17:00UTC (Noon EST) on Thursdays each week.
Channels
Currently the SIG controls/manages the following channels:
- #fedora - This is the main support channel
- #fedora-social - This is the main social channel.
- #fedora-unregistered - This channel is used to hold unregistered with freenode folks before they join #fedora for support. Channel operators of #fedora and #fedora-social are also operators of this channel if they wish.
- #fedora-ops - This channel is for coordinating and discussing management of the other 3 channels above. All #fedora and #fedora-social operators are also operators in this channel by default.
Operators in #fedora, #fedora-social and/or #fedora-unregisterd are welcome to join and idle in #fedora-ops.
Invited contributors can be allowed temporary invitee status by nomination from an op and a second from any other operator for a maximum of 2 weeks. For longer term invitee status a vote should be required as defined below.
Those not in the above 2 groups are welcome to join and discuss an issue or concern from the other 3 channels, but are asked to then depart after their issue or concern is noted.
Voting Members And Voting
A subset, irc-support-operators FAS group, of the SIG will be voting members and be able to vote on issues brought up for a vote before the SIG.
- Voting members are anyone who is an operator in any of the above listed channels (4 channels as of 2012-05-11), anyone voted in as a voting member, and the FPL (Fedora Project Leader) only in the case of a tie vote. Voting members should remember to listen to the community as a whole when making decisions.
- In all cases (aside from promoting/removing members), broad consensus should be attempted first and if no clear consensus can be reached a vote should be taken. All new operator/voting member tickets require a vote.
Items Requiring Votes
All tickets requiring a vote must have 2 meetings: one for discussion, one only for final voting. At the discretion of the nominator and/or the primary chair for the meeting, voting can be extended before or at either of these meetings. The ticket should include the discussion meeting date and voting meeting date. At this time meetings are held on Thursdays, a ticket filed on Tuesday or Wednesday does not have to be discussed at that Thursday's meeting at the discretion of the nominator and/or the primary chair for that week's meeting. Should the primary chair of the discussion or voting meeting feel more time is needed they have the option of extending the discussion period there by changing the vote date, this should be noted in the ticket description.
Voting members and the community will have a chance to discuss items requiring a vote in an open forum at the discussion meeting prior to casting their vote.
After the discussion meeting the ticket will be voted on by using the ticket system and the final voting meeting. A +1 means a yay (yes) and a -1 means a nay (no) with a +0 (abstain) option. Any final issues should be brought up on the ticket during this period.
At the final voting meeting, all votes from the ticket will be tallied and voting members will be queried for votes if they have not or if they would like to change their posted vote on the ticket. These ticket items should be brought up as the last order of business for the final voting meeting before the open floor. Wherein the ticket is either passed or denied based on the majority of +1/-1 votes, abstaining (+0/-0) votes not being counted. In the case of a tie the sig should ask the FPL to either have the final word or appoint a non-voting member to do so for them. The final voting meeting is not a time for discussion, all discussion should be taken care of at the discussion meeting or on the nomination ticket prior to the final voting meeting.
Operator/Voting Member Tickets
New operators/voting members are nominated by existing operators and/or voting members using the ticketing system. If you are interested in one of these positions please contact an existing member to sponsor and nominate you. Please include the nominee's primary IRC nick and what channels they are being nominated for in the ticket subject. Nominees are encouraged to be active on the ticket for their nomination and to attend the discussion meeting so they can respond to any questions or address any concerns if they are able, this is not required.
Existing operators/voting members can be removed in roughly the same way as the process to add them. Inactive members can be removed if there is a majority vote as described in the voting part of this document.
When and if other channels wish to join the sig, rules for that can be added for that channel.
Mailing List
The IRC Support SIG has an open mailing list (subscribe to post) at: https://lists.fedoraproject.org/mailman/listinfo/irc-support-sig
General ideas or discussion welcome there.
Trac Instance
The IRC Support SIG has a trac instance at https://fedorahosted.org/irc-support-sig
Use your Fedora account (FAS) to login and leave us a ticket.
FAQ
Q: I wish to bring up an issue to the sig, how can I do that?
A: Please file a trac ticket on our trac instance: irc-support-sig it will be looked at at the next meeting.