Summary

  • AfNOG’s dated 2007 call described classroom-style tutorials that might include hands-on components.
  • The page did not state what facilities or proposal disclosures supported that option.

A teaching format can create dependencies before a session begins. AfNOG’s 2007 call described tutorials as in-depth technical workshops, conducted in a classroom-style environment, that might include hands-on components.

Those are the documented facts. The source does not list equipment, software, connectivity, participant prerequisites or a fallback format. It does not identify who assessed feasibility or report how any tutorial was delivered.

As governance analysis, the optional practical component widens what a tutorial can do while making preparation relevant to both organisers and participants. A lab may depend on devices, accounts, network access or prior installation, but the source does not say that any of these were required. It reports no shortage or failed session.

A future call could retain format flexibility while asking proposers to list required equipment, software, connectivity and participant preparation. A fallback plan could make clear how the session would proceed if a dependency were unavailable. These are prospective design options, not claims about 2007.

This dated page is not evidence of current AfNOG policy. Its narrow lesson is that an optional delivery method becomes easier to coordinate when its dependencies are visible at proposal time.

Sources