Membership Request: Benni Mack (TYPO3)

[Benni Mack]

Hello group,

as our PHP-based Content Management System TYPO3 CMS is getting closer to the PSR standards in the past years and we really like the work, I would like to join and participate in the further standardization ideas.

Our project: TYPO3

Our website: www.typo3.org

My name: Benni Mack

My email: be...@typo3.org

Twitter account: @bennimack

I'm the Leader of the Development Team and currently coordinating the incorporation of PSR-7 in our next version - I'm happy to contribute our ideas to the further progress of the PSR group.

Karsten from our sister project TYPO3 Flow with a different code basis, is already with the PSR-FIG.

Thanks for consideration!

All the best,

Benni Mack

---

TYPO3... Inspiring People To Share!

[Larry Garfield]

On 5/19/15 4:50 AM, Benni Mack wrote:
> Hello group,
>
> as our PHP-based Content Management System TYPO3 CMS is getting closer
> to the PSR standards in the past years and we really like the work, I
> would like to join and participate in the further standardization ideas.
>
> Our project: TYPO3
> Our website: www.typo3.org
> My name: Benni Mack
> My email: be...@typo3.org
> Twitter account: @bennimack
>
> I'm the Leader of the Development Team and currently coordinating the
> incorporation of PSR-7 in our next version - I'm happy to contribute our
> ideas to the further progress of the PSR group.
>
> Karsten from our sister project TYPO3 Flow with a different code basis,
> is already with the PSR-FIG.

Can you clarify the Flow/CMS relationship? I'm not familiar with how
the two groups are run and how they relate, leadership-wise, so it's not
clear if they are sufficiently distinct to be represented separately.

--Larry Garfield

[Benni Mack]

Hey Larry,  

 

Can you clarify the Flow/CMS relationship?  I'm not familiar with how
the two groups are run and how they relate, leadership-wise, so it's not
clear if they are sufficiently distinct to be represented separately.

Sure. 

The TYPO3 project started in 1998, in 2006 a group from the TYPO3 community started a separate project "Flow" (the PHP Framework) and "Neos" (The CMS on top of that) originally to be planned as the successor to TYPO3. However, during the last few years it become more and more obvious that it's actually a complete separate product and not a successor, thus resulting in having two products, two separate teams, two strategies with the connection that we share a few concepts in Domain Driven Design. We meet sporadically, but not on a technical level but more in a relaxed exchange on certain events.

Leadership-wise we have two products, Flow/Neos led by Robert Lemke and Karsten Dambelkans, and TYPO3 by Mathias Schreiber (as Product Owner) and myself.

In the course of this year, Flow/Neos will become a separate community which is not related to TYPO3 anymore due to naming and marketing reasons, thus being separate entities and OSS completely.

Does this explanation clear things up for you a bit?

All the best,

Benni.

[Matteo Beccati]

On 20/05/2015 13:47, Benni Mack wrote:
> In the course of this year, Flow/Neos will become a separate community
> which is not related to TYPO3 anymore due to naming and marketing
> reasons, thus being separate entities and OSS completely.
>
> Does this explanation clear things up for you a bit?

I think so. I personally have nothing against TYPO3's application. I
even picked it among the competitors for the company website I was
working for some ~12yrs ago.

However, my suggestion would be to wait until later this year and
re-submit the application once such split is complete.

That will avoid the confusion caused by the TYPO3 Association
technically having two representatives for a certain time.


Cheers
--
Matteo Beccati

Development & Consulting - http://www.beccati.com/

[Karsten Dambekalns]

Hi there.

> On 20.05.2015, at 15:28, Matteo Beccati <mat...@beccati.com> wrote:
>
> However, my suggestion would be to wait until later this year and re-submit the application once such split is complete.
>
> That will avoid the confusion caused by the TYPO3 Association technically having two representatives for a certain time.

Well, the split has been announced (see typo3.org/news/article/typo3-project-focuses-on-typo3-cms-neos-to-start-its-own-community/) and the things being discussed are “only” about infrastructure issues.

The software projects as such (teams, technical leadership, …) are separated already, the whole process is more or less only acknowledging the facts.

So, for what it’s worth: I am fine with TYPO3 becoming a member here.

The hardest question for right now is whom I will be representing (i.e. what name will we give ourselves). :)

Regards,
Karsten

[Cal Evans]

FWIW, I agree that since the split has been announced, we can go ahead and discuss/vote on TYPO3.

Cheers!

=C=

--
You received this message because you are subscribed to the Google Groups "PHP Framework Interoperability Group" group.
To unsubscribe from this group and stop receiving emails from it, send an email to php-fig+u...@googlegroups.com.
To post to this group, send email to php...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/php-fig/DCD58400-D37B-420D-A9CA-2D412982AFF9%40dambekalns.de.

For more options, visit https://groups.google.com/d/optout.

--

Culture of Respect

How to find, hire, and retain developers

[Lukas Smith]

+1

regards,

Lukas

To view this discussion on the web visit https://groups.google.com/d/msgid/php-fig/CAPf%3DPy%2BaGihNdXvZS0mhkRcNFEFBqXbVf4jgxn8G7bVx3-WXxQ%40mail.gmail.com.

[Matteo Beccati]

Hi Karsten,

My suggestion was based on past experience with the first application
from Kayla for the League and the goal was to avoid useless drama. I am
extremely happy to see that there was none.


Cheers
--