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.

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.

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

VOTE
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.

VOTE
MLP: Use multilanguage features as they are now?
Xavi: I'd suggest to use intertiki, and french doc. being set at doc.tw.o. Granting editor perms to editors at fr.tw.o that write documentation, etc.
dthacker: agree with Xavi
chibaguy: agree with Xavi

— Xavi's side wins but what does this mean wrt the motion?

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

VOTE
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

• 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.

VOTE

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

Overview
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 2.0.0.4. 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)

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

1. Which color should be used for doc.tw.o?
   • Proposing Blue: Xavi
2. If none of these colors is right, please make suggestions.
   • Xavi: They are right (and very nice, thanks Gary 😊. Looking at drupal.org and joomla.org, for instance, their sites tend to be more colourful. These Mittwoch themes are by far much better than many of previous styles in Tikiwiki (my personal opinion, of course - I love white background with colourful details here and there...), and I just wanted to suggest that for further improvements, to include some more color on top of white background (hec.css is quite in that way..., even if simpler compared to Mittwoch).
3. In some places (dropdown select) there may be contrast problems (i.e., not enough contrast), so those can be changed. I haven't checked on a variety of displays.
4. Is the small plus sign sufficient to indicate the page edit, etc., tools dropdown?
   • Xavi: I don't think so, if we think in new users, newbies in computer science, ... (usability). I would suggest a much bigger icon, or just a word like "tools" or similar (like in andreas09.css). However, usability geeks frequently complain about those hidden things (when thinking in potential new users with low skills of computer usage - remember talk from Alain in TikiFest198 ).
5. Or would people prefer the standard Tiki wiki page tools layout (for edit, print, etc.)?
   • Xavi: If this is going to be a standard theme for doc.tw.o only, then I would vote for this option (most tiki sites have standard layout for tools). If Mittwoch can be released as LGPl, then I would HIGLY encourage making this nice new theme as the default for 1.10 sites, and thus, also for doc.tw.o.
6. The horizontal navbar can be either static links or a PHP Layers menu, so this should be decided.
7. Styling is also done for a PHP Layers menu in the side column so that's an option.
8. The Site Identity header is done, to match the current one at doc.tw.o.
9. Other suggestions/changes/etc.?
   • Underline (dashed in greys) h2 and h3 headers in default css's for new tikiwiki sites
   • make some kind of "A+" "A-" "Reset" sings on tikiwiki site identity header (a new option) so that users can increase or decrease in a click the default size of text in the site. (similar to many more usable sites: example: http://joomla.org header...
10. ??

-- Gary/chibaguy

Thanks heaps Gary for your nice (and hard) work! (Xavi)

VOTE
(interpreted votes below wrt amended motion 2)
dthacker: agreed. propose alpha sort (am I the only persone that looks up a feature by name!!!?)
mlpvolt: disagree - we need to sort the features into categories, so people are aware of related/overlapping features. categories plus alphabetical is fine with me.
chibaguy: disagree. I think we should follow the pattern of a book: the table of contents lists things in a meaninful hierarchy. Additionally, there could be an index page that lists alphabetically.
ricks99: disagree. a toc is not meant to be alphabetized — it should reflect the actual structure of the document. Maybe you're looking for an index instead?
xavi: disagree. The problem might be in the motion summary. (The original idea-motion was "in a logical way, or as alphabetical list"). So if motion was the one stated by mlpvolt, probably more people would have agreed at the first glance?

VOTE

Xavi: I agree.
MLP: agreed.

VOTE
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.

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

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

Next meeting: Sept 2007