Proposal to relocate repo / org

Offen
  • Stimmt etwas nicht?
#3,326 4 Kommentare 39 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Maintainer antworten meist innerhalb von 1 Tag

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
4/5
Geschätzter Aufwand
1-2 Tage
Anfängerfreundlichkeit
8/100
Issue-Typ
Refactoring
Klarheit
Größtenteils klar
Aktivitätsstatus
Aktiv
Tech-Stack
csharp, redis
Bereich
backend

Rechercherichtung

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.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

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"
Vorherrschende Sprache
C#
Sterne
6.2k
Forks
1.6k
Ø Merge
9 Std. 42 Min.
Gemergte PRs (30 T.)
51

Entwicklungsumgebung

In Codespaces öffnen

Startet den Dev-Container des Projekts im Browser, mit Ihrem eigenen GitHub-Konto.

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus StackExchange/StackExchange.Redis

Alle Issues in StackExchange/StackExchange.Redis

Ähnliche Issues

Weitere Issues zu C#

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.