Overlap.org Wordpress Code & Patches

Updated October 28, 2007 @ 17:05 PDT

Overlap.org Logo

I’m trying to clear out the patches I’ve written that are chilling on my system (near bitrot). Since I don’t code that much anymore, sounds like a good time to get them out and about.

Here is my themed login patch with additional hooks (and additional plugin called overlap-profile-feed.php) to the brilliant themed login plugin by James Kelly. I’ve added some additional actions to James’ 1.1 version which allow for some pre and post registration calls to add a user to a mailing list if they so please and add a default feed they can edit on their profile page. This is used to automatically aggregate their valid feed onto http://overlap.org/tag/commons using feedwordpress.

Also, here is a custom plugin I wrote which hooks into the feedwordpress action system which allows you to put html before and after an aggregated post. We use this on overlap.org to put content into a blockquote and to provide a link back to the original page (to get trackback love).

Here is the public SVN repo with the latest changes to custom overlap plugins.

I released the above code under LGPL.

UPDATE: I forgot to put this Patch for authors.php for authors.php (diff’d against authors.php 1.0)which adds feed support.

OpenMoko Wiki Face + Late OM Indoctrination

Updated September 10, 2007 @ 03:12 PDT

NOTE: I’m writing this post as I go through updating my OpenMoko, so it is a bit of a narrative journey…please bear with me…

I’ve spent some time helping to advocate OpenMoko, pushing on some various projects like liblicense at Creative Commons, which is to help get licensing into the desktop for devices like the OLPC and OpenMoko, and believe it or not, I’ve stayed out of the down-n-dirty software hacking of either OLPC or OpenMoko. Today though I got an itch to burn some time (that I don’t have) on getting my OpenMoko up to date…I’ve had it with my crappy T-Mobile Dash!!!

First thing is I went to the OpenMoko wikit and first ran into the nastay web of information, and got stuck there first to clean up the main wiki page with a nice clean table approach that Ryan Lerch has done on Open Clip Art Library and Inkscape, and I have copied lots of places since.

I next went to the Getting Started page, which led me to where I needed to be, the USB Networking page. From here, I found that I needed to setup iptables on my gentoo box (I call it futurebox…) and just use ScaredyCat’s gta01 connection script. So, that is simple and everything. After all this, I can now just run ./gta01 on my system, then boot up the OpenMoko (GTA01B_V4), and then ssh root@192.168.0.202 and just hit enter once the password is asked, since there is none!

Then, I expected to get my OpenMoko all up to speed, since I met a nice OpenMoko dev in Taiwan who flashed my phone to a semi-new OpenMoko image. I ran:

ipkg update && ipkg upgrade

And, rebooted the device and bam, looks ike the distro dies on starting up matchbox on the neo daemon and some other problems with the recent package updates :(

So, I hopped over into the #openmoko chat channel and asked around for some questions, which Rod Whitby so graciously answered. While it seems that the OpenMoko-specific code in the distribution, Angstrom, has some broken code committed to it, from the likes of my update, I’m not convinced of this (and didn’t look deep enough to talk about this affirmatively).

Regardless, the status update of how to get your OpenMoko working as a phone with the latest builds, seems to be these steps outlined by Rod Whitby:

Here’s my recipe for current image boot and gsm registration success:

1) Get into u-boot console by stopping the bootloader with the AUX
button and using ttyACM0 on the host. Remove “console=ttyACM0,115200″
from bootargs_base

(This tip from Harald in http ://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=788#c10)

2) ipkg upgrade from buildhost to the latest versions of all packages.
(You might need to ipkg remove -force-depends libmokojournal2 and ipkg
install libmokojournal2-0 if your starting from a very old rootfs)

3) Build and install from SVN revision 2946 for openmoko-dialer2 (this
revision fixes a bug which stops you from being able to dial).

4) Restart gsmd in /etc/matchbox/session

5) You can also comment out the “load-sample startup” line from
/etc/pulse/session if you need to not have the reboot wake up your 2yr
old daughter …

Yes, that’s the current state of the GTA01 software - you have to go
through all these hoops just to be able to reliably make a phone call
after boot.

– Rod

I’m not writing this to complain, but am hopeful that the OpenMoko team and any contributors have their sites locked on these key ideas:

  • Never commit broken code to the development tree, esp. don’t pull this into a distribution. Make this the law.
  • Get the key goal of your project accomplished as fast as possible. For OpenMoko I would say this is to make a phone call (Yes, could argue that just getting ssh access is key, but I think getting this thing to be a useful phone is key to integrating into all developers and peoples lives…the more people using it as a phone, the more people who will hack on it)

Ok, I didn’t have enough time to do Rod’s method to get my Moko working, so that means I’m back up to my neck in more CC work and not more time on all my other projects for a few. Hopefully though when I come up for air again, I’ll get my OpenMoko working as a phone and chuck all these other junk phones out the window.

“please get a newer Subversion client” one-liner

Updated July 10, 2007 @ 00:31 PDT

Heya, this is a sign-post for google and anyone looking to get around updating their checked out repos that are used with a higher versioned subversion (svn) and then you have to migrate that content where the svn client is an older version. If you do svn up on with the older client, you will get this: “please get a newer Subversion client.”

The trick, provided by OSUOSL’s own, emsearcy, is to checkout a fresh copy (we’ll call it the source) to sit besides your old checked out copy. Then run this one-liner:

rsync -r --progress --include='*/' --include '.svn/**' --exclude '*' \
SOURCE/ DESTINATION/

You will then be able to use svn once more! There might be some pitfalls like needed to do -av rather than -rv if you want read-only files to not be touched. Big ups to emsearcy!

NOTE: I’ve been working on openclipart.org and openfontlibrary.org migration and we’re almost there…thanks for hanging tough like NKOTB.