[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: [Subclipse-dev] Here we go again

From: Alain Pannetier <alain.m.pannetier_at_gmail.com>
Date: 2006-07-13 10:06:26 CEST

All,

If a merge needs to happen, I'll suggest the following combination :
   - Drop the subversive code, keep the subclipse code
   - Contribute the subversive PR (the name says it all no ?) to subclipse.

The best of both worlds !

This is what OSS is all about : 10 years ago, it wouldn't have crossed
Polarion's decision makers minds that they needed to give away
subversion to enter the market.

Nevertheless, on one side there's a long established vibrant
community, on the other a noisy old-style product software house
cladding itself in OSS outfits. Glaring fact.

Other than that I see no reason for a merge.
  - For one thing, competition leads to productivity and is good for
the consumer we all are.
  - From my personal experience, merging java projects in general and
eclipse plugins in particular is not straightforward and most of the
times results into wobbly hybrids bearing congenital malformations for
their entire life.

It seems to me that switching to subversive is like dumoing your old
wife to go with a new youger one :
  - You might find her prettier (I've read former comments in this
list denigrating subclipse on the ground that the icons were not as
pretty as the ones in subversive (!!)), but
  - She won't cook as well as the old one (subclipse in its present
state is more than the result of a few dedicated individuals serving a
community, it's a well polished productivity tool that has benefited
from the constructive critics and testing of many users).
  - She can dump you any time. If Polarion's folk discover that the
ROI is low they will dump the project and you'll be left to you're own
devices.

Morality : stay with your old wife. After all she's staying with you ;-)

The ambition of subversive to become an eclipse project a few weeks
after going public whereas subclipse has been around for the last 3
years is a tell tale sign of strong PR.
That would probably be better perceived if it had gone hand in hand
with a strong established market share underpined by a solid community
a respected committer team and a feature rich datasheet.

Everyone's entitled to choose of course.
As for me, for the time being, I'll stay with subclipse and will carry
on spreading it among the various projects I'm managing.
Since we've switched from CVS to Subversion, projects have been more
collaborative, a key factor of succes, and
the availability and reliability of Subclipse have been instrumental
to their success.

Sorry for the rant...

Alain Pannetier

On 7/13/06, Denny Valliant <valliant@unm.edu> wrote:
> > This project is at a great stage in its lifecycle to make this move and
> > that is why it is happening.
> >
> > Mark
>
> I agree. And who knows- maybe Polarion pays Alex enough to change his
> license, and everyone joins forces as Team-SVN. =]
>
> Thanks for all the hard work Mark, Alex, and everyone!! I appreciate it
> and am excited about the future.
>
> :Denny
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@subclipse.tigris.org
> For additional commands, e-mail: dev-help@subclipse.tigris.org
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subclipse.tigris.org
For additional commands, e-mail: dev-help@subclipse.tigris.org
Received on Thu Jul 13 10:06:32 2006

This is an archived mail posted to the Subclipse Dev mailing list.