Meetings

Project Plan

Architecture Overview

Collaboration Model

What follows is the beginnings of a discussion about what sorts of data elements different tools
look for in their project model. The goal here is to identify and exploit overlaps between Kepler and other Eclipse projects, in order to have a common API and set of providers to adapt external project information into the system. (By external project information I mean project data that doesn't originate within the specific Eclipse project in question, and is not therefore in a "native" format.)

If you have more information on this topic, please feel free to expand on what's already here. We're attempting to find a way to make a unified, extensible project model for general consumption...so we're going to need a lot of input.

I use Eclipse to develop, how does Kepler benefit me?

Think how many plugins you have to configure for each project, if you use a source control manager like SVN or CVS, if you want to use an issue tracking system, or build with external tools like Ant or Maven, and even worse if you have different configurations as the JDK version.

What can we do to alleviate this pain? By autoconfiguring several Eclipse plugins so you don't have to.

My developers use Eclipse, why should I talk to them about Kepler?

Imagine they use a project, open source or from another department and they hit a problem. They could instantaneously know what is the mailing list for the project, or who are the developers and their contact information.

How many times did you wanted to track information about a project and ended with an Excel spreadsheet or a text document? Formalize that into a Kepler facet and you'll be able to use that information in a structured way, index it, search,... be organized