TODO - nicholasdavidson/pybit GitHub Wiki

BitConf 2013 :)

First off:

  • Get some food (BBQ?)
  • Discuss future and compare with competitors.

Immediate Tasks:

  • Remove TCL-isms done
  • Move packaging to another repo (codehelp/pybit-debian). Will allow us to discuss making it self-hosting - could be very nice. done
  • Make bottle/bootstrap a remote in git, rather then copying. not relevant

Review:

  • Fixing crappy javascript mess.
  • Review correctness of daemon/logger implementation
  • Review usage of dbconfig-common - moved to Debian packaging
  • Review open bugs
    • Ticket: Pybit Watcher should support multiple repository and watch paths
    • Ticket: Clients should support multiple dists.
    • Ticket: Add weighting to build environment
  • Review PEP8 compliance

Discussions:

  • Discuss making VMs - not too hard if we pool knowlege, we all did it before at TCL.
  • Discuss making setup easier - documentation. - latter easy, former, not so much, but VMs could mitigate
  • Discuss if we want to support packaging for pip type install, as well as debian.
  • Discuss python3 compatibility - Problems more like with 3rd party stuff than our own
  • Discuss git and/or redhat support
    • Drop Squeeze support? - confirmed.
    • The only debian-specific bit in web is 1 use of dpkg --compare-versions.
    • If these happened, could be a big win for me.
  • Discuss django etc
    • Wins as huge db.py can go away
      • Easy support for other DBs
      • Reduce boilerplate
      • Easy support for auth
      • Not as easy to do APIs.
      • Serialisation?
  • Discuss replacement of Rabbit with 0MQ - SaltStack?
  • Discuss not using apache as webserver - something like GUnicorn behind nginx should be a supported scenario.
  • Discuss JSON hook to allow users to specify a pre-built chroot of the right architecture to match the build environment requested.

New Features:

  • Remote logging from buildclients over HTTP could be useful and easyish
  • Web interface on the buildclients - themselves? - Saves using apache to serve the logs like we used to..... - easyish
  • Provisioning clients - sending requests to spin up chroots, get health etc... - Ties into possible webUI on client.
  • Mobile app?

Testing:

  • See if web-side is capable of running on other likely platforms i.e. RedHat.

Basically, discuss all areas, take the beneficial wins, ticket, and sprint hard!