Re: [native-lang] Update: Sun/NLC meeting

Hi Jörg,

....

>
> What did you foresee would happen with the RFE process? AFAICT the 
> plan was to implement a better RFE process for the release after 2.0, 
> and this is still possible and you can participate in making that a 
> reality. If you don't participate, you shouldn't complain if it 
> doesn't happen. And if you and others don't participate because you 
> 'foresee' it not becoming a reality, then that may simply be a 
> self-fulfilling prophecy.

Well .. the RFE process is (imho) very complicated an something that 
will take a *very* long term to get feedback. Although it is obvious to 
me, that this is a "Must be" for long term planning, it is something 
that fit's not very well with the community style. As we work with 
volunteers, who's intention ist often just "fun" , we should make it
- simple
- fast
and we should
- relase early
- release often

The RFE-process startet. We had people, who worked on the first stages 
(look at Christian's mail). But after that, not much happened. But this 
is a problem of the process (no, I don't want to blame Sun for that).
Again .. I know, this needs time (if we work in the futere, as we work 
now). But we don't need to start a process with such "planned delays", 
as we would get people frustrated.

>
> Of course the very long release cycle we've been having is a large 
> part of the problem and because of it most RFE submitted after the 2.0 
> planning phase are still waiting in some queue. But that this is a 
> problem is known and there is an ongoing discussion how this problem 
> can be avoided - again for the time *after* 2.0.
>
>> Honestly saying, I don't really know, why I care about issues, that 
>> could be resolved within minutes .. 
>
>
> How do you know that? If you know, why don't you resolve them 
> yourself? Do you have examples? Do you consider that changing the user 
> interface requires more than changing the code (e.g. specifications, 
> documentation, translation).

Well .. Robert gave an example, another was the quickstarter.
A (not that important but frustrating one) is here:
http://qa.openoffice.org/issues/show_bug.cgi?id=46289
I even don't know, if this is easy to fix, or if tooke the right way, as 
there has been no answer.

And why don't I fix it by myself? Because I try to fokus on bug hunting 
/ qa. I tried for a very long time to do "as much as possible" witin 
this project .. and ended up frustrated (and burned out).
I really would like to fix some simple things by myself .. but how, if I 
get no answer or guidance?


And .. sorry to say that. I'm with this project for about three years 
now and I think, I know a part of this project (so I don't feel, I'm a 
community beginner). I've been subscribed to several lists, trying to 
get the idea, what should belong where and what could be resolved where. 
I won't do this agian, as I really felt, my head got bloated.

Andre