Marc Bantle wrote:
Marc,
Very well put. I think this is the best way to read these events. No
intentional hiding of facts, no secret decisions. Just simply "how can
we make this work in the least amount of time with the greatest chance
of success".
Communication is always a difficulty in any organization, and we are
very spread out geographically. Additionally, we have an extremely
strong policy of conducting as much of our communication as possible on
the public lists. As a result you will sometimes learn of things at the
same time that we Openmoko employees do.
This is a feature of our openness policy, and not a bug in our
communication policy.
Michael
_______________________________________________
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community
| Heiko Carstens | Re: -mm merge plans for 2.6.23 -- sys_fallocate |
| Linus Torvalds | Linux 2.6.21-rc4 |
| Michael Kerrisk | nanosleep() uses CLOCK_MONOTONIC, should be CLOCK_REALTIME? |
| Linus Torvalds | Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3 |
git: | |
| Gary Thomas | Marvell 88E609x switch? |
| Gerrit Renker | [PATCH 15/37] dccp: Set per-connection CCIDs via socket options |
| David Miller | [GIT]: Networking |
| David Miller | Re: [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
