-
-
Notifications
You must be signed in to change notification settings - Fork 50
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
Improve contribution guide #348
Comments
@carsten-j Better instructions and a Docker container (separately) would be great contributions! |
@twiecki I would like to help but I need input to do so. I do not have the time to do a complete re-engineering of all the conda env files, requirements, github workflows etc. But I am happy to drive the initiative if someone with experience will point me in the right direction. |
@carsten-j Can you write up just instructions that would have helped you? |
I can try that as a start!
…On Sun, Jun 9, 2024 at 8:13 PM Thomas Wiecki ***@***.***> wrote:
@carsten-j <https://github.com/carsten-j> Can you write up just
instructions that would have helped you?
—
Reply to this email directly, view it on GitHub
<#348 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAUNYSIGHVBUHOOCXW37RL3ZGSLNLAVCNFSM6AAAAABI6YOFDCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNJWG4ZDINRXHE>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
It is not easy for newcomers (or at least not for me) to get pymc-experimental up and running locally. The repo contains 3 requirements files and 2 conda env files.
It would be great with a description of the scenarios in which these different files are supposed to be used.
It would also be a help if there were more info about formatting, linting rules etc.
Did you consider adding a devcontainer.json file etc such that you can run this in a Docker container?
I am happy to help out with this one if someone will guide me.
The text was updated successfully, but these errors were encountered: