Editorial Board Meeting July 2007 | |
This is a meeting of the Editorial Board - it runs online from July 1 to July 31. 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: | |
|
Naming conventions for features. (Forwarded) | |
[+]
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 (Approved) | |
[+]
|
Batch creation from structures (Failed) | |
[+] Motion 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 roles of tikiwiki sites (forwarded to August) | |
[+]
Motion
|
info.tw.o | |
|
tw.o: | |
|
doc.two | |
|
dev.tw.o | |
|
themes.tw.o, | |
|
workflow.tw.o | |
mobile.tw.o | |
|
mods.two | |
|
i18n.tw.o | |
Future project to ease translations (in favor: dthacker) |
Multilingual development (forwarded) | |
[+]
Motion: encourage documentation at fr.tiki.org?
|
feature_autolinks enabled (Approved) | |
[+]
|
Organic growth using Keywords (Approved) | |
[+]
Motion
Create at least one 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 Keyword pages must link to all sub pages under that and vice versa, Backlinks is used (either automatically with the Backlinks Plugin or manually by checking.
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 sites (forwarded) | |
[+] Motion
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
|
Documenting doc bugs with tracker8 (forwarded) | |
[+]
Motion
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. 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. |
New Business: | |
New theme (forwarded) | |
[+] |
Latest news | |
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:
|
Older discussion | |
-- Gary/chibaguy Thanks heaps Gary for your nice (and hard) work! (Xavi) |
Site config (tabled) | |
[+] ML added a logout button, to be approved
|
Table of Contents in .pdf from documentation (forwarded) | |
[+] Motion: reorder features in docs as alphabetical list.
Opinions?
|
Modules Documentation Project (discussion item) | |
[+]
Motion (suggestion) (from irc chat on July 6th):
[08:54] btw, checkout this message I posted this morning to your work on Games pages: http://doc.tiki.org/tiki-view_forum_thread.php?topics_offset=1&forumId=1&comments_parentId=438
(...) [09:20] xavi, I don't know what to do about the page names. I strongly feel natural language should be the test. If people generally refer to something in plural form, if it's listed as a Tiki feature in plural form, etc., then I think it's page name should also be plural. But there is also a "make everything singular" trend going on, so how to resolve that?
|
Add doc.tw.o as a custom search provider (forwarded) | |
[+] 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. 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........ Next meeting: August 2007
|