Application as a co-maintainer
还没有人认领这个 Issue。
评估
- 难度
- 5/5
- 预计耗时
- 一周以上
- 新手友好度
- 15/100
- Issue 类型
- 功能
- 描述清晰度
- 需要澄清
- 活跃度
- 停滞
- 技术栈
- rust
调研方向
该 issue 提到了 rama::http 模块和相关的 hyperium/headers crate，但没有指出仓库文件、测试或具体的入口点。先查看维护者的回复和链接的未关闭 issues；在选定具体的 API 变更或维护任务之前，不存在单一的完成定义。
由索引模型根据 Issue 内容生成。
描述
Hi, http is a critical piece of the prime FOSS project of my company, rama. And as such we even have it embedded and exposed it directly in the core http types crate and rama::http module: https://docs.rs/rama/latest/rama/http/index.html.
I love this as where it makes sense I do like to work within and with a wider ecosystem. However given that this crate is critical in the http part of that project and I honestly do not want to fork yet another project (unless it is needed) I would prefer to continue using this crate.
Same goes btw for other libraries of hyperium such as https://github.com/hyperium/headers. What you read here also applies for that crate.
There are on both crates a lot of open issues:
- Can I help you as a co-maintainer and start tackling some of these issues?
- I understand that you have strong opinions around RFC compliance and such, which I do respect. But would you be interested in features and escape API's so one can more easily extend this crate within their own code by building on top of a lot of what this crate has to offer. Examples are:
- Make it more easy for someone to add headers that you do not wish to add (you use a neat macro for this, but do not expose it in any way, so one would have to copy paste it)
- In the typed headers crate you often keep the options for a header very limited. E.g. the Content-Type as a random example has some options, but anything not fitting in there, you kinda are out of luck.
- and so on and so on
You are the maintainers so I would respect any answer or choice. But where there is a degree of freedom I would love to weight in as an individual and as a participant of the wider community.
I also messaged to you @seanmonstar over discord about this, but I can understand that you are a busy person with probably way to many stuff going on at all times. I fully respect and understand that. It's another reason why I gladly help you out here as a co-maintainer. I could begin by chopping of open issues and whatever else you have in mind, and I could start making new proposals once we have a process and good communication setup.
These crates are really awesome and I would be very humbled if I can help maintain and grow it.
- 主要语言
- Rust
- 星标
- 1.4k
- 派生
- 385
- 平均合并
- 2 天 4 小时
- 30 天内合并 PR
- 1
环境准备
这个项目没有提供开发容器、Dockerfile 或贡献指南，环境需要你自己搭建：先看它的 README，通用步骤见我们的新手贡献指南。
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
hyperium/http 的其他 Issue
-
难度 2/5 1-3 小时 新手友好度 68/100
-
难度 4/5 3-5 天 新手友好度 45/100
-
难度 3/5 1-2 天 新手友好度 62/100
-
难度 3/5 1-2 天 新手友好度 58/100
-
难度 3/5 1-2 天 新手友好度 62/100
相似的 Issue
-
Progress difficulty filter lists Hard before Medium可能已有人在做 @Pandamachi 今天认领。 未关闭
难度 2/5 1-3 小时 新手友好度 86/100
sysprog21/codetrial#281 · 1 条评论 ·
维护者通常 1 天内回复
-
C-bug
难度 2/5 1-3 小时 新手友好度 78/100
rust-lang/rust-analyzer#23501 ·
维护者通常 1 天内回复
-
Streamable HTTP client: a 401 or 403 with a JSON-RPC error body and no WWW-Authenticate loses its HTTP status可能已有人在做 关联的 PR 仍在进行中或已合并。 未关闭bug P2 ready for work T-security T-transport
难度 2/5 1-3 小时 新手友好度 68/100
modelcontextprotocol/rust-sdk#1339 ·
维护者通常 3 天内回复
-
scripts/gen-gallery.py:118: a ready session now reports in_progress, so SESSION_READY_OLD can go未关闭nightly-audit
难度 2/5 1-3 小时 新手友好度 84/100
antithesishq/snouty#396 ·
维护者通常 1 天内回复
-
French BIP39 wordlist starts with a UTF-8 BOM, so generated French mnemonics carry U+FEFF and derive a non-canonical seed可能已有人在做 @Kshot3000 今天认领。 未关闭
难度 1/5 1 小时以内 新手友好度 91/100
ergoplatform/sigma-rust#976 ·
维护者通常 1 天内回复