Quickstarts repo needs to be split up

[rawlingsj]

We need to split up the quickstarts repo, here's a suggested split but there a few questions so a bit of feedback is needed...

4 questions numbered below.

Looking at the current quickstarts directory structure..

quickstarts To remain..

app-groups <-- [Q1] split out into own repo?
apps <-- contents to be moved into separate devops, management apps as detailed below and this folder deleted
archetype-itests <-- keep
archetypes-catalog <-- keep
archetypes <-- keep
distro <-- keep
quickstarts <-- keep

management-apps

apiman
cadvisor
elasticsearch
fabric8
grafana2
heapster
keycloak
kibana
prometheus
templates

devops-apps

artifactory
brackets
cdelivery
chaos-monkey
fabric8-forge
gerrit
gogs
hubot-irc
hubot-letschat
hubot-notifier
hubot-slack
image-linker
jenkins
kiwi-irc
letschat
nexus
orion
sonarqube
taiga

ipaas-apps Not sure about these. [Q2] Should the ipaas apps be the two we have in the quickstarts/app-groups today and we need to add more?

move and rename https://github.com/fabric8io/quickstarts/tree/master/app-groups/quickstarts-http ->  ipaas-http
move and rename https://github.com/fabric8io/quickstarts/tree/master/app-groups/quickstarts-rest ->  ipaas-rest

To be deleted? see https://github.com/fabric8io/fabric8/issues/4600#issuecomment-131027037 [Q3] Do the mq apps have to be removed now or can they stay until the MaaS solution is available?

amqbroker
fabric8-http-gateway
fabric8mq-autoscaler
fabric8mq-consumer
fabric8mq-controller
fabric8mq-producer
fabric8mq

[Q4] Should these apps still be maintained or have they been replaced by different apps or approaches?

api-registry
app-library
grafana
influxdb
infinispan-server
jadvisor
jbpm-designer
registry
zookeeper

[davsclaus]

@rawlingsj are there more work on this ?

[rawlingsj]

@davsclaus no I think we can close this and raise issues if there is anything found to be outstanding.