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 "G-Eclipse/Meeting Minutes/2009-05-05"
< G-Eclipse | Meeting Minutes
m (→Topics) |
|||
Line 26: | Line 26: | ||
* IP issues: Ariel marked the contribution bugs (about 160) with patches; the bugs are now reported in the [http://www.eclipse.org/projects/ip_log.php?projectid=technology.g-eclipse automated IP query] | * IP issues: Ariel marked the contribution bugs (about 160) with patches; the bugs are now reported in the [http://www.eclipse.org/projects/ip_log.php?projectid=technology.g-eclipse automated IP query] | ||
* [http://it-republik.de/jaxenter/jax/sessions/?tid=1076#session-16 Talk @ JAX]: About g-Eclipse, Equinox, AWS, Cloud - about 25 attendees, positive response | * [http://it-republik.de/jaxenter/jax/sessions/?tid=1076#session-16 Talk @ JAX]: About g-Eclipse, Equinox, AWS, Cloud - about 25 attendees, positive response | ||
− | * Globus: Removing hard coded dependencies, re-using the VOMS VO, externalizing things | + | * Globus: Removing hard coded dependencies, re-using the VOMS VO, externalizing things,... progress! |
+ | * Hands-on session at LRZ; only 50 percent of the submitted jobs (gLite) were successful | ||
+ | |||
* ..... | * ..... | ||
− | |||
− | |||
* Software installation on gLite for the course will be solved by Sylva and Ariel. There seems to be no issue on g-Eclipse itself. Main problems seems to be inherited from gLite infrastructure. | * Software installation on gLite for the course will be solved by Sylva and Ariel. There seems to be no issue on g-Eclipse itself. Main problems seems to be inherited from gLite infrastructure. | ||
* Release 1.0 review is planned now. We aim for a release at the end of may. Ariel will take care on list of contributors and contributions itself. | * Release 1.0 review is planned now. We aim for a release at the end of may. Ariel will take care on list of contributors and contributions itself. | ||
* release review documentation must be written in CVS in Karlsruhe. Harald will start with the document. Important part is the planning items for the next milestone. | * release review documentation must be written in CVS in Karlsruhe. Harald will start with the document. Important part is the planning items for the next milestone. | ||
* Release will be on Ganymede and we will provide an update site and epp package for the Eclipse code base. | * Release will be on Ganymede and we will provide an update site and epp package for the Eclipse code base. | ||
− | * Some work to reduce | + | * Some work to reduce dependencies in the core should be done! |
* we will not wait for the ssh IP CQ, but go ahead instead! | * we will not wait for the ssh IP CQ, but go ahead instead! | ||
* we plan for a three month milestone setup | * we plan for a three month milestone setup |
Revision as of 10:28, 5 May 2009
Meeting Title: | g-Eclipse Conference Call |
Date & Time: | Tuesday Mai 05, 2009 at 1500 UTC / 0700 SFO / 1000 NYC / 1500 London / 1600 Berlin |
Dial-in: | The conference calls are open to the public, and we invite everyone to participate. All you need is an Internet connection, the EVO software, and a EVO user id. You can get everything you need at evo.caltech.edu. |
Attendees
- Harald Kornmayer
- Sylva Girtelschmid
- Ariel Garcia
- Markus Knauer
- Thomas Koeckerbauer
Regrets
Topics
- Wayne Beaton was contacted concerning the future top level project and we aim for a stay in the technology part.
- No progress on the release review document
- IP issues: Ariel marked the contribution bugs (about 160) with patches; the bugs are now reported in the automated IP query
- Talk @ JAX: About g-Eclipse, Equinox, AWS, Cloud - about 25 attendees, positive response
- Globus: Removing hard coded dependencies, re-using the VOMS VO, externalizing things,... progress!
- Hands-on session at LRZ; only 50 percent of the submitted jobs (gLite) were successful
- .....
- Software installation on gLite for the course will be solved by Sylva and Ariel. There seems to be no issue on g-Eclipse itself. Main problems seems to be inherited from gLite infrastructure.
- Release 1.0 review is planned now. We aim for a release at the end of may. Ariel will take care on list of contributors and contributions itself.
- release review documentation must be written in CVS in Karlsruhe. Harald will start with the document. Important part is the planning items for the next milestone.
- Release will be on Ganymede and we will provide an update site and epp package for the Eclipse code base.
- Some work to reduce dependencies in the core should be done!
- we will not wait for the ssh IP CQ, but go ahead instead!
- we plan for a three month milestone setup
Action
- contributing to the release review document
Reminders
- JSDL problem from earlier meeting
- data management gets important.
Additional Topics
- Ariel will teach DESY about g-Eclipse in a seminar