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.
Difference between revisions of "EMIWG/Face2Face-EclipseCon2009"
< EMIWG
(→Review Meeting Agenda (Draft v3.0) (Dino: 9:00 - 9:15)) |
|||
| Line 13: | Line 13: | ||
The Mobile Industry Working Group meeting is parallel to the "New Member Jumpstart" meeting, assuming most members of the EMIWG have been longer time members in Eclipse. | The Mobile Industry Working Group meeting is parallel to the "New Member Jumpstart" meeting, assuming most members of the EMIWG have been longer time members in Eclipse. | ||
| − | == Review Meeting Agenda (Draft | + | == Review Meeting Agenda (Draft v3.0) (Dino: 9:00 - 9:15) == |
9:00 - 9:15 Welcome and Round Table introductions | 9:00 - 9:15 Welcome and Round Table introductions | ||
| + | |||
== Brief Overview of Pulsar: Components, Roles and Responsibilities (Christian: 9:15 - 9:30) == | == Brief Overview of Pulsar: Components, Roles and Responsibilities (Christian: 9:15 - 9:30) == | ||
| Line 25: | Line 26: | ||
* Pulsar SDK extensions | * Pulsar SDK extensions | ||
| − | * Pulsar Server infrastructure | + | * Pulsar Server Hosting infrastructure |
| + | ** Login to servers | ||
| + | ** Licenses | ||
| + | |||
* Pulsar deployment and testing | * Pulsar deployment and testing | ||
** Of the packaged IDE Product | ** Of the packaged IDE Product | ||
** Of the SDK extension packs | ** Of the SDK extension packs | ||
| − | == Strategy Workshop - The Four Pillars of Focus (9:30-10: | + | == Strategy Workshop - The Four Pillars of Focus (9:30-10:00) == |
| − | === | + | === Roadmap - Strawman of Roadmap === |
| − | + | ||
* Survey – Priorities, JavaME, Web, Native, Other | * Survey – Priorities, JavaME, Web, Native, Other | ||
| − | * | + | * What is our strategy to combine Java/Native/Web development focus |
** Parallel workstreams? how to maximize synergy | ** Parallel workstreams? how to maximize synergy | ||
| − | * | + | ** Goal: (1) download covering all 3 areas, or separate downloads?� |
| − | + | ||
| − | + | ||
| + | === Product, Pulsar Platform Implementation === | ||
| + | ** Topics covered in Technical Work stream | ||
| − | === | + | === Best Practices (relevant to Application developer) - Brainstorm === |
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
* Documentation/Training | * Documentation/Training | ||
* Test Suites (might include references to Java Verified, etc) | * Test Suites (might include references to Java Verified, etc) | ||
| Line 58: | Line 51: | ||
* Technical Support forums | * Technical Support forums | ||
| − | === | + | === Promotion – Brainstorm === |
| − | + | ||
* First step – Pulsar microsite? | * First step – Pulsar microsite? | ||
* Pulsar platform – Branding (eg OEM SDKs) | * Pulsar platform – Branding (eg OEM SDKs) | ||
| − | * | + | ** What are our needs |
| − | * | + | ** How do we address them |
| − | * | + | *** Extension point API |
| − | * | + | *** Packaged Product Configuration, Splash Screen, etc. |
| − | * | + | |
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | |||
| − | == | + | == Technical Workshop (With Scope of the Galileo Time Frame) (10:00 - 12:00) == |
| − | === Pulsar | + | === Pulsar Galileo Packaged Product (10:00-11:05) === |
| − | === Pulsar | + | === Pulsar SDK Extension Packs (11:05 - 11:20) === |
| + | === Pulsar "readiness" of MTJ (11:20 - 11:30 ) === | ||
| − | |||
| − | |||
| − | |||
Craig, Gorkam: Device properties Database | Craig, Gorkam: Device properties Database | ||
Revision as of 21:37, 20 March 2009
Contents
- 1 Proposed Face 2 Face Meeting
- 2 Review Meeting Agenda (Draft v3.0) (Dino: 9:00 - 9:15)
- 3 Brief Overview of Pulsar: Components, Roles and Responsibilities (Christian: 9:15 - 9:30)
- 4 Strategy Workshop - The Four Pillars of Focus (9:30-10:00)
- 5 Technical Workshop (With Scope of the Galileo Time Frame) (10:00 - 12:00)
Proposed Face 2 Face Meeting
Date: March 23, 2009
Time: 09:00am-12:00pm
Location: Hyatt Regency Santa Clara, Camino Real Room
Agenda: Face-to-Face Meeting of the Pulsar Workgroup
Please Note, Monday is also the day of the Eclipse Members Meeting.
The Mobile Industry Working Group meeting is parallel to the "New Member Jumpstart" meeting, assuming most members of the EMIWG have been longer time members in Eclipse.
Review Meeting Agenda (Draft v3.0) (Dino: 9:00 - 9:15)
9:00 - 9:15 Welcome and Round Table introductions
Brief Overview of Pulsar: Components, Roles and Responsibilities (Christian: 9:15 - 9:30)
Create a common language for the meeting, define Components and Roles
- Pulsar IDE extensions
- Pulsar Packaged Product
- Pulsar SDK extensions
- Pulsar Server Hosting infrastructure
- Login to servers
- Licenses
- Pulsar deployment and testing
- Of the packaged IDE Product
- Of the SDK extension packs
Strategy Workshop - The Four Pillars of Focus (9:30-10:00)
Roadmap - Strawman of Roadmap
- Survey – Priorities, JavaME, Web, Native, Other
- What is our strategy to combine Java/Native/Web development focus
- Parallel workstreams? how to maximize synergy
- Goal: (1) download covering all 3 areas, or separate downloads?�
Product, Pulsar Platform Implementation
- Topics covered in Technical Work stream
Best Practices (relevant to Application developer) - Brainstorm
- Documentation/Training
- Test Suites (might include references to Java Verified, etc)
- Sample code
- Technical Support forums
Promotion – Brainstorm
- First step – Pulsar microsite?
- Pulsar platform – Branding (eg OEM SDKs)
- What are our needs
- How do we address them
- Extension point API
- Packaged Product Configuration, Splash Screen, etc.
Technical Workshop (With Scope of the Galileo Time Frame) (10:00 - 12:00)
Pulsar Galileo Packaged Product (10:00-11:05)
Pulsar SDK Extension Packs (11:05 - 11:20)
Pulsar "readiness" of MTJ (11:20 - 11:30 )
Craig, Gorkam: Device properties Database
Gustavo, Craig: API discussion for Pulsar Platform
- Extension points
- Packaging
- What the SDK providers need to watch out for