this is in essence what you can see on the linux kernel mailing list (and many others):
gee, i have a great idea for this new solution to your existing module XYZ. i want to replace it with ABC. if i do, will you take it? the answer is that 'carte blanche' does not exist. the proof is in the code. you write the code. you submit the code. the code is peer reviewed. at the end of the day, you get an answer. > Look making the change to XML is a straitforward > project its enough work that doing it before there is > agreement to accept it makes no sense. I don't think > I'm putting the cart before the horse. look, it's not hard to understand what people are saying. what it boils down to is this: you have an idea. you have not sold the idea as a winning scenario. so prove it is better by doing it. people don't like changing for no reason. why rewrite the entire X project into java/perl/awk scripts/foo just because foo is the 'latest and greatest' invention? if you have an idea, and want to pursue it as a new strategy, then provide a working code base, decent documentation, and submit it to the public lists for peer review. if people like it, they'll accept it. if they don't, they will either tell you explicitly why not, or will simply give you te dreaded one-liner "no thanks". and you might get useful feedback on how to make it better. note, however, that you are explicitly stating that you will fork the xfree code base if people say no. so it sounds ike you're going to implement this one way or another. fine. implement it. submit it. get a reject? stick a fork in it. -josh _______________________________________________ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
