| 23 | |
| 24 | === 3.2 Tying up loose ends, part 1: the Mini Note Well Summary (Barry) === |
| 25 | |
| 26 | We seem to have gotten consensus on this: |
| 27 | http://trac.tools.ietf.org/group/iesg/trac/wiki/DraftNoteWellSummary |
| 28 | |
| 29 | What's the next step toward using this by Atlanta? |
| 30 | |
| 31 | === 3.3 Tying up loose ends, part 2: The draft boilerplate change (Barry) === |
| 32 | |
| 33 | We talked about having a specific boilerplate for cases where we are |
| 34 | publishing something (such as documentation of a vendor-specific |
| 35 | mechanism) where the community has consensus to publish, but consensus |
| 36 | on the content doesn't make sense. We seem to have consensus on this: |
| 37 | http://trac.tools.ietf.org/group/iesg/trac/wiki/DraftBoilerplateChange |
| 38 | |
| 39 | What do we have to do next with this? |
| 40 | |
| 41 | === 3.4 Tying up loose ends, part 3: The document shepherd writeup revision (Barry) === |
| 42 | |
| 43 | I've gotten and posted feedback on the current proposal for a new shepherd writeup format: |
| 44 | http://tools.ietf.org/group/iesg/trac/wiki/DraftShepherdWriteupWgAlternate |
| 45 | |
| 46 | The feedback is at least somewhat favourable, and I've asked a couple of shepherds to try it out. The first writeup has come in (to Pete), but we haven't acted on it yet. It looks good, at least as I see it; it's what I had in mind, at least. |
| 47 | |
| 48 | Is it time to try it out with a few more shepherds? Are other ADs willing to give it a shot? Are we willing to change the ballot text correspondingly, at least for the trial cases? |