Re: [gentoo-dev] [PATCH] metadata.dtd: add gnu, nongnu remote-ids
> On Mon, 29 Aug 2022, Sam James wrote: >> I think they should be called savannah and savannah-nongnu because gnu >> isn't savannah. There are many GNU packages that are hosted elsewhere, >> e.g. gcc, gdb, glibc, or binutils. > It's a fair point and it's one I raised in #gentoo-qa, although the same > comment applies to gitlab, GitHub, and sourcehut. Exactly. How would you name the ID if only savannah.gnu.org existed (but not its nongnu sibling)? "savannah" or "gnu"? > savannah-nongnu unfortunately sounds very clunky. Thinking about it, "nongnu" is probably fine. nongnu.org even redirects to savannah.nongnu.org. Ulrich signature.asc Description: PGP signature
Re: [gentoo-dev] [PATCH] metadata.dtd: add gnu, nongnu remote-ids
> On 29 Aug 2022, at 22:42, Ulrich Mueller wrote: > >> On Mon, 29 Aug 2022, Sam James wrote: > >> Both for their respective Savannah instances: >> - https://savannah.gnu.org/ >> - https://savannah.nongnu.org/ > > I think they should be called savannah and savannah-nongnu because gnu > isn't savannah. There are many GNU packages that are hosted elsewhere, > e.g. gcc, gdb, glibc, or binutils. > It's a fair point and it's one I raised in #gentoo-qa, although the same comment applies to gitlab, GitHub, and sourcehut. savannah-nongnu unfortunately sounds very clunky. Also, I can't really imagine what else 'gnu' would actually refer to? Best, sam signature.asc Description: Message signed with OpenPGP
Re: [gentoo-dev] [PATCH] metadata.dtd: add gnu, nongnu remote-ids
> On Mon, 29 Aug 2022, Sam James wrote: > Both for their respective Savannah instances: > - https://savannah.gnu.org/ > - https://savannah.nongnu.org/ I think they should be called savannah and savannah-nongnu because gnu isn't savannah. There are many GNU packages that are hosted elsewhere, e.g. gcc, gdb, glibc, or binutils. Ulrich signature.asc Description: PGP signature
