[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[IETF57] coach BOF
bernard aboba's "let's make wg process better" was a good presentation.
margaret's "make wg process visible" "silence != consensus" - i agree.
brian's "review team"
question (maybe i'm dumb): what is the exact difference w/ what problem wg
is targetted to do?
---
exisitng rfc editorial guidelines - scott bradner
quality: overview and framework
a comprehensive approach to quality
ietf problem resolution processes
starting new work
the bof process: the critique
iesg overload and quality of wgs
mindset
the truth is out there, somewhere
reading list
people who have read at least three of the documents, please sit ni the first two rows
a format
strict time limit for each topic and presentation
q&a at the end
use mic
---
exisitng rfc editorial guidelines - scott bradner
how to write a high-quality standard track document
increase interoperability of independent implementations
---
wg quality plan
public document no more than 5 pages long
developed in concert with the wg charter
signed off by the ad and the wg founders
reviewed by AD
wg charter - the foundation
challenge assessment - what's in the way (reality check)
tools plan
mailign list, web site, issue tracking tools, revision control system,
document production and build environment
review plan
checkponits
required reviewer skill set
review process
reviewer recruitment
many WGs doing this informally
let's make it more widespread