History

Extbase Team Meeting 2011-05-26¶

Participants:¶

we collected them from different sources (mailing lists, Twitter, blogs, personal feedback, ...)
we'll address them in a separate posting, and announce our response on the mailing list
if you have any questions, we can discuss detailed critic points at the next meeting
we think most critics can be summed up in the following way:
- Missing communication, missing documentation, missing manpower

Many misunderstandings due to lack of communication & documentation
We need a central collection of documentation.
Question: what documentation formats do you prefer?
➜ Forge wiki
➜ improve structure / style
➜ collect docs there
➜ please join the book translation!
You (the community) have more real life experience. So we really need and valuate your input

TODOS:

Improve visibility of Forge
- add a microsite on typo3.org (linking to the wiki) #27062
Communicate more with the (4.6) release team
We need to improve roadmap -> see below
Discuss implementation of a doctrine persistence layer
collect and document strong & weak points of Extbase #27063
collect performance data, to reproduce the performance tests #27064

we have quite some good tools (Gerrit, Forge), but we don't really use them correctly
- Interconnect these utilities more (like Linking the git in forge.typo3.org - Redmine can do that) ?
What's missing? What keeps you from contributing?
- [ben] In general documentation on typo3.org is not there or written well. When we improve that it will attract more people. This is also a general problem Oliver Hader and me are working on now. That will probably also improve with launch of the new typo3.org.
  - better categorization (filter domcuments in categories, eg Frontend Plugin, Backend, etc.)
  - search functionality for documentation (only)
- A central collection of all the tools used would be good.
We need a CLA, as we sometimes forward-port things to FLOW3
- currently a big hurdle (takes very long), we will work on that.
- It's on Karstens todo list
ViewHelper-Incubator: Is it a good idea? It is not used, why is that?
- [zalan] I think it's not known enough (link it at typo3.org, document it in wiki).
- [christian] definately a good idea, but no VH have been ported to the core yet(?) and there is no process to decide which VHs go in there.
- maybe an extension with lesser used (but helpful) ViewHelpers could be set up

TODOS:

Improve CLA process #27065
Bugtracker:
- Clean up / compile roadmap #27066
- Add voting functionality #27067
- Add "steps to reproduce" field #27068
Document ViewHelper Incubator #27069

You can basically exchange everything (f.e. persistence backend), using Dependency Injection
- however, nobody did... (or only very few people)

support deeper hierarchies ( http://forge.typo3.org/issues/26861 )
support testing of repositories and controllers in the Base Test class for TDD (?)
clean up extbase code (see lines 00418 and 00399 for example in http://www.t3node.com/typo3api/trunk/de/d50/ActionController_8php_source.html#l00417)
We will merge pending issues and backport them to the 4.5 branch

TODOS:

Address update scenarios [will be discussed at T3DD11] #27070
- e.g. compatibility flag
- discuss if it should be per-extension or global [TODO: Discuss on next meeting]
backport new Property Mapper #27059
Backport bugfixes to old branches #27071
improve Persistence layer #27072
- Dirty Monitoring
- better relation handling in the Persistence Backend
- fixed handling of Value Objects
- better support for deeply nested domain models
- use transactions
- DBAL support
- readOnly mode (switchable "on the fly"?)