Dogfood Team

The Dogfood Team ensures that all *.tiki.org sites are configured and working well, according to the software engineering principle of "Eating your own dog food". Team leaders: luciash d' being 🧙 and Roberto Kirschbaum

Release responsibilities

Determine an upgrade calendar for all relevant domains, from less risky to most risky. Order is Branding, Themes, Documentation, Community (tiki.org), Development, Profiles. It's the ultimate DogFood and the goal is that all major sites are upgraded before it's released.
In collaboration with the Infrastructure Team, proceed to these upgrades and ensure everything is still working fine.
After the upgrade, implement new features on *.tiki.org to help test and make the community more open efficient and welcoming
- In the weeks and months before an upgrade, this can be tested daily thanks to the Pre-Dogfood Server
- Update Dogfood with any new features used. This serves as a case study.
Review Tiki Welcome, as all new registrants are sent to it after validating their email link.

We want a bigger button somewhere
UI issue: Provoke error "Password must be different from the user login." and you loose capcha , some fields like Country, and you get "You do not have permission to insert an item"
Tiki Welcome merge with Custom registration message (templates/mail/user_validation_mail.tpl)

Cleanup and harmonization of the *.tiki.org footer
Harmonize theme usage and top navigation
Re-model the registration process to be more Social Networking
Along with i18n Team, fix the i18n perspective on tiki.org
Stickiness Project
- After registration: Ideally, another message a week or two later. Thanks for registering... all good?
tiki.org Teams and Social Networking Dogfood
Convert more (all?) sites to Federated Search

Implement Serious Dogfooding of a user tracker to gather information about our community and update the nice Community Worldmap
- Retire the previous attempt (migrate data?)
It would be nice to be able to build the community and determine why new users register at t.o. Maybe we can include a user tracker (post registration, perhaps as part of the Welcome page to collect/analyze:
- Why are they registering for a Tiki account?
  - Prompted after installation?
  - Want to have access to forums?
  - Want to become a committer?
  - etc.
- What do they expect from the community?
  - Support?
  - Involvement in active community?
  - The chance to "shine"?
- What can they give to the community?
  - Coding -> Development
  There are lots of ways to contribute other than coding:
  - Layout/design -> Themes
  - Marketing/PR
  - Legal
  - Doc/support

Help with Accounts along with Community Building Team
Determine where content should go.
Maintain all *.tiki.org sites to an optimal configuration -> Preferences of *.tiki.org
- Including Pre-Dogfood Servers
Oversee any shared content (ex.: footer)
Determine which site should be at each version (we want active sites running in all supported versions)
Maintain Domains list in collaboration with the Infrastructure Team
Track issues categorized at Dogfood on dev.tiki.org
tv.tiki.org in conjunction with Video Authoring Team
demo.tiki.org

irc.tiki.org: Freenode #tikiwiki (update topic, make sure web interface is working, interact with freenode, make use of IRC bots, make sure irc.tiki.org has logs and is functional, etc.)
- http://www.donarmstrong.com/posts/switching_to_kgb/
live.tiki.org and interactions with BigBlueButton.org community
- Make sure site is up and that useless recordings are deleted from the list (just install a Tiki10 to connect to BBB to do this)
Management of Mailing Lists (ex.: bounces, errors) and adding/maintaining forum to mailing lists integration
Clipperz accounts
Mail server
- To manage accounts, contact Marc Laporte in private
- For technical issues about the software: Frank Guthausen