making apps, making webs.

As part of the pygame move to bitbucket, we are converting a bug database stored in bugzilla. Work is progressing on the issues migration: https://bitbucket.org/illume/bugzilla_bitbucket Bugzilla is more comprehensive compared to bitbucket. So not all things can be migrated from the bugzilla bugs to the bitbucket issues. Also, the bitbucket API is limited in what it can do. You can't add user comments or add attachments. To get around the attachments part, I made the migration script create a directory of attachments, and then link to them in the bug text. Then I've extracted the attachments from bugzilla and put them online. To hack around the lack of comment adding in the bitbucket API, I'm just combining all of the comments into the content text. Other features bitbucket issues API does not have are priorities, and platforms. The issues features _does_ support priorities, but it doesn't look like the API is set up yet. You can't add pl...

I'm starting to move most of my projects off launchpad onto bitbucket. launchpad just hasn't gone in the direction that is useful for me, or my projects. It still has some nice features, such as packaging farms (PPAs) and of course bzr integration. However, github and bitbucket have just been moving more towards making it easy for developers compared to launchpad which is more geared towards for distributors who work with an upstream. Last year I hoped launchpad would improve after it went open source, and it has improved. Just not really in the direction useful for my projects. Many people these days are able to use hg, or git... but still very many people have never even heard of bzr. I feel bzr+launchpad was holding one project back a little from gaining collaborators because of this. By that logic, I should be using svn for it... but I don't want to do that :) The documentation to convert repositories to mecurial is on the hg wiki. The conversion seems to mostly...