Hacktoberfest 2026 : les issues que les mainteneurs ont marquées pour octobre, ouvertes et accessibles aux débutants. Parcourir les issues Hacktoberfest

Application as a co-maintainer

Ouverte
#742 0 commentaires 0 réactions 0 personnes assignées Voir sur GitHub

Personne n'a encore pris cette issue.

Évaluation

Difficulté
5/5
Temps estimé
Plus d'une semaine
Accessibilité débutants
15/100
Type d'issue
Fonctionnalité
Clarté
À clarifier
Activité
À l'abandon
Stack technique
rust

Piste de recherche

L’issue mentionne le module rama::http et le crate associé hyperium/headers, mais ne nomme aucun fichier du dépôt, test ou point d’entrée précis. Commencez par examiner la réponse des maintainers et les issues ouvertes liées ; il n’existe pas de définition of done unique tant qu’une modification concrète de l’API ou une tâche de maintenance n’a pas été sélectionnée.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

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.

Langage dominant
Rust
Étoiles
1.4k
Forks
385
Merge moyen
1 j 5 h
PR mergées (30 j)
2

Préparer son environnement

Ce projet ne fournit ni conteneur de développement, ni Dockerfile, ni guide de contribution : l'installation est à votre charge. Commencez par son README, et consultez notre guide de la première contribution pour les étapes générales.

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de hyperium/http

Toutes les issues de hyperium/http

Issues similaires

Plus d'issues Rust

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.