+1
I would appreciate if the tools become part of the SDK.
This would make the entry barrier for developers to start playing with e4 much lower.
I would volunteer to help.
Kai
From: e4-dev-bounces@xxxxxxxxxxx [mailto:e4-dev-bounces@xxxxxxxxxxx]
On Behalf Of John Arthorne
Sent: Sonntag, 19. Januar 2014 17:11
To: E4 Project developer mailing list
Subject: Re: [e4-dev] e4 tools build moving to Luna?
If parts of the e4 tools graduated into PDE, then all active contributors to those tools would be granted PDE commit rights as part of the graduation/restructuring. We did
the same thing with commit rights on other parts of e4 that graduated into the platform. So I don't think commit rights will be a problem at all. It does of course require active committers to keep maintaining it wherever it ends up.
John
From: Lars Vogel <lars.vogel@xxxxxxxxx>
To: E4 Project developer mailing list <e4-dev@xxxxxxxxxxx>,
Date: 01/18/2014 05:02 AM
Subject: Re: [e4-dev] e4 tools build moving to Luna?
Sent by: e4-dev-bounces@xxxxxxxxxxx
I personally like that we can adjust the tooling as needed. PDE seems very inactive at the moment.
But test, better Javadoc and fixing the outstanding bugs is good in general, no matter if the tools get officially released or not, so no need to hold such activities of.
Best regards, Lars
Am 18.01.2014 09:40 schrieb "Wim Jongman" <wim.jongman@xxxxxxxxx>:
There are things missing in the model editor and in the tooling in general. Most notably unit tests, javadoc and user documentation. We need to fix these before a release can be considered.
I am also happy to join a dedicated team that tackles this. So that makes two. Who wants to join us?
Regards,
Wim
_______________________________________________
e4-dev mailing list
e4-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/e4-dev
_______________________________________________
e4-dev mailing list
e4-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/e4-dev
