Re: [eclipsefp-develop] Defining the relationship between Cohatoe and EclipseFP

[Thiago A. <thi...@gm...>]

On 7/25/07, Leif Frenzel <hi...@le...> wrote:
> as mentioned earlier, I'd like to discuss the future relationship
> between Cohatoe and EclipseFP with you

Yup! We're hearing.

Its's been a long time since my last patch and even longer
from my last message to the list, but I am still around.

> Looking back, I'd say the experiment was successful

Very good to know. As far as I know, Cohatoe is the most
promising initiative for extending Eclipse with Haskell code
and it is good to hear that it is getting the attention it
deserves from the Haskell community. Maybe a day will
come when it gets wide attention from the Eclipse community
as well.

> So I think we should now think about how to organize this. There are
> basically two possibilities:
>
> A - merge the Cohatoe codebase back into EclipseFP
> B - leave Cohatoe separate (would need to create a new sf project or
> Google code project) and use it as a dependency in EclipseFP, or at
> least in some plugins in EclipseFP.

I have to say that my first thought was towards the second option.
Keeping the two things untangled will help people see that it is much
possible to extend Eclipse with things other than Java and EclipseFP
will play the proof of concept role. If EclipseFP manages to get things
right, it won't only strengthen the Haskell point but every other
language's as well. I can see that maybe the most obvious interest in
the beginning will be building developer, IDE-related stuff. But who
says that we need to limit ourselves to the obvious? A separate set
of plugins will encourage people to just do their stuff, while merging
the whole thing back into EclipseFP may hide the capabilities.

In the end I think my vote is for letting everyone be free (or "more
free") to choose what they want to do with the code.

By the way, if you choose to go down the separate project, I don't
see how all those benefits can be reached without treating
cohatoe like a full blown project. That means setting up its own
home page, wiki, mailing list and everything that people will expect
to find in an open source project.

Cheers,

Thiago Arrais