Editorial Board Meeting 2009 06 | |
Note About Quorum and Voting[+]This methodology changed in May 2009, as an attempt to resurrect the effectiveness of the EBM, which had been stopped since October 2008. We hope this way meetings are more agile to create, and decide upon.
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 June 1st to June 30th, 2009.
|
Motions Passed Last Month | |
1.1. Use proposal plugin for future EBM | |
|
Motions Defeated Last Month | |
none |
1. Motions Carried Over | |
|
1.1. Change doc.tw.o menus | |||||||||
Motion: Change menus according to doc.tw.o revamp proposal page: http://tikiwiki.org/doctwo+revamp .
marc: I hope top menu will one day be used for global *.tiki.org navigation 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.) lindon again: would also like a link to my user page for registered users Things like Author resources would appear only for authors. Not sure I agree about having User Pages on doc.tw.o. IMHO, User Pages should be limited to the community site. (ricks99) I'd also like to see the registration process change for tw.o changed so that new registrants can choose:
|
1.2. Change doc.tw.o modules | |||||||||
Motion: Change modules according to doctwo revamp proposal page.
|
1.3. 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?
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.
|
1.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
-1 — color is different than colour (ricks99) +1 No disrespect meant to UK people, but many languages have regional variations but are still essentially understandable and considered a single language. Tiki's en-uk is probably meant for UK-focus sites. (chibaguy)
|
1.5. Remove my footnotes | |||||||||
to simplify interface
Discussion: +1, i never used it myself — luci
-1, I haven't used it but think it could be useful. Not sure if staging would replace it for me. (lindon)
|
2. New Motions | |
2.1. New Motion 1 | |||||||||
Motion: I would like to have the following entry added in its FAQ sections found at http://doc.tiki.org/tiki-list_faqs.php
|
2.2. New Motion 2 | |||||||||
Motion: I would like to have the following entry added in its FAQ sections found at http://doc.tiki.org/tiki-list_faqs.php
Security:
|
2.3. New Motion 3 | |||||||||
Motion: I would like to have the following entry added in its FAQ sections found at http://doc.tiki.org/tiki-list_faqs.php
RSS:
|
2.4. New Motion 4 | |||||||||
Motion: Provide the perms to the "doc.tw.o_contributors" group to add faqs.
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.
|
2.5. New Motion 5 | |
Motion: Keep doc.tw.o for docs (what Tiki does) and send all support requests (how should I do this?, does Tiki do this?, etc) to http://tikiwiki.org/forums and bug reports/feature requests to dev:report a bug (what we wish Tiki did). So remove this page and ones like it: Feature Problems and review/clarify get help. Here is an example of pollution
Maybe we can have a custom module or plugin on each doc page: For This Feature
And, ideally, all doc pages that have corresponding sister wiki page on dev.tw.o should have a prominent link. {PROPOSAL(caption="Motion #")}
|