Ted Lemon <mellon@xxxxxxxxx> wrote:
> Unfortunately I think that in order to do this job effectively, better
> tooling is required. Right now we have very poor conflict detection tooling,
> which essentially only works for WG chairs. I had a little brainstorm about
It's only visible to WG chairs and ADs, but actually can be applied to
additional people if we can figure out who is authorized to add those people.
> tooling prior to the last IETF, when I had a slot with four sessions in it I
> wanted to attend, but unfortunately didn’t have the energy to actually lay
> down any code. I think we would also need even shorter slots, and more of
> them, to make this work. But for that to work, we’d need to get disciplined
> about how we use time.
I have been pushing for more short slots at the beginning of the week, which
would have full conflict detection. And then a much more relaxed Wed/Thur.
in which bigger slots could be allocated, but with much less promise of no conflicts.
> This means that WG chairs need to say “no” a lot more
> than they currently do to presentations that aren’t ready for
> discussion.
I agree completely.
> While I understand the tendency to get triggered by any change to the status
> quo, I actually support the IESG in trying to work this issue, because it’s
> an issue that won’t go away as long as we have more working groups than time.
> I served on an IESG where we discussed this, but took no action, and that was
> quite a few years ago. It’s high time that some creativity was applied to the
> problem.
> I think our time would be better spent trying to figure out how to make the
> IETF function under its present workload than requesting a return to the
> status quo ante, which, quite frankly, still had a _lot_ of conflicts, and
> was in no way satisfactory.
What I see is that some conflicts were resolved in favour of some areas,
while other cross-area people were regularly having difficulties. I find
that I have about the same conflicts as before.
--
Michael Richardson <mcr+IETF@xxxxxxxxxxxx>, Sandelman Software Works
-= IPv6 IoT consulting =-
Attachment:
signature.asc
Description: PGP signature
