Hi Andreas, *
first a disclaimer: my comments represent only my own views about the
project - I'm not speaking for anybody else (esp. not for Torsten)
Addition to the disclaimer: I have been a long-term contributor to the
project but have never really contributed code (ok a ~10 LOC patch).
I've been deeply involved in community-QA andam now in l10n. For those
reasons I was elected to the council - at this time as one of the "5
Project Leads", but surely not the "One Project Lead or Co-Lead who is a
programmer not working for Sun." (Just quoting the old Council Charter)
SOmore or less I've been a "Product development representative".
...
Andreas Bartel schrieb:
...
However, I am worried not because I wouldn't know how much you love
the project, I really do. Ironically, that is exactly the issue I am
worried about. In my understanding, for this position you would need
to love the product more than the project.
Surely not! The thing we (you) are going to elect is the *Community*
council - and the project *is* the community. So althoug,there are
people within the council who should rather focus "product development"
*each* member should love the Community and the project.
Any member who favours product over community should rather be elected
to an "I'll do it my way" Council (or become a product manager in one of
our sponsoring companies).
And definitely more than code ;-) From my end-user driven perspective,
the project exists for the love of the product, and the Product
Development Representatives should coordinate the cooperative efforts
of all OpenOffice.org projects towards one vision. A vision of
OpenOffice.org as a product that brings true value to our project by
providing true value to our users. Ultemately, it's the outcome that
matters.
Correct :) We need all our different flavours of community members with
all the activities that need to be done to deliver a good product. But
once you did understand this (that we need *all* the components) it does
not really matter, if you prefere one above the other. If you
reallyunderstood,you will make compromises.
But (and once again:I am not a code hacker at OOo) there is one thingto
consider: without UX, QA, l10n or marketing you will deliver a product
of very poor quality that hardly anybody would like to use. But without
code, there will be no product (and no users) at all. The very hard job
for a product developer is to teach code hackers, that "just a product"
is not enough ;)
If I recall it correctly, you consider our current processes for
functional quality (QA) and design quality (UX) as unnecessary
impediments posed by a bureaucratic instance to maintain its influence
on the project. I mean, at least to me, it's big gap in here that
matters a lot for the position you are applying.
I did not attend this discussion, but I don't know, why there is a gap.
There is a difference between the necessity to have processes for
functional and design quality and the statement, that our *current
processes* are unnecessary (or not fitting the project's needs).
IMO,our current process have many flaws - that are not relevant, if you
work in a company - but become disturbing, if you work in a community
environment.
E.g. changing visual identity or introducing new features in a bugfix
release would be almost impossible for a community member outside the
main sponsoring company. But if you are "within", you can "just do"
(because the defined processes can be fully handeled within the company).
kind regards,
André
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@openoffice.org
For additional commands, e-mail: dev-h...@openoffice.org
