Very busy day. In the mourning, a meeting to talk about free software adoption by the Federal University of Bahia (www.ufba.br).
After, another meeting about a free software video that will be produced for an important event at FACED (www.faced.ufba.br). I’ll be the content director of this thing. I don’t know what this means but i think this role is cool. I never worked on video making. :-)
Then, in the afternoon, I integrated a Debian GNU/Linux workstation to the University M$ Active Directory and worked on a nautilus view and VFS module to manage apt packages with nautilus. It’s based on James HenstridgeÂ´s rpmdb.
Here is an interesting flamed political discussion about US and South America that arose at GnomeDesktop.org.
“You cannot have Free Software without free minds.”
I’ve been very busy on writing my mastering pre-project for the selection process. Deadline is 3/11/04. The project will deal with issues like posmodernist society, cyberculture, hackers and free software. I think this will be very interesting.
Well, that’s it. I hope to have some more free-hack-time after this hurry.
Testing GNOME Blog Entry Poster…
I’ve been wondering on what are the consequences of languages imposed programming standards on the productivity on open-source projects…
Pre-defined programming language standards make it easy to understand code written by other people because you don’t need to read any aditional docs to know how a certain application was organized.
For example, Java imposes a file/archive structure that must reflect the class packages structure and suggests a standard for naming your class namespaces (the reversed version of your domain: br.com.mysite.mypkg, org.opensourcetool.foopkg, etc). In my opinion, stuff like this make it easy to understand more rapidly other’s code because my hacking is already based on a java universal pattern and not on a application specific one.
In languages like PHP, C/C++ (which doesn’t impose any standards), every application has its own way to organize “things”, and sometimes it gets very hard to understand the internals of some program…
There are some tradeoffs of course! These standards may turn themselves into a limitation factor on the development practice because they force you to think in way that maybe is not what you think is apropriate.
well, that’s it…