I agree with @redlar that simpler deployment, a cleaner UI, and a RESTful API would be huge wins for Aggregate, but before we can do all that, we need to be deliberate about how we move it from UW into the community so we can incentivize contributions from more folks.
I'd propose that we first do the things we've done to all the community-managed tools.
- Document how to get started (readme, contributing)
- Standardize on build tools (IntelliJ, Gradle, etc)
- Introduce continuous integration and codestyle
- Move and triage relevant issues to Aggregate repo
- Move and triage the relevant documentation
I think the above will take a month or so, and once we have that in place, it will be easier to bring on contributors to add some basic changes.
- Upgrade to latest version of JavaRosa
- Add some basic usage analytics
- Take on one or two bug fixes
- Start to simplify deployment for users
Once that's done, we'll have developed some experience in the community about the state of Aggregate, we'll know what the long-standing issues are, and then we can plan a way forward as far as new functionality.