Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Tigerstripe » What would happen if a significant number of end tool vendors simply dropped what they had to Eclips
What would happen if a significant number of end tool vendors simply dropped what they had to Eclips [message #5017] Fri, 30 November 2007 14:20 Go to next message
Eclipse UserFriend
Originally posted by: merks.ca.ibm.com

This is a multi-part message in MIME format.
--------------090505020501080105000303
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Hi,

I was just reading this blog

http://sureshkrishna.wordpress.com/2007/11/30/need-some-expe riences-on-topcased-oaw-for-mda/

It's a good reminder that diversity can also appear like chaos. For me,
it drives home the fact that it's important to compare this Tigerstrip
initiative to Topcased, Anyware, Obeo, Acceleo, oAW, ILOG, Borland, IBM,
and others who have a stake in the MDD space. Clearly we are all
helping model driven development reach the masses by working together to
create a coherent story. It's better for the community, in my opinion,
if being part of the Eclipse Modeling Project results in a loss of brand
identity. As such, while it's important and clearly desirable to draw
in the Tigerstripe community that the Tigerstripe technology has
attracted around its specialized model driven development vision, I
think it would be a shame to see a community that remains partitioned.
Creating a coherent set of technologies focused on solutions is the most
important long term goal for building a unified community.

For these reasons, I remain concerned that open sourcing the Tigerstripe
brand as an Eclipse brand with an associated dump of the existing code
base will add to the community's confusion about what exactly is the MDD
vision at Eclipse. We already have more than enough problems with that
very problem today. I would so much rather see this Tigerstripe
initiative begin as an integral part of the modeling project rather than
as a code dump that gradually migrates the Tigerstripe community onto a
replacement set of technologies. To my mind, such a migration process
is not all that different from slowly tearing off a band-aide. Each
time a hair gets pulled, it hurts, and soon you are anticipating the
next pulled hair, which is sure to come and somehow will hurt more than
the last one.. Better to tear it off and be done with it.

I'm not sure if I can do anything to help convince the Tigerstripe folks
to reconsider their current strategy. I'd really like to include you
guys as an integral part of the community as is the case for the long
list of organizations above (which overlooks the very sizable set of
individual committers also working on a holistic vision). It seems so
much better to starting by looking at where Tigerstripe can add value to
what already exists and where we can make existing things more flexible
so they is more easily molded to provide the kinds of solutions the
Tigerstripe community needs rather than have that be just long term good
intentions. As I've said before, good intentions often fall by the
wayside when the realities of development costs rears its ugly head...

Sorry if anything I've said seems like a slight. That's certainly not my
intent. I value the community above all other things and want to see
you folks as a part of it...








--------------090505020501080105000303
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
</head>
<body bgcolor="#ffffff" text="#000000">
Hi,<br>
<br>
I was just reading this blog <br>
<blockquote><a
href=" http://sureshkrishna.wordpress.com/2007/11/30/need-some-expe riences-on-topcased-oaw-for-mda/"> http://sureshkrishna.wordpress.com/2007/11/30/need-some-expe riences-on-topcased-oaw-for-mda/</a><br>
</blockquote>
It's a good reminder that diversity can also appear like chaos.&nbsp; For
me, it drives home the fact that it's important to compare this
Tigerstrip initiative to Topcased, Anyware, Obeo, Acceleo, oAW, ILOG,
Borland, IBM, and others who have a stake in the MDD space.&nbsp; Clearly we
are all helping model driven development reach the masses by working
together to create a coherent story.&nbsp; It's better for the community, in
my opinion, if being part of the Eclipse Modeling Project results in a
loss of brand identity.&nbsp; As such, while it's important and clearly
desirable to draw in the Tigerstripe community that the Tigerstripe
technology has attracted around its specialized model driven
development vision, I think it would be a shame to see&nbsp; a community
that remains partitioned.&nbsp; Creating a coherent set of technologies
focused on solutions is the most important long term goal for building
a unified community.&nbsp; <br>
<br>
For these reasons, I remain concerned that open sourcing the
Tigerstripe brand as an Eclipse brand with an associated dump of the
existing code base will add to the community's confusion about what
exactly is the MDD vision at Eclipse.&nbsp; We already have more than enough
problems with that very problem today.&nbsp; I would so much rather see this
Tigerstripe initiative begin as an integral part of the modeling
project rather than as a code dump that gradually migrates the
Tigerstripe community onto a replacement set of technologies.&nbsp; To my
mind, such a migration process is not all that different from slowly
tearing off a band-aide.&nbsp; Each time a hair gets pulled, it hurts, and
soon you are anticipating the next pulled hair, which is sure to come
and somehow will hurt more than the last one..&nbsp; Better to tear it off
and be done with it.<br>
<br>
I'm not sure if I can do anything to help convince the Tigerstripe
folks to reconsider their current strategy.&nbsp; I'd really like to include
you guys as an integral part of the community as is the case for the
long list of organizations above (which overlooks the very sizable set
of individual committers also working on a holistic vision).&nbsp; It seems
so much better to starting by looking at where Tigerstripe can add
value to what already exists and where we can make existing things more
flexible so they is more easily molded to provide the kinds of
solutions the Tigerstripe community needs rather than have that be just
long term good intentions.&nbsp; As I've said before, good intentions often
fall by the wayside when the realities of development costs rears its
ugly head...<br>
<br>
Sorry if anything I've said seems like a slight. That's certainly not
my intent.&nbsp; I value the community above all other things and want to
see you folks as a part of it...<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
</body>
</html>

--------------090505020501080105000303--
Re: What would happen if a significant number of end tool vendors simply dropped what they had to Ec [message #840931] Tue, 10 April 2012 17:36 Go to previous messageGo to next message
Eclipse UserFriend
1
Re: What would happen if a significant number of end tool vendors simply dropped what they had to Ec [message #888124] Sun, 17 June 2012 18:24 Go to previous message
Eclipse UserFriend
1
Previous Topic:[Announce] Eclipse/OMG Symposium 2010
Goto Forum:
  


Current Time: Fri Nov 28 20:49:59 GMT 2014

Powered by FUDForum. Page generated in 0.01898 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software