Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Difference between revisions of "E4/Resources"

< E4
 
(14 intermediate revisions by 4 users not shown)
Line 1: Line 1:
 +
__NOTOC__
 +
 +
<table border="0"  width="100%" cellspacing="6">
 +
<tr>
 +
<td valign="top" width="66%">
 +
 
The E4 Resources work is about improving Eclipse Platform [[Resources]],
 
The E4 Resources work is about improving Eclipse Platform [[Resources]],
 
both in terms of '''APIs and end-user usability'''.<br/>
 
both in terms of '''APIs and end-user usability'''.<br/>
Line 4: Line 10:
 
concept of a '''Project''' more flexible.
 
concept of a '''Project''' more flexible.
  
'''The Goal''' is to enable Eclipse-based products (and especially IDE's)
+
'''The Goals''' are listed in detail on the [[E4/Resources/Requirements|Requirements]] page, in short:
to better adapt to the way how their users are working, provide simpler
+
* Make the Workspace, Project and Resource structure flexible enough to embrace any existing (legacy) structures.
and safer programming models, building a solid base of Eclipse for the
+
* Build an architecture that's easy to understand, reliable, simple and safe to code against.
next 10 years.
+
* Support future environments (client/server, distributed, web, collaborative) - building a solid base of Eclipse for the next 10 years.
  
Interested Parties:
+
'''Interested Parties:''' (alphabetically) - See also the [[E4/Resources/Meeting/19-Sep-2008 Kick-off#Interested_Parties_and_Background|Kick-off meeting]]:
* Wind River - Doug Schaefer (Lead), [[User:martin.oberhuber.windriver.com|Martin Oberhuber]]
+
* Broadcom, Cloudsmith, Embarcadero, Freescale, Google, IBM, Nokia, NVidia, Wind River
 +
* Component Lead: '''Doug Schaefer (Wind River)'''
  
Documents:
+
'''Documents:'''
 +
* [[E4/Resources/Strawman]] - Strawman proposal
 
* [[E4/Resources/Brainstorming]] - Notes and Ideas from early meetings
 
* [[E4/Resources/Brainstorming]] - Notes and Ideas from early meetings
* [[E4/Resources|Work Areas]] - Planning
+
* [[E4/Resources/Comparison]] - Comparison of Eclipse with other systems
* [[E4/Resources/Meeting Notes]]
+
* [[E4/Resources/Requirements]], Use-Cases and Goals
 +
* [[E4/Resources/Definitions of Terms]]
 +
* [[E4/Resources/Work Areas]] - Planning
 +
** {{bug|252647}} is the master plan item. Look for bugs blocking on that one.
 +
* [[E4/Resources/Meeting Notes]] - Our meetings are on the E4 Calendar.
  
 +
</td>
 +
<td valign="top" width="33%">
 +
 +
<h3>Communication Channels</h3>
 +
* [https://dev.eclipse.org/mailman/listinfo/platform-core-dev platform-core-dev mailing list]
 +
* [[E4/Resources/Meeting Notes]]
 +
* Bugzilla as per the [[E4/Resources/Work Areas]]
 +
* ...as well as the other [[E4]] communication channels
 +
<googlecalendar width="100%" height="300" mode="AGENDA" title="e4 Calendar">ctri5teoag0n87t2qu9bla8u3g%40group.calendar.google.com</googlecalendar>
 +
This calendar is available in the following formats:<br>
 +
[[Image:Ical.gif]][http://www.google.com/calendar/ical/ctri5teoag0n87t2qu9bla8u3g%40group.calendar.google.com/public/basic.ics iCal],[[Image:Xml.gif]][http://www.google.com/calendar/feeds/ctri5teoag0n87t2qu9bla8u3g%40group.calendar.google.com/public/basic ATOM News Feed],[[Image:Html.gif]][http://www.google.com/calendar/embed?src=ctri5teoag0n87t2qu9bla8u3g%40group.calendar.google.com&ctz=Canada/Toronto HTML]
 +
</td>
 +
</tr>
 +
</table>
  
 
[[Category:E4|Resources]]
 
[[Category:E4|Resources]]

Latest revision as of 06:14, 26 November 2008


The E4 Resources work is about improving Eclipse Platform Resources, both in terms of APIs and end-user usability.
The Flexible Resource Model is especially about making the concept of a Project more flexible.

The Goals are listed in detail on the Requirements page, in short:

  • Make the Workspace, Project and Resource structure flexible enough to embrace any existing (legacy) structures.
  • Build an architecture that's easy to understand, reliable, simple and safe to code against.
  • Support future environments (client/server, distributed, web, collaborative) - building a solid base of Eclipse for the next 10 years.

Interested Parties: (alphabetically) - See also the Kick-off meeting:

  • Broadcom, Cloudsmith, Embarcadero, Freescale, Google, IBM, Nokia, NVidia, Wind River
  • Component Lead: Doug Schaefer (Wind River)

Documents:

Communication Channels

This calendar is available in the following formats:
Ical.gifiCal,Xml.gifATOM News Feed,Html.gifHTML

Back to the top