This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/ripe-list@ripe.net/
[ripe-list] RIPE NCC Community Projects Fund 2017 Recipients
- Previous message (by thread): [ripe-list] RIPE NCC Community Projects Fund 2017 Recipients
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Nigel Titley
nigel at titley.com
Wed Dec 27 12:17:28 CET 2017
On 27/12/17 10:39, Jim Reid wrote: > >> On 22 Dec 2017, at 15:39, Alistair Strachan <projectsfund at ripe.net> wrote: >> >> The RIPE NCC Community Projects Fund Selection Committee has reviewed the applications and is happy to announce that the following seven projects have be awarded funding for 2017: >> >> Congratulations: >> >> ... >> - Tajikistan K-Root DNS Mirror > > Hmmm. An anycast root server instance doesn’t seem to be in scope for the Community Projects Fund. Surely a DNS server should have been paid for from a different NCC budget which is expressly for that sort of thing? IMO it’s a bad idea to intermix support for community projects with root server operations (or other routine NCC activities). This may well set an awkward precedent. > > Suppose an NCC department overspends its budget. Could they apply to the Community Projects Fund to balance the books? > > Now OK, it’s all ultimately funded by the one pool of NCC members’ money. But even so... > > The selection committee is independent of the NCC. I guess the question should be addressed to them. Nigel
- Previous message (by thread): [ripe-list] RIPE NCC Community Projects Fund 2017 Recipients
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]