Player Menu
Quick Guide
Guía rápida
Player Handbook
FAQ
Join
Captain Menu
Capt Handbook
TD Menu
TD Handbook
Announcements
Bylaws
Constitution
Statutes
Admin Rules
Player Handbook
Capt Handbook
TD Handbook
FAQ
SC Agenda
Contact the TD
Questions
OC Chair
Webmaster
Español
Chief TD (DTR)
On the Fly
Future Events
Past Champions
GOTW
Comments
CJ's Wall
Gomer
PGN's
Links
Privacy Policy
Disclaimer
Copyright
Archive
ICC
Logos, Banner by KaitlinB and Tom45. |
Team 45 45 LeagueSerious Chess and Team Spirit on the ICC
T36-37 STEERING COMMITTEE AGENDA
Permanent Members: DaveTheRook (chair), BosqueVerde, chesskix, rgadoury General Members: Budzo, bmw2002, f5, Gomer, Kingofknights, RedAttack Standing Subcommittee (Rules): Standing Subcommittee (Technology): The role and purpose of the Steering Committee is to manage the affairs of the league, to set its direction and expansion, see to its advertisement and management, writing the Constitution, Statutes and Handbooks, and reviewing the rulings of the previous Oversight Committee. This is the ultimate governing body of Team 45 45 League with all rights and responsibilities. (Article III of the League Constitution) League Members may stay informed of potential rules
changes by watching this page. Prior to voting results being
displayed here, members may make their comments known by notifying
any Steering Committee member, who may choose to forward your
comments to the Steering Committee. The Committee members will not
disclose any details of the Committee discussions. Item 1 - T37 Tournament Parameters - Approved Item 1. T37 tournament parameterssSubmitted by the Chief TD; 03/11/2008 Time Control: 45 45 Team entries accepted: April 1, 2008 – April 15, 2008. Round 1 Posted: 22:00 April 22, 2008.
Count of team RR reductions (if any) precedes board removal
tie-breaks. Approved - 10 yes, 0 no; 10 Mar, 2008 Item 2 Scheduled Evaluation of Reliability
Rating System At the time of its enactment in 2006, a two-year moratorium was placed on making any major changes to the Reliability Rating (RR) method of handling forfeits. Rules has completed its review of the program. It is the unanimous opinion of Rules that this method should be continued, but with some modifications, notably to situations where a scheduled game is conceded ahead of time and temporary loss of server access; in the latter we feel an administrative rule would be appropriate. We also suggest some fine tuning of how forfeits are “forgiven” and multiple forfeit suspensions. Other than the changes proposed in Item 2, we think we should keep the method in place. Item 2 has several parts for the SC to consider. Item 2.a. Resolved: Continue the RR system. We suggest a vote on enactment or rejection be tabled until the various changes below are approved or rejected. Approved - 10 yes, 0 no; 30 Mar, 2008Item 2.b. Rules feels that some consideration other than an automatic RR reduction should be applied when a scheduled game is conceded ahead of time. Our suggestion is to allow the SecTD to recommend either (1) the standard 1 point deduction be applied or (2) that no point be either deducted OR ADDED in regards to this forfeit. In other words, that instead of the usual addition of 1 point for a tourney without incident (forfeit) the player’s rating would remain unchanged for the next tournament.
The 24 hour figure is somewhat arbitrary, but does allow the opponent time to make other personal plans and discourages last minute attempts to avoid a forfeit. The merit of the rule itself is that a player is extending a courtesy to his opponent by not making him wait around for a game that is not going to get played anyway. The original draft of our text started out like this: “Because of the courtesy being extended to the opponent ahead of time, a conceded game is an exception to the automatic reliability rating reduction for a forfeit…”; Approved - 10 yes, 0 no; 1 April, 2008Item 2.c. We have an inconsistency in how RR points are added.
The two passages are inconsistent. 17.A.i.c. harkens back to when we had yellow cards for forfeits; two forfeits meant automatic suspension. We see no merit in adding a point if a player did not play a tourney, nor two points for simply playing a tourney incident free. Rules suggests that 17.A.i.c be deleted, leaving 3.A.vi.b as our only rule on the earning of RR points. Approved - 10 yes, 0 no; 1 April, 2008Item 2.d. There is not now any restrictions placed on “repeat offenders” of suspensions for forfeits. We have had a few players with literally more forfeits than played games! Rules Subcommittee suggests that a rule be adopted similar to one we now have for red cards; a second suspension means a year’s wait.
Approved - 9 yes, 1 no; 7 April, 2008Item 2.e. Administrative Rule sought, summarized here by a committee member: The main issues presented with the RR system were conceding a game and allowing some excuses that could be independently verified by league staff (e.g. major weather or other disaster or internet outage effecting parts of the world but not ICC itself). Discussion of how to handle forfeits when the server is not down, but large numbers of members cannot access it, due to widespread internet issues or other emergencies. The Chief TD has issued Administrative Rule #8. April 18, 2008 Item 2.f Member suggestion to award an extra Reliability Rating point to TD volunteers, up to +3. Pros include: provides a token of appreciation and an incentive to TD's. Cons include: volunteers who fill jobs other than TD are also valued; and the proposed practice may be susceptible to perceived favoritism in TD selection. League Disclaimer states: "Services provided by the Team 45 45 League are provided free of charge, by volunteers giving freely of their time and resources." Not Approved - 1 yes, 9 no; April, 2008Item 3. Editorial Implementation of SC 35-36
Item 8.c Under our editorial revision policy, unless a SC member wishes to bring it up for further debate, this change will be incorporated into the Statutes in one week.
5.C. revisionsWhen the number of teams in a Section exceeds 35, the divisions within the section shall be split into two sub-Sections, Section A and Section B. Each sub-Section shall compete for its own championship and prizes. When the number of divisions is odd (9, 11, 13, etc), the greater number of divisions, all of which are Quad divisions, shall be placed in Section A, and the lesser number of divisions, but including any Hex divisions, shall be placed in Section B. When the number of divisions is even (10, 12, etc) any Hex division(s) shall still be assigned to Section B. Previous SC Agendas: |
|||
|