On 2002.01.18 16:55 Jose Fonseca wrote: > ... > > The first idea can be put in practice right now. It's an excellent > opportunity for me to learn about DRI and make a contribution at the > same time. With that in mind I've developed a quick python script to > dump all the dri-devel into a standard unix mbox format and I'm now > reading it in my mail reader application. I invite everybody in the same > position as I to do the same. (We can then focus special features, merge > notes, etc...) You can find the mailbox and the script at > http://mefriss1.swan.ac.uk/~jfonseca/dri/ . (There have been some > network problems here at the university so the server can be temporarily > unavailable sometimes...) > > ... > > Regards, > > Jose Fonseca >
I'm not sure how many of you are really interested in this but I'm posting in this list anyway just to avoid work duplication. I've finished reading (diagonally of course) through the dri-devel mailing lists. It's interesting see 2 years of the DRI development flashing in your eyes in 8 hrs - it's like a novel in that you feel for the characters, i.e., the developers.. :-) More important, after that you start to get used to terms and how things work more or less. But it's not an exercise that is exciting to do: skimming through more than 8000 messages to find less than 5% messages worth seeing. Nevertheless those 5% are a pure gemm. So in this process I've cutted&pasted the more insteresting ones and I'm now compiling them in a DRI Developer FAQ. As David Johnson showed in his mail there is a lot information available, although somewhat out of date. So what I'm also doing is complementing the FAQ with information from these documents. This ways we have a single document that is more easy to maintain instead of a handful of old ones. Of course that a FAQ is not suitable for all information. I'm thinking in especially the low level API. It would be best if these could be generated from sources. I must tell you that I'm somewhat concerned with the DRI future: I don't know if it has critical mass to go on... This is why I'm using the Open Source you-can-do-it-yourself idealogy and take the documentation issue in my own hands: it's no longer a question of getting Unreal Tournament running faster on my laptop's mach64 based card, but also that underused S3 Savage 4 chip I have back at home (Portugal) that I can't even find drivers for Windows, or for the next desktop card or the next laptop, etc... I think of it as an investment: the more people participate in the project more likely things will get magically done. Well, I won't bother you more with my opinions. Regards, Jose Fonseca _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com _______________________________________________ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
