• Easy Hosting / SaaS / Hosted solutions / Wikifarm (D)
• Teams / Working groups / Special interest groups / local user groups / p2p leadership (C)
• Integration of new contributors to the community (D)
• Migration to Tiki (C-)
• First impression / New users / Ease of installation (C)
• User Experience / Look & Feel / Themability / User interface / Usability / Ease-of-use (C)
• tiki.org Information / Promotion / Marketing / Public Relations (C)
• Dashboard / Stats / Metrics / Key Performance Indicators (KPI) (C)
• Licensing / Legal (C)
• Extensibility / Expandability / Mashups / Integration with 3rd party apps & code reuse (C)
• Relations with the outside World / Standards / participation to events (C)
• Money and Fundraising (C)
• Sites & infrastructure (C)
• Customizability / Hackability (B)
• Performance / Scalability / Server load (B)
• Security (B)
• Commercial support options / Paid support / Commercial opportunities (B)
• Total cost of ownership (TCO) (B)
• Decisional structure / Governance / Guidelines / Rules / Strategic planning (B)
• Documentation (C)
• Install base / Adoption (C)
• Long term sustainability / Future-proofness / Lock-in protection (B)
• i18n / translations (B)
• Components / Platform independence / Code infrastructure / Architecture (B)
• Lifecycle, releases and packaging (A)
• Upgradeability (A)
• Community / Volunteers / Free support (A)
• Features / Development / Stability / Interoperability (A)
• Eating our own Dogfood (A)

Priority of the Packaging Team.

Priority of Tiki Admin Group and Community Building Team

Strengths Tiki as an app has pretty much all the features to support this.	Weaknesses Too few functional Teams.
Opportunities Growth Easier integration of newcomers DogFood for Social Networking	Threats Without teams, the organization can't scale
Recommended action Assign more & more responsibilities to contributors and improve that page with pictures & bios Make a global list of tags/categories/responsibilities Promote Teams by dogfooding workspaces November 2009 (Tiki4), Workspaces will be used for a more p2p organizational model for the community. Establish groundwork for emergence of local user groups like Drupal by using all the revamped Map features in recent versions of Tiki, TikiFests and i18n.tiki.org Setup Viral Tiki and Connect Formalize and make a strategy around the Evolution of participation	Related links http://shirky.com/writings/group_enemy.html http://en.wikipedia.org/wiki/Dunbar_number http://www.lifewithalacrity.com/2004/03/the_dunbar_numb.html http://www.spring.org.uk/2009/07/10-rules-that-govern-groups.php http://www.wikisym.org/2009/08/10/wikisym-2009-keynote-community-performance-optimization-making-your-people-run-as-smoothly-as-your-site/

Priority of Community Building Team and Wishlist Triage Team (because they see the good bug reports and patches)

Strengths It's a friendly place Easy to get commit access: How to get commit access	Weaknesses Learning curve will scare many away Not clear how to get involved, who to talk to All in one design makes it more challenging to start contributing. External modules in other apps can be very simple and easy to learn from, without bothering with big picture (at first, anyways)
Opportunities Rick's blog is an "attempt to combat the Tribal Knowledge Syndrome that too often plagues software development projects"	Threats Not having fresh energies could lead to staleness.
Recommended action Make sure tiki-register.php is useable/useful Better documentation and examples. Plugins and modules are great to learn from. Shoutbox is a good example as well. More formal Teams Mentorship program Better promotion of IRC & Mailing Lists Better explain Where to find information and to participate.	Related links

Priority of the Consulting Ecosystem Team.

Once marketing worked and people do indeed decide to try it out.
Priority of UX and Themes Team (for visitors and content editors) and Configuration Profiles Team (for site admins)

