[TYPO3-team-core-v5] Flow Performance Optimization Code Sprint

[Robert Lemke]

Hi folks,

as mentioned in the tweet, you can participate but also consider sponsoring the sprint. I expect that we'll find more spots which can be optimized that can be completely solved during the sprint. So, if you generally want to help or have a specific bottleneck in mind, you might want to offer sponsorship for a specific task.

Cheers,
Robert


On 20.12.2012, at 16:19, Christopher Hlubek <hlubek at networkteam.com> wrote:

> I set up a doodle poll for a Flow performance optimization code sprint (http://doodle.com/bnqsmzgxf9gg3qgc) and invited some people already.
> 
> I think performance in general is one of the most pressing issues in the framework (besides more documentation and guides, but that's not really stopping someone from using the framework who is willing to dig a little deeper) which cannot be solved by most users (or even core team members) alone.
> 
> The idea is to prepare use cases that need improvement and do some profiling to identify "low hanging fruits" in advance. We should also collect user feedback on performance issues and ask the community for giving us examples or setups that should perform better. We should have at least one Hangout before the sprint to collect all the information and a common setup for every participant.
> 
> As a result of the sprint we should have changes in Gerrit which can be integrated and refined later in addition to standardized measurements that will show the effect of the code sprint and should be published as an official news entry.
> 
> I would also like to see a continuous improvement by adopting these measurements in an automated build after each change to the core packages in the future.

-- 
Robert Lemke
Lead Developer TYPO3 Neos and TYPO3 Flow
Co-Founder TYPO3 Association

Blog: robertlemke.com/blog
Get involved: typo3.org – flow.typo3.org – neos.typo3.org