Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
E4/Meeting Minutes/Status 20090108
< E4 | Meeting Minutes
Agenda
- Contexts
- Futures
- Community building
Attendees
- Boris Bokowski
- Ed Merks
- Eric Moffatt
- John Arthorne
- Kevin McGuire
- Michael Scharf
- Mike Wilson (McQ)
- Oleg Besedin
- Paul Webster
- Simon Kaegi
- Steve Northover
Minutes
- Status
- XWT code from Soyatec is in repository and in our builds
- SWT browser edition code is in the e4 repository
- GWT implementation is lagging behind the others but overall ready to play with
- Getting the photo demo running again with styled widgets
- Fleshing out concept of contexts and working through implementation details
- Currently e4 build produces an unrelated collection of features, rather than a single application or runnable thing
- Welcome to Simon Kaegi joining e4 to look at multi-language support (Javascript in particular) and e4 on the server side
- Work progressing on e4 commands support
- Compatibility layer making progress
- Resource navigator, project explorer, and Java editor working (although you can't save the editor)
- Contexts
- Oleg gave an introduction to contexts. Without rehashing here, see recent discussion on e4-dev and bug 259423.
- Paul has been looking at other context-like mechanisms: core.expressions evaluation contexts and the IServiceLocator hierarchy, to look for synergies or opportunities to combine them
- Futures
- There is an interesting discussion going on about some new concurrency APIs for e4. There is now a rough API available and some example code that uses it. It is getting to a state where people should grab it and start playing around with it to see how it works for them.
- There is a good summary about recent state of the API in bug 253777 comment 74.
- The future work has also been a good example to us all about how to engage community and leverage community input. Scott has been providing nearly daily snapshots of the code state and has incremented the design numerous times in response to feedback.
- Community
- How do we engage a wider community
- How do we provide useful summaries of things that are going on for people who can't follow everything
- We need to start blogging/wikiing about things once they are in a state where we are looking to solicit feedback and wider community involvement. We should each individually devote some effort to our communication channels
- Milestone builds, New & Noteworthy covering both end users and interesting API/infrastructure will be a big help
- Proposed initial e4 milestone builds are M1 on February 6th, and M2 on March 20th
- Other ideas on community engagement welcome
- For next call:
- Discuss M1 content/shape
- EclipseCon demos
- Let's start discussing these items on the mailing list because next call will be close to M1