torpor
hack hack hack, the little machines fight back
Reading about the WLAN issues of the PandoraOS recently, I suddenly realized that I haven't seen the PandoraOS kernel sources talked about much.
So my question is this - where are the sources located?
Doing a bit of boot-strapping on the issue of the WLAN driver problems, I ran into this recent thread on the subject:
http://permalink.gmane.org/gmane.linux.kernel.wireless.general/47781
So what about putting the sources out there, notaz/DJWillis and co., and letting us throw a few more eyeballs at the problem? Its also, probably, about time you guys got that work cleaned up in a form that other developers can start using it and contributing to it properly, so what about doing that instead of any further debugging for now?
And, this leads me to another question: just how are we going to organize Developer resources around the PandoraOS codebase .. is it going to be all pushed upstream to Angstrom, or is it already pushed up to Angstrom, or are you elite guys already forking and maintaining your own cache of coveted materials on the subject? From my perspective as an outside developer with the skills to contribute, it sure seems to me like there's not much love happening for the idea of a common repository being used to generate nightly/weekly builds that all developers can hack on and if indeed this is the case then I implore you guys to set up the servers, properly, so that we can all contribute rather than just having an elite core that covets its contributions and doesn't really have a standard focus on the mainline product development as a core issue ..
So my question is this - where are the sources located?
Doing a bit of boot-strapping on the issue of the WLAN driver problems, I ran into this recent thread on the subject:
http://permalink.gmane.org/gmane.linux.kernel.wireless.general/47781
So what about putting the sources out there, notaz/DJWillis and co., and letting us throw a few more eyeballs at the problem? Its also, probably, about time you guys got that work cleaned up in a form that other developers can start using it and contributing to it properly, so what about doing that instead of any further debugging for now?
And, this leads me to another question: just how are we going to organize Developer resources around the PandoraOS codebase .. is it going to be all pushed upstream to Angstrom, or is it already pushed up to Angstrom, or are you elite guys already forking and maintaining your own cache of coveted materials on the subject? From my perspective as an outside developer with the skills to contribute, it sure seems to me like there's not much love happening for the idea of a common repository being used to generate nightly/weekly builds that all developers can hack on and if indeed this is the case then I implore you guys to set up the servers, properly, so that we can all contribute rather than just having an elite core that covets its contributions and doesn't really have a standard focus on the mainline product development as a core issue ..