The Agent Modeling Platform has been approved as an Eclipse Incubation Project.

Metascape founder Miles Parker proposed the project and will serve as project lead, and Metascape will be donating the entirety of the MetaABM code-base to this effort as well as some pretty cool stuff we've had in the skunkworks. We encourage other members of the ABM community to become involved as well! You can read more details here:

Original Proposal

Creation Review

This is a really exciting time for us as it means that we will be able to contribute as part of a much greater whole and the tools formerly know as Metascape will be available to a much wider audience. Eclipse has an important principal of vendor-neutrality and that's one we fully support, so as part of the submission, we'll be changing all of the naming and branding. The MetaABM functionality will be part of AMF, the "Agent Modeling Framework" to relate it to the Eclipse Modeling Framework, or EMF. The "metaabm" metamodel itself will evolve to "acore" to relate it to "ecore".

Miles Parker, lead of the AMP project, says:

"The whole point of AMP is to be an open pan-community effort building really extensible tools. AXF / AGF will provide a lot of Eclipse-based (EPL) infrastructure, so in addition to fostering new tools, AMP can benefit existing ABM software projects as well as proprietary tools; in fact this is exactly the kind of thing that AMP is intended to enable. So while there is a technical vision for the core infrastructure, to make this work we really need your input and involvement. This could take any form, from offering ideas and use cases, to integrating with or extending AMP, to project committer status. Eclipse has two unique technologies that play a key role here. First, Eclipse EMF / Modeling provides the best Model-Driven Software Development platform going. Second, OSGi and the adapter mechanism make it possible for components to easily integrate at runtime without any build-time dependencies on each other. This means that, for example, one developer could provide a high-performance dynamic scheduling engine while another provided a unique visualization tool, and these could be user selectable at runtime. But just as important, the Eclipse community process has been very successful at marrying inclusiveness and transparency with developer-driven design and a mania for quality, and I'm delighted that this project can be a part of all of that."