protein over pablum
< rant > [ trying to clarify what i meant at the mic; but probably just digging a deeper hole ] i would not be up at 2am if i did not care about the CoC, DB, ... like you, i think these things are important. and the folk working on them are really good and nice and also care a lot (but i am already married). and they are working hard and really trying and usually succeeding in getting stuff done. so please tell us about it! the content, not the form/process. yes, i could join your mailing list, read your documents (i often do), ... but i have a life and two full-time jobs, and come to the plenary, WG, or whatever at 2am to get a high content summary. i stay up to 3am for content, not form. we are becoming humorless and fear based. i am thinking of making a generic Task Force Report slide deck, where it shows X meetings, Y consultations, Z surveys, and thanks for NCC support. you just put the TF's name at the top, plug in X, Y, and Z, and it's done! because i *care* about the subject, i *really* want to learn of the interesting issues that were found and how they were resolved. what issues remain? what did the TF learn that was unexpected? protein, not process. i trust you for the process, and really doubt you can make it interesting to me at 2am. yes, 42 engineers will have opinions on these; and half those opinions will be um, questionable. and some, such as this one, will be presented a bit roughly. sorry. welcome to a world filled with us funny monkeys. you did want input. and you get the big bucks for filtering and using it. but talk is cheap. how can i help TF folk to feel comfortable enough to put your content out? i just heard a svp of a massive net company ask their team and peers "what would you do if you were not afraid?" randy --- randy@psg.com `gpg --locate-external-keys --auto-key-locate wkd randy@psg.com` signatures are back, thanks to dmarc header butchery
Hi Randy, Responding on behalf of the Code of Conduct TF, the update we gave falls between the publication of our initial draft and the publication of our updated draft. The reason we did not publish an updated draft, or describe what it will say, is that it is not ready. As I stated, we plan to publish the update before July. What I can promise, is that when we publish our updated document, we will accompany it with an explanation of what changed and why. We have tried to communicate clearly and regularly as we have made progress with our work. We have used this list, RIPE meetings, and RIPE Labs. We'll work on improving our communications. Kind regards, Leo Vegoda for the Code of Conduct TF
On May 21, 2021, at 10:20 AM, Randy Bush <randy@psg.com> wrote:
< rant >
[ trying to clarify what i meant at the mic; but probably just digging a deeper hole ]
i would not be up at 2am if i did not care about the CoC, DB, ... like you, i think these things are important. and the folk working on them are really good and nice and also care a lot (but i am already married). and they are working hard and really trying and usually succeeding in getting stuff done.
so please tell us about it! the content, not the form/process. yes, i could join your mailing list, read your documents (i often do), ... but i have a life and two full-time jobs, and come to the plenary, WG, or whatever at 2am to get a high content summary.
i stay up to 3am for content, not form. we are becoming humorless and fear based. i am thinking of making a generic Task Force Report slide deck, where it shows X meetings, Y consultations, Z surveys, and thanks for NCC support. you just put the TF's name at the top, plug in X, Y, and Z, and it's done!
because i *care* about the subject, i *really* want to learn of the interesting issues that were found and how they were resolved. what issues remain? what did the TF learn that was unexpected? protein, not process. i trust you for the process, and really doubt you can make it interesting to me at 2am.
yes, 42 engineers will have opinions on these; and half those opinions will be um, questionable. and some, such as this one, will be presented a bit roughly. sorry. welcome to a world filled with us funny monkeys. you did want input. and you get the big bucks for filtering and using it.
but talk is cheap. how can i help TF folk to feel comfortable enough to put your content out?
i just heard a svp of a massive net company ask their team and peers "what would you do if you were not afraid?"
randy
--- randy@psg.com `gpg --locate-external-keys --auto-key-locate wkd randy@psg.com` signatures are back, thanks to dmarc header butchery
Dear Randy, I think Leo has already responded to most of your points. I just want to let you know that I am listening and that I am taking this seriously (we definitely don't want people to feel uncomfortable to bring up content). You are right that this is a bit of process-heavy time (with two task forces, updating the PDP and other documentation). But don't worry this won’t last forever. Kind regards, Mirjam On 21/05/2021 19:20, Randy Bush wrote:
< rant >
[ trying to clarify what i meant at the mic; but probably just digging a deeper hole ]
i would not be up at 2am if i did not care about the CoC, DB, ... like you, i think these things are important. and the folk working on them are really good and nice and also care a lot (but i am already married). and they are working hard and really trying and usually succeeding in getting stuff done.
so please tell us about it! the content, not the form/process. yes, i could join your mailing list, read your documents (i often do), ... but i have a life and two full-time jobs, and come to the plenary, WG, or whatever at 2am to get a high content summary.
i stay up to 3am for content, not form. we are becoming humorless and fear based. i am thinking of making a generic Task Force Report slide deck, where it shows X meetings, Y consultations, Z surveys, and thanks for NCC support. you just put the TF's name at the top, plug in X, Y, and Z, and it's done!
because i *care* about the subject, i *really* want to learn of the interesting issues that were found and how they were resolved. what issues remain? what did the TF learn that was unexpected? protein, not process. i trust you for the process, and really doubt you can make it interesting to me at 2am.
yes, 42 engineers will have opinions on these; and half those opinions will be um, questionable. and some, such as this one, will be presented a bit roughly. sorry. welcome to a world filled with us funny monkeys. you did want input. and you get the big bucks for filtering and using it.
but talk is cheap. how can i help TF folk to feel comfortable enough to put your content out?
i just heard a svp of a massive net company ask their team and peers "what would you do if you were not afraid?"
randy
--- randy@psg.com `gpg --locate-external-keys --auto-key-locate wkd randy@psg.com` signatures are back, thanks to dmarc header butchery
participants (3)
-
Leo Vegoda -
Mirjam Kuehne -
Randy Bush