Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

Application as a co-maintainer

Aperta
  • Qualcosa non va?
#742 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
15/100
Tipo di issue
Funzionalità
Chiarezza
Da chiarire
Stato di attività
Ferma
Stack tecnologico
rust
Ambito
backend-api-design

Direzione di ricerca

L’issue menziona il modulo rama::http e il crate correlato hyperium/headers, ma non indica file del repository, test o uno specifico punto di ingresso. Inizia esaminando la risposta dei maintainer e le issue aperte collegate; non esiste un’unica definizione di done finché non viene selezionata una modifica concreta dell’API o un’attività di manutenzione.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

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.

Lingua principale
Rust
Stelle
1.4k
Fork
385
Merge medio
1g 5h
PR unite (30g)
2

Preparare l'ambiente

Questo progetto non fornisce container di sviluppo, Dockerfile né guida per i contributori, quindi l'ambiente è a tuo carico: parti dal suo README e consulta la nostra guida al primo contributo per i passaggi generali.

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di hyperium/http

Tutte le issue di hyperium/http

Issue simili

Altre issue su Rust

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.