|
I see this as a negative comment against IETF processes in general. IETF leadership cares about community response, where “community” reflects the whole set of people who have been active in doing IETF relevant work. What should matter most is the extent to which some behaviors may interfere with getting the IETF’s collective job done. Actively discouraging people from participating can be one such “interfering” behavior. However, on one side you have shown a tendency to feel “squashed” as a result of (possibly terse) responses that criticize a technical idea, while – on the other side – you may have people who are actually trying to help steer a participant
in a possibly better direction, who feel “squashed” because of the criticism they get as a result of making the effort. Both sides are bound to feel some degree of “interference” in their efforts to get the job done. Obviously balance is required. And a critical part of achieving this balance is to not look for a “personal attack” in any exchange that
might simply be the result of someone trying to help. Also, read your mail before you hit send in an attempt to “filter” out anything that might be seen as a personal, rather than a technical, comment. Just my thoughts… From: ietf <ietf-bounces@xxxxxxxx> On Behalf Of
Stan Kalisch On Mon, Mar 25, 2019, at 5:00 PM, Keith Moore wrote:
They do, but what is significant is the common, shared subset of those ideas within a community. That subset alone can significantly determine who is part of a community, and who is not. Thanks, Stan |
