[TYPO3-core] Updated Roadmap for Logging in TYPO3 CMS 6.2

[Steffen Müller]

Hi.

The goals for logging in 6.2 have been discussed in the core team/active
contributors meetup in Nürnberg. Ernesto as release manager and me as
logging task force leader sat upon the next steps and wrote down a rough
roadmap. Let me give you an impression about our goals for the TYPO3 CMS
Core.
(This document can also be found on forge [1])

We have introduced a nice Logging API in TYPO3 6.0, which is scalable,
simple and very well thought. It is also very well documented
Now for 6.2 LTS it's time to finish the missing gaps by making
productive use of this API and getting rid of older constructs. This
sums up in the following tasks:

Creating an overall concept
---------------------------
  * Collect information on the different logging implementations
available throughout the core right now.
  * Make a concept about what we want to achieve with the logging in the
future of CMS (for example the logging when changes happen on content
elements)

Implementation
--------------
  * Create a shippable basis configuration for the new logging API for
the Core
  * Extend the LogRecord model to cope with the input and the
requirements in the output (i.e. the backend log module)
  * Replace all log implementations from the old log methods by the new
logging API
  * Deprecate all old log methods in the core

Optional steps
--------------
* Become compatibile with PSR-3. We're not far from that and there's an
umbrella issue for all needed tasks to be done [1]
* Create modern logging Writers:
  * Build an aggregate of DatabaseWriter and LogProcessors to support
logging to the existing BE-module as an intermediate solution.
  * Alternatively write a dedicated TYPO3-BackendLogWriter.
  * GraylogWriter for enterprise level logging (already pending in
gerrit [3])
* Document best practices logging setting for
  * Development instances
  * Production instances
  * Stealth instances
* Create a new BE log module using similar technologies as the new
Extension Manager (Extbase, jQuery, simple but powerful and scalable
interface using DataTables)

Next action steps
-----------------
* Cleaning up and updating the issue tracker to highlight the tasks for 6.2.
* Evaluating the actual logging in core for the overall concept

Wanna join the team?
--------------------
We would be happy to find interested people to push the logging topic
forward for 6.2 LTS. The logging project so far has mainly been driven
by the community. Let's continue with this!

Don't hesitate to apply for team membership [4] and add some notes which
topic you're interested to help. Once the issues have been updated, you
are invited to add yourself as a participant for any task.

[1] http://forge.typo3.org/news/646
[2] http://forge.typo3.org/issues/48874
[3] https://review.typo3.org/#/c/21257/
[4] http://forge.typo3.org/projects/typo3v4-logging

-- 
cheers,
Steffen

TYPO3 Blog: http://www.t3node.com/
Twitter: @t3node - http://twitter.com/t3node