Proposal to relocate repo / org

Aperta
  • Qualcosa non va?
#3,326 4 commenti 39 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
1-2 giorni
Idoneità per principianti
8/100
Tipo di issue
Refactoring
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
csharp, redis
Ambito
backend

Direzione di ricerca

This is a governance proposal to move the StackExchange.Redis repository to the seredis GitHub organization, not a code change, and the payload names no files, tests or entry points. Read the two comments and the linked seredis organization first to see what the maintainers have already agreed. Done means a maintainer decision on the move, carried out through GitHub's repository transfer, so a newcomer has no code to write here.

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

Descrizione

So: SE.Redis has been under the StackExchange org for... well, forever.

This is historically apt. The primary maintainers have not left the library - we have, however, left Stack Exchange (the company), years ago.

Effectively, the primary team are:

  • @mgravell (currently at Redis, ex Stack Exchange, ex Microsoft)
  • @NickCraver (currently at Microsoft, ex Stack Exchange)
  • @philon-msft (currently at Microsoft)

I'm not suggesting for a moment that Stack Exchange would ever do anything malign, but it does make me a little nervous re supply-chain when the library is at the whim of an org that the core maintainers don't represent.

For the same reasons, and for politics / "ownership claim" reasons, I'm also nervous of moving the library directly under the umbrella of Redis or Microsoft.

My proposal: move it under the seredis org:

  • we, the primary team, own that org
  • we, the primary team, own seredis.dev, which is where we are serving the docs etc
  • (we, the primary team, also own the NuGet keys - but this is unrelated to the GitHub repo)

As I understand it, GitHub should automatically take care of redirects if we move it.

Thoughts?

Pre-empting questions:

  • this has zero impact on anything like licensing
  • this has zero impact on support
  • mostly it just changes the URL and org-level access (the latter of which impacts nobody except the maintainers)
  • no, there is no drama or background story underpinning this suggested move - just "an abundance of caution"
Lingua principale
C#
Stelle
6.2k
Fork
1.6k
Merge medio
9h 42m
PR unite (30g)
51

Preparare l'ambiente

Apri in Codespaces

Avvia il container di sviluppo del progetto nel browser, con il tuo account GitHub.

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 StackExchange/StackExchange.Redis

Tutte le issue di StackExchange/StackExchange.Redis

Issue simili

Altre issue su C#

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.