Building OpenKinect
Thankfully, our new project is being developed on the current release of Ubuntu. The instructions for downloading the OpenKinect source code and building it are quite accurate, as of today. There is a note that says the instructions are subject to change, but with the project only being a few months old, I guess there haven't been many drastic dependency changes yet. All told, this project took about 3 minutes to download and build.
TOSS Ch 6
4. One problem I have with our new project is that the only bug-tracker I've found is Github issues, a sub-page of the project's github site. There are only 2 bugs listed there, and they're both 2 months old. That's two-thirds of the project's life to date. The oldest is related to packet loss in the depth view.
5. Creating a github account was a simple task. Click login, select pricing options, select free for open-source, input the data, and you're done.
6. I don't personally have a Kinect controller, so I will have to rely on Ashley to reproduce the bugs we find.
7. Another severe limitation with github issues is that it's not really a bug-tracker. According to FOSS chapter 6, a bug-tracker should have a Summary, a Description, Comments, a Reporter, an Owner, a Version, a Severity and Priority, a Status, and a Resolution. Github allows Reporters to tag their issues as bugs and they can write a description of the bug. Other users are able to leave comments on those bugs. Unless the Reporter has foresight, the Version could be completely left out, and Owner, Severity/Priority, Status, and Resolution aren't even addressed at all. With these limitations, performing triage on our project's bug list would require porting all the information to a real bug tracker, like Bugzilla for instance.
Despite the failings of Github as a bug-tracker, we can at least build the source, and with Ashley's Kinect controller, we can attempt to replicate and test the reported bugs.
No comments:
Post a Comment