I wanted to take the opportunity and inform you about things going on in the Eclipse Auto-IWG. We had a face-2-face meeting in Stuttgart at ETAS GmbH. We have made a lot of progress with the work packages as you can see from the meeting minutes and the updates made on the wiki.
In addition, we were listing to presentations from Stefan Voget (Continental) about EATOP, a potential Eclipse project implementing EAST-ADL, a presentation from Bosch India on an OSEE for Automotive package that they have created and finally from Oscar Slotosch from Validas in Germany on tool qualification. All the presentations are already available or will be made available at http://wiki.eclipse.org/Auto_IWG#Documents.
I'm also very pleased to welcome Validas AG from Munich, Germany and The Virtual Vehicle Competence Center from Graz, Austria as new Solution Members to the Eclipse Foundation. They have expressed strong interest in participating in the AutoIWG, and we are very happy to have their industry know-how and experience on board.
Is Eclipse important to Automotive and is Automotive important in Eclipse? Looking at the program of the upcoming EclipseCon in Reston, Virginia, I note that Ford's "What's next guy, Mr. Prasad and Peter Semmelhack, founder of Bug Labs will talk in their keynote presentation about the App Development Platform of the future car.
And in the 'normal' program, I can also find quite a number of talks that are of interest to the automotive crowd.
And last but not least, we will have an 'automotive meeting' at EclipseCon. Please add yourself to this Doodle poll if you are interested in participating or presenting.
Ralph
Showing posts with label LIfe Cycle Management. Show all posts
Showing posts with label LIfe Cycle Management. Show all posts
Thursday, March 1, 2012
Friday, June 10, 2011
Welcome GitHub to the Eclipse Foundation
GitHub has just recently joined the Eclipse Foundation as a Solution Member.
Based in San Francisco, GitHub is the largest open source code host with over 2 million Git repositories. As I hear from GitHub's clients it is the easiest way to share and collaborate on code and offers unlimited public repositories for free.
GitHub has committers working on the Eclipse EGit project as well as Mylyn tooling for issue tracking, code review and snippet sharing through github.com. This work will be presented at the Eclipse Indigo demo camp at eBay in San Jose, CA.
We look forward to having GitHub participating in the Eclipse eco system!
Based in San Francisco, GitHub is the largest open source code host with over 2 million Git repositories. As I hear from GitHub's clients it is the easiest way to share and collaborate on code and offers unlimited public repositories for free.
GitHub has committers working on the Eclipse EGit project as well as Mylyn tooling for issue tracking, code review and snippet sharing through github.com. This work will be presented at the Eclipse Indigo demo camp at eBay in San Jose, CA.
We look forward to having GitHub participating in the Eclipse eco system!
Monday, May 30, 2011
Long Term Support Initiative: Workshop Invitation
For over five years, Eclipse has provided a coordinated release of projects on the last week of June. Subsequently, each September and February there are service releases known simply as "Service Release 1" and "Service Release 2" respectively. SR1 and SR2 only address bugs and fixes in the releases. New features and API changes are developed exclusively in the code stream for the next major release. This cycle repeats yearly.
The consequence of this aggressive and successful development style is that organizations that need to remain "API stable" are left behind after SR2. All future bug fixes will only occur in the subsequent (and API changed) versions. For many organizations, this is not a major issue. Users are on a leading edge of technology, and welcome the major new updates each year.
As the number of Eclipse projects used by the company grows and as this company is shipping products based on the Eclipse platform, the need better organized support structures arises, since the company may have a support obligation for many years towards their customers. Other companies may be bound to such support obligations due to regulations in their specific domain (e.g., medical devices, aerospace).
We from the Eclipse Foundation have been asked in 2010 by a number of large Eclipse consumers to come up with a proposal how a long-term support eco system could be formed.
A good summary of the problem space and a solution scenario was provided by Jochen Krause and Karsten Schmidt in their talk at Eclipse Con 2011 (http://www.slideshare.net/KarstenSchmidt1/econ-2011-eclipse-lts).
A draft of the program as presented to the Eclipse Board of Directors in November 2010 can be found at the board minutes section of the Eclipse Home page (http://www.eclipse.org/org/foundation/boardminutes/2010_11_exhibits/ExhibitK.pdf).
After various discussions with consumers such as SAP and Ericsson, typical support providers such as Atos Origin and organizations that have the technical skills to provide bug fixes such as EclipseSource we have created a proposal, including the business side as well as the technical implementation.
To discuss this proposal and its implications SAP and Eclipse Foundation are hosting a one-day workshop on July 11th, 2011 in Walldorf, Germany. If you'd like to participate, send an email to ralph.mueller@eclipse.org. The number of participants is limited, so let me know as soon as possible.
The consequence of this aggressive and successful development style is that organizations that need to remain "API stable" are left behind after SR2. All future bug fixes will only occur in the subsequent (and API changed) versions. For many organizations, this is not a major issue. Users are on a leading edge of technology, and welcome the major new updates each year.
As the number of Eclipse projects used by the company grows and as this company is shipping products based on the Eclipse platform, the need better organized support structures arises, since the company may have a support obligation for many years towards their customers. Other companies may be bound to such support obligations due to regulations in their specific domain (e.g., medical devices, aerospace).
We from the Eclipse Foundation have been asked in 2010 by a number of large Eclipse consumers to come up with a proposal how a long-term support eco system could be formed.
A good summary of the problem space and a solution scenario was provided by Jochen Krause and Karsten Schmidt in their talk at Eclipse Con 2011 (http://www.slideshare.net/KarstenSchmidt1/econ-2011-eclipse-lts).
A draft of the program as presented to the Eclipse Board of Directors in November 2010 can be found at the board minutes section of the Eclipse Home page (http://www.eclipse.org/org/foundation/boardminutes/2010_11_exhibits/ExhibitK.pdf).
After various discussions with consumers such as SAP and Ericsson, typical support providers such as Atos Origin and organizations that have the technical skills to provide bug fixes such as EclipseSource we have created a proposal, including the business side as well as the technical implementation.
To discuss this proposal and its implications SAP and Eclipse Foundation are hosting a one-day workshop on July 11th, 2011 in Walldorf, Germany. If you'd like to participate, send an email to ralph.mueller@eclipse.org. The number of participants is limited, so let me know as soon as possible.
Monday, August 9, 2010
Welcome Intland Software to Eclipse
Intland Software has just recently joined the Eclipse Foundation as a Solution Member.
The company is a provider of collaboration and Application Lifecycle Management solutions for software development.
Within the Eclipse ecosystem, Intland is actively pursuing the following activities and projects:
To further enhance the seamless integration of Mercurial, a leading Distributed Version Control System, to Eclipse, with the MercurialEclipse plugin project. Intland is a firm believer in the superiority of the Distributed Version Control paradigm over the traditional centralized approach, and is actively developing several commercial and free software packages that support Mercurial and Git.
To reuse the first hand experience gathered while working on the Mercurial integration, and contribute to the EGit project - the Eclipse plugin that integrates Git with Eclipse - Intland has been invited to participate in EGit and team up with SAP, Google, Tasktop and other individual contributors.
Furthermore, Intland is working on defining and developing a generic integration layer between the leading Distributed Version Control implementations and the Mylyn task-focused interface. The primary aim of this initiative is to develop the most complete distributed ALM functionality available in the Eclipse universe. It includes sophisticated issue management, offline working and powerful associations between issues and source code change sets.
Intland’s collaborative software development solutions are used by major international organisations in industries, such as automobile, avionics, defence, finance and telecommunications. The company’s headquarters is based in Stuttgart, Germany, with a subsidiary in Silicon Valley, USA.
We appreciate Intland's membership and look forward to many joint activities
The company is a provider of collaboration and Application Lifecycle Management solutions for software development.
Within the Eclipse ecosystem, Intland is actively pursuing the following activities and projects:
To further enhance the seamless integration of Mercurial, a leading Distributed Version Control System, to Eclipse, with the MercurialEclipse plugin project. Intland is a firm believer in the superiority of the Distributed Version Control paradigm over the traditional centralized approach, and is actively developing several commercial and free software packages that support Mercurial and Git.
To reuse the first hand experience gathered while working on the Mercurial integration, and contribute to the EGit project - the Eclipse plugin that integrates Git with Eclipse - Intland has been invited to participate in EGit and team up with SAP, Google, Tasktop and other individual contributors.
Furthermore, Intland is working on defining and developing a generic integration layer between the leading Distributed Version Control implementations and the Mylyn task-focused interface. The primary aim of this initiative is to develop the most complete distributed ALM functionality available in the Eclipse universe. It includes sophisticated issue management, offline working and powerful associations between issues and source code change sets.
Intland’s collaborative software development solutions are used by major international organisations in industries, such as automobile, avionics, defence, finance and telecommunications. The company’s headquarters is based in Stuttgart, Germany, with a subsidiary in Silicon Valley, USA.
We appreciate Intland's membership and look forward to many joint activities
Subscribe to:
Posts (Atom)