mesa-geo icon indicating copy to clipboard operation
mesa-geo copied to clipboard

Standardize repo into the same practices as core mesa repo

Open jackiekazil opened this issue 2 years ago • 6 comments

We want to make sure that this repo matches the practices of https://github.com/projectmesa/mesa. Here is a checklist. I am sure I forgot things, so please add them as you see fit.

  • [x] Add issue template
  • [ ] Add CI/CD
  • [x] Add discussions
  • [x] Convert to rebase to PRs
  • [x] Get PyPI access for deployments
  • [x] Create a Read the Docs
  • [ ] Add cookiecutter

Anything else?

jackiekazil avatar Apr 02 '22 01:04 jackiekazil

  • [x] Rename master to main

rht avatar Apr 02 '22 01:04 rht

  • [x] Add code of conduct
  • [x] Update license year
  • [x] Add CONTRIBUTING.rst
  • [x] Add CITATION.bib (but I figured that there is no publication on Mesa-Geo yet?)

rht avatar Apr 02 '22 01:04 rht

  • [ ] Add CITATION.bib (but I figured that there is no publication on Mesa-Geo yet?)

That's right! But I'm working on it at the moment.

wang-boyu avatar Apr 02 '22 01:04 wang-boyu

There are two remaining items:

  • [ ] Add CI/CD

Currently the CI/CD of Mesa-Geo is pretty much the same as that of Mesa.

  • [ ] Add cookiecutter

Do we really need a separate template for Mesa-Geo? Perhaps mesa startproject is already sufficient?

If not shall we go ahead and close this ticket?

wang-boyu avatar Nov 16 '22 15:11 wang-boyu

since I have been in the cookiecutter stuff recently -- I would like to take a few minutes today to consider the last item.

We need more improvements in general in our CI/CD, but if it the same as the main project, then that is what we are looking for at this time.

jackiekazil avatar Nov 16 '22 15:11 jackiekazil

Having a separate template for Mesa-Geo might be a good idea - to have a template that creates GeoAgent and uses GeoSpace in models.

Have created https://github.com/projectmesa/mesa-geo/issues/133 for this.

wang-boyu avatar Feb 07 '23 01:02 wang-boyu