[TYPO3-english] Rebranding: Get the green back

[Andi]

Great Gina Thanks

Guidelines for creating good open source software

There are 19 guidelines for creating good open source software listed in his essay[2]:

Every good work of software starts by scratching a developer's personal itch.
Good programmers know what to write. Great ones know what to rewrite (and reuse).
Plan to throw one away; you will, anyhow. (Copied from Frederick Brooks' The Mythical Man Month)
If you have the right attitude, interesting problems will find you.
When you lose interest in a program, your last duty to it is to hand it off to a competent successor.
Treating your users as co-developers is your least-hassle route to rapid code improvement and effective debugging.
Release early. Release often. And listen to your customers.
Given a large enough beta-tester and co-developer base, almost every problem will be characterized quickly and the fix obvious to someone.
Smart data structures and dumb code works a lot better than the other way around.
If you treat your beta-testers as if they're your most valuable resource, they will respond by becoming your most valuable resource.
The next best thing to having good ideas is recognizing good ideas from your users. Sometimes the latter is better.
Often, the most striking and innovative solutions come from realizing that your concept of the problem was wrong.
Perfection (in design) is achieved not when there is nothing more to add, but rather when there is nothing more to take away.
Any tool should be useful in the expected way, but a truly great tool lends itself to uses you never expected.
When writing gateway software of any kind, take pains to disturb the data stream as little as possible—and never throw away information unless the recipient forces you to!
When your language is nowhere near Turing-complete, syntactic sugar can be your friend.
A security system is only as secure as its secret. Beware of pseudo-secrets.
To solve an interesting problem, start by finding a problem that is interesting to you.
Provided the development coordinator has a communications medium at least as good as the Internet, and knows how to lead without coercion, many heads are inevitably better than one.

----

Compare it with what actually happened in the past weeks.

if each single point would have been followed we would really be much much further and noone would complain.

Kay's idea is good but as with most lists beside the main mailinglist english it will reach again not all not the whole community. But it could be a good start and a place for very good ideas.



Sent from Andi's iPhone

On Oct 11, 2012, at 21:24, Gina Steiner <gina at typo3.org> wrote:

> hi kay,
> 
>> Proposal:
>> To improve communication: I'm proposing to implement a mailing
>> list "typo3-about" @lists.typo3.org to have the right space for
>> meta discussions like this one. I'm asking you to support this
>> idea. Or is there a better idea?
> 
> this sounds great.
> 
> if you ask me, who i would give such an input i would spontaneously say:
> i would ask the community manager if such an idea makes sense. i know a
> lot of people want to enhance the communicational situation and if this
> is your personal itch and you want the community to communicate better i
> would try to get in touch with other people who also work on such a
> thing. and my guess would be to ask ben van 't ende if he can put me in
> touch.
> 
> i am a single person, i have my personal way. i have *my* natural way to
> work on such things and this would be my way. i don't suggest anything
> for you personal, i see that you care. i think there should be a
> solution for people who care to discuss. and ben e.g. works on this
> since quite some time and there are enhancements but we have a lot of
> work to do. really i can't say much more. it's also about the bazaar of
> the typo3 universe, i mean the bazaar kasper often referred to:
> http://en.wikipedia.org/wiki/The_Cathedral_and_the_Bazaar
> 
> aloha gina
> _______________________________________________
> TYPO3-english mailing list
> TYPO3-english at lists.typo3.org
> http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-english