[TYPO3-english] Rebranding: Get the green back

[Tolleiv Nietsch]

Hi,

well, this post has hardly got any response from any of the Core (CMS 
and Neos) team members for a good reason. The way you all responded to 
Rasmus is exactly what's keeping the actually active people away from 
these newsgroup discussions.

Why didn't you start the discussion in a polite way and asked for 
further explanation on the "lost green" and instead brought up a your 
own "lets revert everything" proposal. How did you expect people to react?

I saw how the community reacted when the T3O stuff was brought to 
preview last year - angry blogposts, useless blaming never asking for 
reasons - all of that, but no additional contribution. And even the ones 
that seemed to be constructive didn't get up and do things. The same 
happens over and over again. Sure, more and more communication is good - 
but look at the way you (community) communicate back.

The TYPO3 association was always asked to communicate more, especially 
regarding the budgets - right at the moment the budget applications [1] 
have got ~310 responses. Assuming that the authors responds are counted 
in, these 49 budget proposals together just got as much attention as 
this single flame. There's the chance to be part of discussions upfront 
- doesn't seem that this chance is properly used.

Better concentrate to initiate the communications you want to be part 
in. Did one or two years (or event months) ago anybody of the ones who 
gave their +1 to the "green" ask whether a rebranding would make sense - 
or had suggestions on how the brand should evolve?

I am being very constructive when I say that another newsgroup isn't 
needed, but better language and actually useful discussions in the ones 
we have.

Cheers,
Tolleiv

[1] - http://forge.typo3.org/projects/t3a-eab-budget2013/boards

Martin Bless schrieb:
> Hi Tolleiv,
>
> ((blushing for having sent that unfinished post)),
>
> here now the real one:
>
>> Imho typo3.english is a fine place to discuss stuff when everyone watches
>> their language and tries to respect the work of others.
>
> Alright, could be. The advantage of a dedicated "typo3-about" list
> for "meta" discussions I see are:
>
> We usually have different groups for different topics.
>
> People can select that group if they are interested.
>
> You can post a short info in "typo3-english" about a new topic in
> "typo3-about". That way we can reach almost anybody and still keep
> "typo3-english" "clean".
>
> Posts are being archived. If you want to find out later about what
> has been said it's much easier it it's in an archive specialized
> for meta stuff.
>
> In contrast to you I think it will *reduce* the risk of initiating
> flame wars.
>
> @Xavier: I guess it's not the amount of newsgroups that's keeping
> us busy but the amount of postings we're watching. A separate
> group can lower that number, and IMHO it's easier to prevent
> flamewars. Which reduces the number again.
>
> It could serve as an information channel where one can let the
> community know that some process is going on which will influence
> the community.
>
> Now that "TYPO3" stands for many products I definitely see the
> need to have a place to talk about how they relate. And no, I'm in
> no way thinking about flame wars.
>
> Looking back: It has been admitted regretted by Kian, Robert and
> those involved that communicating the process of the rebranding
> stuff did not really take place. All said they'll definitely do
> better next time. I'm sure they have the best will. But *how* can
> they do it if there is no well instantiated place for this?
>
> I'm afraid, if we don't have a mailinglist=newsgroup dedicated for
> community issues the next communication disaster is bound to come.
> Not because somebody is intending that. It it's due to the fact
> that there isn't a well implemented way to start or influence
> opinion building in the community.
>
> There's one more reason to invoke a dedicated "typo3-about" group:
>
> If we're continuing to have "typo3-english", which I assume, this
> now has a really broad meaning: It stands for everything that the
> term "TYPO3" now encompasses. I find that much to unspecific. I
> don't think it's fair to ask everyone who is interested in
> community developments that (s)he has to scan the "typo3-english"
> list for that.
>
> In fact, I'm much more seeing the chances of having a
> "typo3-about" list.
>
> I somebody comes up with a better solution: Let's see and have
> that!
>
> Martin
>

-- 
Tolleiv Nietsch
TYPO3 Core Developer


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