Well, after many moons I blog again! I was going to write soething short because I'm somewhat sleepy.
My cat seems to continue to have personality changes. The guy has developed quite a temper of late. He's been itching to go outside like all the time. Which is totally understandable because the days are gorgeous. Unfortunately, he always gets unwell when he goes out for a long time. But this one time we took him outside but never sat him down and then took back inside. Oh man, he was so mad he was trying to bite my wife and just overall showing his displeasure. hahaha. Silly kitten.
Hacking has been going downhill. I've been too busy enjoying the weather. Been doing a lot of gardening and working on my sprinkler/drip system. I think I'm at the stage where it would be nice to connect it directly to the water main coming into the house. But I'm going ot need so help there I think.
Finally, d.g.o is fixed and people can actually see the summaries. I've been working on them without releasing anything. I know I have one in the works that I need to finish and then I need to start on this weeks too. All my volunteers seem to be busy with other projects and I've been plodding on doing them myself. </whine>
I finally got time to look at rb's status bar code again. Goddam, what a pain in the ass. I have to do some serious re-working I think to actually get somewhere including changing the RBStatusBar struct somehow. I haven't figured out what all that needs to be done but I need to do it soon, but my motivation is not that great.
One thing I find when reading DDL is that technical arguments come up but there is never any follow up. It just sort of flares up and then there is never an concrete direction. I remember way back when we used to have flame wars that the GEP processes was put in place so that we can discuss and approve technical items. We should go back to that.
Finally, I'd like to talk about 2.8 direction for GNOME. One thing I've found is that our documentation sucks badly. I'm not talking about quality but rather quantatively things like APIs are not complete. It's hard for companies and external developers to use GNOME APIs if they aren't complete. It's just not professional. GNOME-VFS for instance has only 85% completion. Furthermore, I have no idea how much of that API documentation needs to be re-audited for accuracy. What I propose is to have a documentation day like we do a gnome love day (or it could be gnome love day) and we have a number of people come in and start writing API documentation with maintainers hanging around to ask questions. By 2.8 I would like to see core GNOME modules at least 90% API complete. I personally plan on working on GNOME-VFS which needs a lot of love.
I know I said 'finally'. But I lied. One last thing though, I promise. There is some truth from detractors like oGalaxyo when they say that GNOME apps are not all behaving consistently. For instance, GNOME branded apps like inkscape, Gnumeric and others should be able to read documents on remote filesystems through sftp:// and samba:// urls. Recently, Jody has made the fixes for Gnumeric to support this, but Id like to see all other GNOME applications behave similarly. We should start pushing on application writers to make things behave consistently.