Bill of Rights and Obligations

This is the Bill of Rights and Obligations setting the rules and expectations on our software development, quality and engineering.

Done

Development Tasks

For a development, configuration and/or integration task, when we say I'm Done! here's what we mean:

  • Feature is integrated in Git
  • Tests exist for this feature (unit and/or system tests)
  • Feature in packaged by Maven into StratusLab packages
  • Build, tests and packaging is intergrated in Hudson (via a job)
  • Feature is documented (wiki and/or ??)

Therefore, when a user story containing such a task is declared done, we know what this means. This also means that if a bug is found, the setup exists to fix the bug, but also make sure that no regression is caused by the fix.

If at the end of a sprint we're missing one of these steps, it's not a shame, we're just not done!!

Operations Tasks

TODO

Packages Layout

All of our installation are following a Linux standardised layout. Here's an example of the OpenNebula package:

  • Configuration files in /etc/one
  • Executables in /usr/bin
  • Examples/documentation in /var/share/one
  • Log files in /var/log/one
  • Libraries in /var/lib/one
  • Image repository /var/lib/one/images (default)
  • Daemon files in /var/lock/one and /var/run/one
  • VM repository /var/lib/one/vms (Quattor default)
  • Bookmark at
  • Bookmark "Bill of Rights and Obligations" at del.icio.us
  • Bookmark "Bill of Rights and Obligations" at Digg
  • Bookmark "Bill of Rights and Obligations" at Reddit
  • Bookmark "Bill of Rights and Obligations" at Google
  • Bookmark "Bill of Rights and Obligations" at StumbleUpon
  • Bookmark "Bill of Rights and Obligations" at Facebook
  • Bookmark "Bill of Rights and Obligations" at Twitter