[FLOW3-core] Forge issue handling

[Adrian Föder]

Hi Core-Team,

I'd like to drop some words regarding the issue handling at Forge; I 
don't want to upstir something, just consider everything I say as 
suggestion and especially as how "people" (which is me) might perceive 
the current situation.

What I, and therefore many other *users* surely observe, is:
there are many open *issues*, and I mean everything: Features, Tasks and 
Bugs, in Forge. They are not even "open", they are especially "new", 
red, and that's the problem.
People have suggestions, ideas, motivation, high spirits and they all 
want to make the product better (at least in their sense). They post 
that idea to the Forge, maybe post inline code suggestions; and the 
suggestion now lies there in the sunline, status set to "New", and 
nobody seems to care or even taking notice about.

It's not hard to understand that this frustrates people. I'll even go so 
far and say that this circumstance might influence that whole 
discussions currently out there a bit.

So, what we *could* do, and this is my suggestion as a base of discussion:
Basically new issues should be set to Rejected or Accepted more heavily, 
or even at all. Of course a Rejected may also upset people, but, we must 
be honest, some people have strange ideas which still do not match for 
the core.
But, when a suggestion is rejected, the author at least will know that 
he shouldn't rely on that anymore.


A bit more difficult is for Accepting, Accepting now would mean a 
feature is definately OK and'll go in the Core; a Bug is definately 
present and verified.
We may need an intermediate step, something like "a responsible person 
has read this and it looks OK".


So far; all of this leads to the question "who and when". Well, maybe a 
two-daily or weekly date could be established where responsible guys 
that have required competence, look over the Forge and check whether a 
feature makes sense or whether not; and if a bug is a bug or only a 
misusage.

There's definately the need for such, else the whole Forge issue 
handling might be doubtful.
There are years-old entries in that, I'm sure many of them could even be 
made obsolete (I've seen entries in the FLOW3 section even affecting 
extbase only, status: New)...


That's it.
I'll close with my favorite words: "what do you think?" :)


Best regards!

-adrian