Re: [Iasa20] Call for volunteers: IASA 2.0 design team

Howdy,

On Tue, May 9, 2017 at 1:56 PM, Alissa Cooper <alissa@cooperw.in> wrote:

> I think the community is at a point in the IASA 2.0 discussions where we
> are ready to form a design team to start evaluating options for the path
> forward. We have a good articulation of the set of problems we are facing
> in draft-hall-iasa20-workshops-report and draft-daigle-iasa-retrospective.
> We have some sense of the outcome properties that people are looking for
> here, based on list discussion. So I'd like to task a design team to go
> examine potential solutions to the problem set that fit the outcome
> properties, and come back to the community with recommended solutions.

So, I find it somewhat surprising that we are the "form a design team"
phase, as I would have assumed that the next phase was "charter a working
group".  You have an active mailing list, a couple of good -00 drafts, and
a problem to solve.  Writing a charter and going to the community with the
plan and timelines and getting confirmation seems like the next step.

Refreshing my memory with the minutes of the meeting:

https://www.ietf.org/proceedings/98/minutes/minutes-98-iasa20-00.txt

There was no charter discussed and no workplan set out.

> The scope of the solutions to be explored would include:
>
> - Structural and organizational changes, both externally (with ISOC and
> contractors) and internally (within the IAOC and subcommittees)
> - Changes to personnel resources, both volunteer and paid
> - Transparency changes
>
> For now, changes to the funding model would be out of scope to the extent
> they fall outside the categories above, although the design team's work
> should be informed by the prior discussion of funding challenges. The IAOC
> sponsorship committee is currently in the process of getting off the ground
> and I think it would make sense to have some of that discussion start there
> before merging it back in with the administrative discussion. And I think
> the administrative problems are articulated well enough for a team to get
> going with that focus.
>

My hope is that the design team would have something (even an interim
> something) ready for community discussion around the time frame of IETF 99.
> From there we can figure out what a logical next step would be.
>
> Perhaps I'm totally misunderstanding this.  Is this design team is
preparing a 2nd BoF or a charter for consideration at IETF 99? If so, I am
very supportive.

If the design team, to be picked by the middle of next week, is to be
working on proposals for substantive changes to the IETF structure based on
where the IASA conversations are right now, I think you have to define how
the community consideration of those will take place.  A plenary discussion
at IETF 99 will take us from 77 people at the last IASA 2.0 meeting to a
room of many hundreds; more structure than that seems to me necessary.

If you’re interested in volunteering and willing to dedicate time to this
> work over the next several months, please send me email off-list by May 17,
> 2017 and I’ll sort out the team composition.
>
>
When do you intend to make the design team membership public?

regards,

Ted

> Thanks,
> Alissa
> _______________________________________________
> iasa20 mailing list
> iasa20@ietf.org
> https://www.ietf.org/mailman/listinfo/iasa20
>