Re: RFC Editor model

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Wed, Jun 26, 2019 at 03:45:59PM -0600, Sarah Banks wrote:
> Michael,
> 	Please see inline. I’ve snipped, because scrolling pages annoys me. :)
> 
> Thanks
> Sarah
> > 
> > 
> [...]
> > 2) Because of this the RSOC decided we needed to recompete the RSE
> > and used the excuse of needing to tweek the RFP process - said
> > process that could have been delayed for almost 3 years but was
> > considered by the RSOC to be of critical importantance (why?) that
> > the RSE just did it now.
> 
> SB// I’m trying to understand why the RSOC is being belittled like
> this. Help me understand. We don’t need an excuse. The IAB doesn't
> need an excuse to reseat the RSOC - we serve at their pleasure. The
> contract doesn’t need “an excuse” to be extended, or not, for up to 2
> additional times after being awarded; there’s nothing in 6635 that
> states we need a reason. One would assume there’d be one; one might
> even hope there’d be one, and one should certainly expect a
> conversation about it. [...]

That seems to be the rub.  You didn't need a reason so you didn't think
you had to finesse the matter.  Now you have to find an RSE in a hurry
and you've upset a large part of the community.  Indeed, we're talking
about revamping the process significantly as a result of this incident.

Remember, that you *may* take some action X doesn't mean it's advisable
to do so.

Also, one does not take some business action X for no reason.  You might
want to keep your reasons private, understandably (e.g., your reasons
might hurt Heather's reputation and/or yours?), but that's so difficult
to do in an open organization answerable to its volunteer participants..
that it's difficult to understand why you'd even try.

Now, why would you tell a contractor that soon that you'll renew now but
not again later if not precisely because you want the contractor to not
re-up now?  Either RSOC lacks business acumen or RSOC thought no one
would notice that something went askew.  The latter case would be rather
surprising for such an open organization.

I don't think there's any way to avoid concluding that RSOC screwed up...

We could stop crying over spilled milk, but RSOC and IAB owning up to
their fault might help get the community there.

(It's also possible that the community shouldn't second guess RSOC, but
I think the community would not agree with that, clearly.)

Nico
-- 





[Index of Archives]     [IETF Annoucements]     [IETF]     [IP Storage]     [Yosemite News]     [Linux SCTP]     [Linux Newbies]     [Mhonarc]     [Fedora Users]

  Powered by Linux