[TYPO3-english] (TYPO3) Surf as official product?

[Steffen Gebert]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi Karsten,

thanks for your answer.

I agree that we should not complicate matters. I think we're not that
far as apache, so we shouldn't take two steps at once.

I hope you don't think that I'm against you ;) And I don't want to say
"go away".
But the "by members of the core team" is interesting - what if other
people from our community want to put sth. under an official umbrella?
But well, that's again one step ahead I think (or is there any candidate?).

I was just interested in the process behind making it TYPO3 Surf.

Kind regards
Steffen

- -- 
Steffen Gebert
TYPO3 CMS Core Team Member
TYPO3 Server Administration Team Member

TYPO3 .... inspiring people to share!
Get involved: http://typo3.org

I work for TYPO3 solely in my spare time. If you think that
my work helps you running your business, you are invited to
send me a donation via PayPal to this email address. Thanks

On 11/6/12 10:13 AM, Karsten Dambekalns wrote:
> Hi.
> 
> On 04.11.12 18:59, Steffen Gebert wrote:
>> Why is Surf not a product of people from our community, like all the
>> extensions are? What are the steps for a product to be called "TYPO3
>> <whatever>"? We come from a CMS community and have a PHP framework now
>> (which is nice, of course :-)), and we get a deployment tool, and.. ?
> 
> First of all, as a motivational background bit, Neos is not "just a
> CMS", but comes with some needed bits of infrastructure / ecosystem
> everyone needs eventually. That's why we think Surf makes sense - we
> needed a tool to deploy Flow applications and Neos sites.
> 
> Second: it is a product of the community, why would it not be? We - you,
> me, they - are the community, no? I sense a feeling of "why is my stuff
> not as important", "why is that better"… don't go that way! ;)
> 
> 
> 
> On naming: only "official" stuff may use the TYPO3 namespace and only
> things using the TYPO3 namespace may use the TYPO3 brand as part of
> their name.
> 
> On being official: Like in the old days, if something is maintained by
> the core team, thus not depending on a sole developer for survival, is
> important enough, of adequate quality, … it is "official".
> 
> On being a product: Whether something is a product or not, depends on
> it's "standalone usefulness" obviously. And on whether it makes sense to
> market it as a product.
> 
> 
> 
> To sum it up using Surf: it is maintained by the core team (Christopher,
> Robert, Tobias, Sebastian, …), it is important and of adequate quality.
> Thus it uses the TYPO3 namespace and may be called TYPO3 Surf. We
> *treat* it as a product, because it can be used for Neos, Flow and CMS
> deployments - as well as things not even related to TYPO3. But, no,
> there is no website for it yet, we do not *market* it as a product so far.
> 
> Compared to Fluid: Definitely official, yes. Uses the name TYPO3 Fluid.
> Not a product yet, because it cannot yet be easily used outside the
> TYPO3 universe.
> 
> 
> Future? I see five products currently: TYPO3, Neos, Flow, Fluid and
> Surf. They are not yet all "products" - but I do not see any more on the
> horizon right now. YMMV.
> 
> 
> That's how I would sum it up - it would be good to refine those points
> and put them up somewhere for everyone to read. But, please, let's not
> overregulate it. Common sense will get us a long way, before we'll
> actually have the first problem with any of this.
> 
> Regards,
> Karsten
> 
> Disclaimer: When I say "we" I mean the people I work with in the project
> on a day to day basis. If you feel included and are offended by that,
> keep it to yourself and ignore that fact.
> 
-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.19 (Darwin)
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJQmTe2AAoJEIskG/rSlyw4w/kH/3IOGeeygfzqWWsxTehjIfiO
c2zGIYXqyjxq1R4nxu5x5Zn+ErMHZ5jkXQX5SLCEbwr4Rh4p7suwB9BwSCna5rMy
XxaFT0oTyRbbCFY5J4OFro6+Hn7uBVNPlTA28u42ye2BPhVfAanjbbS/ZxNrnFXz
g2VdgH09OY9DHqcddOMlk9gWVnemwJ3gdIW8Lt4hv2ib0vATnLP9cmwMSXgpNuzD
eUFBPLcerML8Ie14J0EKmK/mOa4SA2RNKe3Ud5Z6AScL2YwbYPi3AVDsgk9p0vmn
ZVhuRERj4yulJd+W2ug4L10DFbiF+/asjqtZmvjlUyIwUEzXdJl530m5laIJZQk=
=eJXJ
-----END PGP SIGNATURE-----