meeting agendas

Establish project areas, then a loose priority list for tackling tasks in each area.

Initial needs

1. a project management system and tools. use a wiki for now
2. a regularly scheduled project meeting
3. a public communication medium to discuss project things

Projects on deck

This will track things that are on board as prospects for moving in to the "in progress" stage.

Projects in progress

This will track things that are actively being worked on. We will use a wiki for now.

Project areas

This will track nebulous areas that we want to work on that have not graduated to being "on deck"

• community-sourced contributions
  • metadata fixing
  • make a view that presents videos that need fixed metadata, e.g. everything with no speakers attached
  • make it easy to recruit contributors for a video to do things like subtitles?
• curated playlists: Building whatever infrastructure we need to create a "Learn Python in 5 videos" list or a "Learn Django in 5 videos" list or a "How to be a solid engineer" list. There's a lot of value to those lists. Those lists have to evolve over time as new videos come out and ways of doing things become antiquated.
• search
• reduce contribution pain
• reduce administration pain: This can be grouped in to different types of administration
  • project management administration
  • curation administration
    • make it easier to have "official admins", not just community contributors
    • make admin views that make it easier to go through different types of clean-up tasks, e.g. find all videos with no speakers, normalizing names, ...
    • make admin view experience that allows "in context" editing rather than jumping between display view and django admin view
  • OPs administration
    • avoid folkloric knowledge of how to fix things, what needs fixing, etc.
    • automate tasks to make setup deterministic. this will also avoid folkloric practice.
    • set up logging and monitoring system so that we get alerts when appropriate and so that we can have an information dashboard

Things to keep in mind

• What is it we're trying to accomplish?
• What are the requirements?
• What are the anti-requirements--things we're specifically not going to deal with?
• What's the minimum viable first version?
• What are anti-patterns to avoid?
  • going overboard with wiki gardening
  • upfront issue proliferation. avoid spending inordinate amount of time on issue bookkeeping or "gardening".
  • overkill on ops. we aren't deploying scads of services to scads of boxees.