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/[email protected]/
[ncc-services-wg] New RIPE Labs Article - Building a stable future for the RIPE NCC
- Previous message (by thread): [ncc-services-wg] New RIPE Labs Article - Building a stable future for the RIPE NCC
- Next message (by thread): [ncc-services-wg] RIPE NCC Access Security Investigation Report Published
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Remco van Mook
remco.vanmook at gmail.com
Thu Apr 18 15:59:02 CEST 2024
Dear colleagues, apologies for the second email but it appears I forgot to actually add a link to the article: https://labs.ripe.net/author/remco-van-mook/building-a-stable-future-for-the-ripe-ncc/ Building a Stable Future for the RIPE NCC labs.ripe.net Kind regards Remco van Mook RIPE NCC Executive Board > On 18 Apr 2024, at 15:17, Remco van Mook <remco.vanmook at gmail.com> wrote: > > > Dear colleagues, > > I’d like to draw your attention to an article that was just published on RIPE Labs, about building a stable future for the RIPE NCC. > > As it touches on some very foundational aspects all across the various working groups and NCC membership, I thought it important to share, and I would very much like to ask everyone for their input and ideas. > > In order to not spread the discussion too much across the various mailing lists, I suggest that we use the general RIPE list (which I’ve put into the reply-to field of this email. > > I’m currently in the process of organising a BOF during RIPE 88 on this topic as well and am looking forward to a constructive discussion! > > Kind regards, > > Remco van Mook > RIPE NCC Executive Board > > -------------- next part -------------- An HTML attachment was scrubbed... URL: </ripe/mail/archives/ncc-services-wg/attachments/20240418/623dc21c/attachment-0001.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: d02c8849-0a3f-45df-95ef-9accfc53af42.jpeg Type: image/jpeg Size: 36113 bytes Desc: not available URL: </ripe/mail/archives/ncc-services-wg/attachments/20240418/623dc21c/attachment-0001.jpeg>
- Previous message (by thread): [ncc-services-wg] New RIPE Labs Article - Building a stable future for the RIPE NCC
- Next message (by thread): [ncc-services-wg] RIPE NCC Access Security Investigation Report Published
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]