Look, let's keep this thread strictly professional, if you want to trade insults, do it via pm's and not to jam up this thread - this thread is about far more than just about "unprofessional" conduct.
is the key here, there's a jvaughan's github, who's using it?
I am in agreement with your comments and yes it is a sad day, we should all be able to help each other to put patches, fixes and show ZTE what and how it should be done. Unfortunately, the reality lies elsewhere, all very fine for ZTE to bring out the sources, but there's a lot missing, of course, if ZTE does not wish to disclose the sources to their proprietary drivers at their discretion, fine, we can work together and find a way to get it to work - take the ril layer for example... what is worrying me about this whole thread is there's no single tree to work from, and transparency for the kernel sources.
Sure, one can be shifty on it and say "Oh, I cannot remember the name of so-and-so and submitted the patches..." etc and be vague on the details, etc, that's not going to help unify and to work together is it?
Each of the ROM's have their own plus'es and minus'es, one kernel is overclocked, another isn't, I do know that ZTE-BLADE
has the overclocking stuff used by Japanese Jellyfish, it's just seems disparate that there's different trees... there's r3pak's who has gingerbread stuff as well....against the same kernel version...
Even writing a tutorial put together on how to recompile the kernel was helpful to others (I hope!) to be able to experiment for themselves....
I am all for transparency, and to help out in any way I can.... no sniping or snarky comments please... leave that at home!
So what you say? Work together yeah?