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

Proposal: invite contributors to the LibreSign organization after their first merged PR

Aperta
  • Qualcosa non va?
#8,360 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
35/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Ambito
documentation

Direzione di ricerca

Inizia con la proposta e le relative domande di consultazione nell’issue #8360, quindi esamina le reazioni e qualsiasi discussione prima della scadenza del 25 settembre 2026. Il lavoro sarà considerato completato quando i maintainer pubblicheranno il riepilogo della discussione e la decisione finale, con la policy canonica accettata documentata su docs.libresign.coop; l’automazione tecnica è esplicitamente rinviata a un issue o pull request separato.

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

Descrizione

Context

We would like to discuss a simple policy to recognize contributors and make it easier for them to feel part of the LibreSign community.

Proposal

After a human contributor has their first pull request merged in any official LibreSign repository, LibreSign would invite them to join the GitHub organization as a regular member.

Organization membership would represent participation in the community.

It would not automatically grant:

  • write or merge permissions;
  • CODEOWNERS status;
  • membership in the maintainers team;
  • repository administration permissions.

Privileged access would continue to be managed separately through teams and repository roles.

Membership can also make it easier to grant specific responsibilities later, such as participating in reviewer teams or receiving repository permissions, when appropriate. These permissions would still require a separate decision and would not be granted automatically with organization membership.

Bots and automated accounts would be excluded.

Implementation

If accepted, this should be implemented once for the organization, not independently in every repository.

The automation should:

PR merged
   ↓
human contributor?
   ↓
already a member or has an active pending invitation?
   ↓
invite as organization member

The implementation should follow least privilege and avoid distributing powerful credentials across repositories.

The technical implementation should be handled in a separate issue or pull request after this policy is accepted.

Documentation

If accepted, the canonical policy should be documented on docs.libresign.coop.
Repository CONTRIBUTING.md files should remain useful as entry points, but organization-wide contributor and governance policies should link to the canonical documentation instead of being duplicated across repositories.

Community consultation

Please use reactions on this issue:

  • 👍 if you support the proposal;
  • 👎 if you do not support it.

If you disagree with part of the proposal, see a risk, or prefer another approach, please leave a comment explaining why.

Reactions will help us understand community sentiment, but this is not intended to be a simple majority vote. Important technical, security, governance, and maintainability concerns should also be considered.

This consultation will remain open until September 25, 2026.

After that period, maintainers should publish a short summary of the discussion and the final decision.

Questions

We would especially like feedback on:

  1. Is one merged pull request a good threshold for organization membership?
  2. Should membership represent community participation while maintainer permissions remain separate?
  3. Should this apply to every official LibreSign repository?
  4. Should this policy and related contributor documentation live primarily on docs.libresign.coop?
Lingua principale
PHP
Stelle
818
Fork
146
Merge medio
7h 38m
PR unite (30g)
490

Preparare l'ambiente

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 LibreSign/libresign

Tutte le issue di LibreSign/libresign

Issue simili

Altre issue su PHP

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.