[TYPO3-core] FYI24 #12025: Make statuses in the status report sort alphabetical

[Oliver Hader]

Hi,

thanks to Georg for sharing the impression. I'd like to state my point
of view:

Since TYPO3 is a real community project, not driven by a large company
but by the community members, everyone plays a vital part of a whole
scenario. It is obvious that we cannot always have the same point of
view and thus it's very important that we discuss about these issues and
are open for feedback and comments - indeed, "RFC" is an abbreviation
for "request for comments" and nothing else. I expect that contributors
are open towards criticism if it's meant to be contructive and leads to
improving a situation. However, some threads grow and grow and never
come to an end since there's always something that is not perfect. If it
turns out that an RFC is not perfectly feature complete and the last
steps require some more work, it would be fine to continue with that
working version, write down the requested enhancehents and solve them in
a different RFC. That way it's more helpful than just blocking ideas
with a "No!" or "Do it on your own!".

However, everybody is trying to get the best out of it, be it writing
patches, reviewing and testing them, coming up with a better idea,
creating documentation for other users or...
As you can see, the possibilities of contributing to TYPO3 are endless
and each is highly appreciated since it adds more and more value to our
project.

I feel that the TYPO3 core team is not an elitist crew of
super-developers. Each team member once started as everybody did. Due to
motivation, taking over responsibility for a core project and a severe
persitence in being active inside the community, people got and still
get invited to the core team. It's also impossible that only the core
team handles the releases on its own. The whole community is again the
vital part to deliver new gems to TYPO3.

This was generally spoken. Concerning to this thread, we realized that
there are some problems under the cover. Since they are more of a social
nature, there is no requirement to expatiate on that in this thread - a
solution and consense will be elaborated internally and also in private.

So: Everybody, your work and contribution to TYPO3 is highly appreciated!


Rock on!
Olly


Georg Ringer schrieb:
> Ingo Renner schrieb:
>> It was rather meant to address all those in this list (and other
>> lists) who keep demanding things and complaining about stuff althought
>> not being in a position to do so. They'd be in that position if they'd
>> contribute - another explanation of what I mean with Do-acracy.
> 
> I am sorry - and I really am - that I am not as good as you and maybe I
> will never be!
> 
> Because of my lack of knowledge I can just concentrate on pretty basic
> stuff in the core: A small bug here, a stdWrap there and some labels in
> between!
> 
> What do I wanna say?
> I am feeling that you are talking about people like me - who are allowed
> to be on this list (thanks for that) and who still don't share a
> complete class or something worth like that.
> 
>> The main point again in the end boils down to my frustration and
>> resignation to all these complaints without contributions from the
>> ones requesting changes.
> 
> I do invest quite a few hours for TYPO3 - especially in the german
> forums and got there more than 20.000 postings online - helping
> beginners and others to handle TYPO3 - quite boring work to explain
> things 1000 times but it makes me and others happy too!
> 
>> So I contributed to make it happen as far as I could. That's how it's
>> supposed to work. Give and take.
> 
> Yeah. Give and take! But shouldn't everything seen as one big thing?
> Maybe I don't give much here in this list but I really do in another world.
> 
> Am I only allowed to test patches and give a +1 (which doesn't really
> count much) but not allowed to say to some RFC (which means Request for
> comments and not Ready for commits) that maybe another way is better? Is
> this not a kind of contribution too?
> 
> Georg, off that list because of OT
-- 
Oliver Hader
TYPO3 Release Manager 4.3