In reply to Hugh Lashbrooke.

Hugh, I read your piece.

I mentioned (as an example) that TRAC has become almost useless. It's passibly good for dealing with broken existing features, but it's not a core influence thing. New ideas generally get shut down or merged into vaguely similar concepts, usually those that have already been "answered" as not possible or not required. You need only go look at the number of TRAC items related to comment handling to see how things generally get shut down.

Most importantly, TRAC is mostly about fixing what is broken, not about deciding what gets to be included (and broken) in the future.

Are you expecting the core team to just stop what they’re doing because you said so?

Nope, I am however expecting more than a casual brush off of "I don't see the use for me, so your needs end user are not that important". We don't just come up with random things to ask about for fun, we don't make code changes ourselves for amusement, we do it because we see and feel a need. That our situation may not match a core developer's situation doesn't make the ideas and needs less valid.

I will look more into the Make blog, but honestly, it seems quite a bit more on the technical and "talk at you" announcement of features more than a spirited give and take about future developments and ideas. Seem again to be more oriented towards "this is what we are doing..." as opposed to "what do you think we should be doing?".

then also eventually by submitting patches

Alas, for those of us who cannot code at this level, are we left out in the cold because we cannot properly code our own fixes?

I have been around since wordpress 1.x - it's been a long hard slog that doesn't get any easier by the day!