Why your web agency should adopt Tiki as a major web platform | |
|
Tiki.org | |
Tiki Wiki CMS Groupware
|
The general idea | |
|
How? | |
|
Specs & stats | |
|
Use cases/features | |
|
The Tiki Model ("Software made the wiki way") | |
|
All-in-one design | |
“In later discussions Torvalds explained the reasons for its choice: a fully modular architecture, like the one adopted for HURD, would have posed problems to a degree of complexity that it could have compromised the accomplishment of the project. To avoid such risks and keep the degree of complexity of the project as low as possible, Torvalds decided to design a monolith and he actually wrote all the architectural specs himself, avoiding all the problems related to collective projects (e.g. division of labor, coordination, communication). On the other hand, the HURD micro–kernel, a project in direct competition with the Linux kernel, has paid for the choice of pursuing a fully modular approach from the beginning in terms of the continuous delays that have plagued its development. Nowadays, it is still under active development and still lacks the stability and performance assured by the Linux kernel.” Source: Modular Design and the Development of Complex Artifacts: Lessons from Free/Open Source Software http://oss2005.case.unibz.it/Papers/25.pdf
|
Benefits of integrated model | |
|
Challenges of the integrated model | |
|
More about complexity and files | |
Tiki 7.1 contains 11348 files and it's the FLOSS Web application with the most built-in features. About half the code in Tiki is maintained by the Tiki community and the other half is re-using code from external libraries like Smarty, Zend Framework, jQuery, etc. So say we maintain about 6000 files. Sounds like quite a bit, but let's put this into perspective:
See: http://tiki.org/Coping+with+Complexity
|
profiles.tiki.org | |
|
How much is it "worth"? | |
|
Power users | |
|
Devs | |
|
SysAdmin | |
|
Mass deployments | |
|
Next 10 years | |
|
An example of app building: CartoGraf | |
|