The AeroGear github organization needs to be cleaned up and organized for the launch.

Right now it have forks of jboss-as/quickstarts and /archetypes. We don't want to have all of the quickstarts and archetypes in our repo because keeping them in sync with so many updates is a pain. It also makes it more confusing to new users what parts are from the AeroGear team.

We need to look into using git sub-modules or some other approach so that the AeroGear quickstarts and archetypes are included in jboss-as repos, but pointing to AeroGear repo.

BTW - one issue with git submodules is it is likely that only repo's can be pointed too. That means AeroGear quickstarts and archetypes for jboss-as would each need their own repo. This is not ideal. Perhaps go with Wesley's suggestion and just have a readme fine in the AeroGear quickstarts/archetypes in jboss-as that points to our repo for the latest versions.

I'll need to talk with Pete about this, and also about possible workflows with this.

Because it will be important that our examples are included with the quickstarts. The primary reason being exposure for AeroGear, and vs versa for JBoss AS quickstarts.

So maybe with that it just makes sense to keep the complete /archetypes, and just keep whatever jboss-as quickstart/archetype we have in there? Then any other examples - like aerogear-7 - should exist on their own in aerogear repos.

We will need to review JBoss AS workflow, and talk with Jason to see if they have it written down. It is not following gitflow, but does have a multi-step workflow for commits, merges, rebasing, etc... It is similar to the dictator+trusted lieutenants approach from pro-git, but might have changes - http://progit.org/book/ch5-1.html