Hi Andrea,

thank you for your reply. Perhaps sometimes or always my mails look "argumentative", my concern is not.

If you invite to participate and then "use it not at all", that is not motivating for engaged users. But this thread is past. (The next thread will come ;-).

Am 11.06.2013 22:11, schrieb Andrea Pescetti:
...
All indications from the 5000+ survey participants were given to the
designers. Designers converged towards a common design and, if you see
the final pool where we picked the final one from, you'll notice that
they became all very similar to each other, and the final round picked
the adapted version of the most voted logo in the survey. So the
community at large was decisive the logo selection.

That's true and accepted. All "last" logos resembled the old one with little differences. Therefore a synthesis of all could have been again a little bit better. (Sure it would have taken more time.)

F.e. for me the gulls of Kevin are more "dynamic", fonts etc. of the old logo more harmonic.

But this case is finished.

Why shoudt we, users (and supporters) of AOO, do any tests and BZ
reports if they are not used "at all"?

Because all contributions are welcome and we surely don't look too much

See 2. para at the top.

at who reported a bug, we look at the bug. Let's take the Sidebar for
example. As you can see in
https://issues.apache.org/ooo/show_bug.cgi?id=121420 the Sidebar had 121
bugs reported so far, coming from regular contributors but also from the
public at large, and all have been taken seriously (97% of them have
already been fixed).

As I wrote in other mails, I absolutely accept priorities.

Perhaps a not so "efficient" technocratic view like yours would be
better for the product in such cases, although in many (or most) other
aspects it's adequate.

The project in general does not have a "technocratic" view. But we are
still in a situation where unless one regularly reads this list (and
traffic here is likely too much for someone who only wants to get some
basic updates) it is difficult to stay informed. We have margin for

I read not all mails but most of the mails in "important" (for me) threads.

improvement in internal communication. Maybe we would need something
like an "OpenOffice Weekly News", a summary periodically posted to the
list by someone, so that all contributors can read it to be sure that
they aren't missing anything important...

Perhaps this would increase the information wave and be contraproductive. On the other side structured information about this would be an advantage for the projekt but time consuming work.

So for now let us argument a (not too) little bit.

--
Grüße

Günter Marxen


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Reply via email to