I've decided to retire this blog — I don't really see myself updating it any time soon, and haven't for over two years anyway. I intend to leave the content on-line for the forseeable future, but have converted it to a static site. As a result, dynamic things like search and comments aren't really going to work.

You can find me on Twitter or on Google+ if you like. Alternatively, I'm usually on IRC as LawnGnome on Freenode.

Thanks for reading!

You gits

I’ve been looking at GitHub more and more of late. Initially, it was just because lots of people were using it, but since I’ve been using Git on my own server for my own projects for a while anyway, it started making sense to upload some bits and pieces to it to save me worrying quite so much about trivial things like backups. Plus, GitHub seems like a pretty good home for those random bits of code that you tend to churn out from time to time as a developer.

So, I’ve spent the last couple of days pushing a few things up. It’s not going to completely replace my need to have some Git repositories on my own server (there are things that aren’t open source or aren’t for public consumption, like my resume — although making that open source could be entertaining), but it’s definitely handy for other things.

Obviously, my user page is going to cover the full list of things at any given time, but the projects I’ve uploaded so far include:

  • CineJS — the Javascript video processing library originally introduced at LCA 2010 and in an earlier blog post. There are a couple of releases probably coming for this in the next few months: an interim release to work around what looks like a bug in Mobile Safari on the iPad, and a more featureful release which will hopefully have the first steps towards WebGL support. I’ll probably get rid of the Google Code site for CineJS in the near future, since there’s no point having two issue trackers.
  • Dubnium — long time readers will remember this as my Google Summer of Code project back in 2007, and it’s been neglected far too long. It is, in essence, a cross-platform GUI debugger for PHP code. It’s gotten a bit of love in the last few months and I really just need to spend a day or two cleaning it up for a release. Unfortunately, part of that process involves getting a Windows build environment set up, and that’s rather killed my motivation so far.
  • A couple of little Gopher related things: the source tree for wp-gopher, my Python-driven Gopher interface to WordPress (which you can see in action on this very blog) and a Gopher stream wrapper for PHP that I knocked up on my lunch break today just for the hell of it, which I’m currently imaginatively calling php-gopher. Let’s face it: these are obviously Important Projects.

So, yay GitHub, helping me procrastinate from doing actual development work in my spare time for two days now. (Yay may not be the right word.)

3 Responses to “You gits”

  1. 7php.com Says:

    Like you, recently I heard alot about github. And I read some very good things about it. I was more used to svn, but the philosophy of Github goes steps forward, specially if you want to collaborate with other like-minded developers around the globe.

  2. Five Minutes » Blog Archive » You gits | Source code bank Says:

    [...] the article here: Five Minutes » Blog Archive » You gits If you enjoyed this article please consider sharing [...]

  3. wapa Says: