This is a meeting of the Editorial Board - it runs online from August 1 to August 30 2007. 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.


  • please use a short clear statement as a motion (not a question) and place it in a box.

Last meeting: Editorial Board Meeting 2007 07
Next meeting: Editorial Board Meeting 2007 09

Old Business


Naming conventions for features. (PASSED)

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

It was agreed to avoid hard rules for now

  1. Natural Language - prefer most natural usage (no hard rules)
  2. Prefer most common keyword - use the most common keyword for that feature typed into google.
  3. Redirect to/from plurals: Whatever the feature uses for a name (plural or singular) (whatever sounds most natural) we must redirect from the other e.g. Blog redirects to Blog, Articles to Article.
  4. Shorter is better, Two words or less.
  5. No punctuation. Plain words only no camelcase
  6. Renaming an existing feature requires an EB vote, and notice to dev list.


MLP:in favor (of whatever lets cap this!)
chibaguy: in favor (I also thought this was tabled for now.)
Xavi: in favor

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.

note we gotta harmonize it across atleast two, doc and dev.

Clarify roles of tikiwiki sites (PASSED)

2009-09-20: This is now being maintained: Where



  • feature tour!
  • hype!
  • tiki news!


  • front desk (shoutbox)
  • user pages
  • prominent links to tiki sites


  • how to, faq and "official" documentation (whatever that means)
  • Factual information about what Tiki does now.
  • glossary of terms
  • links to dev. for bug reports
  • user forums! (moved to doc to better integrate with the documentation)


  • Wishlist of what Tiki could or should do in the future (bugs, RFEs, etc), contributor user tracker


  • themes repository
  • themes support
  • theme-related tutorials, howtos, etc.
  • extending Tiki visually such as by means of mods to .tpls, etc.




  • specialized sites


  • custom modules
  • commits that never made it in
  • extending Tiki functionally via hacks to .php files, etc.
  • eventually make it gforge-like area (maybe with workspaces?)


Future project to ease translations

dthacker: in favor
mlp:in favor
chibaguy: in favor generally, but I don't see why info.tw.o is necessary. I think tikiwiki.org should be the place for news, feature tour, etc. There's a danger of too much info diffusion/fragmentation here, I think. If user pages and shoutbox, etc., shouldn't be at tw.o, then I think a good breakdown would be to move them to a community.tw.o site. In other words, the "front page" of Tiki is tw.o. As the top domain, it's what the visitor should see first. "info.*" to me has a secondary ring to it, which I don't think is appropriate for the main face of the site/program. Also, I think it'd be good to get more feedback on this. Any proposal should go to the dev (especially) and user mailing lists just in case anyone wants to speak up.
xavi: I agree with chibaguy.
ricks99: in favor. my thinking is that the top domain of tw.o could be redirected to info.tw.o (so users would not notice the difference and none of the content currently on tw.o would need to be moved. my thoughts are that the "content" on info.tw.o should be: short, sweet, and sexy — a lot of flash and pizzaz. The "meat" is (already) on tw.o.

Multilingual development (Decided?)


Underline h2 and h3 headers in default css for Tikiwiki sites (PASSES)


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 )
(replace the "..." by the current details for that header in each css):

Copy to clipboard
H2 { ... border-bottom: 1px dashed grey; } H3 { ... border-bottom: 1px dashed lightgrey; }

Line type options:

  1. Dashed
  2. Dotted

Line Colour

  1. black
  2. grey
  3. lightgrey

Xavi: I suggest the example in the box above: dashed grey for h2, dashed light-grey for h3. no line for h1.
chibaguy: In general I think these details are best considered in the context of the theme design as a whole, but I vote in favor of this motion, for a general guideline.
mlpvolt: in favor

Discontinue tracking documentation bugs with tracker8 (PASSES)


Discontinue tracker8 here at doc.tw.o. Use Documentation Status instead, with author coffeeshop as backup. either through the "discuss" button of the related page, or directly as a new thread.
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.

dthacker says:

  • All items in tracker 8 were added by me
  • All items in the tracker were replaced by tags, which I think is a much more effective solution
  • No new items have been added to this tracker for 9 months
  • My goal was to make reporting doc errors a one-click process. Tags are not one-click, but they are one step. They update the content page and the status page simultaneously. I would love to put a big user-friendly button that would say "tag a problem on this page". Then we'd have the best of all possible worlds.
  • While I appreciates Rick's desire for limited noise, it's important to remember noise can be a symptom of a problem that needs to be solved.

I continue to urge that we use the coffeeshop for page discussion and tags for page problems.


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).
dthacker: I thought I killed it already! agreed.
MLP: in favor documentation status is best for errors in documentation, bugs in code should go to dev.

