This the web page for the OpenPegasus Architecture Team. This is the group which exists to guide the technical development aspects of the project. The Architecture team does as much of its business by electronic means as is practical. Membership of the Architecture Team is open to anyone interested. To participate you need to subscribe to the Architecture Team mailing list.

Changes to the project occur by two possible routes - Bugs and PEPs.

Bugs are what you would think - reports of unexpected behavior by the system, and requests/suggestions for enhancements. The bug repository can be found at bugzilla.openpegasus.org.

PEPs are Project Enhancement Proposals, and are used to capture detailed information about the design and implementation of new functionality. PEPs are also used to introduce concepts, and also to define project processes.

The PEP repository is divided into two sections, approved PEPs, and PEPs for review. Discussion of PEPs takes place on the Architecture Team mailing list.

Ballots to approve PEPs will appear on this page and will be notified bt mail to the Architecture Team mailing list.

Approval of bugs id done electronically using the processes defines in PEP#336 and PEP#337. All bugs are reviewed and must be and must be approved before they can be committed to the CVS repository. Bug approval activity (requests and approvals) will take place on the Architecture Team mailing list.

This is the public, read-only, view

In order to gain logged-in access, you need to be a member of the pegasus-architecture mailing list.

If you have not already obtained a login to the site, follow the Mailing Lists link at the left. Then you will be able to login and join other mailing lists.