Document process for setting up office hours

[reshamas]

cc: @cluhmann

Checklist

• share on PyData Discord server in "#pymc" channel

[canyon289]

Why is this here and why was it even in pymc.io? this has nothing to do with the docs or the code. This needs a better home we should make one.

I ask because I ran into this when looking for what I could to be useful with code, and would have never found it if I was looking for what needed to be done to improve the community

[ricardoV94]

Oops sorry everyone, I forgot this had been transferred from here in the first place!

[OriolAbril]

I think (and have been building everything on this basis so far) that other than passwords and private info all the team documentation should be in the same place and be public.

Contributors (especially new but also members of the team) will generally not be aware of all the different types of contribution one can do to help the project. If the documentation related to community activities is in a different place, only those who already know it exists and want to do that will see it. If it is visible also from the same page that gives guidance on code contributions it can attract more people. It also helps transmit the message that all contributions are important and equally valued.

Re having been doing this for a while. The pymc examplew website has no contributing section*, instead the jupyter style guide and the how to review PRs on pymc examples pages are in the contributing section together with the code contributions guidance. Even if they are for a different repository

• it should be on the navbar as an external link, the navbar of pymc examples needs a lot of work but it should point to stable docs so in general so it is partially blocked by the v4 release

[canyon289]

public is no problem! moreso is the pymc codebase issue tracker or pymc.io tracker the right public place to for this. that's all :)

…

On Thursday, May 19, 2022, Oriol Abril-Pla ***@***.***> wrote: I think (and have been building everything on this basis so far) that other than passwords and private info all the team documentation should be in the same place and be public. Contributors (especially new but also members of the team) will generally not be aware of all the different types of contribution one can do to help the project. If the documentation related to community activities is in a different place, only those who already know it exists and want to do that will see it. If it is visible also from the same page that gives guidance on code contributions it can attract more people. It also helps transmit the message that all contributions are important and equally valued. Re having been doing this for a while. The pymc examplew website has no contributing section*, instead the jupyter style guide and the how to review PRs on pymc examples pages are in the contributing section together with the code contributions guidance. Even if they are for a different repository - it should be on the navbar as an external link, the navbar of pymc examples needs a lot of work but it should point to stable docs so in general so it is partially blocked by the v4 release — Reply to this email directly, view it on GitHub <#21 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABXBFYOLYWYESAPWCTDEUS3VKY2WFANCNFSM5WL66T2Q> . You are receiving this because you commented.Message ID: <pymc-devs/pymc. ***@***.***>

[canyon289]

apologies I get it now. a good. Thanks oriol!

…

On Thursday, May 19, 2022, Oriol Abril-Pla ***@***.***> wrote: I think (and have been building everything on this basis so far) that other than passwords and private info all the team documentation should be in the same place and be public. Contributors (especially new but also members of the team) will generally not be aware of all the different types of contribution one can do to help the project. If the documentation related to community activities is in a different place, only those who already know it exists and want to do that will see it. If it is visible also from the same page that gives guidance on code contributions it can attract more people. It also helps transmit the message that all contributions are important and equally valued. Re having been doing this for a while. The pymc examplew website has no contributing section*, instead the jupyter style guide and the how to review PRs on pymc examples pages are in the contributing section together with the code contributions guidance. Even if they are for a different repository - it should be on the navbar as an external link, the navbar of pymc examples needs a lot of work but it should point to stable docs so in general so it is partially blocked by the v4 release — Reply to this email directly, view it on GitHub <#21 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABXBFYOLYWYESAPWCTDEUS3VKY2WFANCNFSM5WL66T2Q> . You are receiving this because you commented.Message ID: <pymc-devs/pymc. ***@***.***>