1# Technical Committee 2 3_This document only makes sense with the rules from [the community document](community)_. 4 5The Technical Committee (**TC**) is here to arbitrate and make decisions when 6technical conflicts occur in the project. 7 8The TC main role is to resolve technical conflicts. 9It is therefore not a technical steering committee, but it is understood that 10some decisions might impact the future of the project. 11 12# Process 13 14## Seizing 15 16The TC can take possession of any technical matter that it sees fit. 17 18To involve the TC in a matter, email tc@ or CC them on an ongoing discussion. 19 20As members of TC are developers, they also can email tc@ to raise an issue. 21 22## Announcement 23 24The TC, once seized, must announce itself on the main mailing list, with a _[TC]_ tag. 25 26The TC has 2 modes of operation: a RFC one and an internal one. 27 28If the TC thinks it needs the input from the larger community, the TC can call 29for a RFC. Else, it can decide by itself. 30 31If the disagreement involves a member of the TC, that member should recuse 32themselves from the decision. 33 34The decision to use a RFC process or an internal discussion is a discretionary 35decision of the TC. 36 37The TC can also reject a seizure for a few reasons such as: 38the matter was not discussed enough previously; it lacks expertise to reach a 39beneficial decision on the matter; or the matter is too trivial. 40 41### RFC call 42 43In the RFC mode, one person from the TC posts on the mailing list the 44technical question and will request input from the community. 45 46The mail will have the following specification: 47* a precise title 48* a specific tag [TC RFC] 49* a top-level email 50* contain a precise question that does not exceed 100 words and that is answerable by developers 51* may have an extra description, or a link to a previous discussion, if deemed necessary, 52* contain a precise end date for the answers. 53 54The answers from the community must be on the main mailing list and must have 55the following specification: 56* keep the tag and the title unchanged 57* limited to 400 words 58* a first-level, answering directly to the main email 59* answering to the question. 60 61Further replies to answers are permitted, as long as they conform to the 62community standards of politeness, they are limited to 100 words, and are not 63nested more than once. (max-depth=2) 64 65After the end-date, mails on the thread will be ignored. 66 67Violations of those rules will be escalated through the Community Committee. 68 69After all the emails are in, the TC has 96 hours to give its final decision. 70Exceptionally, the TC can request an extra delay, that will be notified on the 71mailing list. 72 73### Within TC 74 75In the internal case, the TC has 96 hours to give its final decision. 76Exceptionally, the TC can request an extra delay. 77 78 79## Decisions 80 81The decisions from the TC will be sent on the mailing list, with the _[TC]_ tag. 82 83Internally, the TC should take decisions with a majority, or using 84ranked-choice voting. 85 86The decision from the TC should be published with a summary of the reasons that 87lead to this decision. 88 89The decisions from the TC are final, until the matters are reopened after 90no less than one year. 91 92