Appropriate Forum For PR Priorities?
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 2.2k
- Forks
- 242
- Avg merge
- 11m
- Merged PRs (30d)
- 1
Description
There are a couple of PRs that are very little code, but quite useful:
https://github.com/nmwsharp/polyscope/pull/107
https://github.com/nmwsharp/polyscope/pull/138
I've tried to figure out what the best way to get a YES/NO on these is. I'm unsure if they're just going to be ignored or if there are some issues they bring up that should be discussed.
I know it's a lot of work to manage open source projects. I'd like to be as helpful as possible and not add to the maintenance burden. How can I help move these forward?
Some background ... I've been using Polyscope from Python a lot the last few months and have built a number of extensions. I'd like to work the changes into master to the degree that it makes sense so that I don't have to constantly keep managing my fork as master moves forward. Any guidance as to how to participate is welcome. Thank you for the excellent library!
I'm using it for 5-axis CNC machining applications:
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing pull requests #107 and #138 and the six comments on this issue to understand the requested decisions and any concerns. The issue is done when maintainers provide a clear yes/no decision or documented guidance on how these changes should be advanced.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, python
- Domain
- developer-experience
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100