Hey, so I’ve been pretty busy (again! *Shock* ) with school and haven’t had a ton of hacking time as of late. I’ve learned this means definatly pick jobs that don’t require a lot of follow up or that someone else is waiting on.
Anyways, I had some beagle-fun last night and was somewhat productive.
- I started a Launchpad Team and Branch to maintain our Ubuntu beagle packages. I think the trick here is going to be paying closer attention to Debian, as both an upstream developer and a 2nd tier packager, I always think I’m going to be on top of the Debian packaging solution/patches, but rarely ever am. So anyways, I’m hoping to parallel/stalk what they do so we can avoid more nasty merges right after Upstream Version Freezes are instated.
- Documentation! A long while back I started to fill out the automatically generated Monodocs for Beagles public API. While they’re still nowhere near done (API Docs are a royal pain to write, you feel so redundant), I have started to pick that up again, so should you want to write some bindings for BeagleClient, start working on Dashboard again, or even start another search interface, at some point and time, there should be some quasi-complete API coverage in addition to the Beagle Wiki.
- And just so everyone knows, its easy to help out! if you have monodoc installed, you have everything you need! There is another bzr branch just for the BeagleClient docs. If I made you a member of the “Beagle Packers” team, you can commit straight to the branch, just let me know you did and I’ll update it on my server. As for the actual editing, it couldn’t be easier:
monodoc –edit ./path/to/docs/dir/ and your editing!
p.s. More Documentation news, I updated my libbeagle docs that are online too.
Technorati Tags: linux, gnome, mono, beagle, documentation,
