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 July 1st to July 31st, 2009.
Members considered current for this meeting (4): lindon, ricks99, marclaporte and xavi
3 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.
Motion "Change doc.tw.o menus" according to doctwo revamp taking into account the observations from the past ebm 1 current member voting for, and 1 current member voting undecided.
Motion "Remove my footnotes"
2 current members voting for it.
...
Motion XN: bla bla...
Motions Defeated Last Month
Motion "Remove en-uk as a possible language"
1 current member voting against, and 1 current member voting undecided.
1. Motions Carried Over
1.1. Motion Change doc.tw.o modules
Motion: Change modules according to doctwo revamp proposal page.
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.)
xavi: so do I. I'm ok with the general proposition with your additional comments, lindon
For an end-user, what value does the "Registered Users Online" module give? (ricks99)
If I register for a site like this, where just about the only reason to do so is to collaborate and "volunteer" in some way, then I enjoy seeing who else is online. It's motivating to me. If I just want info then I don't login here. But that's just me 😉 Certainly not a deal-breaker one way or the other, but I would miss it if it went away. (lindon)
I guess to have it for Registered only would be OK. But for Anonymous visitors, I see little value.
Agree - my original suggestion above was for registered users only. (lindon)
lindon again: would like a bookmark module for adding own bookmarks
Hmm... To be honest, I've never used Tiki's bookmarks. I've always simply used bookmarks directly within my browser.
But nice to give the option for those that like such modules? Or do you think it clutters things too much? (lindon)
For me, it is just visual clutter. But if we enable Registered users to configure their own modules, then people like me could remove it, and folks like you could keep it. (ricks99)
Great idea. (lindon)
What about using polls, surveys, etc. to ask users for opinions on what modules they would like or not like (like "Would you like to see a bookmark module on the side menu?", "Do you find the keyword list useful?" etc.). We could expand it to cover other things periodically like "What area of documentation needs the most work?", "What pages do you think work best?". Just a thought. Not sure what the experience has been with this sort of thing. (lindon)
IMHO this should be posted in the Documentation forum on tw.o. I really think we should strive to keep doc.tw.o neat and clean — KISS.
Motion #
Accept
Undecided
Reject
1
1
1
ricks99
xavi
lindon
1.2. categories for status
Motion: keep Categories to indicate also the status of wiki pages, besides the wiki tags and freetags
Discussion: are there but not being used. Do we use? or do we nuke?
ricks99:
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.
xavi: I propose to remove all categories for status, since they are applicable to the whole wiki page, and I find the status tags and backlinks (implemented by mlpvolt and dthacker, afaik) much more versatile in a per version, section or paragraph basis.
+ I suggest to keep categories only for monitoring specific groups of pages like in EBM pages. CLick once to monitor somewhere for EMB pages, and you receive emails about changes on all pages, even if you forget the monitor the page for the new month (in case it has been properly categorized, of course 😉 ).
marclaporte: if we keep, who will clean up the 1000 pages? We need a reset/clean-up. Perhaps erase all and build organically from now on.
Installation and Setup:
How do I know I have the latest/current version of TikiWiki?
The latest version is always the one you find on the Sourceforge download site http://sourceforge.net/project/showfiles.php?group_id=64258 or available from http://info.tiki.org/tiki-index_raw.php?page=Get+Tiki From a running installation, you can verify you are up to date by performing a release check. This is done by selecting the first item in the General section of the Configuration Sections.
Discussion: I find it dangerous and cumbersome to not be informed of new and potentially security related versions, upgrades and bugfixes of TikiWiki. While there is no solution to that problem, I find it important to provide the information how to overcome it, by checking before installing, or using the release check.
Does this really need to be an EBM Motion? Why not simply submit this as a new Suggested FAQ? Isn't that the purpose of enabling the SUGGEST AN FAQ option? (ricks99)
It was entered here since I was recommended to do so on IRC. (tobi_h)
Security:
How do I find out about vulnerabilities and security issues of my TikiWiki installation?
Currently, the best way to do that is to subscribe to the RSS feed of insert relevant website here, and checking that on a regular basis. Maybe we will dedicate an announcement mailing lists later on.
Discussion: I find it dangerous and cumbersome to not be informed of new and potentially security related versions, upgrades and bugfixes of TikiWiki. While there is no solution to that problem, I find it important to provide the information how to overcome it, by using the RSS feed. I'd appreciate if there were a commitment by the developers WRT the location of such announcements. 😉
Discussion: Concerning the RSS feed of comments: I am bitten daily by this, and have several users of my site on my back with this. I guess I am not the only one looking for that information. 😊
Motion #
Accept
Undecided
Reject
3
0
0
xavi
tobi_h
lindon
1.6. allow doc.tw.o_contributors to add faqs
Motion: Provide the perms to the "doc.tw.o_contributors" group to add faqs.
Discussion: xavi mentioned this to be a good idea. I agree. 😊
Is a doc contributor the same as a doc editor? If yes, then I agree. If not, then the doc contributor should be using the "Suggest an FAQ" feature, and the doc editor should approve/reject the suggestion.
Doc contributor belongs to the DocContributors group in tw.o, while Doc editor, belongs to DocTwoEditors in tw.o. For more information, read the ebm from June'08 (a passed motion reported at the meeting in july'08).