fix: should we rename this repo to "scikit-package-conda-forge"?

[bobleesj]

The goal is to remain consistent..

User can generate meta.yaml by running 'package conda-forge' once the user has done pip installed scikit-package?

[bobleesj]

If this is a good idea, I can implement "package conda-forge" in scikit-package to run "cookiecutt" this repo URL.

[sbillinge]

It probably depends if we are just going to keep this as our local place where we keep our group conda-forge meta-yamls under git control or if we want this to be part of scikit-package

[bobleesj]

Maybe as a separate repo because cookiecutter uses the github repo URL to initiate it:

When package create is entered, the following is executed in app.py:

cookiecutter https://github.com/Billingegroup/scikit-package

I believe that when we run package conda-forge, we could run:

cookiecutter https://github.com/Billingegroup/scikit-package-conda-forge

To me it's the simplest solution since we just need to modify the repo name and also we could create other commands linking other community's repos in the future.. (we could view https://github.com/Billingegroup/scikit-package-conda-forge like a plugin/independent project)

[sbillinge]

OK, that sounds reasonable.

[bobleesj]

Could you pls update the repo URL?

[sbillinge]

sorry, done it. Renamed to scikit-package-conda-forge

[bobleesj]

Closing - repo name changed