Konstantin,
The "scope" section of the project proposal is the most important
section (yes, I know, that's not obvious and it sure would be helpful
to have your handy "propose a project" form to make that clear), and
the scope section needs to describe the encompassing scope of the
project and not a plan. The scope defines the space the project will
work in - the whole space, not just today's space. Thus the scope
section should not include any time-based words such as "at least" and
"future".
Additionally, the scope section of this proposal needs to be fleshed
out a little to explain the project to Eclipse community members who
are not code insiders. In fact, the purpose the project proposal is to
announce the new project to the larger Eclipse community and that
community includes people in other projects who are not directly
familiar with this code and it includes the marketing and business
people at our various member companies - people who have no experience
at all with the code. The scope section needs to be readable by all
those people.
- Bjorn
Konstantin Komissarchik wrote:
Scope
The project would be composed of at least two components:
- Core Framework
- API for building facets and manipulating faceted projects.
- UI for manipulate faceted projects. Includes a project
properties page for adding and removing facets and a base wizard
implementation for creating new faceted projects.
- Documentation for writing facets.
- JDT Enablement
- Java facet that's built around JDT's Java Project Nature.
- Modeling of runtimes that are JVM-based.
- Tools for making it easier to build facets for Java-based
technologies. Includes tools for helping facets manage libraries.
- Other Enablement (future)
- Integration with other Eclipse Projects. This is an area
for possible future work.
--
[end of message]
|
