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

skill: requirement levels (RFC 2119), and settle its name

Aperta
#6 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
3/5
Tempo stimato
1-2 giorni
Idoneità per principianti
56/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Tranquilla
Stack tecnologico
javascript
Ambito
documentation

Direzione di ricerca

Read the existing skill and spec section 3.3, then check the RFC 2119 and RFC 8174 references to verify the stated constraints. Create the skill guidance without reproducing RFC text, ensure every matrix row is marked E, and make the no-digest rationale explicit. Resolve the skill name among the listed candidates; completion means all three acceptance checks are met.

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

Descrizione

new skill

A skill for MUST, SHOULD, and MAY in specifications, per RFC 2119 and RFC 8174.

This one breaks the doctrine, deliberately

The IETF Trust Legal Provisions permit copying an RFC whole and unmodified, and permit translation. They do not license modification outside the IETF Standards Process. Our doctrine requires a digest in our own words, and a source that forbids derivative works cannot have one.

So this skill ships no digest. It ships our applied guidance plus a pointer, and it cites RFC 2119 for the definitions rather than restating them. That is what the specifications using these keywords already do.

Every row in its matrix is therefore an E row, because the guidance is ours and not the RFC.s. See spec section 3.3.

The name is unsettled

normative-keywords is jargon. It describes the thing correctly and communicates nothing to someone who has not already met the term. Candidates:

  • requirement-levels — what the RFC itself calls them.
  • must-should-may — names the actual words, and is searchable by someone who does not know the jargon.
  • normative-keywords — the status quo.

Opinions welcome. The name is load bearing, because it is what an agent matches against when deciding whether to load the skill.

Acceptance

  • No RFC text is reproduced.
  • Every row is an E row.
  • The skill explains why it carries no digest, so the exception is visible rather than looking like an oversight.
Lingua principale
JavaScript
Stelle
2
Fork
2
Merge medio
10g 9h
PR unite (30g)
2

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 rookslog/stylewright

Tutte le issue di rookslog/stylewright

Issue simili

Altre issue su JavaScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.