This is a meeting of the Editorial Board - it runs online from June 1 to June 30. Undecided motions are carried over to the next month. Passing a motion requires 50% plus one of the current members. Members who miss two consecutive meetings are no longer considered current.
Old Business: - Done!
Renovate home page
See next home page
DT: xavi helped get items postitioned on the page, let's make sure all links work and install it
MLP:Looks good! Latest version at http://zukakakina.com/tiki-switch_theme.php?theme=mittwoch.css. See Coffeeshop post. Discontinue Right ColumnMotion: Discontinue the right column. Keep the Left column. Use phplayers menu for top bar login
in favor: xavi, MLP, sylvieg, chibaguy, ricks99
New Business
Naming conventions for features.
Motion To add to our Naming conventions a rule about feature names, and make it universal on doc.tiki.org, dev.tiki.org and tikiwiki.org, it is important to have a common way of naming features. So we always know that doc:Newsreader is it does and dev:Newsreader is what we wish it did.
Motion: Naming Rules for Features
MLP: Ok "prefer the singluar" dropped in favor of a more natural approach. chibaguy (after reading Skype log discussion of singular vs. plural for page names): [soapbox mode on] I think "natural speech" vs. "search term" isn't the best way to approach this question. People doing searches generally enter the singular form because it's the most common, most-root form and thus most likely to return good results. But there is a different rationale for page names. What is the logic for, for example, a page named "Comment" that has a title (h1 headline at page top) of "Comments"? This inconsistency shows there is something wrong with the page name, which doesn't correctly label the page content. If the page defines (the concept or whatever of) "comment," as in a glossary, then singular is appropriate. But the doc pages here are more comprehensive than that, and the plural form is often more suitable. This is the logic as I see it: reflect in the page name the use of the term in the Tiki context. People may search for "smiley" but they don't think "How do I use smiley?" An index will contain "smiley", but it will often refer to a page called "Smileys" or "Using Smileys" or whatever. That's the nature of that connection. Keywords can still be (and generally should be) singular, but they can link to pages named with either the singular or plural form (or a multi-word term if that's appropriate). It's counterproductive to streamline for simplicity's sake if comprehensibility is reduced in the process. When I see singular forms of words where I (as a user of the language) expect them to be plural, it strikes me as taking a principle too far. The impression is skeletal output that needs a commonsense touch to make it (in this case) good English. [soapbox mode off] Current features for renaming
Batch creation from structuresMotion No more batch creation of page in 6 languages from structures + let's erase all non English pages which have no content. Sylvie is looking into a batch delete of all pages which have no content.
MLP: Oui!
Clarify role doc.two vs dev.tw.o
Motion
tw.o:
doc.two
dev.tw.o
themes.tw.o,
workflow.tw.omobile.tw.o
mods.two
i18n.tw.oFuture project to ease translations
Multilingual development
MLP: Use multilanguage features as they are now?
feature_autolinks enabled
Organic growth
Motion
Let's create at least of page per Keyword and have Tiki helps links to there, but let's wait for a need to create Feature Admin, Feature Setting, Feature Ref, etc
Xavi: However, I like the basic common structure for all pages (Feature User, Feature Admin, Feature Details). I would suggest to keep it as it is, and and new pages when and where needed. But for new documenters, that basic division in three basic pages per feature allow organizaing content, etc. MLP: About the Tikiwiki documentation - updated.
Underline h2 and h3 headers in default css for Tikiwiki sitesMotion
Make header2 and header3 styles in css be underlined with either dashed or dotted lines, either black or grey colours. Not h1 headers. Many people wants to separate more visually the sections between headers (a la mediawiki/Tikipedia style), and they are using hr html tag instead (uglier). Look in here at this page itself, as example (some people added here and there --- tags to visually separate sections...) For instance, what I'm using in many places (see demo at http://www.moviments.net/drecerca/Ajuda )
Copy to clipboard
Discontinue tracker8 here at doc.tw.o (doc. bug report through trackers)Motion
Discontinue tracker8 here at doc.tw.o. Use Author Coffeshop forum instead, either through the "discuss" button of the related page, or directly as a new thread. Xavi: I hadn't seen that before (just discovered it today), and I think it's not needed, or even that it diverts to much the places to invest energies for new documenters. I propose to use the plain Wiki way (most documentation bugs could be fixed by normal registered users, nowadays, since they can edit almost all pages). If motion is accepted, link from http://dev.tiki.org/Documentation to http://doc.tiki.org/tiki-view_tracker.php?trackerId=8 ("Doc Bugs & Wishlist") should be removed, and write Author Coffeeshop forum instead. Next meeting: July 2007
|