Hi.
On 10.11.12 17:27, Stefan Neufeind wrote:
I was just interested in the process behind making it TYPO3 Surf.
I'd still be interested to learn about it in more detail. And if
somebody could write something together that could also be stuffed in a
small site to show it's an official
On 11/06/2012 05:15 PM, Steffen Gebert wrote:
[...]
I was just interested in the process behind making it TYPO3 Surf.
I'd still be interested to learn about it in more detail. And if
somebody could write something together that could also be stuffed in a
small site to show it's an official
Hi Steffen.
On 06.11.12 17:15, Steffen Gebert wrote:
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?
Well, how does that work right now? That is not a problem that is really
new, is it? And maybe the
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
-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
Hi,
From what I picked up from the brand presentation almost every
product inside the TYPO3 universe can be prefixed TYPO3
slightly different topic, but since the right audience is here:
Having TYPO3 blank product as naming scheme doesn't look
like a wise decision to me.
The real world
Good morning Olivier,
I will be reading:
http://incubator.apache.org/incubation/Incubation_Policy.html for
inspiration.
Will you join me?
yes ...
Martin
___
TYPO3-english mailing list
TYPO3-english@lists.typo3.org
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
From what I picked up from the brand presentation almost every
product inside the TYPO3 universe can be prefixed TYPO3
Well, but what if sb. builds something crappy and calls it TYPO3
Foobar. Not good, if everybody can use the name TYPO3
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
after some random thinking, I was asking my self, who defines/defined
Surf to be called TYPO3 Surf, thus make it a product of the TYPO3
community and Association.
Don't get me wrong: It's not that I dislike Surf - what I've seen so far
looks
On 11/04/2012 06:59 PM, Steffen Gebert wrote:
after some random thinking, I was asking my self, who defines/defined
Surf to be called TYPO3 Surf, thus make it a product of the TYPO3
community and Association.
Don't get me wrong: It's not that I dislike Surf - what I've seen so far
looks
Hi Steffen,
I think Surf was just used as an example to show the potential of having
a maker brand. As far as I can see it is not handled as a separate
product, just as Fluid isn't either.
Like Stefan already mentioned: They both don't even have their own
website...
Greetings, Michael
Am
Am 04.11.12 18:59, schrieb Steffen Gebert:
The Apache project is nice and a shining example, but we're not that far
that we have things like Apache Incubator or any defined process for
becoming an official product, yet, don't we?
Its not who you are, but who you want to be.
I would be in
In my opinion the TYPO3 Namespace should be open to the community. The
community forms the association, so everyone who decides to use the NS
for his own Products should do that. There are individuals out there
which kickstart a great product and gather a team around them
afterwards. The
13 matches
Mail list logo
