[TYPO3-english] Last TYPO3 version without fluid/extbase

[Tonix (Antonio Nati)]

Hello Philippe,

sorry for answering you so late, but I was involved in a complex 
migration, and only now I'm back to normal work.


Il 16/11/2012 19:28, Philipp Gampe ha scritto:
> Hi Tonix,
>
> Tonix (Antonio Nati) wrote:
>
>> So, you are publicly declaring that there is no central coordination and
>> planning on future releases of TYPO3, and the direction of a release may
>> be a surprise for core members themselves.
> I am not a member of the core team. But I always had a slight idea on what
> was going to happen by reading the news articles published on T3o and Buzz.
>
> I also spoke to some core team members and took part in the public
> discussion.
>
> IMHO, this have been main focuses of 6.0:
> * integration of FAL with much buzz around it, including the decision to
> name the release 6.0 instead of 4.8
> * refactoring the bootstrap (mostly done by Christian), not much buzz, but
> mostly technical
> * renaming all classes and files, some buzz on the tech channels and in the
> meeting protocols, but once again, this is mostly technical
> * integration of new EM, planned and announce publicly at least via the tech
> channels
> * rewrite of the BE user module, no buzz before, because a non core dev just
> did it
>
> Other than that, lots of bugfixing has taken place and quite a lot of people
> introduced new features.
>
> Nobody can plan ahead without knowing who will do what. People can just
> announce that they are working on something, like Susanne for the extension
> manager, Christian on the bootstrap and the FAL team on FAL.
>
> There is a fixed release date together with a schedule for feature freeze.
>
> What is in (merged) before feature freeze will build the next version. That
> is it.
>
> There is no definite plan, but only announcements and ideas. It then all
> depends on people actively doing some work.

My first approach with TYPO3 was when I had to decide if to invest on my 
CMS or look around for something comparable (or better).

In my CMS I put all efforts on semplifying life to graphics and have an 
excellent integration with them, and easiness of coding.

When I discovered TYPO3 I was impressed because of the architecture and 
because the goal was the same: semplify life to graphics, and have a 
great integration among different skills. More, I've found a strong 
architecture for development.

Luckily, the learning curve has been very short, also because I'm very 
used to analisys, so after a while I could understand the basics, and 
starting to design advanced designs, writing my own extensions.

I appreciated a lot Kasper Skaarhoj work, and I can feel he had (has) 
strong development and analisys skills.

It was less incouraging putting first questions in this mailing list, 
because it was very hard to have good answers... sometimes the experts 
seemed to not understand some TYPO3 behaviours which are essential for 
making a good analisys. I could understand that after years, so I 
started asking myself if people did really understand the real potential 
of typo3 as framework (forget it as an end user tool).

Now, I've the feeling that the raising curve of TYPO3 has finished. What 
has been developed based on a great analisys, is now developed following 
day by day technical needs, without a clear architectural vision.

It was a professional tool, written by professionals for professionals, 
now I do not have the same feeling.


> This is how TYPO3 CMS is done. Whoever feels responsible to do something
> does it. For bigger changes it is a wise idea to first collect some feedback
> before investing time into something that will not be accepted, but this
> should be clear to everyone.
>
> TYPO3 CMS is done by the hands-on strategy. Without payed coders, this will
> not change.

This is perhaps the main problem. Expert or not payed?

Payed is an attribute, not a quality. Quality is expert, solid, 
realiable, which can take to a well paid coder.

A coder could be not payed, but very skilled, so, generally speaking a 
pool of expert coders could make a better job than a pool of payed coders.

Initial works of Kasper were paid by companies, so there was an 
excellent coder, well paid from companies, which decided to share this 
payed work with other companies (for a lot of reasons, inclusing 
easiness of mantainance).

This should be the way, again, but I do not see any paying company 
trusting this project. I do not see how a company could put any money in 
a project like the actual one.

A lot of beer, meetings, festivals for TYPO3, but nothing really 
interesting. It could be evaluated if it would be better to give all the 
software to a normal company, instead of a foundation, having the double 
release: community version - payed version.


Regards (and happy season greetings to all),

Tonino


> Cheers


-- 
------------------------------------------------------------
         Inter at zioni            Interazioni di Antonio Nati
    http://www.interazioni.it      tonix at interazioni.it
------------------------------------------------------------