Summary

  • AfNOG’s dated 2007 call asked contributors to state the time allocation they requested.
  • The page did not publish how a requested duration related to programme planning.

A duration field turns agenda time into a contributor input. AfNOG’s 2007 call asked for the proposed title and nature of a proposal, then requested the time allocation sought by the contributor.

The page also gave duration guidance elsewhere for presentations, panels and tutorials. Those are the documented facts. It did not explain on the cited page who assessed a requested time, whether it could change, or how any schedule-driven adjustment would be communicated. It reported no actual request, decision or outcome.

As governance analysis, the field makes a desired duration visible while leaving its relationship to finite programme time unstated. The source does not show that any request was shortened, negotiated, prioritised or rejected.

A future call could keep the field while publishing available slot bands and a short communication rule for schedule-driven changes. A separate prompt could ask which elements must be preserved if less time is available. These are prospective design options, not claims about 2007.

This dated page is not evidence of current AfNOG policy. Its narrow lesson is that a request field becomes easier to interpret when the possible next steps are visible.

Sources