Hi Michael, > On Feb 5, 2020, at 1:14 PM, Michael Richardson <mcr@xxxxxxxxxxxx> wrote: > > > IETF Chair <chair@xxxxxxxx> wrote: >> I'd like to introduce a new volunteer team that has been created in the >> General area: the Tools Architecture and Strategy (TAS) team. > > I think it is a really good idea to organize this. Great! > I wonder if you considered just creating a WG in the general area? > What would seem to let the tools team leverage... the tools. > But, I guess you can create groups that aren't WGs based upon the links below. > >> It is not the role of the TAS team to implement, maintain, or manage >> the operation of individual tools. Those responsibilities remain with >> the IETF tools team. Once TAS team guidance documents become available, >> the IETF Tools Project Manager (currently Robert Sparks) will establish >> plans and workflows to align ongoing and future tools development with >> the guidance. > > I believe that the team will mostly produce plans, and those plans will not > be in the form of RFCs, and probably not even in the form of IDs. Right, and that’s a good reason to have a team rather than a WG. Also, for the time being it’s meant to be a fairly small group to be able to progress quickly. Many of the topics within the team’s purview don’t necessarily benefit from a consensus process, same as the tools team itself. > >> The TAS team is expected to consult widely with the IETF community, to >> draw on best practices from the software development industry and open >> source communities, and to evolve its guidance over time as practices >> change. The team's online presence resides at: > >> Datatracker page: https://datatracker.ietf.org/group/tools-arch/about/ >> Mailing list (only open to members, with a public archive): tools-arch@xxxxxxxx >> Github organization: https://github.com/ietf-team-tools-arch > > May I suggest that one of these people be designated as the liason to the > WG-chairs list? And another as the liason to the EDU-team? As with EDU, we’ve got a bunch of WG chairs in the team, so I think keeping the lines of communication open should be straightforward. Thanks, Alissa > > -- > ] Never tell me the odds! | ipv6 mesh networks [ > ] Michael Richardson, Sandelman Software Works | network architect [ > ] mcr@xxxxxxxxxxxx http://www.sandelman.ca/ | ruby on rails [ > >
