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] Should we have a RIPE archivist?
- Previous message (by thread): [ncc-services-wg] Should we have a RIPE archivist?
- Next message (by thread): [ncc-services-wg] Should we have a RIPE archivist?
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Sander Steffann
sander at steffann.nl
Sat Apr 28 17:51:50 CEST 2018
Hi, > That said, there might be some value in capturing documents and memories from the early days. [Wasn’t there some sort of history project launched a few years ago?] Many of the Old Farts will be retiring soon. Some already have. And a few, sadly, are no longer alive. It would be useful to gather that information before it’s lost or forgotten forever. I’m not sure how to best go about doing that. A full time(?) archivist on a permanent or indefinite contract seems wrong though. Would you be happier to give the NCC the task "making sure documents and memories from both current and past RIPE activities are properly archived" and leave the implementation details to them? I personally think having a dedicated person for this is an acceptable solution, but I see other do not. And maybe specifying roles instead of tasks is too much micro-management anyway :) Cheers, Sander -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 488 bytes Desc: Message signed with OpenPGP URL: </ripe/mail/archives/ncc-services-wg/attachments/20180428/96306fb2/attachment.sig>
- Previous message (by thread): [ncc-services-wg] Should we have a RIPE archivist?
- Next message (by thread): [ncc-services-wg] Should we have a RIPE archivist?
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]