Date: prev next · Thread: first prev next last
2011 Archives by date, by thread · List index

Hi Christophe, *,

On Tue, Jul 5, 2011 at 4:50 PM, Christophe Strobbe
<> wrote:
At 16:14 5-7-2011, Christian Lohmaier wrote:
On Tue, Jul 5, 2011 at 3:34 PM, Christophe Strobbe
<> wrote:
At 23:16 4-6-2011, Christian Lohmaier wrote:
Well, as seen on this list (by Malte's post), apparently there has
been work on a *private* cws that nobody in the community (and yes,
people who are working on private cws are not part of "the community"
in this regard - they are of course for that part of their work that
happens in public)
All promises IBM is making/has made so far is only lip service for me.
I only believe it after I see the actual contributions from them.
(And as written I don't consider code dumps that need a man-year of
work to get integrated as contribution)

If Oracle asks IBM to implement IAccessible2 on version 3.1 and releases 3.2 before IBM has submitted the IAccessible2 implementation,
how is IBM to blame?

Reality check please. 1st of all: What is stuff you know, and what is
stuff you guess?
Do you know that the 3.1 based ia2 dump/work is because Oracle asked for it?
If Oracle asked for it, do you know when Oracle asked for it?
Do you think Oracle really is so stupid to explicitly ask for code
based on an old branch?
If Oracle did ask for it, and IBM did "contribute" - why wasn't the
cws integrated?
2nd) Obviously you cannot integrate something that is not ready.
Why was it not ready? Because nobody worked on it. Who could do the
work on it? Of course best the developers who know the code, i.e IBM
And you cannot delay a release for years. (the cws Caolan mentioned in
the blog-comment was created in 2010-05 - while the branch-off for 3.2
already happened 2009-09 more than half a year earlier)

Between 3.1 and 3.2 the code had changed and had been moved to another
type of repository.

Again reality check. Oracle surely did ask for the code to be
contributed against the current, actively being-worked-on codeline. A
codeline that is not in feature-freeze. What IBM then delivers is a
completely different question. Also whether Oracle/Sun asks for it in
2008, but IBM delivers in 2010, it's obvious that code makes progress.

That is the reason for the complex and time-consuming
integration work that Oracle needed to do for IAccessible2.

NO! Why does it have to be Oracle to do the integration work. Again
one of the points about collaboration. Just uploading a
million-line-codepatch somewhere is not contributing. It is complying
with whatever deals that were signed or to comply with license matters
at best.

The integration and testing were still in progress when Oracle decided
to stop investing in As far as I know, that is why
the IAccessible2 code did not end up in public repositories.

Again this is stupid argumentation. We're talking about a OpenSource
software here after all. And we're not talking about weeks, but years.
We're talking about big announcements to dedicate more than 30
developers to work on the officesuite and collaborate with upstream,
but no results after 4/5 years.
And this further proves my point about questioning IBM's commitment.
Lip service, but no actual work that ends up "upstream".
They did not contribute to OOo, but they did drop some code at Oracle.
Again this is not my idea of contributing to the project.

The contribution to the 1.1.5 codeline is irrelevant because completely
outdated. I added that note merely as backgound information.

No, it is not irrelevant, because it is the very same situation. Big
announcement "we will conribute, we have lots of manpower" but no
results. That's the whole point. IBM doesn't have a record of being a
good contributor, the opposite is the case. And to change this, we
don't need another lip-service announcement, but actual code
That you can only point at Ia2, but not at other work is further prove
of this topic.

And don't get me wrong, I'm sure that you'll see IBM contributing to
apache-OOo, at least until you can actually build something from
Apache-OOo sources you can ship to the users, but after that I'm
pretty sure that IBM will focus again on its very own Symphony and
only do the necessary stuff to keep their own stuff compatible.

And don't get me wrong²: I'd be happy if IBM proves me wrong.

If Sun/Oracle engineers state that IBM donated the IAccessible2
implementation, it is unlikely that this piece of work was done
by Sun/Oracle.

Again it is not about the Ia2 work itself, but the porting from the
old 1.1.5 codedrop to "current" codeline.
You apparently don't know any hard facts about this, neither do I. So
while you claim that Oracle did ask IBM for the code ported to the 3.1
codeline, and that IBM then followed this request, I question this
Or even if IBM did contribute it against the 3.1 codeline: Why is it
still not integrated? This can only mean that a huge amount of work
is/was still left.

You mentioned that the vcs moved between 3.1 and 3.2 - but sorry
again, this is /no/ technical hindrance to switch from one vcs system
to another. The code is the same, no matter what. And you got the very
same "branch points" to base your work on in the new VCS system.

At this moment I know no one at Oracle who can or wants to say how much
the IAccessible2 implementation will end up in 3.4.

Well, then you missed Malte Timmermann's post.

Yes, I missed that. (Curiously, he sent that message from a private
address, not an Oracle address.)

Not curiously, as Oracle does not contribute to Apache-OOo apart from
donating the code.
All Oracle-devs who joined Apache-OOo did so privately/not as Oracle-employees.

(about the status of
iaccessible2), As Rob is strongly against releasing OOo 3.4 with the
"blessing" of the apache-OOo project ("take that discussion to the old
OOo-lists" basically (paraphrased)), I doubt there will be a OOo 3.4.0
at all.

If that is true, that will be a loss for the accessibility of
and LibreOffice on Windows.

The project did wait 5 years for it, it can wait another two...


Unsubscribe instructions: E-mail to
Posting guidelines + more:
List archive:
All messages sent to this list will be publicly archived and cannot be deleted


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.