History: TikiFestPostPostMuskoka
Preview of version: 32
Table of contents
What
- Planning TikiFest by Citadel Rock & AvanTech.net
Why
- As a follow-up to TikiFestMuskoka and TikiFestPostMuskoka
- Plan major devs for both companies
- What goes in Tiki12 LTS?
- What goes in Tiki13
When
- August 16-17-18, 2013
Where
- AvanTech.net offices in Montréal
Who
- Nelson
- Pascal
- Marc
- Louis-Philippe (two days)
Follow-ups / Decisions
- 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 more tricky projects are progressing
- CR will fund unprecedented
- Search Dilemma is one of the biggest potential threats (and opportunities)
Agenda
- Review all planned developments
- Review all teams, and see which ones require assistance
Specific discussions
- Working on *.tiki.org instead of Google Docs or CR internal wiki
- Dogfood PluginTowTruck
- show.tiki.org
- domain name
-
more versions availablesolved
- Video Team organization and tv.tiki.org goals
- Wishlist reports
- Watching on submit
- Security Conference call with Pete J.
- Releases
- Scanning opportunities
- Security Dashboard
- Search Dilemma
- Console, backups and Tiki DB Scrubber
- Bootstrap & Mobile
- Bank account & deposits
- Re-imburse expenses
- Official filing
- Legal Team: follow-up with what the students made
- Steve's suggestions
- Quality Team and code.tiki.org
- 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.
- Review progress on WishList
- Discuss workflow
- Create interesting dashboards to help WishList and Dev Teams
- Prepare map-cartograf-demo
- LP / Nelson
- 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 upstreamThe 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
Updated Teams
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
Nelson Ko
- 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 (Will vote and help if / when Quality Team makes a comeback, but won't lead the comeback)
- Testing
- 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
Pascal St-Jean
- Wishlist (show.tiki.org)
- The wishlist should now explicitly be used for tracking all wishes, not just feature-related. So community projects, etc.
- Documentation
- Consulting
- Profiles
- Legal (Let's ask Steve to help)
- Partnership
- Video
- Analytics
- Fundraising