Update the install install-pymc step in env setup about pymc-data-umbrella

[reshamas]

@symeneses We can close this, right?

[reshamas]

cc: @cluhmann @OriolAbril

[cluhmann]

This appears to be fixed in the latest version of the docs. We just need to make sure that we are sharing that link (rather than the "stable" version) for now.

[OriolAbril]

We have an extended version of the pr tutorial on the sprint website. It also needs to bw updated and I think it would be best to share this one: https://pymc-data-umbrella.xyz/en/latest/sprint/tutorials/environment_setup.html

Note: installing pymc should now be the same for all operative systems, but afaik, installing all development dependencies (different than the ones needed to use pymc) is still different

[OriolAbril]

The contributing workflow in the sprint website is covered in the following docs (on mobile, copying an old slack message, not everything is 100% relevant here)

I also think we should recommend doing docstring updates to anyone who is unsure about what to do as it is relatively fast, useful and impactful to both devs and users and completely self-contained. For the docsting, we splitted the guide in 3, so now the steps are:

• https://pymc-data-umbrella.xyz/en/latest/sprint/tutorials/environment_setup.html (only needs to be followed once, preferably before the os-ws)
• https://pymc-data-umbrella.xyz/en/latest/sprint/tutorials/docstring_tutorial.html (should be followed once per docstring, that is the guide on what should the contribution be, what changes and where do they go). This is the step that depends on the type of contribution, if doing other doc changes or code changes it should not be followed, the other two are common for any code or docs girhub contribution
• https://pymc-data-umbrella.xyz/en/latest/sprint/tutorials/pr_tutorial.html (once per PR, also useful if doing contributions different than docstring ones)