I wanted to follow up on this while HotRFC is still on my mind.
Aaron did a fabulous job of backstage preparation, and Liz Flynn with the Secretariat and the Meetecho team provided fabulous last-minute support to make this happen, even when Aaron was moving from Boston to LA, with little or no Internet access this past weekend.
We had about 50 attendees in Meetecho, and I'd guess about 30 people in the room, which isn't a bad turnout.
We had 8 speakers, at least two of whom were first-time attendees. IIRC, four were in the room, and four were remote via Meetecho.
I'm not impartial, but I think HotRFC is one of the best things that the IESG put in place while I was on the IESG.
CoViD-19 was not kind to us - we didn't have a HotRFC from IETF 107 to IETF 111, and Aaron and Alexa did a great job of putting SOMETHING in place for IETF 112, using Gather. At IETF 113, we were back to Aaron's original format, except that we also had remote presenters this time.
I'd like for the IESG to think a bit about how the IETF can use HotRFC more effectively. Most of the work behind HotRFC has been done by people who weren't on the IESG, so I'm talking about making sure that we don't forget to think about when to schedule it, who should be hosting it, and how to publicize it - given that, the rest of HotRFC is easy.
Even making it visible to people who might not arrive early for the Hackathon or for tutorials, but would want to arrive early for HotRFC, before they make their travel arrangements would be helpful.
I haven't talked with Aaron about any of this (when he unpacks, he would likely have opinions), or with any of the presenters or participants, but they can reply here, and tell you what they think as well.
Best,
Spencer
p.s. thanks to Alia Atlas and Deborah Brungard, who helped think HotRFC up in a bar in Singapore. Always spend time in bars at IETF meetings. 😉
