This page describes how the Packaging Training Coordinators coordinate the planning of the next sessions.

General

Tips for planning new sessions

• Encourage developers to just prepare 15-20 minutes of content. It's not too much, especially with lots of questions that get asked.
• If somebody explained in a normal conversation something really well, ask them to give a session about it.

Session Ideas

• Packaging/Training/Suggestions

• Development Q&A sessions (easy to do, make sure you invite folks from IRC to help out.)

• Code Review session.
• Adhoc Sessions (come with your problem and a developer will help you sort it out)

• Get questions from the Packaging forums

• Investigate "Beginner's Programming Challenge" ##These have primarily been focused on actual programming, not packaging (as creativity and trying out new languages is a big part of it. I'm not sure how much we could do with this.

Additional ideas

• Should presenters give "homework"?
• Ask presenters to let you know if their session needs some kind of preparation.

Announce

• Update Packaging/Training

• Update MOTU/Headers/NextPackagingTraining

• Ensure session is on the calendar (contact nhandler or someone in #ubuntu-classroom-backstage if you don't have access)

• Send mail to ubuntu-motu@lists.ubuntu.com

• Blog at http://ubuntuclassroom.wordpress.com/ (contact nhandler or someone in #ubuntu-classroom-backstage if you don't have access)

• Post at http://www.facebook.com/pages/Ubuntu-Development/141173545934275

• Announce on #ubuntu, #ubuntu-bugs, #ubuntu-devel, #ubuntu-motu (and elsewhere) a few minutes before we start.

• Get on Packaging forums.

• Get on development testing forum (current).

Afterwards

• Add log to Packaging/Training/Logs.

• Update Packaging/Training

• Update MOTU/Headers/NextPackagingTraining

Go back to Packaging.
CategoryPackaging