Distinguishing Long-Term Roles from Ad-Hoc Delegated Tasks

[dhruvdhody]

In the proposal, long-term responsibilities typically assigned during the March meeting (such as liaisons to the IESG, NomCom, etc.) are grouped together with ad-hoc delegated tasks that arise between meetings. I’m wondering if we should keep these long-term roles separate from short-term, ad-hoc activities—like planning a specific workshop or program committee—that we initiate and wrap up as needed. Thoughts?

[tfpauly]

That's a good point. I think that we should still have the long term roles we sign up for be at the start of the yearly cycle.

Performing those roles can and should be something that is considered a responsibility between meetings--being a liaison coordinator is a task that can take up the slot for what an IAB member does between meetings.

However, some of the roles we take on aren't always as active. NomCom liaison is much more active in half of the year. Also, roles like liaison coordination may be more busy than other times.

Note that IAB members are very free to take on multiple responsibilities, but we want each member to have at least one.

Essentially, the logic is that if you are doing a longer term role like IESG liaison and want to have that be what you do between meetings, that's okay. But if you're not actively doing work for such a role between meetings, it would be good to also take on something else.