Cross post from corona-dev@xxxxxxxxxxx
From: corona-dev-bounces@xxxxxxxxxxx
[mailto:corona-dev-bounces@xxxxxxxxxxx] On
Behalf Of O'Flynn, Dennis
Sent: Tuesday, October 17, 2006
4:13 PM
To: Corona
development
Subject: RE: [corona-dev] Eclipse
Collaboration Projects
Meeting Minutes:
- Eclipse Collaboration Projects
- Monday, October 16, 2006 @ 11:00 AM EDT
Attendees
- Project: Corona
- Dennis O’Flynn, Glenn Everitt, Joel Hawkins
(Compuware)
- Marcin Okraszewski, Edyta Kalka, Pawel Kaczmarek,
Piotr Jaworowski (Compuware)
- Brian Roberts, Paul Styles (Compuware)
- Project: ALF
- Brian Carroll (Serena)
- Summer Ficarrotta (Serena)
- Tim Bus (Serena)
- Kelly Shaw(Serena)
- Project: ECF
- Project: Mylar
- Project: Apogee
- Other
Minutes
- Scope of the meeting: Is there a need to align
“collaboration” technologies and frameworks.
- The consensus is yes.
- Even though each project is part of the Technology top-level
project, they each operate as independent projects.
- Collaborating on collaboration will help the projects
to better align themselves within a stronger Eclipse collaboration
offering.
- Possible other projects that would be interested in
collaborating on collaboration
- A consistent use of terminology is needed to improve
the communication from Eclipse to the market. Each project lists
“collaboration” as one of its values however,
“collaboration” is a broad topic. It was decided that
there is confusion in the collaboration community about the focus of each
of the Eclipse collaboration projects and a unified diagram and
description would be helpful.
- Initial set of common issues were listed. These
will be addressed during follow-up conference calls.
- Server-side environment
- Collaboration context
- Repository access
- Security / Identity management
- Communications
- Manageability
- Development /Build environment infrastructure
- Consolidated release of collaboration projects.
- Participation in Europa release train scheduled for
June 2007
- EclipseCon
- Suggestion to have an Eclipse
“collaboration” presentation where all collaboration related
projects are clearly positioned.
- As a group, host sessions and BOFs to provide
information to Eclipse community re: collaboration projects
- Collabnet
- Working on an Eclipse plug-in for Collabnet’s
bug tracking system
- IBM Jazz
- How does IBM’s commercial / proprietary
collaboration offering (Jazz) participate in an Eclipse collaboration
solution?
- Initial attempts to establish any relationships /
contacts with Jazz have not been successful.
Open
Issues
- Would there be any value of having a collaboration
development mailing list? Or should developers / users continue to
post messages to each project’s dev mailing list.
Action
Items
- [Paul Styles] Define common set of terminology to use
to provide consistent communication to the market.
- [Paul Styles] Coordinate EclipseCon presentation that
presents an overview of all Eclipse collaboration projects
- [Dennis O'Flynn] Schedule follow-up meeting to begin
discussion regarding common issues / needs.
From:
corona-dev-bounces@xxxxxxxxxxx [mailto:corona-dev-bounces@xxxxxxxxxxx] On Behalf Of O'Flynn, Dennis
Sent: Tuesday, October 10, 2006
4:01 PM
To: Corona
development
Subject: [corona-dev] Eclipse
Collaboration Projects
We have recently worked with Scott Lewis (ECF Project Lead) on some
common collaboration initiatives. During this time, it became apparent to
us that there are several Eclipse projects that are involved with some form of
collaboration technologies / frameworks. These projects are all part of
the Technology top-level project and are currently working independent from one
another.
Based upon information posted to each project’s website, wiki,
and mailing list, it is noticeable that there are several issues that we all
have in common. In addition, there may be some technologies that each
project could leverage from one another.
From our perspective, the projects are addressing the following
collaboration areas:
- Corona - tool collaboration
- ECF – data
collaboration
- ALF – process
collaboration
- Mylar – task
collaboration
- Apogee –
content management
We would like to explore any possible synergies our projects may
share. We propose that key members from Corona / ECF / ALF / Mylar / Apogee meet and
discuss possible ways our projects can work together.
The preliminary agenda includes:
- Scope of
collaboration
- Concepts
- Terminology
- Identify common
issues / needs
- Server-side environment
- Collaboration
context
- Security / Identity
management
- Communications
- Manageability
- Technology synergies
The meeting logistics are:
- Date: Monday,
October 16, 2006
- Time: 11:00 AM EDT
- Conference call:
866-213-1962 or 609-454-9912
- Access code: 2277433
If you are interested in collaborating on collaboration, please post a
message to corona-dev@xxxxxxxxxxx
to let us know. Share with us any additional topic items as well as your
view of how Eclipse can better address collaboration technologies and
frameworks.
The contents of this e-mail are intended for the named addressee only.
It contains information that may be confidential. Unless you are the named addressee
or an authorized designee, you may not copy or use it, or disclose it to anyone
else. If you received it in error please notify us immediately and then destroy
it.
The contents of this e-mail are intended for the named addressee only.
It contains information that may be confidential. Unless you are the named
addressee or an authorized designee, you may not copy or use it, or disclose it
to anyone else. If you received it in error please notify us immediately and
then destroy it.
The contents of this e-mail are intended for the named addressee only. It contains information that may be confidential. Unless you are the named addressee or an authorized designee, you may not copy or use it, or disclose it to anyone else. If you received it in error please notify us immediately and then destroy it.
