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 "Agenda for 1.23.2009 Siemens Meeting"
(→Draft Agenda) |
(→Draft Agenda) |
||
| (8 intermediate revisions by one other user not shown) | |||
| Line 15: | Line 15: | ||
==Attendees== | ==Attendees== | ||
| − | *Thomas Kiesslich - Siemens, Viktor Ransmayr - Siemens | + | *Thomas Kiesslich - Siemens, Viktor Ransmayr, Phillip Konradi - Siemens |
*Scott Lewis, Marcelo Mayworm, Jan Rellermeyer, Markus Kuppe -- ECF | *Scott Lewis, Marcelo Mayworm, Jan Rellermeyer, Markus Kuppe -- ECF | ||
*Jeff McAffer -- Equinox | *Jeff McAffer -- Equinox | ||
| Line 23: | Line 23: | ||
*Introduce Team Members to one another, both Siemens and ECF | *Introduce Team Members to one another, both Siemens and ECF | ||
*Siemens Team: Describe existing RFC 119 implementation. Answer questions and provide pointers to docs and/or code for post-meeting review. | *Siemens Team: Describe existing RFC 119 implementation. Answer questions and provide pointers to docs and/or code for post-meeting review. | ||
| − | *ECF | + | **Primarily have discovery portion of spec. |
| + | **Discovery code is part of Apache reference implementation | ||
| + | **Siemens is owner of code and so can expose to ECF project as desired | ||
| + | **'''ACTION''': Determine when ECF can have access to source code for review/understanding | ||
*Siemens Team: Describe intended plan WRT current codebase vis a vis ECF contribution | *Siemens Team: Describe intended plan WRT current codebase vis a vis ECF contribution | ||
| + | **Plan to contribute discovery implementation for RFC 119 to ECF/RT project | ||
*ECF Team: Describe existing ECF approach for discovery and remote services APIs (provider architecture). Answer questions and provide pointers to docs and/or code or bugs for post-meeting review. | *ECF Team: Describe existing ECF approach for discovery and remote services APIs (provider architecture). Answer questions and provide pointers to docs and/or code or bugs for post-meeting review. | ||
| + | **[[ECF_API_Docs | ECF Discovery and Remote Services API Docs]] | ||
| + | **[http://www.osgi.org/wiki/uploads/CommunityEvent2008/21_RemoteServices_OSGi_CommEvent08.pdf|OSGi Community Event 2009 slides] | ||
| + | **[http://www.eclipse.org/ecf/presentations/ese08/ESE_2008_ECF.pdf| ESE 2009 slides] | ||
*ECF Team: Describe ongoing work for ECF enhancement [https://bugs.eclipse.org/bugs/show_bug.cgi?id=249240 #249240]. | *ECF Team: Describe ongoing work for ECF enhancement [https://bugs.eclipse.org/bugs/show_bug.cgi?id=249240 #249240]. | ||
| − | *ECF Team: IP/Licensing discussion ( | + | *ECF Team: IP/Licensing discussion |
| + | **Siemens Able/Willing to Contribute under EPL (?) | ||
| + | **Need to get CQs for Galileo in place (see [http://dev.eclipse.org/mhonarc/lists/eclipse.org-committers/msg00726.html mailing list posting]). | ||
*F2F meeting in Europe (probably Munich) in January | *F2F meeting in Europe (probably Munich) in January | ||
| − | *EclipseCon09 | + | *EclipseCon09 |
| + | **Collaborate with Thomas on [http://www.eclipsecon.org/2009/sessions?id=618 Distributed OSGi - The ECF way] | ||
==Proposed Meeting Output== | ==Proposed Meeting Output== | ||
Latest revision as of 15:02, 23 January 2009
Contents
Purpose
- To discuss joint work at Eclipse Foundation between Siemens team and RT/ECF on supporting RFC 119 in Eclipse Runtime Project.
Day and Time
Friday, Jan 23, 2009. 1500 UTC 7:00am pacific
Call Information
- International: 613-287-8000
- Toll free: 866-362-7064
- Participant passcode: 892048#
Attendees
- Thomas Kiesslich - Siemens, Viktor Ransmayr, Phillip Konradi - Siemens
- Scott Lewis, Marcelo Mayworm, Jan Rellermeyer, Markus Kuppe -- ECF
- Jeff McAffer -- Equinox
Draft Agenda
- Introduce Team Members to one another, both Siemens and ECF
- Siemens Team: Describe existing RFC 119 implementation. Answer questions and provide pointers to docs and/or code for post-meeting review.
- Primarily have discovery portion of spec.
- Discovery code is part of Apache reference implementation
- Siemens is owner of code and so can expose to ECF project as desired
- ACTION: Determine when ECF can have access to source code for review/understanding
- Siemens Team: Describe intended plan WRT current codebase vis a vis ECF contribution
- Plan to contribute discovery implementation for RFC 119 to ECF/RT project
- ECF Team: Describe existing ECF approach for discovery and remote services APIs (provider architecture). Answer questions and provide pointers to docs and/or code or bugs for post-meeting review.
- ECF Team: Describe ongoing work for ECF enhancement #249240.
- ECF Team: IP/Licensing discussion
- Siemens Able/Willing to Contribute under EPL (?)
- Need to get CQs for Galileo in place (see mailing list posting).
- F2F meeting in Europe (probably Munich) in January
- EclipseCon09
- Collaborate with Thomas on Distributed OSGi - The ECF way
Proposed Meeting Output
- Steps for Siemens contribution to be assessed, used, and reviewed by ECF team
- Steps for access to ECF current and planned work by Siemens team (if needed)
- Team Contacts/Communications