Hacktoberfest 2026:維護者為十月標記出來的 issue,仍然開放、適合新手。 瀏覽 Hacktoberfest issue

Appropriate Forum For PR Priorities?

未關閉
#141 6 則留言 0 個 reaction 已指派 0 人 在 GitHub 檢視

還沒有人認領這個 Issue。

評估

難度
5/5
預估耗時
一週以上
新手友好度
20/100
Issue 類型
文件
描述清晰度
需要釐清
活躍度
停滯
技術堆疊
cpp, python

研究方向

首先查看 pull request #107 和 #138,以及此 issue 中的六則留言,以了解所要求的決策和任何疑慮。當維護者提供明確的「是/否」決定,或提供關於應如何推進這些變更的書面指引時,此 issue 即完成。

由索引模型根據 Issue 內容生成。

描述

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:
Screen Shot 2021-09-22 at 10 04 26 AM

主要語言
C++
星號
2.2k
分支
242
平均合併
11 分鐘
30 天內合併 PR
1

貢獻指南

這個儲存庫沒有索引到貢獻指南

從這裡開始

  1. 先讀完整個 Issue,再讀專案的貢獻指南。
  2. 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
  3. Fork 儲存庫,在一個分支上完成修改。
  4. 送出 Pull Request,並在描述裡引用這個 Issue 編號。

nmwsharp/polyscope 的其他 Issue

查看 nmwsharp/polyscope 的全部 Issue

相似的 Issue

更多 C++ Issue

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。