APRICOT Presentation Guideline

APRICOT is a technical conference focused on operational technologies in the Asia Pacific region. In line with established Network Operator Group practices it is important that all talks are technical in nature, and NOT marketing talks. In line with All speakers must be from a technical and not primarily marketing background.

These guidelines are based on those of the North American Network Operator Group (NANOG) at http://www.nanog.org/presentations.html

If you are proposing a talk for an APRICOT conference, please keep the following in mind as you prepare your presentation.

What Makes a Good Talk?

To increase the chance that your talk will be accepted, we recommend that you:

- Highlight operational experience, i.e., present a case study.
- Identify anomalies or counter-intuitive (interesting) aspects of your experience
- Educate in your area of expertise (so the audience can learn something)
- Motivate action (so the audience goes out and does something as a result of the talk)
- Keep it interesting (so the audience stays in the room)

APRICOT attendees come from many different countries and for many English is not their first language. This needs to be kept in mind when preparing slides, and particularly when presenting.

Slide Format

• Company logos should only appear on the first and last slides of your talk. Full-page logos on cover slides are discouraged.
• Presenters/authors may retain copyright of their material, granting APIA a perpetual license at no cost to archive and redistribute the material. Unobtrusive copyright notices may be on any or all slides of the presentation.
• A plain white background is recommended.
• A PDF is recommended rather than the source file for the slides, e.g. a Power Point file.
• Some conference rooms are very large and it can be difficult to read slides from the back. To be legible, slides must use at least 28-point fonts.

Using Configuration Examples

We recognize that configuration examples are a useful, and often necessary, means of conveying information. In order to provide the maximum benefit to the largest number of APRICOT attendees, we encourage speakers to give examples using the configuration language of more than one vendor.

Talks or tutorials that only use a single vendor for configuration examples will not be excluded on that basis, but will receive lower priority than talks that use multi-vendor configuration examples.

Note that this does not necessarily mean that each example should be replicated in multiple vendors' configuration language. APRICOT recognizes and values the contribution that specific configuration examples bring to talks and tutorials, and understands that multi-vendor configuration examples are not always possible. We ask that every effort be made to use them, though, to increase the value to the APRICOT community.