Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision |
| committees:tcs:meetings:2015-11-14:minutes [2015/11/22 13:21] – impyy | committees:tcs:meetings:2015-11-14:minutes [2015/11/22 13:34] (current) – impyy |
|---|
| ===== TCS Committee Meeting #1 Minutes ===== | ===== TCS Committee Meeting #1 Minutes ===== |
| This meeting was held on 2015-11-19 23:00 UTC. | This meeting was held on 2015-11-19 23:00 UTC. |
| | |
| | Attendees: |
| | * zero-one |
| | * Jfreegman |
| | * grayhatter |
| | * chuongv |
| | * Impyy |
| | * stal |
| | * iphy |
| | * JX7P |
| | |
| | During the meeting, some other community members were also present. Only the committee members who attended are listed here. |
| |
| ==== General ==== | ==== General ==== |
| TCS meeting agenda's and minutes will be made available publicly in a separate namespace on the wiki. Meetings will be held whenever a member of the committee feels it's needed. | TCS meeting agenda's and minutes will be made available publicly in a separate namespace on the wiki. Meetings will be held whenever a member of the committee feels it's needed. |
| |
| Whenever a committee member (or anyone else) thinks a change to the TCS is needed, he will submit a pull request or an issue on GitHub. When there has been some discussion and the author of the proposed change thinks it's ready to be merged, an email will be sent to the mailing list with details about the proposed change so voting and additional discussion can take place. | Whenever a committee member (or anyone else) thinks a change to the TCS is needed, they will submit a pull request or an issue on GitHub. When there has been some discussion and the author of the proposed change thinks it's ready to be merged, an email will be sent to the mailing list with details about the proposed change so voting and additional discussion can take place. |
| |
| Any client that complies with the standard will have the privilege of using The Tox Project's services like jenkins and appearing on the downloads page. Proof of TCS compliance has to be provided by the client developers wherever possible. If a requirement is hard to provide proof for, an independent party has to test if the client complies with that particular requirement. Projects that don't fall under the definition of a Tox client will be handled on a case-by-case basis regarding access to The Tox Project's services. | Any client that complies with the standard will have the privilege of using The Tox Project's services like jenkins and appearing on the downloads page. Proof of TCS compliance has to be provided by the client developers wherever possible. If a requirement is hard to provide proof for, an independent party has to test if the client complies with that particular requirement. Projects that don't fall under the definition of a Tox client will be handled on a case-by-case basis regarding access to The Tox Project's services. |
