Upstreaming of GNU tools patches.
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 5/5
- Tiempo estimado
- Más de una semana
- Aptitud para principiantes
- 10/100
- Tipo de issue
- Nueva funcionalidad
- Claridad
- Necesita aclaración
- Estado de actividad
- Estancado
- Área
- build-system, compilers
Línea de trabajo
No files, tests, or entry points are named. Start by reviewing the GCC and binutils patch provenance and the contributor checklist in the issue; completion depends on the remaining contributors choosing one of the stated copyright responses and the patches being accepted upstream.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
I'd like to attempt to upstream the patches to preserve a bit of digital history, and to ensure that PSP support in the GNU toolchain is always up-to-date (I will take up maintainership of the PSP specifics in the GNU toolchain).
I see there were some efforts to upstream the psptoolchain patches, but they hit a roadblock because of no one trying to get a assignment to copyright FSF or public domain.
In order for the patches to be upstreamed there are some legal prerequisites. Please don't hesitate to ask if you have any queries.
Would you be willing to assign the copyright to the Free Software Foundation or sign a copyright disclaimer to put this change in the public domain, so that it could be integrated into the patches' respective package? (This means if you contributed to the GCC patch then you release your contributions into the public domain or assign copyright to the FSF, same for the binutils patch etc).
Below is a list of the contributors I have found who would need to agree to the terms in order to make this a reality.
GitHub Contributors:
- @Bracket-
- @elsonLee
- @SopaXorzTaker
- @WinterMute
- @himanshugoel2797
- @davidgfnet
- @dogo
- @FTPiano
- @xantares
- @n00neimp0rtant (Scott Marnik)
- @caffinatedmonkey
- @SamRH
- @artart78
- @uppfinnarn
- @take-cheeze
- @libcg
- @John-K
- @ooPo
- @igetgames (Mrbrown)
- @Lukaszdk
- @nem-arch
Original ps2dev contributors:
- Pixel
Reply with either:
I assign copyright to the Free Software Foundation of all my contributions to the psptoolchain patches.
I release my contributions to the psptoolchain patches change into the public domain.
No, I don't want this. (With a reason, preferably.)
- Lenguaje dominante
- Shell
- Estrellas
- 409
- Forks
- 126
- Métricas de merge de PR
- Sin PR fusionados en 30 d
Preparar el entorno
- Incluye un Dockerfile o un archivo de Docker Compose
- Sin plantilla de pull request
- Sin guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de pspdev/psptoolchain
-
LicenseAbierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 35/100
pspdev/psptoolchain#103 · 5 comentarios ·
Todos los issues de pspdev/psptoolchain
Issues similares
-
enhancement needs:sonnet ready-for-agent
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
oracle/vagrant-projects#594 ·
-
package-update
Dificultad 2/5 1-3 horas Aptitud para principiantes 65/100
oSoWoSo/oco#889 · 2 comentarios ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 76/100
fish-shell/fish-shell#13084 · 1 comentario ·
Los mantenedores suelen responder en 2 días
-
good first issue priority:low type:bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 82/100
crazy-goat/fdb-php#182 ·
Los mantenedores suelen responder en 1 día