[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
RE: Future of VE was [[ve-dev] Re: ve-dev Digest, Vol 31, Issue 1]
|
Hi Steve:
And thank you for your detailed answer!
> I have spent a lot of the time since the last CVS checkin on issues
> related to the build of VE, to ongoing testing, and to
> building a deeper understanding of VE internals to resolve some
runtime
> problems. I'm in the process of preparing a VE 1.3.0 download page,
which will be a
> milestone build, rather than a true release. It will be usable with
> Europa, but as my platforms for testing are limited, I'd like to get
> some feedback on its current state before deciding how much
> additional work is necessary before it can be considered
release-ready. To this
> end, if anyone is able to give it a serious workout on a Linux or Mac
> platform and post feedback here, it would be very helpful to me.
I think we should realease nightlies or weeklies, vene before promoting
to a misletone so that folks can tests it.
As far as building in concerned this is an area where I am comfortable,
and Nick Boldt may be able to chip in a bit too too.
> Since you have already contacted me separately regarding becoming a
> committer, I know you are interested in helping.
Of course!
There is alareday a ptach and a link to a build there:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=202562
It includes the patch contributed by Erik Hecht
(Erik btw, could you subcribe to this list and create a bugzilla account
> For those subscribing to this list, the project could use additional
committers to
> help move it along at a faster pace.
I think that getting back in a groove of making frequent builds
available (at the minimum monthly, to be not too ambitious) , getting
some scheduled committers calls and IRC meetings, and starting to do
some serious triage on the bugs could go a long way.
> In particular, since I was unable to commit
> to the Europa release based on build issues at the time, I'd like to
> make sure that VE stands a good chance of making it into the Ganymede
> release train.
Once again this an area where help is readily avaialble.
> There are lots of things that need to be done,
> and since my day job doesn't include developing VE, I need to do my
work in
> evening and weekend time, so it doesn't go as quickly as I would like.
same here, and I think that getting an all volunteer project roaster is
a true blessing.
> There are many other uses to which VE could be put based on the
> appropriate level of community involvement - anyone who would like to
> step up and help would be welcome. If you are interested,
> please respond to this mailing list (rather than directly to me) and
I'll do
> my best to monitor the list and respond in a timely fashion.
As I said, I am interested. Erik stated to me he was too.
So has Nick and a few others.
There are also a few smaller improvements that could go a long long way
in making VE better. One is getting rid of the multi-VM-one-per-editor
architecture to get to something slimmer and less resource hungry.
> Many of the historic VE committers have other responsibilities these
days and can't devote
> the time the project needs, so it is a good time for the community to
step up.
Exactly. I am aalso trying to reach out to companies that have adopted
VE in their products.
They would have a vested interest in the project health.
Companies like Canoo and Nokia come to mind. There must be many more.
Many linux and eclipse distro shipped VE, and I have been and will
continue shipping VE in EasyEclipse at the minimum.
--
Cheers
Philippe
> -----Original Message-----
> From: ve-dev-bounces@xxxxxxxxxxx
> [mailto:ve-dev-bounces@xxxxxxxxxxx] On Behalf Of Steve Robenalt
> Sent: Monday, September 10, 2007 6:41 PM
> To: ve-dev@xxxxxxxxxxx
> Subject: [ve-dev] Re: ve-dev Digest, Vol 31, Issue 1
>
>
> Hi Philippe,
>
> I have spent a lot of the time since the last CVS checkin on issues
> related to the build of VE, to ongoing testing, and to
> building a deeper
> understanding of VE internals to resolve some runtime
> problems. I'm in
> the process of preparing a VE 1.3.0 download page, which will be a
> milestone build, rather than a true release. It will be usable with
> Europa, but as my platforms for testing are limited, I'd like to get
> some feedback on its current state before deciding how much
> additional
> work is necessary before it can be considered release-ready. To this
> end, if anyone is able to give it a serious workout on a Linux or Mac
> platform and post feedback here, it would be very helpful to me.
>
> Since you have already contacted me separately regarding becoming a
> committer, I know you are interested in helping. For those
> subscribing > to this list, the project could use additional
committers to
> help move > it along at a faster pace. In particular, since I was
unable
> to commit
> to the Europa release based on build issues at the time, I'd like to
> make sure that VE stands a good chance of making it into the Ganymede
> release train. There are lots of things that need to be done,
> and since
> my day job doesn't include developing VE, I need to do my work in
> evening and weekend time, so it doesn't go as quickly as I would like.
>
> For those who are interested in volunteering, it helps to have a
> background in the prerequisite technologies, principally EMF,
> GEF, and
> JEM. It would be helpful if you've built VE in a local
> environment, as
> Erik Hecht has done, even more so if you've fixed a bug, updated an
> override file, or implemented new functionality. For some of the
> potential Ganymede timeframe work, it would also help to have some
> background with any of the following: EMFT, JET2, JFace databinding,
> platform debug and launch APIs, ECF, RCP development, and JSR 295 and
> 296 (Swing databinding and app framework). While none of these
> technologies have been defined as actual projects yet, they
> all can play
> a part in what VE will become if given the attention it deserves.
>
> There are many other uses to which VE could be put based on the
> appropriate level of community involvement - anyone who would like to
> step up and help would be welcome. If you are interested,
> please respond
> to this mailing list (rather than directly to me) and I'll do
> my best to
> monitor the list and respond in a timely fashion. Many of the
> historic
> VE committers have other responsibilities these days and can't devote
> the time the project needs, so it is a good time for the community to
> step up.
>
> Thanks,
> Steve Robenalt
>
>
> ve-dev-request@xxxxxxxxxxx wrote:
> > Developers:
> > I was wondering if anyone is ready to comment on the future of the
> > project?
> > The last commit was on Mat 31st 2007.
> > This would really be a shame to let it die!
> >
> >
>
> _______________________________________________
> ve-dev mailing list
> ve-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/ve-dev
>
