Proposal to relocate repo / org

Abierto
  • ¿Algo no está bien?
#3,326 4 comentarios 39 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
1-2 días
Aptitud para principiantes
8/100
Tipo de issue
Refactorización
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
csharp, redis
Área
backend

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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"
Lenguaje dominante
C#
Estrellas
6.2k
Forks
1.6k
Merge medio
9 h 42 min
PR fusionados (30 d)
51

Preparar el entorno

Abrir en Codespaces

Inicia el contenedor de desarrollo del proyecto en tu navegador, con tu propia cuenta de GitHub.

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de StackExchange/StackExchange.Redis

Todos los issues de StackExchange/StackExchange.Redis

Issues similares

Más issues de C#

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.