[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[news.eclipse.technology.kepler] Re: Thoughts on a Common Project Model

On 2007-07-12 16:12:21 -0400, Philip Dodds <philip.dodds@xxxxxxxxx> said:

User-Agent: Unison/1.7.9

We have been doing some thinking on creating an extensible common project model.

Why do we need a common project model?

A large part of providing a holistic view of the community resources and technologies in play within a project is understanding broader information about the project. The Maven styled pom.xml adds a rich set of information that can be used to understand both the structure of the project, its dependencies but also additional information that would support a developer looking to work in a loosely coupled manager with a project.

Continuing this thread of thought -

Would calling it a collaboration model rather than either common or community model. Since the aim of gather information about the project (everything from mailing lists through to some level of information about its dependencies and even possiblity its source structuring).

The thought here that standard structuring of this information would lower the barrier to entry for collaboration both as a co-developer but also a consumer of the project?

P