Presentation Comm506

Tiki.org

Tiki Wiki CMS Groupware

Like Wikipedia, but for code instead of content
The general direction of computing -> everything is going to the browser (Firefox, Chrome, Safari, Explorer, Opera, and mobile browsers) -> The client.
The Server is a collection of software installed on a server and designed to generate HTML/JavaScript for these browsers.
Tiki is the Free/Open Source Web Application with the most built-in features. It runs on top of other software (Linux, MySQL, PHP that the user doesn't see)

Collaboration: Wiki, Forums, Tasks, File management, Permissions,
Publishing: News articles, Blog, RSS, Newsletter, Maps, Themes, Banners, etc.
Commerce: Shopping Cart, Payment, Membership, Accounting, etc.
Social networking: Friends, Inter-user messages, Surveys, Chat, Share link, Comments,
CRM: User database, Bug & issue trackers, FAQs, polls, etc.
Office productivity tools: Calendar, Spreadsheet, Drawings, Webmail, Time Sheet, Reports, etc.
E-learning: Quizzes, Slideshow, BigBlueButton webinar integration, etc.

$20 million according to the Basic COCOMO model
- https://www.ohloh.net/p/tikiwiki/estimated_cost
- "Beyond just development time, COCOMO is meant to include the design, specification drafting, reviewing and management overhead that goes along with producing quality software."

Yet, the Tiki Software Community Association (TSCA) has no employees
Tiki doesn't depend on any funding from any company, foundation, government or anyone. It thrives thanks to the community.

Stakeholders collaborate
- Consultancies
- IT departments
- Volunteers
Commercial eco-system based on services, not code.
- No free/community code vs proprietary code situation
Half the code is including code from other projects: "Standing on the shoulders of giants"

Questions?