NomCom Disbanded - No More Blog
Dear colleagues, Just a short note that the 2020 NomCom is no longer. All data on our server has been securely deleted as have all back-ups, so we are sure any personal data is suitably randomised. In March we published a comprehensive report with a lot of reference material: https://www.ripe.net/ripe/mail/archives/ripe-list/2021-March/002170.html At RIPE81 some people including Rüdiger Volk requested that we keep the NomCom Blog available and I promised to do so. It turns out that doing that safely after turning off the original server is a lot more work than expected for a lot of different reasons. Therefore I hope that nobody really insists that we do that. In case you have suggestions on this or you feel the urge to volunteer for doing this work please contact me *privately*. So long Daniel
hi daniel, out of curiosity, what is the blogware that would need to be kept alive? randy
Ghost.org Should have used wp but felt adventurous. The other major issue is getting permission from all contributors. --- Sent from a handheld device.
On 26. May 2021, at 15:50, Randy Bush <randy@psg.com> wrote:
hi daniel,
out of curiosity, what is the blogware that would need to be kept alive?
randy
On 26 May 2021, at 10:48, Randy Bush <randy@psg.com> wrote:
Ghost.org
a service, not freeware to be thrown on a vm
The blog was definitely hosted in a private, dedicated OS on private, dedicated hardware.
The other major issue is getting permission from all contributors.
yikes!
I'm also surprised that this is seen as a major issue. From memory, there were not many of us who wrote content for the blog. I won't speak for the others but I certainly don't believe I have (or should have) any control over what happens with my text. I think an archive of some kind might be useful for future reference. The mechanics of building an archive seems like the kind of thing the RIPE NCC is usually happy to take care of for RIPE community to me, but perhaps there are difficulties there I'm not aware of. Joe
Joe Abley wrote on 26/05/2021 15:53:
I think an archive of some kind might be useful for future reference. The mechanics of building an archive seems like the kind of thing the RIPE NCC is usually happy to take care of for RIPE community to me, but perhaps there are difficulties there I'm not aware of. The blog is already archived here:
https://web.archive.org/web/20210301124504/https://blog.ripe-nomcom.org/ Nick
Hi Nick, On 26 May 2021, at 10:57, Nick Hilliard <nick@foobar.org> wrote:
Joe Abley wrote on 26/05/2021 15:53:
I think an archive of some kind might be useful for future reference. The mechanics of building an archive seems like the kind of thing the RIPE NCC is usually happy to take care of for RIPE community to me, but perhaps there are difficulties there I'm not aware of. The blog is already archived here:
https://web.archive.org/web/20210301124504/https://blog.ripe-nomcom.org/
I am a huge fan of the archive.org <http://archive.org/> crew's work, but I think there's also some value in the RIPE community managing its own historical record and not relying solely on the good work of others. Joe
On 26 May 2021, at 16:59, Joe Abley wrote:
I am a huge fan of the archive.org <http://archive.org/> crew's work, but I think there's also some value in the RIPE community managing its own historical record and not relying solely on the good work of others.
Colleagues, RIPE traditionally maintains its history in RIPE documents, mailing list archives, meeting minutes and, more recently, recordings of meetings such as videos, presentation material and stenographic transcripts. The NomCom proceedings are all recorded in these places as they happened. Everything is also comprehensively documented in our final report. This report can already be found in the archive of this list and will be published as a RIPE document soon. In my mind the blog was never intended to be permanent. It served the purpose of an *additional* channel to engage with the community. Do we really need to keep it given all the other material that is in the traditional places? We can do that but it does not happen magically. It costs a non-trivial effort because the NomCom set up its infrastructure, including the blog, separately from anything else in order to stress the independence of the NomCom and its process and in order to be able to delete all confidential and personal data once we were finished. I believe that without explicit permission from the people whose data the blog contains we should not just keep it for much longer than originally intended. While this may sound overly formal at first glance I consider it necessary. Obtaining this permission requires an effort, not a big one but it is not free. Again, do we really need to keep this blog publicly accessible? I still have the data *of the blog only* because of the promise I made in the community plenary at RIPE 81. I would feel much better if I could delete this too. Daniel
On 27/05/2021 08:47, Daniel Karrenberg wrote:
Again, do we really need to keep this blog publicly accessible? I still have the data *of the blog only* because of the promise I made in the community plenary at RIPE 81. I would feel much better if I could delete this too.
I would say to go ahead and delete it. And given that I'm one of those most closely affected... Nigel
On 26 May 2021, at 10:57, Nick Hilliard <nick@foobar.org> wrote:
The blog is already archived here:
https://web.archive.org/web/20210301124504/https://blog.ripe-nomcom.org/
Depending on the links you follow you will get these in places. https://web.archive.org/web/2/https://blog.ripe-nomcom.org/nomcom-starts-can... "Hrm. The Wayback Machine has not archived that URL. This page is not available on the web because of server error”
Oh my! I apologise to everyone for copying this list on conversation with Randy I thought was private. As with any real screw up there are multiple causes: distraction, haste, sub-optimal UI on a mobile device and last but not least cognitive bias as I expected the private conversation I had requested in the original message. I’ll try to be more mindful the future. Daniel On 26 May 2021, at 17:54, Daniel Karrenberg wrote:
No. Freeware on own server. Docker container.
--- Sent from a handheld device.
On 26. May 2021, at 16:48, Randy Bush <randy@psg.com> wrote:
Ghost.org
a service, not freeware to be thrown on a vm
The other major issue is getting permission from all contributors.
yikes!
I thought was private.
welcome to dmarc randy --- randy@psg.com `gpg --locate-external-keys --auto-key-locate wkd randy@psg.com` signatures are back, thanks to dmarc header butchery
participants (6)
-
Daniel Karrenberg -
Fearghas Mckay -
Joe Abley -
Nick Hilliard -
Nigel Titley -
Randy Bush