Disclaimer: None of the "yous" in this post are directed to any particular person.
usability should become a stronger part of the Allegro mythos
Again, nobody would seriously disagree with that. What people don't agree with is being told what to do with the time they volunteer. Same response I gave to Edgar: head up a usability project. Things don't get done because you have a good idea.
Regarding documentation, good programmers are not necessarily good technical writers. And does somebody with good technical writing skills really want to do the boring task of writing documentation. For what gain? So somebody else can use the library with a little more ease? No thank you, I'd rather sleep in.
That's the fundamental problem here. We need a bunch of communists who believe in laboring for the good of somebody else with nothing in return. Or else we need to turn Allegro into a commercial product with commercial support.
Sample case: I wrote the documentation for the menu system I built. Since I'm the one who took the time to add that functionality, I'm the person who gets to design the interface. So naturally it works like I want it to.
Then I have the chore of writing the minimal amount of documentation needed so that the patch will be accepted. Now, I tried to do a decent job of explaining how to use it, but I'm not going to bust my butt over it just because you want a nice document.
And the OS X implementation is left undone because I don't have a system to work on and I don't have any experience with OS X. However, I don't expect that somebody else should just drop what they are doing and write it just because somebody should, and after all, I put in the time, so somebody else needs to put in equal time.
And am I somehow lazy or selfish because I took the time to implement something but didn't provide an OS X port or documentation to your satisfaction? If so, isn't the laziest and most selfish person the person who does nothing at all?
In terms of the "your time for my time" concept ... well, the core developers are so far ahead of the score, you'd have to really have to spend a lot of time (or money) to catch up...
And if you agree with the idea that whoever can do it the quickest should be the one to do it... well, why don't you just start writing all the newbies' code for them? It would be quicker, for any particular instance, for you to just do what they want, instead of them learning how to do what they want to do.
But it seems silly that I should have to explain any of this to anybody. Surely everybody here grasps the concept that nobody owes anybody anything, and if you want something that nobody else wants to implement, either do it yourself or pay somebody to do it.