Re: [Tools-discuss] Time in States on Datatracker

On Thu, Jun 16, 2022 at 2:44 AM Lars Eggert <lars@eggert.org> wrote:

> Hi,
>
> On 2022-6-16, at 11:39, John C Klensin <john-ietf@jck.com> wrote:
> > More broadly, would it be useful to ask that every change that
> > might result in a reduction in functionality (or in obvious
> > access to information) be announced to the community in advance
> > with an opportunity for comment rather than deployed,
> > effectively seeing if anyone screaming in agony?
>
> I think this would really slow down development of the tools. I much
> prefer an approach where we let the volunteers improve things, and if stuff
> gets inadvertently broken, it gets fixed again. (A fix for this one is
> queued up already.)
>

+1. Requiring every change to be individually cleared through the community
will have a very large impact on engineering velocity.

There are many respects in which the current tools are not ideal, and I
don't think it's a good idea to require a set of processes that reinforce
status quo bias.

-Ekr

> >  If nothing
> > else and with respect to Lars (and I generally agree with his
> > design taste), making design decisions based on "downward
> > pressure" is a little bit more top-down than the IETF is
> > supposed to operate.  That is especially problematic when the
> > pressure and decisions are invisible to the community until
> > after the fact.
>
> Just to be clear, I'm not wearing any leadership hat here. I'm a tools
> volunteer that is trying to make a tool work better.
>
> Thanks,
> Lars
>
> ___________________________________________________________
> Tools-discuss mailing list - Tools-discuss@ietf.org
> This list is for discussion, not for action requests or bug reports.
> * Report datatracker and mailarchive bugs to: datatracker-project@ietf.org
> * Report all other bugs or issues to: support@ietf.org
> List info (including how to Unsubscribe):
> https://www.ietf.org/mailman/listinfo/tools-discuss
>