This article has been published in Portuguese in http://espiritolivre.org
Table of contents
Introduce yourself to our readers. Where do you live and which area do you work these days?
Introduce Tiki Wiki. What does "Tiki Wiki" mean?
Tiki is a full-featured, web-based, multilingual (35+ languages), tightly integrated, all-in-one, open source Wiki+CMS+Groupware. Tiki can be used to create all kinds of Web applications, sites, portals, knowledge bases, intranets, and extranets. The underlying technology is PHP/MySQL/Zend Framework/Smarty/jQuery. http://info.tiki.org/Fact+Sheet
How has the idea of creating a CMS born? Tiki Wiki is based on another CMS?
An early interview, when Tiki was awarded "Project of the Month" on SourceForge.net in July 2003, offers some interesting historical perspective:
What are the differentials between Tiki Wiki and other CMS software? What public is Tiki Wiki indicated to?
How? In a nutshell "Software made the Wiki Way". Wikipedia is using the wiki way to build a free body of knowledge. We are doing something similar but to build a web application. The "Tiki model" consists of:
For example, we
Most CMSs don't have a powerful wiki (As proof, they don't dogfood). And most Wikis are missing important features of a CMS (ex: no template engine). Tiki is one of the rare solutions which offers both, and it has since very early on. There is no set limitation on what Tiki should do. For example, Tiki5 saw the addition of a shopping cart, and there are discussions about accounting functionality. So this means just about anybody with a web project should take a look at Tiki. http://tiki.org/Model
Tiki Wiki is licenced under what licence? Is there a corporate version? What are the prices? What are the differences between community and corporate versions?
There is no "corporate" version. While the license is permissive in terms of integrating with commercial applications, the culture of the community is to share all the available code in the core. If you want to invest funds in Tiki, the way to do it is to hire community members for support, training, etc. and to sponsor features (which become part of the core). You can also make a donation to the Tiki Software Community Association.
Is there a company that offer official support services to the product? What is it and why should users chose it?
http://info.tiki.org/Consultants How is your relationship with the open source community?
In the past, many CMS became known for their security troubles. How is the "security factor" treated in Tiki Wiki?
It's very important that site admins can upgrade quickly or turn off the feature which is vulnerable. The all-in-model makes upgrades easy. Site admins are warned of new versions in the admin panel (can be turned off). As part of our release procedures, we review that every executable file has a feature and/or permission check. Thus, the site admin can disable the vulnerable feature without having to upgrade or to take down the site. By default, risky HTML & ))JavaScript(( is blocked which is more secure but not very user-friendly in the case of a blog, where only trusted users have logins. So we have different permissions so the site admin can decide who is allowed to use potentially risky features. We have a security team, which responds to alerts and pro-actively improves various features according to our security dashboard. In your opinion, what is necessary to build a CMS with quality, elegant, safe and stable? Is it possible combine those four elements in just one solution?
Everyone can participate to any & all aspects of the code or the community:
Who don't you encourage using Tiki Wiki?
So, don't use Tiki if you intend to modify it heavily without sharing back the code. There are 600-700 commits per month. Within one year, your Tiki instance will be out of sync with the rest of the project.
Try to explain or summarize Tiki Wiki in 3 words.Wiki way webware Do you think a CMS make web developers lazier and less concerned about programing itself?
It really depends on the use case.
What are the plans for the future? What comes next?
We will continue our fast-pace of releases. Tiki6 (October 2010) will become Long Term Support (LTS), and thus, we'll be in a position to do some re-architecture in Tiki7 (April 2011). For example, to upgrade to Smarty 3 and Zend Framework 2 (if it's ready by then) Integrating with source control systems (SVN at first) will make Tiki a good all-round solution for software project management (we already have a ticket system, etc.) Over the years, we have pretty much done most of the features possible with existing technology and we integrated with other open source projects which rely on Flash. ))BigBlueButton(( for real-time collaboration tool (Audio/Video/Screensharing/Chat) and Kaltura for web-based video editing. The next big thing will be to adopt HTML5 and do the missing bits like image manipulation. We tried with java applets but we never got something stable and user-friendly enough. http://dev.tiki.org/Roadmap
For those who want to know more about Tiki Wiki, what should they do? Where should they search for? Where do they start?
Leave some words to our readers at Espirito Livre Magazine.
Add that knowledge to a wiki
And share their knowledge
|