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.
Difference between revisions of "E4/Meeting Minutes/Status 20081002"
< E4 | Meeting Minutes
(→Discussion Topics) |
(→Discussion Topics) |
||
| Line 63: | Line 63: | ||
# Provisioning | # Provisioning | ||
## decisions on component structure | ## decisions on component structure | ||
| − | * /cvsroot/eclipse/e4/ ...? | + | ##* /cvsroot/eclipse/e4/ ...? |
| − | * access right for everyone | + | ##* access right for everyone |
| − | * Marcelo suggests EMF structure, ie standard plugins,features,doc,tests subdirectories under /resources, /ui, etc. | + | ##* Marcelo suggests EMF structure, ie standard plugins,features,doc,tests subdirectories under /resources, /ui, etc. |
| − | * all components must keep "team project sets" up to date | + | ##* all components must keep "team project sets" up to date |
| − | * each work area gets it's own sandbox (UI, Resources etc.) | + | ##* each work area gets it's own sandbox (UI, Resources etc.) |
## assign website update rights | ## assign website update rights | ||
| − | * everyone has rights | + | ##* everyone has rights |
## download server rights for builds | ## download server rights for builds | ||
| − | * Boris and Doug | + | ##* Boris and Doug |
## mailing list | ## mailing list | ||
| − | * new name: e4-dev | + | ##* new name: e4-dev |
| − | * encourage use of [] tags to enable filtering of e4 list posts | + | ##* encourage use of [] tags to enable filtering of e4 list posts |
## Bugzilla | ## Bugzilla | ||
| − | * components are the names from provisioning list | + | ##* components are the names from provisioning list |
# Pervasive themes | # Pervasive themes | ||
| − | * talk about that on next call | + | #* talk about that on next call |
Latest revision as of 17:39, 2 October 2008
Status updates
Steve
- SWT/BE for ActionScript is alpha
- how do we ship? no milestones
Eric
- compatibility page * Eric to send pointer to list
Kevin
- e4 talks in London and Poland
- why isn't the model live?
- feedback
- future of RCP
- why not all web apps?
- CSS round up, looked at requirement from Lotus and Innoopract
- TK-UI and XAML based were interesting
- experiment with TK-UI, commit to e4 when legal clears * Kevin to drive the legal process
Boris
- e4 project was created!
Paul Webster
- investigating context
- context == bag of state for command execution
Ed
- declarative discussions happening (not on the list)
- should we move them there? Too early
Pat
- interested in web content in SWT browser
Doug
- had first meeting on resources work area, good debate on mailing list
- next phase is to get concrete
- Doug to create "straw man" proposal
McQ
- how to deal about copies of the code
- ie. compatibility with 3.x
- 2 approaches, copy and hack, keep up to date with 3.x HEAD
- copy at a release or milestone, tag and document so you know where you got it from
- Martin O: "There is a CVS standard way ..."
- Martin to describe this on the mailing list
Discussion Topics
- builds/milestones
- reuse Nick's build work
- our deliverable may end up being a list of patch features
- dowloads page is nightly build results and examples
- Provisioning
- decisions on component structure
- /cvsroot/eclipse/e4/ ...?
- access right for everyone
- Marcelo suggests EMF structure, ie standard plugins,features,doc,tests subdirectories under /resources, /ui, etc.
- all components must keep "team project sets" up to date
- each work area gets it's own sandbox (UI, Resources etc.)
- assign website update rights
- everyone has rights
- download server rights for builds
- Boris and Doug
- mailing list
- new name: e4-dev
- encourage use of [] tags to enable filtering of e4 list posts
- Bugzilla
- components are the names from provisioning list
- decisions on component structure
- Pervasive themes
- talk about that on next call