{thread changed to add a maybe late comment} Dear RIPE DB-WG, Hope this email finds you in good health! Please see my comments below, inline... Thanks. Le vendredi 9 juin 2023, denis walker via db-wg <db-wg@ripe.net> a écrit :
Hi Randy
That would be fine if we had a very active and engaging community. Like we had 20 years ago.
Hi Denis, Thanks for your email, brother! No excuse! to try to bypass the reminded principle. ...imho!
But the vast vast vast majority of this community is silent on almost all database matters. The vocal people are a handful of well known members of the community,
...i suspect that it's not only an era problem; my guess is simply that it might be more a matter of natural growth of the population/community. If you check old and current stats of participation ratio, i submit that it would be *almost* influenced only by the population/community growth, with relatively nearly the same numbers of real active participants... That argument of delegitimating those who are voluntarily participating, is not convincing me... How come that those who.are participating are *blamed*? Where are, actually, the others? What's the $threshold of non-representativity? ...i would agree with a *WG's goal* tasking the DB-WG Co-chairs to find a way to have more participation than that $threshold.
whose views on many matters are also quite well known.
Are we really able to handle more various opinions? ...i mean, you know, suppose half of the accounts subscribed show up here with theirs contributions. ...i agree that it might not be what you asked for; then maybe you should work (or ask RIPE NCC) on finding a way to address the $threshold issue, when identified.
Sometimes someone raises a point and it gets little or no response. Like assigning an allocation. Often the chairs know from face to face discussions, people want this option. But there is no discussion. In situations like this I've found that a chair needs to drive the discussion.
Maybe you could (non exclusively): option#1: start with regular reports or blog articles to inform the whole community of those issues raised privately option#2: advise those, who choose to discuss public matters privately, to post it on list; in order to expect the support of part of the WG. option#3: collect allowed private comments to the Staff; for inclusion consideration into their next PIER [*].
Even if that means making an outrageous suggestion that no one will agree to, but it generates a reaction. From the following discussion we can move forward.
Also sometimes a chair needs to throw ideas out into the community to move the service forwards. The chairs talk with the NCC engineers. We often discuss ideas that no one in the community is thinking about. If the chairs don't then raise it with the community the idea can never be considered.
Not sure! imho! the Staff should have a way [1] to share their experience and recommendations regarding their implementation of the Policy Manual. They should share these information on that channel...and if it no longer exists; please ask for a reboot.
So either the chairs or the NCC engineers need to be able to put ideas into the public domain, and sometimes drive the discussion to get it started, or technically and socially the database as a product and service just stagnates.
__ [*]: PIER (Policy Implementation Experience Report) *Purpose of Policy Experience Report* < https://www.arin.net/participate/meetings/reports/ARIN_34/PDF/thursday/nobil...
<quote_page2> *Purpose of Policy Experience Report* *• Review existing policies – Ambiguous text/Inconsistencies/Gaps/Effectiveness • Identify areas where new or modified policy may be needed – Operational experience – Customer feedback • Provide feedback to community and make recommendations when appropriate * </quote_page2>
I often take on this role, as well as the devil's advocate to question what others say. I don't see it as pushing a personal agenda. I have no personal agenda. It doesn't matter to me personally if the database evolves or dies. It does matter to the industry and society. I have no employer or financial interest in how the database evolves. I can look at each issue and consider how it fits in with that old saying...for the good of the Internet.
This is one of the reasons why I've put myself forward again as a chair for another couple of years.
Thanks for your much appreciated engagement, imho! and congrates for your selection as Co-chair.
I hope in that time David can spearhead a new generation of WG chairs.
Congratulations and welcome, Co-chair David! Maybe, raising awareness of the need to participate within your generation-peers, should be considered too...dear David :-)
Then dinosaurs like myself (and others) can ascend into advisory positions instead of decision making roles.
Thanks for continuing to support the community and the DB-WG, in particular. Shalom, --sb.
Cheers Denis
On Fri, 9 Jun 2023, 15:37 Randy Bush via db-wg, <db-wg@ripe.net> wrote:
Some of my goals as a co-chair would be - To support the moderation of the mailing list and facilitate working group tasks - Promote active discussion, sending summary emails to make the content easier to follow - Perform community outreach to raise awareness of this working group and the policy process
/me likes. simple, but what a chair should be doing. leave personal agendas at the door.
randy
[...]
-- Best Regards ! __ baya.sylvain[AT cmNOG DOT cm]|<https://cmnog.cm/dokuwiki/Structure> Subscribe to Mailing List: <https://lists.cmnog.cm/mailman/listinfo/cmnog/> __ #LASAINTEBIBLE|#Romains15:33«Que LE #DIEU de #Paix soit avec vous tous! #Amen!» #MaPrière est que tu naisses de nouveau. #Chrétiennement «Comme une biche soupire après des courants d’eau, ainsi mon âme soupire après TOI, ô DIEU!»(#Psaumes42:2)