alexbakker/tcs_minutes.txt

## tcs_minutes.txt
## TCS committee meeting #1 minutes
This meeting was held on 2015-11-19 23:00 UTC

### 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.

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.

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.

During the meeting, one thing came up already that needs to be added to the TCS.
- A proper definition of what a 'Tox client' is.

### Voting
All committee members have to review the current state of the TCS. Proposing any changes will be done according to the procedure described above. After that, versioning will begin.

Rules for votes:
- Simple majority passes a vote
- Committee members can abstain, which reduces the votes required for a majority
- Voting can be done during a meeting or on the mailing list. Every member of the committee has one week to vote if they want to do so in advance of the meeting.

### Versioning
The TCS versioning system will consist of a major and a minor version number. The major version number will be increased when compatibility is broken or a new security requirement is added. Any other changes will increase the minor version number.

### Misc
A wiki page will be created about The Tox Project and the TCS committee (explaining what it's role is and who the members are).

The next meeting will be held on 2015-12-05 23:00 UTC
	## TCS committee meeting #1 minutes
	This meeting was held on 2015-11-19 23:00 UTC

	### 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.

	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.

	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.

	During the meeting, one thing came up already that needs to be added to the TCS.
	- A proper definition of what a 'Tox client' is.

	### Voting
	All committee members have to review the current state of the TCS. Proposing any changes will be done according to the procedure described above. After that, versioning will begin.

	Rules for votes:
	- Simple majority passes a vote
	- Committee members can abstain, which reduces the votes required for a majority
	- Voting can be done during a meeting or on the mailing list. Every member of the committee has one week to vote if they want to do so in advance of the meeting.

	### Versioning
	The TCS versioning system will consist of a major and a minor version number. The major version number will be increased when compatibility is broken or a new security requirement is added. Any other changes will increase the minor version number.

	### Misc
	A wiki page will be created about The Tox Project and the TCS committee (explaining what it's role is and who the members are).

	The next meeting will be held on 2015-12-05 23:00 UTC