View Single Post
qgil's Avatar
Posts: 3,105 | Thanked: 11,088 times | Joined on Jul 2007 @ Mountain View (CA, USA)
#21
So what would make sense, imho, would be to just open the bugs to the public once the HW is made public and for sales. This actually _would_ lead immediately to the one single bugzilla.
I see no reason why we couldn't do it, other than we are embarassed to show to outsiders our internal struggles in bouncing, squashing, reopening bugs.
I still don't see this day. It's not easy to disclose internal information, and internal bugs are just that. Bringing development and testing to the outside is probably an easier and more logical path. Yes, I know there are 1001 obstacles tied with unannounced hardware and features there as well. Still, there are more business reasons to show your bugs when it's the right time to fix them than once the products are out.

Same goes with the publishing of the source code for the kernel. I think it would make much more sense to publish the entire set of git trees with all the history, than just the tarball with the latest source code.
This day is around the corner and actually when it comes depends a lot on... you? It is not a coincidence that maemo.org git support and contribution guidelines are being put in place as we speak.
 

The Following 2 Users Say Thank You to qgil For This Useful Post: