Manage moban upstream repositories

[jayvdb]

yehua has a key mobans which is uses to manage moban repositories.

This should be a feature of moban itself, as it is useful for other purposes.

@coala is already doing something similar, cloning the moban repo in CI and referring to it in the moban master file.

This then provides cookie-cutter like functionality.

[jayvdb]

e.g. https://github.com/moremoban/yehua/blob/master/yehua/resources/yehua.yml#L31

[chfw]

yep, agree. moban should handle its own dependencies.

[chfw]

This will be a big step forward. Will get this in next release.

[chfw]

the naming convention will be:

All moban extensions will have moban as prefix, i.e. moban-mako, moban-haml ..

All moban templates(so called mobans) packages, will have mobans as suffix, i.e. pypi-mobans, pyexcel-mobans.

And there will be an exercise to convert all mobans repo as python packages. They include pypi-mobans, pyexcel-mobans, echarts-mobans, pypkg-mobans. And I will take care of coala-mobans when I will have covered all potential issues.

These converted packages will be acting as equivalent of cookie cutter packages. However, the difference will be: moban template packages are libraries, whereas cookie cutter packages are "executable" because cookie cutter will make scaffolding out from a single package. In order to cover this gap, it will make sense to include yehua related files with mobans so that, yehua could command yehua files and moban will take mobans as template libraries. For coala-mobans, I think I would better not to replace coala-quickstart with yehua file.

[jayvdb]

As mentioned on #89, coala cant rely on pypi packages of coala-mobans .

We dont trust moban enhancements until they have used their enhanced template in other repos, so they must be able to build PRs referencing branches of the moban templates which are unmerged.

[chfw]

What about the following syntax (#89) for repo and pypi:

requires:
   pypi: 
     - pypi-mobans-pkg
   repo: 
     - https://github.com/moremoban/pypi-mobans
configuration:
  template_dir:
    - "pypi-mobans-pkg:templates" <-- this is how pypi is used
    - "pypi-mobans:templates" <-- this is how repo is used

[chfw]

I suppose this issue is resolved now.