Strengths Tiki has arguably more built-in (out-of-the-box) features than any other Web application so users that are looking for lots of features will be attracted. 3.x installer and general User Interface is much better than 2.x which itself much better than 1.9.x	Weaknesses For years, the Tiki community has been very "developer-focused" Clutter. Tiki has tons of features but it's too long/difficult to get started. "Obscure" features complicate implementation for would-be admins. http://doc.tiki.org/Tiki8#Admin_panels_-_filtering_basic_and_advanced_preferences 6000 to 10000 downloads per month, yet many give up because there are too many features and it's difficult to setup
Opportunities By leveraging all the features with better profiles, the community would grow faster. It would make it easier to have custom distribution-like profiles and cater to vertical markets without causing issues.	Threats Lack of adoption Bad reputation Without growth/recruitment, normal (natural) turn-over of volunteers will hinder Tiki development. Lack of available ressources for small projects makes clients disappointed.
Recommended action Testing Tiki installations on major Shared Hosting companies Focus on 1-click installers Improve install script Done in 3.0 Continue to promote initiatives such as Tiki for Smarties Enhance the profile manager and generate a profile for each of the most important Use Cases and encourage sub-communities around specialties / verticals Started for 3.0 Continue work on the magic admin panel. Clay Shirky (shirky.com) It's Not Information Overload. It's Filter Failure. Instead, admin panels have been re-organized manually in 3.0 Tiki8 has filters in the admin panels which will lower the learning curve. Nicer themes Done for 3.0 This aspect is hindered by disorganization on *.tiki.org sites When an active member is in need for support, "recognised consultants" should complete their mandate. Else, there should be a "notification system whereby some sort of management group about consultants" alerts other clients in regards to the level of reliability of the said consultant. Like a rating system.	Related links Featuritis vs. the Happy User Peak

Priority of UX and Themes Team

Strengths Tiki is very themeable. Themes.tiki.org has good content and permits to test all themes with most features.	Weaknesses Default themes are not as nice as other leading projects. No commercial themes available With all the features, some lack polish & focus Themes.tiki.org is confusing (demo site vs doc site to install/create theme) There is still some inline css style which is hard to deal for designers. There are too much (but decreasing) tables used for presentation purposes. The CSS structure of all the grids is not enough standardized. There are no guidelines for developers about which styles they have to use in which part of the pages. So, they use what they can or try to see in some other grids what is generally used. This is a main problem for newcomers. The community should deploy some efforts to deploy factorized tools (like smarty plugins) which leaves less initiative to coders when they have to choose a structure. Such plugins are well suited to the community which is very open to (quite) anyone. Once we will have less bugs (we are not that far away), will come time to talk about ergonomy. There is A big big work to do. Our target has to be "one guy who knows nothing from wiki, web, etc... has to understand what he can do and what he has to do to achieve his work (change a wiki page, post in the forum...)". Today we are far away from this.... Developpers are, usually, not good in look and feel or ergonomy ! They often consider that the work is done when the functions are running and the buttons are working. Having a good look and feel is just another work.
Opportunities With a little work, Tiki could be sexy.	Threats People will use Wordpress or similar because there are hundreds of nice themes.
Recommended action Setup a theme/UX and Themes Team Gary, luci, Patrick, ricks99, etc. are doing a great job Improve the content editing interface Done a bit for 3.0, more to come in 4.0 Improve the admin interface Much better in 3.0 More user & centric design Done a bit for 3.0, more to come in 4.0 Would it be possible to write a script to batch convert Joomla! or Wordpress themes to Tiki? Maybe a script could do most of the job, finished by a designer. For themes.tiki.org to be less of a theme testing place and more of a I-want-to-download-and-install type of place. demo.tiki.org could be used to test themes. http://UI.tiki.org project Done a bit for 3.0, more to come in 4.0 Skeleton theme for designers done in 5.0	Related links Featuritis vs. the Happy User Peak

Priority of Communications Team, Branding Team and Consulting Ecosystem Team.

Priority of Analytics Team and Tiki Admin Group

Priority of Legal Team

Priority of Developers Team

Priority of the Communications Team and Tiki Admin Group

