Table of contents | |
|
Where (which site?) | |
Info | |
Note Please note the info.tiki.org is a redirect to a perspective view of the tiki.org site now and is the default you see when you access https://tiki.org directly. Introduction, clean gateway to various Tiki sites and pages.
Provide an outlet for the "official" voice of Tiki and the Tiki Software Community Association.
|
Doc | |
https://doc.tiki.org
|
Basic docs exception | |
Tiki documentation about backup is not a Tiki feature, but since it's basic info, it should be on doc as well, along with Install, upgrade, but not Troubleshooting, Toolbox, etc.
|
Dev | |
https://dev.tiki.org
Perhaps this one should be split into more than one perspectives
|
Developers Mailing List | |
(aka tikiwiki-devel AT lists.sourceforge.net)
|
Profiles | |
https://profiles.tiki.org
|
Themes | |
https://themes.tiki.org
What Tiki looks like
For developers |
Community (tiki.org) | |
How to address the fact that many posts are not in the right forum? |
Translations & i18n | |
Should collaboration about translations be on dev or on tw.o? On one hand, it is about improving Tiki code. On the other hand, it's very easy code and it relates to community things (local events, etc.). Perhaps the best is that everything related to translation be a workspace of tiki.org to make it easier for translators. So let's make it that way: dev.tiki.org should assume you only will work in English. From the moment you are working on a non-English site, all the info should be in a workspace of tiki.org or a wish in the i18n category (because we want feature requests and bugs to be centralized). The i18n workspace should cater to the following
Maybe we should have i18n.tiki.org for the translation perspective, and give the translation server another name? |
What not to do | |
Here are examples of what not to do, and why.
|
Related pages | |
|
Undecided | |
Still anything relevant on old doc motion? | |
http://doc.tiki.org/Editorial+Board+Meeting+2007+08#Clarify_roles_of_TikiWiki_sites_PASSED_ |
Pages about a technology or a standard | |
For example, Ajax, Mootools, jQuery, MicroFormats, etc...
|
Documentation about making themes | |
On doc? http://doc.tiki.org/Themes or on http://themes.tiki.org/ ? Xavi:
This being said, if there is a link from Tiki to the doc site, they should be a short page, describing the feature in 1 sentence with a link to the relevant page on themes.tiki.org doc.tiki.org/Themes should be a gateway page with everything related to themes. A long series of short sentences and links. |
Release notes and What is new in each release | |
on Community or Doc? or maybe even info?
Marc Laporte wrote:
For each release, we have an announcement on info.tiki.org, the documentation page about that version on doc.tiki.org and release notes on tiki.org That is too many. How about merging release notes into the doc page?
|
Discussions about themes | |
In community forums or themes site? or here Why Tiki themes never look WOW ? Xavi: if themes.tw.o has to exists (a part from tw.o), then I would suggest to keep discussion about themes in themes.tw.o , and the forum about themes in tw.o close it and leave apost informing everyybody to post about themes at the other site. Gary (chibaguy): I'd prefer theme-related posts to be a themes.tw.o, but as long as tw.o still has a "themes" forum, people will post in it, naturally. Maybe the themes forum at tw.o should be made read-only, with a note and link to post at themes.tw.o instead, if that's our choice.
|
About improving a site. | |
TwoRevamp, DevTwoRevamp, DevTwoDogFood and Admin tasks should be on tiki.org because it's about community organization and planning. |
Pro | |
|
Against | |
|
Demonstrating a bug | |
Sometimes, it's useful to have a page, etc. to demonstrate a bug. http://demo.tiki.org is a good place for this Or even better, the show.t.o instances linked to bug reports. |
Should demo go from community to info | |
Pro | |
Community is for people that are already decided to use Tiki. Demo is more for marketing. |
News | |
|
info | |
|
community | |
Easier to get comments about news
|
Footer | |
This will be a common footer for the main *.tiki.org domains. See http://branding.tiki.org/Footer+code.
|
Where (type of data) | |
If you just have one tool, it is possible to use wiki pages for discussions (ex.: Talk Pages), and forums for permanent content (Sticky posts). However, when you have many tools at your disposal, which one should you choose? Ask yourself the following questions:
|
Wiki | |
Your own wiki page is a great place to express your opinion. Forums too! |
Forum post/Mailing list | |
|
Blog post & news article | |
|
Bug tracker | |
|
Comments | |
|
Events & Calendar | |
|
Private email & chat | |
|
Group chat | |
alias
|