Support/TikiUpstreamTriage: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
Line 37: Line 37:
* Live chat integration
* Live chat integration
* Replication support
* Replication support
* Memcache support
* [http://dev.tikiwiki.org/wish2707 Memcache support]
* Full text search using Sphinx (which should become an abstraction layer for Search)
* Full text search using Sphinx (which should become an abstraction layer for Search)
* Track l10 changes (ie noticing when translations are out of date)
* Track l10 changes (ie noticing when translations are out of date)
Line 43: Line 43:
* Improvements to email watches (inc locale specific watches)
* Improvements to email watches (inc locale specific watches)
* CSAT (Customer Satisfaction)
* CSAT (Customer Satisfaction)
* CSS and JavaScript minification
* [http://dev.tikiwiki.org/wish2706 CSS and JavaScript minification]
* Screencast support
* Screencast support
* Data warehouse and metrics dashboard
* Data warehouse and metrics dashboard

Revision as of 14:41, 29 August 2009

Who

  • Marc Laporte
  • David Tenser
  • You?

What

Goal:

Go trough all modifications and categorize them.

This will take some time as there is a huge list.


Categories will be described below

  • tiki_triage: A new bug that needs to be triaged by TikiWiki to determine the actual tiki status
  • tiki_fixed: Stuff that is already fixed in upstream TikiWiki (just need to check in the fix is OK for SUMO for performance, etc.)
  • sumo_triage: Should be looked at by SUMO, and determined if sumo_only or tiki_triage
  • tiki_string: Pure string changes -> Need to be added here: http://dev.tikiwiki.org/pending+text+corrections
  • tiki_template: UI changes in templates
  • tiki_feature: New/enhanced feature that should be upstreamed
  • tiki_bug: Bug that should also be fixed in upstream TikiWiki
  • sumo_only: Stuff that is related to the administration/maintenance of the SUMO website that can't really be upstreamed

When

Starting 2009-08-26

  • 1st run: go through the whole list, categorize (tag) each item. Refine tag list as needed.
  • 2nd run for further discussion/analysis of the more tricky ones. (merge challenges, etc.)
    • Link to relevant wishlist item on dev.tikiwiki.org or code


Features / enhancements that should go to Tiki

As we add things on this list, we'll only mark one "meta-bug" with tiki_feature. We won't necessarily identify each commit/patch, as the code will be taken in final stage and ported/adapted to Tiki trunk for inclusion/discussion/abstraction of code in 4.x. The individual bugs for that main feature will be marked as sumo_only.

  • Live chat integration
  • Replication support
  • Memcache support
  • Full text search using Sphinx (which should become an abstraction layer for Search)
  • Track l10 changes (ie noticing when translations are out of date)
  • l10n dashboard
  • Improvements to email watches (inc locale specific watches)
  • CSAT (Customer Satisfaction)
  • CSS and JavaScript minification
  • Screencast support
  • Data warehouse and metrics dashboard
  • Showfor plugin
  • Staging & Approval: various enhancements in general and to work with translations
  • Forum enhancements
    • Adding fields for Firefox version, bundled plugins, etc.
    • Facilitate anonymous posting
    • Screenshot upload
    • Even newer enhancements, to permit search before post.
  • Many small performance, l10n, and UX improvements; bugfixes; etc.
  • Also see http://dev.tikiwiki.org/Architecture+Suggestions+From+Mozilla

Related

Support/InterestingTikiLinks


Phone Meeting 2009-09-02

  • Progress on triage list above
  • Adding SUMO devs to Tiki security list and get access to the Security Dashboard
  • Adding Tikidevs to Bugzilla
  • Update on http://dev.tikiwiki.org/Architecture+Suggestions+From+Mozilla
  • From http://dev.tikiwiki.org/SUMO+Upstream+Process, "SUMO will continue on own svn but will create some way for tiki devs to see what happens will be figured out. (e.g. a hook to send commits to Tiki commit mailing list, or a hook to automatically send commits into a tikiwiki SVN branch)". Please have it sent to: tikiwiki-cvs@lists.sourceforge.net (and let marclaporte@tikiwiki.org know what the from email is so an exception is added to the spam filter.
  • Zend Framework use (cache, etc.)
  • Introduce Support/InterestingTikiLinks