Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

Maintenance support (offer)

未关闭
#250 1 条评论 7 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 10 天内回复

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
10/100
Issue 类型
功能
描述清晰度
需要澄清
活跃度
停滞
技术栈
c, python
领域
release

调研方向

未确定任何源文件或测试。首先查看此提议和链接的 PyOxidizer issue,然后等待维护者的指示;要视为完成,需要明确决定维护责任归属,以及由此产生的任何访问权限或仓库转移。

由索引模型根据 Issue 内容生成。

描述

This is a repost of indygreg/PyOxidizer#751 as requested.

Hi @indygreg . I read your blog. Congrats on all of the life changes. Sounds exciting.

I'd like to offer to take over maintenance for python-zstandard and possibly also PyOxidizer projects.

Like you, I've had some life changes, but my changes have given me more time to support open source projects.

My involvement would be modest - I don't have aspirations to make any major changes to the projects. Instead, I'd be focused on occasionally reviewing PRs and issues, guiding users to explore solutions, and cutting releases as needed to keep the projects from growing stale. I'd leverage the same methodology I use to maintain the hundreds of other projects I maintain in the Python ecosystem. I might step in to make important maintenance changes, but more than likely I'd direct the community to contribute most changes. I'd be careful to maintain the stability and quality that users have come to expect, directing contributors to provide well-engineered solutions with test coverage and to be responsive to unexpected regressions. And I of course would be happy to keep you on as a co-maintainer and be prepared to hand the project back should you wish to re-engage with any of them.

Let me know if that sounds at all interesting and if you have any specific stipulations you'd like to include.

Otherwise, feel free to give me ownership access of the PyPI projects and (optional but preferable) transfer the GitHub repos to the coherent-oss org, which I've formed to share maintenance on projects.

主要语言
C
星标
642
派生
118
平均合并
9 天 3 小时
30 天内合并 PR
6

环境准备

  • 没有 Dockerfile 或 Docker Compose 文件
  • 没有 Pull Request 模板
  • 阅读贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

indygreg/python-zstandard 的其他 Issue

查看 indygreg/python-zstandard 的全部 Issue

相似的 Issue

更多 C Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。