[TYPO3-v4] Minutes from the 3rd meeting of the 4.6 Release Team
Oliver Hader
oliver.hader at typo3.org
Mon Apr 4 21:23:52 CEST 2011
Hi dear TYPO3 community,
here are the notes of the 3rd meeting of the 4.6 Release Team.
The minutes are also available in the wiki of TYPO3 4.6:
http://forge.typo3.org/projects/typo3v46-projects/wiki/2011-03-28_-_Minutes_from_the_3rd_meeting
----------------------------------------------------------------------
Minutes from the 3rd meeting of the 4.6 Release Team
*March 28st, 2011*
The 4.6 release team meets weekly for a Skype discussion round on the
current activities. If you find this report interesting or have some
comment or question about a particular topic, don't hesitate to
follow-up on the thread in the v4 mailing list.
On Monday, March 28th 2011 we hold our 3rd meeting with the following
participants:
* Xavier Perseguers (4.6 Release Manager)
* Oliver Hader (Core Team Leader)
* Benjamin Mack (4.4 Release Manager)
* Steffen Kamper (4.5 Technical Leader)
* Ben van't Ende (Community Manager)
Projects
========
Reorganization of the backend
-----------------------------
Xavier and Steffen had a Skype meeting on reorganizing particular parts
in backend module. Here is the list of what has been discussed:
* Log module is some kind of report => integrate it in Reports
* Indexing module contains three submodules
** General statistics => integrate in Reports
** List: TYPO3 pages => does not make much sense, information is
already available (and better organized) with Web > Info > Indexed
Search Statistics
** List: External documents => either drop it (available from Web >
Info) or integrate in Reports
* Scheduler is missing a way for tasks to provide reports about
previous runs => integrate that in Reports
* DB Check contains many submodules:
** Records Statistics => integrate in Reports
** Database Relations => integrate in Reports with links to perform the
suggested actions (delete file with no reference, edit record
references, ...)
** Full Search > Raw search in all fields => should be part of some
Search module just as the top-right search box
** Full Search > Advanced query should be moved to sysaction extension
(and this extension should be put somewhere on Forge I guess)
** Find fileadmin => Part of some Search module as well
** Manage Reference Index => the "check" part should be integrated in
Reports and a link should let user perform the update reference
action. Moreover the text currently corresponds to the output of the
lowlevel_refindex with "-c" parameter, some kind of "--dry-run"
parameter which shows the action as if they would have been
performed. When moved to Reports, the texts should be changed "34
references MISSING" instead of "Added 34 references" which was not
the case as it was just simulated
** Manage Reference Index => Update part, will be available from
Reports as a link but should be encapsulated or rewritten as a
scheduler task too
* Configuration is OK like that, but could be made better with ExtJS
(showing info left and having contextual edit area/textbox on the
right to update info right away)
* User Admin / Compare User Settings:
** Is not really possible to compare two given user settings when those
users are far away in the list from each other
** Having multiple additional information (Filemounts / Webmounts /
...) could be done with some ExtJS grid instead, even with possible
reordering of the columns (I may dream a bit)
** Having an ExtJS grid would give us some "paginator" for free...
** When only using it for managing users or switching to someone, the
recent extension from Steffen (beuserswitch [1]) looks much better
and seems much more usable from my POV
* User Admin / List Users Online:
** Host info is useful for server admins not for "normal" admins
** Additional info for the user could be rendered as a growing area
inside the list itself (just as extension info in new EM)
** Why would you either deactivate or delete some currently logged in
user? When you are being hacked? Then it should not be so prominent
** What could be useful is some chat tool there, clicking on someone
and engaging the conversation. This could and should simply be some
API that may be implemented by third party extension to prevent
cluttering the Core with nonsense stuff
* The Help module should be moved as some "?" icon in the top bar,
which leads to having some API to add icons and fields there, the
same applies for the module top navigation bar
** About TYPO3 and About Modules would be menu items there
** TSref, ... would be added there too
[1] http://typo3.org/extensions/repository/view/beuserswitch/current/
Code Cleanup
------------
Xavier started to change the visibility of class member variables from
var to public, private and protected [2].
Due to the fact that removing deprecated methods from the Core [3] and
changing the visibility and accessibility of variables are considered as
breaking changes, these tasks must be finished until the first alpha
release. This offers the possibility to extension developers to adjust
the accordant extensions and replace calls to the removed functions of
the Core.
[2] http://forge.typo3.org/issues/25334
[3] http://forge.typo3.org/issues/24954
Backend Roles
-------------
Xavier analyzed the roles2 extension [4] which provides a good start for
extending the current permission concept in the backend by proper roles.
However Xavier still wants to go a step further and extend the situation
by having different roles for different parts of the pagetree
(mountpoints). By integrating the roles2 extension now into the Core we
don't have the possibility to change and extend the concept later on.
Thus, the roles project must be kickstarted now and even if it is not
ready to be shipped with TYPO3 4.6, we aim to have a solution for TYPO3 4.7.
[4] http://forge.typo3.org/projects/show/extension-roles2
Dashboard
---------
Steffen evaluated the current implementation of the dashboard extension.
However, since most functionality is currently based on Prototype and
script.aculo.us it's not on the track of a dashboard that easily can be
extended by custom widgets and behaviors. The goal is to have this
project being based on ExtJS - Steffen already started to create a draft
that is based on the portal example [5]. Once there are proper results
to continue with, the will be an accordant project on forge.typo3.org.
Benni mentioned that the available widgets for a user shall be narrowed
down to the required ones.
[5] http://dev.sencha.com/deploy/dev/examples/portal/portal.html
Install Tool Improvements
-------------------------
Benni told that he wants to organize a small Skype meeting with the
project members to discuss the next steps and define priorities.
XLIFF vs. locallang.xml
-----------------------
In general "XLIFF" is the abbreviation of "XML Localization Interchange
File Format". Since the current solution for translating language labels
in TYPO3 is an individual solution which cannot be extended easily,
there is one initiative to switch from the known locallang.xml structure
to the XLIFF standard. XLIFF is already used by other Open Source
Software Projects and will also be used by TYPO3 Phoenix/5.0 [6]
[6] http://wiki.typo3.org/Support_for_XLIFF
General issues
==============
TYPO3 4.5 Performance
---------------------
In the minutes of the last meeting we already talked about general
performance rants concerning TYPO3 4.5. The problems are basically in
the backend:
* new ExtJS pagetree fires multiple AJAX requests to load the tree -
this could take some seconds on sites with many pages
* the state of the pagetree (pages being expanded/collapsed) takes a
lot of storage in the BE_USER->uc and might run out of space
* in general the number of AJAX calls increased between TYPO3 4.4 and
4.5
* the new CSRF security token could be optimized
Steffen and Olly are going to have a Skype meeting on this topic to
determine other flaws and think about possible solutions. In general we
agreed on taking these problems seriously, to revive the performance
mailing list and that we'd like to have a code sprint that is dedicated
only to performance.
Last bugday
-----------
Steffen pointed out that the last bugday was a bit quiet, however there
have been some discussions and questions concerning Git and Gerrit in
general [7]. Steffen raised the question of having official support
hours in the IRC channel to get immediate feedback or support somebody
having question of the infrastructure and tools being used.
[7] http://news.typo3.org/news/article/march-25-2011-bug-day-report/
Dates
=====
* TYPO3 4.6 alpha1 on May 10th 2011
* Feature Freeze and TYPO3 4.6 beta1 on August 2nd 2011
no new features and no exceptions after the feature freeze date
* Final Release of TYPO3 4.6.0 on October 25th 2011
Next steps
==========
If you feel interested in a particular project or task, please reply on
the list or directly get in contact with Xavier Perseguers as Release
Manager of TYPO3 4.6.
----------------------------------------------------------------------
Cheers,
Olly
--
Oliver Hader
TYPO3 v4 Core Team Leader
TYPO3 .... inspiring people to share!
Get involved: http://typo3.org
More information about the TYPO3-project-v4
mailing list