Hello Ian, > I would say that Effecting a full scale 'all in one go' transition is > VERY hard. I would suggest letting Liam make the poage official, and > continue refining the layout.
I don't see how a transition in one go is very hard at all. The DRI website is fairly small, all you have to do is cut-n-paste the existing content and re-arrange it into new pages as you see fit. How do you think I made the current website? If you can't handle cutting and pasting, the you shouldn't be designing websites ... > The original layout of content was so illogical that there is really > no way to transition gradually and still have things make sense. Now you are contradicting yourself. You just said it was hard to make a transition in one go, now you say it is impossible to make a gradual transition. Which is it then? > Liam is a braver man than I - I gave up after doing a significant > amount of re-organisation, because I couldnt face the problem of doing > a phased update. I don't think anyone wants a phased update. For a site as small as the DRI site, a one-go replacement makes sense. That is also what I told you originally when you asked me about it. > I think that unless anyone has a MAJOR complaint about the new site, > it should become the default. Well, I for one don't think so. The current site didn't replace the previous site until I had adressed all the problems people had with it. I went through several revisions of the site on a different server until it went live on dri.sf.net. I don't think the standards should be lowered just because you guys can't handle making revisions to the site before it goes live. And people do have major problems with it (at least me), in that I find the content organization even worse. See my original email with some ideas on how you can solve that problem. > I must confess that I am not surprised that the developers have STILL > not given Liam a complete list of supported features - despite being > aske long ago by him, and several times, more recently by me. I must say that I am not surprised either. The developers have better things to do, such as actually working on the drivers (imagine that), than to compile lists of supported features. > The DRI project as a whole suffers BADLY from a total lack of > communication - partly caused by NDAs that should never have been > settled for, keeping specs out of the hands of most developers, and > partly caused by people working in ivory towers. I don't see a lack of communication at all, the dri-devel mailing list seems very much alive with ongoing discussions. At the point when VA exited from the Linux business, yeah I thought the project was in trouble. But since then people like Jose Fonseca and Leif Glass have put in a lot of effort to drive the volunteer/community side of the project forward. While the guys at Tungsten Graphics have put in a lot of work to keep the business side going. Mad props to all of them. ;) And yes, NDAs suck, but they're part of the harsh reality of this world. As Jose and Leif have shown, if you are really serious about becoming a developer you will be able to obtain documentation anyway. > DRI is in serious trouble - NVidia did it alone, and I think the other > manufacturers are aware of this. If the DRI project loses its USERS, > then I think manufacturers will simply go elsewhere, or do it alone. I can't really comment on that, but from what I see here, DRI seems to be doing quite well. > And one thing users WANT is a list of supported features for their > card. You only need to look at the windows world - theres dozens of > sites like Toms Hardware 'hot video card zone' 'video card shootout > site blah blah'. And if anything, Un*x users are even MORE into > knowing the specs and details of their system. Ah yes, the much discussed supported feature lists. While I was still actively maintaining the current site this issue came up a few times. I think in the end everyone decided that it is too much work to put together in the first place and even more so to maintain and keep current afterwards. On top of that, these users you always talk about: I have never actually received an email from them asking me about supported feature lists. > I can download the linux kernel and Hack HAck Hack - its truely open, > specs and all. I cannot do this with DRI - there are no specs. all I > can do is poke blindly. As I said above, if you were really serious about becoming a developer you would be able to obtain documentation from the companies. Obviously you must be doing something wrong ... Cheers, - Frank ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
