Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [tools-pmc] [objectteams-dev] Requesting exception for patch feature shipped by Object Teams

Hi, me again,

As comments on bug 330312 mostly converge on strict rules,
I must renew my request. Some of yesterday's comments
mean BIG PANIC for the Object Teams project. For that reason
it is difficult for me to keep emotions out off this, but I'll try.

Some comments say that some gurus should help the Object
Teams project to find a better architecture that achieves the
same without doing bad things. Please understand that after
more than 7 years of intensively studying the alternatives and
engineering a solution that finally is well maintainable, I am not
very confident that anybody will just wipe away the conflict after
glancing at the issue for a little while. Do you have any 
suggestions how this idea could be made real?

Some comments say, that the rules should not only be applied
to the release train but to any release. This raises the question
whether being at Eclipse is actually a viable option for the Object
Teams project. Until yesterday I thought we're overdue for
graduation, today we're nowhere.

David said, the fact that the JDT is open-source does not mean 
it's OK to fork that code, because this may have bad impact on
the JDT and the community. So let's weigh the alternatives: 
  (a) the fork happens within the community and we all join forces
       for minimizing any risks involved. Or: 
  (b) the fork is forced to move away from and both
      sides just mind their own business.
What's the effect on collaboration?
What's the message sent to the public? 
As Jeff mentioned on the bug, part of this is about enabling
innovation (thanks Jeff).

In this one question I'd like to generalize (following my point
in ):
To some degree the Object Teams project represents a significant
part of the software engineering research of the past decade:
Advances in programming language design based on Java.
There are *countless* languages in this field, *many* of which would
deserve a JDT-qualitity IDE. Where are they? Will any be attracted
to Eclipse if a pioneer is forced to withdraw? (Yes, I know there is
one brave exception: AspectJ, which had the luck of support by IBM).
What's the message Eclipse sends to academia?

Regarding the risks I can only invite you to specifically discuss
the situation of Object Teams and the JDT/Core. I insist in saying
that things look different if you put aside global principles and
really look at the specifics (after all this is a request for an

Please let's define a controlled experiment, in which the damage
incurred (if any) and the benefits produced will be evaluated so that 
we all learn together and maybe draft a map of some uncharted

Lot's more to say but I'll shut up for now.
may I hope for some courage?

Back to the top