[mat-wg] MAT WG as an advisory body for RIPE NCC tools

On 2019-10-17 17:27, Brian Trammell (RIPE) wrote:
> 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)

Hi Brian,

Speaking from the NCC's perspective: I believe this could be a good
idea. The devil, as always, is in the details :-)

For example, in the RIPE Atlas context, we're consciously encouraging
people who we talk to the float their ideas of new features, behaviour,
direction, ... on the RIPE Atlas mailing list, because that's mostly
where the relevant users are. So arguably, for RIPE Atlas at least, we
already have the "two way channel" you mention. Your proposal would
divert some of that focus into this WG.

RIPEstat does not have its own mailing list, but it does make use of
third party tools (usersnap and feature upvote) to collect and
prioritise bugs and feature requests.

The way I think about it this working group includes, by its very
definition, interested parties in Internet measurements -- including and
beyond the tools the NCC provides. I'm very grateful to all the
discussions seen, ideas presented etc. in this area and consider this
very useful to better understand what the community needs are, and where
our tools can provide the most benefits to RIPE NCC members and others.
This is in addition to the benefits of having the discussion about
specific tools on their respective mailing lists (if applicable).

Regards,
Robert