Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Standardize repo into the same practices as core mesa repo #46

Open
5 of 7 tasks
jackiekazil opened this issue Apr 2, 2022 · 6 comments
Open
5 of 7 tasks

Standardize repo into the same practices as core mesa repo #46

jackiekazil opened this issue Apr 2, 2022 · 6 comments

Comments

@jackiekazil
Copy link
Member

jackiekazil commented Apr 2, 2022

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.

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

Anything else?

@rht
Copy link
Contributor

rht commented Apr 2, 2022

  • Rename master to main

@rht
Copy link
Contributor

rht commented Apr 2, 2022

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

@wang-boyu
Copy link
Member

  • 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
Copy link
Member

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?

@jackiekazil
Copy link
Member Author

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.

@wang-boyu
Copy link
Member

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 #133 for this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants