From what I can gather from the Eclipse guidelines, what should happen is for you to take on developer role for a bit. Here are some suggestions for how to get involved.
-Obviously, try to get the thing built and installed, etc.. :)
-Check out the bugzilla. There isn't a lot there yet, but...
add anything and everything you think of that could be done better or needs to be done or whatever.
even better, take a look at some of the outstanding bugzilllas and work on patches for them.
-Discuss details of meta-model design, API and ideas for what *you'd* like to see in AMP on dev-list. (More user focussed stuff might make sense on amp newsgroup.)
-Write documentation and example models! I'm especially wanting to get some cheat sheets and other internal documentation going. More than anything, right now we need to get people engaged in the project and that means getting them up and running and using the tool as quickly as possible, so I would say that this is the best way to contribute right now. There is actually a lot of stuff there now, but it's worthless if no-one knows how to use it.
-Along with this, any input on website, screencasts, and build issues is most welcome.
Any questions for me?