ricks99: against. currently the discuss link is being used by readers to log issues and request troubleshooting help. This creates a lot of noise (consider: http://tiki-view_forum_thread.php?forumId=1&comments_parentId=470).. if this site is supposed to be for completed, factual info only, should this be removed? I like having the tracker

New theme (PASSES)


Use Mittwoch theme as the base theme for doc.tw.o.
(in case it needs vote).

I uploaded the Mittwoch theme files to this site. Please have a look and make suggestions. Use the URL http://doc.tiki.org/tiki-switch_theme.php?theme=mittwoch.css to use Mittwoch. So far I haven't been able to do this while logged in. Maybe there is a conflict with Intertiki. When I log in, I get switched back to the site's default theme.

The left and main column need a wider margin between, I think. And maybe the line-height should be increased a little. There is also a glitch with the module titles not being the right size.

About the colors, I don't know if the color switching will be possible here because Intertiki might insist on overriding the choice. But probably the switching isn't really necessary. We can use the switching while choosing which color to use here. So far I only tested in Opera 9.2. The switching was a little flakey, with the preference not always being remembered, and sometimes a flash of blue at the beginning of the display (maybe this is a feature, not a bug. ;-) ).

Congrats. Gary. :-). I agree on you comments of needed changes, plus I would suggest:

  • make a clear difference in the box to create a new page in structure navigation bar (bakcgroup of the box for that field is too similar to background of the structure navigation bar surrounding it). Same for fields of login box, search wiki pages, etc. (confirmed on all browsers Firefox, Seabird, Konqueror, and IE 6 on GNU/Linux).
  • Options labels in drop down boxes as shown cut by the lower part, for me. Using Firefox Less cut with Mmozilla Seabird, and ok under Konqueror and IE6 under GNU/Linux.
  • Under Internet Explorer 6 (on a GNU/Linux platform) I see grey background for png images: text logo on header, icons on the "learn" and "write" columnes, etc. It's only me? (Xavi)

(Aug. 20) Thanks for the feedback. I spent a little time increasing margins for more white space, increasing line heights, etc. to improve readability. I still need to make the alternate images for IE6. My target was to have this theme ready to go when 1.9.8 is released, and figure that will be possible. (chibaguy)

Xavi: in favor.
mlpvolt: in favor
chibaguy: in favor



Reorder Table of Contents in .pdf from documentation (PASSES As AMended)


Add doc.tw.o as a custom search provider (PASSES)

Motion: In order to increase visibility of the the doc.tw.o resources, I propose that we add doc.tw.o (and possible tw.o, too) as a custom search provider. This would let users search the docs from their web browser. This is supported in FF and IE.

MLP: agree
xavi: Agree
chiba and ricks have weighed in, i call this a pass - mlp.

I am currently implementing a custom search provider for my site, and user feedback has been overwhelming positive.

See OpenSearch for details.

Just an idea........
chibaguy: If this is just a new file to provide to browsers or whatever (I only skimmed over the opensearch.org docs), then I don't see any problem, if it improves access.
ricks99: it is a single XML file placed on the webserver, then a single link... element added to header.tpl.. See my blog for details.

Next meeting: August 2007
This was a meeting of the editorial board.

New Business

Motion: Remove the long version of the Copyright on printed page. For example, print this page. It's a waste of paper.

And change by something like this:

Copy to clipboard
This is licensed under a Commons Attribution - ShareAlike License. http://creativecommons.org/licenses/by-sa/2.5/

mlpvolt: in favor (fait accompli?)
dthacker: in favor
xavi: in favor

Next meeting: Sept 2007


Get Started

Admin Guide User Guide


Keywords serve as "hubs" for navigation within the Tiki documentation. They correspond to development keywords (bug reports and feature requests):

Accessibility (WAI and 508)
Articles and Submissions
BigBlueButton audio/video/chat/screensharing
Browser Compatibility
Link Cache
Clean URLs
Communication Center
Compression (gzip)
Contacts (Address Book)
Contact us
Content Templates
Custom Home and Group Home Page
Date and Time
Debugger Console
Directory of hyperlinks
Documentation link from Tiki to doc.tiki.org (Help System)
Dynamic Content
Dynamic Variable
External Authentication
Featured links
File Gallery
Friendship Network (Community)
Gmap Google maps
i18n (Multilingual, l10n)
Image Gallery
Inter-User Messages
Kaltura video management
Live Support
Logs (system & action)
Look and Feel
Map with Mapserver
Meta Elements
Mobile Tiki and Voice Tiki
Performance Speed / Load
Platform independence (Linux-Apache, Windows/IIS, Mac, BSD)
Profile Manager
Search engine optimization
Search and Replace
Semantic links
Shadow Layers
Shopping cart
Social Networks
Spam protection (Anti-bot CATPCHA)
Tell a Friend, alert + Social Bookmarking
Theme CSS & Smarty
Tiki Manager
User Administration including registration and banning
User Files
User Menu
Web Services
Wiki History, page rename, etc
Wiki Syntax
Wiki structure (book and table of content)

Tiki Newsletter

Delivered fresh to your email inbox!
Newsletter subscribe icon
Don't miss major announcements and other news!
Contribute to Tiki