Short-term prioritization of PRs/issues

[MilesCranmer]

I think some PRs/issues are quite important and should be merged/fixed soon after #508 is done. Here is a ranking of what I think the most important PRs are:

1. High importance:

• #481
• #493
• #487

2. Simple fixes/typos (could be merged quickly)

• #489
• #486
• #412

3. Mid importance

• #422
• #300
• #204
• #509

4. Other/niche issues

• #213
• #383
• #381
• #312
• #440
• #445

cc @mkitti @tkf @marius311

Feel free to suggest any I missed. Once #508 is merged I think the high importance ones should be merged relatively soonish.

[mkitti]

Would you be interested in joining the JuliaPy Github organization?

[MilesCranmer]

Yeah sure why not!

[mkitti]

@ararslan , could you invite Miles to JuliaPy?

[marius311]

Thanks for injecting some life here. My 2c (which can be readily ignored, since I have no free time to devote atm :cry:) is that the top priority should be removing roadblocks for a non-Julia user that wants to quickly use some Julia code, or to use a Python package which is using some Julia code under the hood. To that end, happy to see #487 at the top of the list, as, from the experience of setting up several users, the experience is sadly really really bad. You might also consider #496 instead, but I think that's harder, so probably best to focus on the low-hanging fruit first.

[MilesCranmer]

No problem. I have zero time to work on new features unfortunately, but I think helping review/merge maintenance PRs should be ok.