Hi,
a couple of random notes:
1. We (well, mostly Michal) are working on (a) migrating the dcloud
API to Sinatra[1] and (b) adding validation and
self-documentation to the API. That is happening on the
dev/sinatra branch in a separate, temporary repo[2] (we are not
doing it on a branch in the main repo since we might do nasty
stuff like rebase a published branch etc.) Once that work has
reached a reasonable state, it will be folded, after a proper
review, into the main dcloud git repo, of course.
2. I had the fedorahosted admins install a couple of commit hooks;
in particular, the hooks forbid pushing merge commits and bad,
i.e. trailing, whitespace. If you have commit access, your
workflow should be based on topic branches and look something
like
git checkout -b dev/mystuff master
.. do lots of work on the dev/mystuff branch
.. time passes, master moves on
.. your patches have been reviewed and you are ready to push
.. these steps should be done quickly, before anybody else pushes
git rebase master dev/mystuff
git checkout master
git pull . dev/mystuff
git push
David
[1]
http://www.sinatrarb.com/
[2]
http://gitorious.org/deltacloud-sinatra/deltacloud-sinatra