On 2016-01-06 18:08:07, Peter Palfrader wrote: > Martin Zobel-Helas schrieb am Mittwoch, dem 06. Jänner 2016: > > > Hi, > > > > On Wed Jan 06, 2016 at 13:55:31 +0000, Marcin Kulisz wrote: > > > If this mirror is not intended to be used by public outside Azure I'm not > > > really convinced that it should be available under debian.org domain for simple > > > reason service is not (and probably not going to be) under DSA control. > > > > with my DSA hat on: none of the mirrors under ftp.CC.debian.org are > > under DSA control. Some of the mirrors might be administrated by > > individual members of the DSA team, but none is official under DSA > > control. Ok, in this case it was a miss from my side. Sorry for making it harder then it really should be, but if something want to be under debian.org domain IMO should be available without location restrictions such as available only from ex Azure, AWS or North Korea. > Yes, but this isn't one of those. > > Hosters usually have their http://mirror.$hoster/, such as > http://mirror.nl.leaseweb.net/debian/. > > I do not see why this should be under .debian.org if it's not intended > for the general public. Having something under mirrors.azure or > whatever this is called seems perfectly reasonable. My thoughts exactly. On 2016-01-06 20:12:00, Donald Norwood wrote: > We did talk briefly about naming conventions for cloud infrastructure, > so this is a nice tie into that conversation, which hopefully we can > have now. Regarding this particular cloud instance, I also do not see > the point in having it under d.o. if it is not for external connections. > Perhaps once an internal consensus is reached on the naming convention > this cloud instance could follow suit. > > As we now have "debian.mirrors.debian.org", I would think about > "$vendor.mirrors.debian.org" and, if they really want to mirror debug, > also "debug.$vendor.mirrors.debian.org". But I'm open to suggestions. > > Separately I do like idea of $vendor.mirror.d.o. as it shows who the > sponsor is and subtly indicates the mirror is not a Debian > owned/operated mirror. A few months back on d-d was a discussion about usage of debian.org and debian.net in relation to official and none official Debian services. I think it's still valid in this case, especially in case where Debian users can't access it from world outside to Azure, so how something can be 'branded' as Debian and have restricted access depending on your location? snip -- |_|0|_| | |_|_|0| "Heghlu'Meh QaQ jajVam" | |0|0|0| -------- kuLa --------- | gpg --keyserver pgp.mit.edu --recv-keys 0x58C338B3 3DF1 A4DF C732 4688 38BC F121 6869 30DD 58C3 38B3
Attachment:
signature.asc
Description: PGP signature