• What
• Why
• When
• Where
• Who
• Follow-ups / Decisions
• Agenda
• Specific discussions
• Updated Teams

• Planning TikiFest by Citadel Rock & AvanTech.net

• As a follow-up to TikiFestMuskoka and TikiFestPostMuskoka
• Plan major devs for both companies
  • What goes in Tiki12 LTS?
  • What goes in Tiki13

• August 16-17-18, 2013

• AvanTech.net offices in Montréal

• Nelson
• Pascal
• Marc
• Louis-Philippe (two days)

• Bigger tasks like automated backups of all *.tiki.org sites should be chopped into smaller tasks and tracked individually
• A Conference call will be held every 2 weeks to follow-up on progress. This conference call will insure that bigger or more tricky projects are progressing
• Citadel Rock will fund unprecedented R & D in Tiki13 (It will blow your mind!)
• Search Dilemma is one of the biggest potential threats (and opportunities)
• We all think Tiki should be a great solution for a small entry level project on shared hosting, all the way to a very large project. AvanTech.net will focus on making Tiki awesome for the small projects and move up. Citadel Rock will focus on the large projects, and move down. Thus, we will meet in the middle.
  • Example of needs of large projects: ElasticSearch
  • Example of needs of small projects: 1-click installers

• Review all planned developments
• Review all teams, and see which ones require assistance

• Working on *.tiki.org instead of Google Docs or CR internal wiki
  • Dogfood PluginTowTruck
• show.tiki.org
  • domain name
  • more versions available solved
• Video Team organization and tv.tiki.org goals
• Security Conference call with Pete J.
  • Releases
  • Scanning opportunities
  • Security Dashboard
• Search Dilemma
  • Unified Search with MySQL Full Text Search
• Console, backups and Tiki DB Scrubber
  • http://dev.tiki.org/item4665
  • http://dev.tiki.org/item4677
• Bootstrap & Mobile
• Bank account & deposits
  • Re-imburse expenses
• Official filing
• Dogfooding for CR
• WYSIWYG
• WikiMatrix
  • LP / Nelson
    • Review new features and issues
    • Review performance benchmarks with ElasticSearch
    • Perform some profiling for memory issues and performance
  • Marc / Pascal
    • Prepare map-cartograf-demo
      • TimeMap, clustering, etc.
• Logs of attacks and errors (and eventually mother.tiki.org)
  • Testing sites (how do we get warnings of regressions)
  • PHPIDS
  • Need logs for things like http://tiki.org/img/flags/USA.gif, seen at http://tiki.org/tiki-view_forum_thread.php?forumId=6&threadId=48626&comzone=show#threadId48626
• Composer: report issues upstream The immediate issues were fixed
• Monitoring
  • Basic checks on all next instances (Is DB up to date?, Search rebuild: there is a pref with last date of success, issues with APC, etc.)
  • Find a way to make use of the 50 checks from tiki-check.php
• Developer documentation

The list below are the teams being supported, in rough order of expected priority/workload in coming months. Compared to the previous TikiFest, Nelson and Pascal swapped the Finance Team and Wishlist team. We think this list of teams should be pretty stable from now on.

Marc Laporte

• User Experience (UX) & Themes (preparing for Bootstrap revamp)
• Community
• Infrastructure
• i18n
• Packaging
• Performance
• Communications
• Branding

• Release (With Bernard)
  • Tiki12: Follow closely and improve the How to release procedures
  • Tiki13 will be a huge release, likely bigger than 7 (Pascal will post that on a page somewhere later)
• Quality (Nelson will vote and help when Quality Team makes a comeback, but won't lead the comeback)
• Testing
  • Access to fresh automated backups for devs is a top priority and redacted versions
  • Monitoring / Nagios tests on all pre-dogfood servers to log / track / quality of trunk
• Developer
  • New developer-focused webinars will be started every 2 months and this will build our developer documentation
• Security
• Finance
  • Move the last remaining payments from Marc's credit cards / PayPal account to the Community account

• Wishlist (show.tiki.org)
  • The wishlist should now explicitly be used for tracking all wishes, not just feature-related. So community projects, etc.
  • Interesting dashboards to help WishList and Dev Teams will be created
  • Feature request: Watching on submit
• Documentation
• Consulting
• Profiles
• Legal Team: follow-up with what the students made
  • Steve's suggestions and let's ask Steve to help
• Partnership
• Video
• Analytics
• Fundraising