Good question, thanks for asking. Here are the basic steps:

• Fetch the source code
  
  Code:

         git clone git://gitorious.org/microfeed/libmicrofeed.git

• Enter the source code directory
  
  Code:

         cd libmicrofeed

• Generate the configure.sh script (autotools are required)
  
  Code:

         autoreconf --install

• Configure the package
  
  Code:

         ./configure --prefix=/usr

• Compile the source code
  
  Code:

         make

• Install the library
  
  Code:

         make install

• Leave the directory
  
  Code:

         cd ..

After that you need to compile and install also the microfeed-utils and the microfeed-providers-unstable packages. Just substitute the word libmicrofeed with those and perform the same steps.

I also wrote these instructions into a wiki page:

http://gitorious.org/microfeed/pages/Compiling

Nice! I discussed about the topic with Ryan in Maemo Summit. Microfeed and Gwibber could be a perfect match and benefit each other.

For Gwibber, it would be enough to either write a new implementation of libmicrofeed-subscriber from scratch in Python or just to make Python bindings for it. For starters at least. As microfeed is operating on top of D-Bus, the subscriber (client) part is fairly straightforward to implement.

See the specification (http://microfeed.org/specification/) and the source code of microfeed-subscriber module (http://gitorious.org/microfeed/libmi...eed-subscriber). Please note that the current version of the specification is a little out dated (new features introduced and others are fine tuned), so the reference implementation is formative for now. This will change of course before version 1.0.

If you want to implement new providers in Python, then it would be feasible to make Python bindings for the rest of the library (libmicrofeed-common and libmicrofeed-provider). Those contain over 10k LOC of logic (caching, for example).

Actually, it is too verbose to write a new provider for now. (See, for example, the current Twitter implementation: http://gitorious.org/microfeed/micro...master/twitter) There are many patterns that have to be copied (mostly as is) when implementing a new provider. I will further encapsulate common logic into the library itself, so the provider implementation should be more straightforward in the future.