Quorum: is defined as the smallest number which is greater than 50% of the number of current members.
Current members: individuals who have voted in both of the two previous meetings.
In other words: Quorum "floats" to match half of whatever the current level of participation is. If someone misses a meeting (or is new) they won't count towards quorum for the next two. It does not mean that they cannot vote.
The list of current members at the top of the page is for reference, anyone may note that so and so voted in some Editorial Board meetings and adds that name. Edit history of a page is the real proof of participation. there must be an edit in that month by that person.
If consensus is not reached on a particular motion, a vote will decide on accepting or rejecting a motion. It takes 50%+1 "current" members voting (for, against or abstain) to decide a motion. For example if the number of current members is 7, then quorum would be 4, which means that if two vote in favor, one against and one abstains, the motion passes.
This is a meeting of the Editorial Board - it runs online from May 1 to May 31, 2009.
Members considered current for this meeting (9): chibaguy, dthacker, klang, luci, marclaporte, MatWho, mlpvolt (MLP), ricks99, xavi
5 votes (for, against or abstain) are needed to reach quorum on the decisions for this month. Please read above the [+] "About Quorum and voting" section.
Contributors to this meeting: see "history" of the page.
Undecided: lindon (I like having the All the Documentation site map link somewhere, also like the current choices under Author Resources. Depending on how reduced TOC in side menu looks, some keywords might still be helpful since lots of things are covered in keywords that wouldn't show in a reduced TOC or freetags. Otherwise menu proposals seem okay.)
2.2. Change doc.tw.o modules
Motion: Change modules according to doctwo revamp proposal page.
Opposed: lindon (I don't mean that i completely oppose but i do like the registered users online, and search by page name modules for registered users. Also assume the developer menu would remain for those users.)
2.3. categories for status
are there but not being used. Do we use? or do we nuke?
I (ricks99) would like to continue to use them (to alert readers as to the "correctness" of a particular page). However I see a potential issue: How can we "split" the category of a page when using the VERSIONS plugin? For example, the 2.x information may be "LIVE", but the 3.x information may be "TO DO." Currently (I think), Tiki allows only 1:1 — category:page.
I (ricks99) would also like to see the categories be simplified. Maybe something like:
Stub — Newly generated page; no real content.
In Progress — Being worked on, not up-to-date or complete.
In Review — Content complete. Needs to be reviewed/verified.
Complete — Page is done & published.
Maybe also use Staging feature?
lindon wrote:
I could take or leave the categories for users, but find the backlinks method used in documentation status and the other tools marc has set up (like All plugins) to be the best for authors.
2.4. Remove en-uk as a possible language
just causes confusion. When we filter by language, there are uk english pages which are not really different to English pages
There is no en-uk version for Wikipedia, with over 250 languages
In favor: marclaporte
Opposed: luci
-1 — color is different than colour (ricks99)
2.5. Remove my footnotes
to simplify interface
need to check in db if any data
Discussion:
+1, i never used it myself — luci
-1, I like having it. It allows contributors to work on pages without actually editing the "real" content. If we implement the Staging system to doc.tw.o, then +1 from me (ricks99)
-1, I haven't used it but think it could be useful. Not sure if staging would replace it for me.