Strengths Tiki already supports a large number of standards via various interactions Participation to WikiSym 2007, 2008 and planned in 2009	Weaknesses Tiki is not good enough at marketing and needs to be more outward facing, and in contact with various actors of the Open Source World.
Opportunities Participating to more standards. More synergy Unexpected opportunities	Threats Lost opportunities & isolation
Recommended action We should apply again in 2009 for Google Summer of Code. Accepted!! 4 projects! Be more active in standards and associations, such as OSCOM http://www.advogato.org/article/544.html http://www.advogato.org/article/657.html Add more support for various: interactions Participate to more events Tiki community members should keep/improve contacts with WikiSym (Using Tiki for WikiSym2009) Open Source Initiative (we are now a member) WikiMatrix OpenSourceCMS OSL Fossology Etc And all project of the Wiki Landscape and CMS Landscape Presence on Social Networks such as Facebook, LinkedIn, etc Encourage presence of firms like Citadel Rock at events like Web 2.0 Expo Invite some of our clients to Tikifest to get their feedback, give them demos, get them involved, gave them a taste of the future, etc...	Related links

Priority of Fundraising Team and Finance Team.

Strengths The Tiki association has a bank account. Easy to make donations at http://tiki.org/Donation	Weaknesses While there are occasional sources of funding, there is no major recurring revenue.
Opportunities Improve Tiki by DogFooding some new accounting features. Get funding to pay for Travel Expenses for TikiFests. Ex.: A yearly TikiFest for top 20-30 active contributors. Source of revenue: Ads, deals with hosts, love money, charity funding.	Threats Getting into political & ideological debates. Jealousy about where the money is allocated Becoming a target for lawsuits
Recommended action Short term: Continue the informal way, where people donate directly to active contributors and make a list of Potential Funding Start a Finance Team Start a Fundraising Team Medium term: Have appropriate discussions about how to best get money, invest it, etc. Transparency, governance, etc And proceed with best solution, presumably to set up a foundation to handle this. Do not engage in unsustainable spending Add recurring revenue generating code in the application (optional of course). It would be a way for Tiki admins to help Tiki at no direct cost to them. It could be Google Adsense type ads visible to Everyone/Admins or no one. Think Firefox Viral Tiki Priorities for TSCA funds	Related links http://producingoss.com/en/producingoss.html#money http://www.spi-inc.org/about/

Priority of Dogfood Team and Infrastructure Team

Strengths Current *.tiki.org are split amongst several community members Tiki has all the feature-set we could want and it's great DogFood dogfood is great long term strategy	Weaknesses Not ready to scale to higher volumes, already doc.tw.o and dev.tw.o are straining current server Lack of some tools like http://www.statsvn.org/ Lack of a dedicated team assigned to this aspect. Not all sites are kept to the latest version. dogfood can taste bad in the short term
Opportunities Greater synergy with Open Source community by collaboration with organizations like Open Source Lab	Threats Disappointing new people as load increases
Recommended action Look into: http://osuosl.org/hosting/services Move all site management to TRIM	Related links http://docs.joomla.org/Sites_and_Infrastructure_Working_Group

Priority of Developers Team

Strengths Tiki has hundreds of optional features built-in so you can customize without changing the code. And upgrades are painless. If you do need to change things, you can do quite a bit with the Smarty Template engine, which permits basic programming logic. Tiki uses simple code and a simple database structure. It is vast but each part is simple. All the data is in a database, for easy re-use. Easy to contribute	Weaknesses It's so vast that there is a learning curve. Because of alternate code model (wiki way, all-in-one), people don't always get it right away
Opportunities	Threats Code changes that will make Tiki less hackable
Recommended action Improve Hello World	Related links

Priority of Performance Team

