Many open source web applications have a large number of features available as add-ons. They need to be installed separately and there are often several add-ons for the same purpose.
Instead, the Tiki community uses an all-in-one Model. One of the consequences is that Tiki is the FOSS Web Application with the most built-in features.
Not only has this been true for a quite a while now, but Tiki also has a much faster than average release schedule, with 2 major releases per year.
- 2008-08: What's new in Tiki 2.0?
- 2009-05: What's new in Tiki 3.0 LTS?
- 2009-11: What's new in Tiki 4.0?
- 2010-06: What's new in Tiki 5.0?
- 2010-11: What's new in Tiki 6.0 LTS?
- 2011-06: What's new in Tiki 7.0?
- 2011-11: What's new in Tiki 8.0?
- 2012-06: What's new in Tiki 9.0 LTS?
- 2012-12: What's new in Tiki 10.0?
- 2013-07: What's new in Tiki 11.0?
- 2013-11: What's new in Tiki 12.0 LTS?
- 2014-08: What's new in Tiki 13.0?
- 2015-05: What's new in Tiki 14.0?
- 2016-04: What's new in Tiki 15.0?
- 2016-11: What's new in Tiki 16.0?
- 2017-04 (planned): What's new in Tiki 17.0?
Even with all the features, there are still several hundred feature requests. But most of these are requests for enhancements to an existing feature. Once a feature is in the code base and is basically usable, it usually evolves naturally/organically. In each Tiki version, most features are refined at least a bit. Some like Webmail need a lot of work. But at least, it's a start.
But when a feature is totally absent, it takes a spark to make it happen and take it to the level where is starts evolving naturally/organically.
Major features totally missing
Desktop publishing as will be needed for the Online Publishing HouseSee mPDF
- Naive Bayes classifier
Something like kfm or elFinderDone in Tiki11
- Social Bookmarking
- Link checker (internal and external)
- Repository Browser for Code Review
Interface with Monitoring tools: Nagios, Zabbix- etc. Would also be part of TRIM and CheckCode for Nagios was adding. Documention: https://doc.tiki.org/Monitoring
- A well-defined API for building applications on top of, or integrating application into Tiki. People often say this but without a specific example, it's difficult to follow-up upon. Current plugins structure is very efficient to interface with 3rd party services. Can you give 2-3 specific examples of applications or types of applications you have in mind? Thanks! --marclaporte
Major features missing from main code base, but available with 3rd party mods or workarounds
- Learning Management features like Moodle (gradebook, class management, etc.) though Tiki does have some 3rd party mods for this
- E-democracy system (we have polls and such but it's not the same as a full-fledged voting/election system)
- Online Help (not d.tw.o)-dthacker / marclaporte: can you explain a little more?
- Event Management system : while most of this can be done by using the wiki, calendar and user trackers, it's too difficult for someone new to Tiki. Added to Use Cases
- Have a calendar in the main code base. Either including Mod extcalculator, Mod calculator or another...
Please Add to Wishlist instead
- External Authentication
- Interface with SiteMinder (http://www.ca.com) (similar to InterTiki, except yield to SiteMinder for authentication as an enterprise-wide intranet authenticator)
- Debian and Ubuntu Packaging Team
- VMware and Xen virtual appliances
- Trackbacks in blogs
See also: Interesting Features from other Web apps