The TODO list

When voting, how to resolve the results?

This is partial topic todo-voting from 2003-05-13.

This is suggestion voting-system submitted by zikap9am tma on 2003-05-13.

There is a majority voting system:

Voting period
is calculated separately for each topic. It is the period of time when votes are accepted. It starts when the first suggestion is entered. It ends 14 days after the last suggestion was entered.
Vote resolution
is the process of determining the suggestion to be accepted for each topic. It takes into account only the state of the votes at the end of the voting period.
Voter
is any potential voter that makes a vote
Potential voter
is any member of "kompilator" group at "jikos.cz" server
Vote
is the insertion of <vote> tag or tags inside the proper <topic> tag in the appropriate format (see cookbook). Each voter can vote at most once for each suggestion in a topic.
Implicit vote
is an implied vote. It is not vote in the sense of the above definition. It is implied by the votes a voter has placed on other suggestions. When the voter placed a "pro" on a suggestion vote he placed an implicit vote "contra" on all other suggestions.
The vote resolution mechanism in detail

After the vote period elapses the winning suggestion is determined as follows:

  1. For each suggestion the number of pro and contra votes are counted
  2. For each voter on the topic, which are the voters that placed a vote to at least one of the suggestions, the implicit votes are added.
  3. All implicit votes on any suggestion that is addressed by the same voter by a nonimplicit vote are disregarded.
  4. A suggestion is passed when there are more "pro" votes than "contra" votes.
  5. A suggestion is rejected if the majority of votes is "contra"
  6. In the case of tie the suggestion is passed.
  7. An amending suggestion is rejected if the amended suggestion is rejected
  8. An amending suggestion is only passed when the amended suggestion is also passed.

Voting on suggestion voting-system in topic todo-voting.

Voter: Voting passwd: procontra

[ Reviewer zikap9am is voting pro on voting-system. ]

[ Reviewer tma is voting pro on voting-system. ]

Should documentation be written in XML?

This is partial topic xml-and-doc from 2003-05-12.

This is suggestion xmldoc-yes submitted by tma on 2003-05-12.

Yes. There are processors available. eg. http://4suite.org/

Voting on suggestion xmldoc-yes in topic xml-and-doc.

Voter: Voting passwd: procontra

[ Reviewer tma is voting pro on xmldoc-yes. ]

[ Reviewer zikap9am is voting pro on xmldoc-yes. ]

source file sharing(write conflicts) rulez

This is partial topic write-conflicts from 2003-05-11.

screenplay:

  1. tma:vi file.c
  2. ps:vi file.c
  3. ps:cvs commit
  4. tma:cvs commit
  5. big bang
This is suggestion wc-ignore submitted by zikap9am on 2003-05-13.

Just ignore it, as if such situation could not possibly happen. There are several reasons:

  1. It never happens
  2. Each developer edits his own files only
  3. If there are conflicting commits, the co-workers can settle it in a chat
  4. It never happens

Voting on suggestion wc-ignore in topic write-conflicts.

Voter: Voting passwd: procontra

[ Reviewer tma is voting pro on wc-ignore. ]

[ Reviewer zikap9am is voting pro on wc-ignore. ]

This is suggestion wc-novote submitted by ps on 2003-05-13.

Don't want to solve it voting-way. ..(never=conflict happened 3 times for me till now...)

Voting on suggestion wc-novote in topic write-conflicts.

Voter: Voting passwd: procontra

How to organize TODOs?

This is partial topic todo from 2003-05-12.

This is suggestion todo-xml submitted by tma on 2003-05-12.

XML will do. This file should demonstrate the point. each TODO topic will be marked by <topic> each topic has state: open|partial|closed

open
no solution known
partial
partial solution known or suggestion only
closed
solution found

Element topic it has id and date. Attribute id is unique. Attribute date is YYYY-MM-DD hh:mm:ss in GMT and hours are optional and mostly omitted. In <topic> there is element <q> -- the question then there is sequence of suggestions <suggest>, solutions <solution>, <comment>s, that are neither of those, and votes: eg. <vote ref="todo-xml" vote="pro" who="tma" /> Attribute vote is pro|contra.

NEW topics should be added to the top.

dl
definition list
dt
definition term
dd
definition description
ol
ordered list
ul
unordered list
li
list item

Voting on suggestion todo-xml in topic todo.

Voter: Voting passwd: procontra

[ Reviewer tma is voting pro on todo-xml. ]

[ Reviewer zikap9am is voting pro on todo-xml. ]

This is suggestion todo-xml--amendments submitted by zikap9am on 2003-05-13 and extends todo-xml.

Amendments to suggestions. They have the form of a regular suggestion, i.e. the tag <suggest> with an extra attribute "amends" having value equal to the id attribute of the suggestion being amended. It is recommended to assign the amendment an id made up of the original id with the suffix "--amendment-name" added. It is possible to amend an amendment, the naming convention stays the same.

An example of such feature is this text itself (use the source, Luke). Another example of a suggestion named "original" with an amendment bringing an idea and a second level amendment correcting that idea:

<suggest who="zikap9am" date="2003-05-13" id="original"> original text here </suggest>

<suggest who="tma" date="2003-05-13" amends="original" id="original--an-idea"> an idea text here </suggest>

<suggest who="zikap9am" date="2003-05-13" amends="original--an-idea" id="original--an-idea--correction"> the correction text here </suggest>

Voting on suggestion todo-xml--amendments in topic todo.

Voter: Voting passwd: procontra

[ Reviewer zikap9am is voting pro on todo-xml--amendments. ]

[ Reviewer tma is voting pro on todo-xml--amendments. ]

pripadam si jak byrokrat v bruselu a ten pocit neni prijemny.