Skip to content
This repository has been archived by the owner on Nov 18, 2021. It is now read-only.

mtg 2016 09 09

Jump to bottom
ghwood edited this page Sep 9, 2016 · 1 revision

ARTICIPANTS

Alexa Morris Russ Housley Ray Pelletier Robert Sparks Greg Wood ACTION ITEMS

Add Henrik to the regular group (done) send list of CRC members to the web team review (done) Greg and Alexa will make a plan for getting Secretariat actively using Wagtail Greg will develop and share a more detailed plan on the community rollout, including how CRC and audience panel input will inform acceptance decision NOTES

www.ietf.org website revamp update 2016-08-26

  1. handover (Wagtail installed on AMS-controlled server) . update applied to improve Wagtail-Datatracker connection performance

  2. confirm data and functionality . working through Wagtail functionality bugs (tracking on https://torchbox.codebasehq.com)

  3. acceptance

Get community review/input before acceptance

. initial acceptance checklist built based on SOW https://docs.google.com/spreadsheets/d/1FkVVXz6y8GigYmfOrx3Y_sc0SMmcHjY3bxNb56iDWpM/edit#gid=0

next steps . confirm acceptance checklist (add who is the individual responsible for each) . confirm appropriate individuals to indicate acceptance (and process/groups required) include output from community testing

figure out how that is done and who does it TMC is ultimate acceptance based on recommendation from the web team subgroup . recommendation includes output from community testing work . Joe?

TMC will indicate to the Chair that the site is ready.

IETF Chair (Jari) is the ultimate authority

** Greg has action item to detail CRC/audience panel input and role

  1. content transition and maintenance . initial content move and documentation complete . engaged contractor (@ChrisDart) to continue transition - added to www.ietf.org on Github/ietf

next steps . complete content transition . finish documentation . confirm editorial flow/approval process . get Secretariat trained and starting to use Wagtail

waiting on . confirmation of data and functionality to complete 5) URL continuity . not begun

next steps . confirm URL continuity list . explore script-based continuity checks

waiting on . completion of content transition
6) community rollout . timeline updated https://docs.google.com/spreadsheets/d/1ctMX2Fu9l5IL8PGfOBofzGGBUmK6Xc0CH2padpdzBqU/edit#gid=0

next steps
. continue working timeline for Wagtail functionality and content transition

waiting on . review of this note by core group 7) production cutover . not started

next steps . URL continuity . develop a script to check as soon as cutover happens

waiting on . completion of community rollout 8) Other issues

follow up development/evolution (for 2017)

Clone this wiki locally