How is it different, you might ask; Some of those differences are listed below:
Complete separation from each aspect of the development cycle.
If you ever have worked in a large development environment, you may understand the importance of this. If you have not, the main reason this is needed, is to limit the amount of time that each department must rely on each other to complete their task. For example, if you have a department which does nothing but the design element of the project, they can complete their side of the project without having to worry about the developer doing the business logic.
Code graduation process
This is a new approach to creating a full fledged framework, which caters to the basis of necessity. It also helps the project in finding worthy developers who have the same mind-set in how suitable programming should be done. The jist of this, is functionality first gets introduced as a module. Once it becomes apparent that the functionality is being re-used in multiple places, it gets re-fined to get put into the API of the project. Apon further use, if it still proves itself to be more fundamental to the project, it will graduate into the Framework group of the project.
This helps Antares also find suitable developers, as if they continually introduce modules that get promoted, they will get elected to be on the development staff to help develop towards the API. If they continue to produce suitable code, they will eventually get elected into the Framework staff. Each level of the development staff will assist in managing and maintaining the mind-set of the project for their group.
At this time, Antares is still very young, and will be gradually growing into the project that it is desired. All feature requests, and support requests will be handled by the core development staff. Eventually, Antares would love to pick up more outside developers, and push the project into a never ended growing state.