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

Services/Programs/Templates to use #6

Open
krischer opened this issue Nov 19, 2018 · 1 comment
Open

Services/Programs/Templates to use #6

krischer opened this issue Nov 19, 2018 · 1 comment

Comments

@krischer
Copy link
Member

We have to decide which services/program/templates to use for the various parts in the example we develop. I assume that participants will just follow these but they are of course free to choose their own.

git Hosting

Possibilities: github, gitlab, bitbucket, ?

I guess github is the obvious choice here although I personally really like the fully integrated approach gitlab is taking.

Programming language for the example

Python 3.7?

License

MIT/BSD

There are good arguments against the GPL variants in the context of scientific software but we of course also have to mention these.

Code of Conduct

https://www.contributor-covenant.org/ but there are many options.

We should probably also mention the various controversial arguments that have popped up over the last years over code of conducts and so on.

Unit testing in Python

I feel like pytest is the only sensible options these days.

CI

travis CI, circle CI, ... gitlab also has a really powerful CI system but it works best when using gitlab

circle CI tends to finish a lot faster which might be useful. But I can live with either choice.

Documentation

readthedocs is probably the only option for hosting. For writing the documentation we could either using sphinx or mkdocs (both work on readthedocs).

@lheagy
Copy link
Member

lheagy commented Dec 4, 2018

Excellent! I think since we are already on github, it is natural to stick with that for now, we can make mention of other platforms during the presentation

Do we want to live-demo these things? or pre-cook them here in the repo?

Or a middle ground: we could start a branch that has all of these items already? (it is helpful to have the answer somewhere in case we get tripped up)

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

2 participants