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]/
[mat-wg] MAT WG as an advisory body for RIPE NCC tools
- Previous message (by thread): [mat-wg] New on RIPE Labs: The New RIPEstat In Other Words
- Next message (by thread): [mat-wg] MAT WG as an advisory body for RIPE NCC tools
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Brian Trammell (RIPE)
ietf+ripe at trammell.ch
Thu Oct 17 17:27:39 CEST 2019
Greetings, all, We ran out of time today to discuss the proposal I alluded to at the beginning of the meeting, so I'm taking it to the mailing list: I would propose that we make the role of MAT WG in providing information and advice to the RIPE NCC's tools teams more explicit. In this proposal, mat-wg at ripe.net mailing would be considered a primary channel for proposals for features for RIPE Atlas. These proposals would then be discussed on the list and/or during MAT WG meetings, and once the discussion on converges, the outcome passed to the RIPE NCC tools team as advice. This would turn the current process, where the tools team disseminates updates about current work and future plans, into a two way street. While I propose that this should be more explicit, I am not proposing that this be made more formal: this would not use the PDP, and would not be in any way binding on the NCC. What do you, the WG, think? Thanks, cheers, Brian (as MAT-WG co-chair)
- Previous message (by thread): [mat-wg] New on RIPE Labs: The New RIPEstat In Other Words
- Next message (by thread): [mat-wg] MAT WG as an advisory body for RIPE NCC tools
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ mat-wg Archives ]