Pavel Janík a écrit :
I do not respect some of your decisions
when important, I always try to not decide myself, but let the Mac Team
decides : there is always somebody with a good idea.
I'm here to give some directions, some visions of the MAc OS X port
future. Not decide for everything.
Please, read again the logs of the IRC meetings.
you as a person because I do not know you. I can only judge you from
your online communication and yes, sometimes your communication style
is really bad (as well as mine is, but the difference is that I know it
;-).
I'm not alone to complain.
This is one of the cases. I simply have the feeling that you want
something, but you are not able to tell it directly...
Sorry, but you are spending your time.
The most important for me is the future of the Mac port, not who/how
provide builds.
What is important is really free OpenOffice.org code. vcl understanding
is a good beginning, but we still have undocumented code, and Mac port
is a mess from that point of view.
Not everything is wrong though : vcl understanding helps other ports to
progress and demonstrated deep code changes were necessary (as example,
read last Kay Ramme blog entry).
This is even extremely positive.
What is important : make things change, make Mac port a major version,
show something else than Windows exists, show other way of software
exists, and create a strong Mac community.
A noisy community : doing noise, and hacks, because creativity is
inside. Creativity is not in "russian administration".
What I have in mind is find a way to fund seriously the expenses of
regular and /or very good developpers). I didn't say pay them, just
provide the minimal, to respect them.
Here is a part of what I have in mind, but I have a lot of other ideas
I'm workiong on currently.
To answer you more completely, I don't fear to say what I think, and
what I'd like to do.
Yes. You or someone else could fix it faster than it got fixed in
unomacli64.
Please read again : I used the word integrated. And the issue was fixed
before Maho started his build, and the fix could have been used.
And the only stupid thing is to argue about this :-(
This is your statement.
We are not Russian administration : OpenOffice.org is supposed to be
a free software, with some compromises when something is wrong, and
quick fixes when needed.
Does the "quick fix" (I call it hack!) break something else? Or some
other platform?
This is not a hack. Extract the cws and apply it to m221 is correct,
mainly when the cws is necessary to make the build work !
As Mac OS X Lead, I'd like to see a project able to provide working
builds first.
;-) So why haven't you fixed the problem before?
Again : the problem was fixed, but not integrated, and I don't see any
difference -excepted theorical- between issues fixed in a cws waiting
for integration, and the same cws already integrated.
I as a project member would like to see the current status as is.
Without hacks.
This is not hacks.
I as a member of QA project would like to see the current status as is.
Without hacks, so I know what I test.
Currently, you cannot test anything, because it doesn't start at all.
So *why* provide such builds ?
I as a l10n co-lead want Mac port sub-project to build for all possible
locales so our members could see the current status and could help in
their language.
Of course I agree to provide all possible locales. but when disk space
is important, something more close to the reality is the compromise.
Instead of discuss about different point of views, could we have serious
figures about what is really downloaded ? I'm sure this will help more
to decide a more "reallistic" number of locales.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
