Sometime back we at [[http://forrest.apache.org|Forrest]] moved away from Forrest Tuesday in favor of a [[http://forrest.apache.org/forrest-friday.html|Forrest Friday]]. Since Cheche and JennyCuran were absent from this friday’s meeting, I took it upon myself to setup a bot and publish some fun stats.

I chose [[http://supybot.com|supybot]] for the logging — its far more advanced than my needs, but since its written in python and has excellent documentation, I stuck with it. I used [[http://pisg.sf.net|pisg]] to generate the stats. This friday’s stats can be found [[http://people.apache.org/~diwaker/for-n.html|here]]. Those interested in full details will find the complete logs in our SVN repository.

So we had another [[http://forrest.apache.org/forrest-tuesday.html|Forrest Tuesday]] 2 days back. I was not able to participate, but I did read through most of the logs later on. A lot of work was done in moving the xmap over to locationmaps. And as usual discussions on views, XHTML2 (here is a [[http://article.gmane.org/gmane.text.xml.forrest.devel/16863|brief summary]]).

A few days before that, Ross, Addi and I sat down for a collaborative editing session using [[http://gobby.0x539.de/|Gobby]]. It was pretty cool actually — I’d never used a collaborative text editor before — these things are quite funky. Real time editing in different colors, real time IRC like chat. It was pretty nifty. And, we were [[http://article.gmane.org/gmane.text.xml.forrest.cvs/5106|quite productive]].

In other news, [[http://www.codezoo.com/|Codezoo]] //still// hasn’t updated its [[http://www.codezoo.com/pub/component/2845|Forrest page]] despite my having submitted the DOAP file several times. Please guys, I’m trying to help you out here — fix this before we lose interest! :)

I have created an initial DOAP file for Forrest. Currently we plan to update it manually since releases are infrequent and require some manual effort anyways.

Having done that, I went back to the Codezoo website hoping to submit the shiny new feed so that they could update the information on Forrest on their website. While Codezoo is a great concept, I think they still need to do a lot of work before it becomes truly usable:

• for one, there is //no// obvious, visible mechanism for users/developers to submit/update their DOAP feeds
• links to using DOAP on Codezoo are sparse and don’t stand out (given that Codezoo is the first biggest deployment of DOAP, I think this should change)
• I’m sure Codezoo is thinking about this already, but right now there doesn’t seem to be any mechanism in place for stopping people from spamming the system (submitting fake DOAP feeds, for instance)
• There is a “feedback” link on the top which seems to mean that we are supposed to give feedback on the Codezoo website. However, on the feedback page they also talk about “submitting new components”. I think this should go in a separate page on its own.

Meanwhile I would request other Apache projects to also get started on creating DOAP feeds for their projects. This is going to be like the RSS of blogs :-) Here are some links to get you started:

• DOAP homepage
• DOAP over Atom
• Keep Codezoo updated with DOAP (doesn’t seem to work)

I am now syndicated on [[http://planetapache.org|Planet Apache]]!

Greetings to all!

A brief introduction — I’m very new to Apache, and got involved primarily due to my interest in Apache Forrest. This blog is where I ramble now and then about technology, philosophy, movies, vim, linux, ubuntu, forrest and anything else that fancies my thought :-)

BTW, I notice that the //feed// link next to pretty much all names (including mine) on the Planet Apache home page under the Subscriptions list point back to http://planetapache.org — is this the correct behavior? Does’t seem like to me. Ideally the //name// should be a link to the home page (if any), and the //feed// should point to the feed, as it says.