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-chair-discuss@ripe.net/
[ripe-chair-discuss] Status of RIPE Chair discussion?
- Previous message (by thread): [ripe-chair-discuss] Status of RIPE Chair discussion?
- Next message (by thread): [ripe-chair-discuss] Status of RIPE Chair discussion?
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Jim Reid
jim at rfc1035.com
Wed May 17 13:07:41 CEST 2017
> On 17 May 2017, at 09:51, Mirjam Kuehne <mir at ripe.net> wrote: > > Hans Petter and I are working on a RIPE Labs article ... We are planning to publish the article next week. Thanks Mirjam. Why does this need/deserve a RIPE Labs article? Is there some reason why it gets published there instead of this list? It seems wrong to be pushing material to RIPE Labs when we already have a mailing list already in place for the topic that’s under discussion. Having two or more fora discussing the same thing will lead to confusion and misunderstanding. And needlessly waste time and resources. That would be unfortunate. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 495 bytes Desc: Message signed with OpenPGP using GPGMail URL: </ripe/mail/archives/ripe-chair-discuss/attachments/20170517/c964f8f6/attachment.sig>
- Previous message (by thread): [ripe-chair-discuss] Status of RIPE Chair discussion?
- Next message (by thread): [ripe-chair-discuss] Status of RIPE Chair discussion?
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]