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 ]
Jim Reid
jim at rfc1035.com
Sat Apr 28 19:19:50 CEST 2018
> On 28 Apr 2018, at 16:51, Sander Steffann <sander at steffann.nl> wrote: > > 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? Probably - though the task would need to be more clearly scoped: milestones, deliverables, metrics, reporting/review/end dates, etc. When proposals for new projects are open-ended and/or vaguely defined, they activities tend to drift or accumulate cruft. Or morph into something different because the expectations and requirements were not clear enough at the outset. That also makes it hard to declare victory or decide when something has outlived its usefulness. IMO we should avoid getting into those sorts of situations. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 528 bytes Desc: Message signed with OpenPGP URL: </ripe/mail/archives/ncc-services-wg/attachments/20180428/a70ff766/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 ]