should we merge the qiime-deploy-conf repo with the qiime-deploy repo?

[jairideout]

Should we merge the qiime-deploy-conf repo with the qiime-deploy repo?

It'll be one less repo to keep track of and I'm not sure what the benefits are of keeping these two separate. Often times I'll have to submit two pull requests and make sure that they both get merged at the same time, which is a pain. Also, it'll be one less repo that users have to clone in order to use the tool.

Are there any objections to this change? If not, I'm happy to work on this.

[antgonza]

+1 Agree, multiple repos for the same tool makes things more complicated.
BTW That's how we had it before making it public but Greg and you decided
to split, Paul and I agreed ... the idea behind was that you only had to
change the config part, which almost never happens.

[jairideout]

Thanks @antgonza! I think we were anticipating the tool having a more general purpose, so we didn't want QIIME-specific stuff (config files) to be included. However, as you pointed out, the two are pretty intertwined and the qiime-deploy tool itself has quite a bit of QIIME-specific code in it already.

[gregcaporaso]

+1, go for it.