| Re: [escet-dev] Eclipse ESCET v0.2 plans |
|
I have 3 fixes for the CIF simulator, 2 of them based on old issues. Will dig up the details next week.
I also have written a railroad diagram generator (a nice constraint solver puzzle) that can be added under the assumption I get permission.
As for other things, I 'll discuss that with Pascal.
One thing that's going to come up often is author of the contributions. Obviously, for code that I wrote, it's simple. For code and patches written by PhD students, it may be simple too but let's discuss that to be sure.
My idea here is, that they wrote that code while being employed by the university, so the university owns that code. The university also has a general agreement with Eclipse, and I commit under the same agreement that would be sufficient?
Albert
From: escet-dev <escet-dev-bounces@xxxxxxxxxxx> on behalf of Beek, Bert van <D.A.v.Beek@xxxxxx>
Sent: Friday, April 2, 2021 15:07 To: escet developer discussions <escet-dev@xxxxxxxxxxx> Subject: Re: [escet-dev] Eclipse ESCET v0.2 plans Hi Dennis,
I have been thinking about this already before you send us this email, but your suggestions cover my ideas for the full 100% and even add more, so I really have nothing more to add. Thanks! Bert > On 1 Apr 2021, at 17:41, Dennis Hendriks <dh_tue@xxxxxxxxxxx> wrote: > > Hi all, > > We've released our first release v0.1. I think we should look at the next steps, i.e. release v0.2. I propose to first identify the big parts that we want to work on for this release. > > To kick off the discussion, I'll indicate my ideas here: > > Dependencies, product, build, etc: > • Include JDK in product again, using JustJ Java releases. Less installation steps. All users have the same Java version. > • Update to Eclipse 2021-03. To keep current and to enable using JustJ. > • Update to latest Java LTS release (currently Java 11). There are no JustJ releases for Java 8. Also Java 8 is (mostly) end of life. > • Use the new Eclipse CBI macOS notarization service, add entitlements, package as .dmg file. > • Customize welcome screen, with links to help, examples, different tools, web links, changelog, etc. > • Crash report should indicate where to report issues. > • Add test code coverage reports to build. > > Website/documentation: > • Generate multiple HTML pages instead of a single HTML page. More stable URLs, not so long pages, etc. > • Website landing pages separate from AsciiDoc-generated documentation. Landing page should be attractive and allow easy navigation, etc. > • Improve documentation style, enable syntax highlighting, etc. > • Reconsider project metadata and project home page, also in relation to the website. Reduce text there and refer to (various parts of) the website instead. > > Other: > • Address known bugs and performance issues. This includes some of the issues in the old TU/e issue tracker, and some new ones I encountered myself more recently. > • Make it easier to use/call CIF functionality from code. E.g. separate CIF applications from their functionality, helper functions to allow running code even if not invoked from application framework context, etc. > > Let me know what you think of these ideas. Also, I'm curious what you want to have in and work on for the next release. > > Dennis > _______________________________________________ > escet-dev mailing list > escet-dev@xxxxxxxxxxx > To change your delivery options, retrieve your password, or unsubscribe from this list, visit > https://eur02.safelinks.protection.outlook.com/?url=""> _______________________________________________ escet-dev mailing list escet-dev@xxxxxxxxxxx To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://eur02.safelinks.protection.outlook.com/?url=""> |