I never stop being amazed by the computer industry's capacity to destroy itself.
While the AUHDL still does need work, I've got to start writing the ClaruxPL. Recent events in the news have made it even clearer the need for such licenses.
I'm waiting for the latest stuff to come in from cheapbytes. I've got better things to do this weekend than downloading and burning ISO after countless ISO. I'll try to get some more coding done over the break, but since this is the summer of HCI reading, that is where most of the break will be going.
I'm not too sure how I should approach the topic of examples for the AUHDL. Certainly the license should contain the suggestion (but not the requirement) that three examples be provided for every variation of every type of procedure. I'm very passionate about examples; the lack of examples I've faced in so many math and science textbooks is the main contributor to this sentiment. Anyhow, I'm not sure whether prohibiting modifications that remove examples would be too impractical in some cases.
My last post was really irresponsible.
I forgot to add man pages to the AUHDL's list of forbidden doc formats. How could I forget the bane of every new user to linux who tries to understand what's going on? How could I forget the category of documentation that gives us the 'M' in 'RTFM'? How could I forget the one?
I should really be smacked on the bottom for such a careless omission.
I believe in freely distributable and modifiable documentation so long as the end-users' Freedom To Use Their Computers is not violated. The freedom to enslave end users in a world of confusing documentation is not a valid freedom.
here's what I've written so far of the AUHDL. I hope to get more down soon.
The Anti-User Hostility Documentation License.
Traditional open-source and free software documentation is meant to deprive an end user of their basic freedom to understand how to get work done with their software. This deprivation of freedom is distilled into a form of oppression, where the only answer to a question born of confusing documentation is "Read The Fine Manual". Further silliness ensues when a world ensconced in 32-bit color and interactive multi-media is eschewed for a world of text-only documentation, whose only attempt at graphic amelioration is pathetic use of more text. We of Clarux feel that the freedom to oppress end-users is not a valid freedom.
It is painfully clear that those who feel it is acceptable to produce documentation that oppresses end-users either through its lack of clarity, lack of examples, or simple lack of existence clearly do not deserve to use, distribute, or take credit for documentation created by those who feel differently. It is the goal of the Anti-User Hostility Documentation License to promote open, accessible, and understandable documentation and thereby create a more open, accessible, and understandable world of technology.
1. All documents produced under the AUHDL must have at least three graphic elements. A graphic element is defined as a diagram, drawing, or a computer monitor screenshot. Any modification to a document protected under the AUHDL that reduces the number of graphic elements by less than 3 is prohibited. By July 1, 2003, the requirement for graphic elements will be extended to the use of at least 3 colors. Modification of a document protected under the AUHDL that reduces the number of colors used for graphic elements by less than three is prohibited.
1.5 While not enforced, it is encouraged that writers of documentation licensed under the AUHDL make their documents accessible to users with visual impairments. It is suggested that authors do not rely solely on the use of the colors to convey relationships, as a significant population has red-green color blindness. It is also suggested that the navigation and display of relationships between pieces of information accommodate blind users.
2. Use of ASCII or Unicode text as a substitute for graphic elements (the practice informally known as "ASCII art") is hereby prohibited from any document protected under the AUHDL. Any modification of an AUHDL document that includes "ASCII art" is expressly prohibited.
3. Any person, company, or entity that wishes to distribute or link to documentation licensed under the AUHDL license must agree not to distribute, link to, or post on the internet the following documentation formats:
c) Any text-only document.
I've still got bunches to add, but it's a start.
Started writing down the Anti User Hostility Documentation License (AUHDL) after months of thinking about doing it. Every day now I tell myself "Ilan, either shut the hell up or do something about it". So I've started to do something about it.
Writing things down is good.
I've been thinking a lot about my licenses to deal with linux's usability problems. I should stop thinking about them and get them down on paper or some kind of storable format. As the needlepoint in Marty Hansen's office once said "there are no good writers. Just good re-writers". I can always re-write them and clarify points later on. The important thing is to get the first drafts done.
I won't we able to post any long meaningful diary entries until my cog psych exam is done on tuesday. But I must say, Joy of Tech has been in rare form the last several days.
Since the last time I've posted, I've brushed up on my xml-rpc so I can working on the syncing part of my Zaurus diet program. As the program is written in python, I'm using the xml-rpc python module, though it would be kind of cool if there was a whole application syncing infrastructure for the zaurus that used the DCOP xml-rpc functionality (I'm buzzword compliant today); that way I wouldn't have the overhead the python interpreter running in the background. Once I get the syncing worked out, I'd like to write the desktop software in Java to make Zaurus syncing truly cross-platform.
As for other zaurus-related things, I've been trying to think of new and better xml file formats the zaurus could use to hold stuff like dates, addresses, etc. The fact that the current file formats from Trolltech really don't have much in the way to support two-way syncing sucks. The fact that the XML tags/attributes are impossible to understand and make sense of sucks twice as much. I suppose I *could* look at their code, but my feeling is that any xml file format that forces you to look at the code to understand it is a file format crying out for reimplementation.
New HTML Parser: The long-awaited libxml2 based HTML parser code is live. It needs further work but already handles most markup better than the original parser.
Keep up with the latest Advogato features by reading the Advogato status blog.
If you're a C programmer with some spare time, take a look at the mod_virgule project page and help us with one of the tasks on the ToDo list!