New contributor looking for guidance: from issue fixes to sustained PyMC contributions

,
1

Hi everyone,

I’m a contributor working to move from isolated issue fixes to steady PyMC contributions.

I’ve started with a docs improvement in the main repo (updating learn/usage_overview and linking it in Learn navigation), and I want to continue in a focused area with better scope discipline.

Could someone suggest:

  1. the best next 1-2 contributions to build on this work, and
  2. how to best get occasional mentor-style feedback (PR comments, Discussions, office hours, etc.)?

I’m happy to do the work; I mainly want to align with project priorities and maintainer expectations.

Thanks!

2

Hi Sanket

Nice to hear you’re interested in the pymc/pytensor ecosystem. I am going through all these introduction posts and copy/pasting the same question and advice. Have you ever worked with Bayesian models before? Even if the answer is yes, seeing you take our tools and apply them to some scientific questions that you’re interested in would be the right place to start. Basically my view is that it will be impossible for you to help develop these tools if you aren’t already using them yourself. If your interests are more in the direction of deep learning, then the same advice applies but with pytensor itself.