Strengths I can personally attest that each new version of Tiki has gotten faster. 1.9 is clearly faster than 1.8, which is clearly faster than 1.7 ( I don't remember before that). Some indexes were added and some optimizations were done as bottlenecks were reached. Tiki4: A new Performance admin panel was added to help people optimize. Some proactive performance profile was done on Tiki5, and our YSLOW score was drastically improved with Minify JS and Minify CSS Reality: we have no metrics to compare Tiki performance to other similar applications (Drupal, Mambo, etc).	Weaknesses Tiki has a really bad reputation for performance because, for the longest time, tiki.org was hosted on a personal server. This server was underpowered and overloaded. Ever since Oliver Hertel took over tiki.org on a server from server4you.de, it has been zippy. Reality: we have no metrics to compare Tiki performance to other similar applications (Drupal, Mambo, etc).
Opportunities Large projects have been very helpful and will continue to be hugely helpful to identify real bottleneck with real data (vs some people interested in theory and worrying about performance bottleneck, which in reality, are not).	Threats FUD: the same way it's difficult for other to prove Tiki is worse than another given app, it's very difficult for us to prove that Tiki is fast/scaleable.
Recommended action Launch Performance challenge Get someone in charge to get metrics and then, ask marketing to explain the situation, good or bad. It is ok to say "Tiki has way more features, but it's a bit slower". Continue work on Performance Friendly challenge to our friends in other Open Source CMS and Wikis for a speed test / stress test challenge. This would be a great topic for a www.codefest.ws and collaborate on these aspects.	Related links

Priority of Security Team

Priority of the Consulting Ecosystem Team.

Strengths There exists a growing market of full-time freelance Tiki Consultants, able to deliver installations that "just work" - for a price. These consultants work well together and share back to the project when they can. Top-2 on WikiMatrix	Weaknesses The small market lacks economies of scale, best practices are not transmitted, small outfits lack marketing, mgt and admin specialists.
Opportunities Create an "un-corporation" - networks of solo/small shops that repeatedly contract each other - encourage specialization in vertical markets, roles, features. Build working relationships between developer teams. All developers become part of the network.	Threats Conflicted interests among competing outfits. Struggle to get the biggest piece of a small pie - rather than focus on growing the pie.
Recommended action Short & Medium term: Grow the Pie 1- Identify & promote Tiki service providers. Started at http://info.tiki.org/Consultants and http://www.wikimatrix.org/consultants/Tiki+Wiki+CMS+Groupware/ 2- Ask these service providers to prepare some guidelines, like a code of conduct of vendors For example: http://typo3.com/Consultancies.1248.0.html http://drupal.org/drupal-services Encourage presence of firms like Citadel Rock at events like Web 2.0 Expo Start a guide to Tiki consulting: best practices Review all Tiki-powered sites to search for web shops that made the site for others tech firms / web shops / consultants / etc which use Tiki and invite them (ML invited 20 towards the end of November 2011) Tiki Suite is a new option Medium term: Monitor tender/freelance sites such as Upwork Invite vendors who list Tiki to participate to the community Have our freelancers be listed WikiFarm - shared hardware platforms. bounty system explicit networks / recommendation system. More Dogfood. Maybe a form on info.tiki.org to reach all consultants at once? Live Support Service	Related links Business Models

Priority of the Tiki Admin Group

Thinking of open source like free kittens/puppies, it is necessary to allocate time for maintenance.

Strengths Tiki's all in-one-model makes upgrades easy Tiki upgrade script is pretty good (can upgrade from any to any future version) 1-click installers support upgrades	Weaknesses Fantastico doesn't upgrade as soon as a version is released. Lots of features: learning curve Not all features are stable in Tiki so it's important to keep experimental features off
Opportunities TRIM is coming along nicely	Threats
Recommended action Improve relationships with 1-click installers (ex.: support LTS) Continue work on TRIM	Related links http://en.wikipedia.org/wiki/Total_cost_of_ownership

Priority of Community Building Team and the Tiki Admin Group.

Strengths Currently, Tiki has a lightweight decision-making process. Decisions are taken by consensus, where whoever does the work has more mojo 😊 If a vote is needed (which is very rarely the case), the Tiki Admin Group has "decisional" power. More on this at model. TAG is large enough, is composed of people with various backgrounds and yet, is highly cohesive (as of 2008-06). Social Contract	Weaknesses Decisions and who does what are not clear for the community, especially newcomers.
Opportunities Dogfood Tiki to become a better E-Democracy system	Threats Some community members could feel that they do not have sufficient influence. There could be doubts about transparency & governance. As of 2008-06, I see no evidence of any risk here. A fork. Forks are usually very bad for everyone. Should be avoided as much as possible. Spending too much time on politics and administration and forgetting that our focus is a a great community building a great community management system (software, the Wiki Way). Rules & guidelines are a means, not a goal. The Tyranny of Stuctureless
Recommended action TAG: (2 + 2 -> we are at a good number now. Renew if some become inactive. Assign more & more responsibilities to contributors promote groups A foundation Clarify Mission statement or something like a manifesto or philosophy http://branding.tiki.org/Goals Community-managed SWOT	Related links http://meta.wikimedia.org/wiki/Wikipedia_power_structure http://en.wikipedia.org/wiki/Strategic_planning http://en.wikipedia.org/wiki/Open_source_governance http://producingoss.com/en/producingoss.html#social-infrastructure http://webmink.com/essays/open-by-rule/ http://www.oss-watch.ac.uk/resources/governanceModels http://www.oss-watch.ac.uk/resources/ssmm

Priority of Documentation Team

Priority of Communications Team, Consulting Ecosystem Team and Packaging Team.

Strengths Tiki has a significant number of installs. In recent versions, a note warns admins of new versions.	Weaknesses People don't upgrade. We find people with 2-3-year-old Tikis We don't know how many installs there are and what features people are using. We can't pull out a feature, confident that almost no one will be affected.
Opportunities A larger install base could bring more energy to the project, in particular, if we include invitations to participate and promotional links in default templates.	Threats Security issues because people don't upgrade.
Recommended action Testing Tiki installations on major Shared Hosting companies Focus on 1-click installers Viral Tiki and better promotion. profiles for easier installs Nicer themes	Related links http://en.wikipedia.org/wiki/Product-Market_Growth_Matrix

Priority of the Tiki Admin Group.

Priority of i18n Team

Strengths Tiki's i18n features are excellent. Wiki-Translation.com 40+ translations (but many incomplete) Suitable infrastructure (UTF8, etc.) to support more languages	Weaknesses Nobody in charge so we have no up to date metrics on the state of our translations. Could be easier to translate No one is actively coordinating with translators.
Opportunities Opportunity for growth in l10n where Tiki would have a local advocate.	Threats None really, just lost opportunities
Recommended action Setup an i18n Team and i18.tiki.org in collaboration with the use of maps. Promote TikiFests and local Tiki user groups Continue to be very active with http://wiki-translation.com/	Related links http://docs.joomla.org/Translations_Working_Group

Priority of Developers Team

Strengths PHP/MySQL/Smarty were excellent design choices 10 years ago and they still are today. Tiki has been able to leverage these re-use their experience. Tiki's current infrastructure has supported a huge number of features. All-in-one structure makes it both easier and more difficult to evolve. Newer additions of PDO, Zend_Framework and jQuery improve Tiki without more code overhead.	Weaknesses All-in-one structure makes it both easier and more difficult to evolve. Easier because we can change everything More difficult because we take everything into account Code is messy in a lot of places, which makes the Code Infrastructure an area that needs improvement to better support new features. Solid code base, but hard to understand sometimes. Lack of coding documentation (like phpDoc or Doxygen) and enforcement. There are many code duplication in many parts. This makes the code easy to read (which is a strength) but gives a code which is hard to evolve easily. A big amount of work was done (eg on trackers) but there is still a big work to do. All the css stuff is not enough standardised all over the code. Some work was done on that point and now titles, or buttons have more or less the same css structure. But, there is still many to do. Architecture Suggestions From Mozilla for high volume sites.
Opportunities TikiObject Use Tiki more & more as Framework HTML5	Threats The hype with new languages. Yet PHP is ahead http://www.ohloh.net/articles/php_eats_rails http://www.ohloh.net/tags/programming_language
Recommended action Developer closer ties with the people at PHP/Zend Framework/MySQL/Smarty/jQuery	Related links

Priority of Packaging Team and Release Team

Priority of Developers Team and Packaging Team

Priority of Community Building Team

Strengths Friendly Excellent collaborative spirit Many people have been active for a very long time Easy to join the project and to contribute: How to get commit access	Weaknesses While it is sizable, it's too small for a project this size. Too few people are taking on specific responsabilities
Opportunities As long as we organized in a scalable way, the more the merrier.	Threats Since the beginning of the project, there have been a handful of individuals which have caused lots of negative vibe. It could happen again. How Open Source Projects Survive Poisonous People (And You Can Too)
Recommended action On a defensive side, give officially the TAG the responsibility to warn, reprimand and then, expel these Poisonous People On the positive side, maybe a community team. This team would play a bit the role of human resources in a company. "recruit early, recruit often" Make it easy to integrate new people Make sure everyone is happy Gets proper training Establish goals in terms of people/activity and send warning signals if we go to low. Mentorship program Polls active contributors Exit survey with everyone who quits CRM approach to managing our developers. (Dogfooding user trackers) Make sure no one has a burn-out Make sure no one is under-utilized. Explain why Tiki is interesting for various types of users (developers, designers, etc). Use Cases Promote Producing Open Source Software: How to Run a Successful Free Software Project to our community as to promote best practices. Follow something like Tiki Hierarchy of involvement	Related links http://producingoss.com/en/producingoss.html#managing-volunteers http://eaves.ca/2007/02/05/wikis-and-open-source-collaborative-or-cooperative/ http://www.alwaysdoneitthatway.com/2007/10/21/six-principles-for-designing-an-architecture-of-participation/ http://www.principledinnovation.com/blog/2008/05/17/cognitive-surplus-and-new-incentives-for-engagement/

Priority of Developers Team and Continuous Integration Team

Strengths FLOSS Web Application with the most built-in features Very active development All-in-one model is very efficient Number of bugs is proportional to number of features	Weaknesses A big strain of dev team for releases. (too much code vs developers) Difficult to know who maintains what. Buggy features are bundled in release and not all tagged as experimental So many features make it difficult to focus. What if I don't want a toolset, but a specific tool?
Opportunities Major Features Missing In Tiki Trackers and Profiles will permit to increase features while keeping the code base manageable.	Threats A Software Engineering Odyssey -> NT 3.1 vs Windows 2000 story
Recommended action Watch out for Earthquakes Continue & enhance communication & collaboration amongst devs Include more developers Make it easier for people to know who works on what TikiTests Have a way to clearly identity all experimental features/settings (as of now, it's just first level. No easy way to see if subfeature of X is experimental	Related links

Priority of Dogfood Team

http://www.typo3-swot.com/
http://plone.org/events/2008-summit/customer-segments-swot-analysis
http://wiki.services.openoffice.org/wiki/Strategic_Marketing_Plan#SWOT
http://bugs.sakaiproject.org/confluence/display/CONF09/Sakai+SWOT+Analysis

• http://en.wikipedia.org/wiki/Open_source_software_assessment_methodologies
• How to Evaluate Open Source Software / Free Software (OSS/FS) Programs by David A. Wheeler
• http://producingoss.com/
• Community Projects
• Teams
• Ease Importance Priority

  
  

This SWOT should stay high-level and most of the specifics should be moved to the relevant Teams or project page.

Should events be its own section?
Should we have an "Enterprise-readiness" section?
Make a new section with reliability & stability (regressions, testing, eyeballs, bug density)
Should "standards" should go with "Extensibility / Expandability / Mashups / Integration with 3rd party apps & code reuse"
Should we split the "Installation" and add a new section "the first 30 minutes"?