4 ms·

The above comment is a good example of non constructive ways to say no. Anybody could reject any RFC with the reasons you gave (especially with the vague “bunc

The above comment is a good example of non constructive ways to say no. Anybody could reject any RFC with the reasons you gave (especially with the vague “bunch of other issues” catch all). So I’d say, yes, you can say no, if there’s specific, written down, largely agreed upon principles or goals. The thing is, when a no is in reference to specific principles and goals, it’s no longer a no. It’s a “yes if it fits with XYZ. Can you explain how this works because I can’t see it.” If it’s a no in reference to vague reasons, it’s just gate-keeping. I suppose I can say yes to gate keeping if you can find a way to be encouraging to the RFC author and value the efforts and thinking that went into it. Otherwise gate keeping breeds frustrated complacency.

ilyt 4y ago
>If it’s a no in reference to vague reasons, it’s just gate-keeping. What if it is yes with vague reasons? Why "yes" should be easier than "no" ? It's potentially extra work and extra code to manage. If something is vague in it's usefulness enough that it doesn't get yes with good reasons it should probably go back to drawing board
- srcreigh 4y ago
  "This proposal is vague in its usefulness" is the same thing as not adhering to specific, written, agreed upon goals and principles. So you could say "yes if this becomes more specific in relation to X". However, this situation can also easily arise where the goals and principles are vague, and in that case it's ultimately means that its more of a vague reasons to say no than a vague proposal. The "it's potentially extra work and extra code to manage" is, imo, another wildcard vague reason to say no. It can be used to deny essentially any proposal anybody makes. It's Machiavellian. In a cooperative teamwork oriented environment, those things are given budgets so there can be some wiggle room for each proposal to progress.

ilyt 4y ago

>If it’s a no in reference to vague reasons, it’s just gate-keeping. What if it is yes with vague reasons? Why "yes" should be easier than "no" ? It's potentially extra work and extra code to manage. If something is vague in it's usefulness enough that it doesn't get yes with good reasons it should probably go back to drawing board

srcreigh 4y ago
"This proposal is vague in its usefulness" is the same thing as not adhering to specific, written, agreed upon goals and principles. So you could say "yes if this becomes more specific in relation to X". However, this situation can also easily arise where the goals and principles are vague, and in that case it's ultimately means that its more of a vague reasons to say no than a vague proposal. The "it's potentially extra work and extra code to manage" is, imo, another wildcard vague reason to say no. It can be used to deny essentially any proposal anybody makes. It's Machiavellian. In a cooperative teamwork oriented environment, those things are given budgets so there can be some wiggle room for each proposal to progress.