> There is one thing we tend to be very tight lipped about. HR issues.
nobody expects to hear internals, but visible information about staff changes, at least when it affects people being some kind of om's face to community, would help. > As to the other issues, there are some cases were the situation is so > fluid and still in process that commenting really isnt possible. I'll > relook at the official buzz fix thread and see if I can add anything > helpful. of course it is problematic. but communication is an important part of community building and community relations. we got those montly community updates, a section like "from om, the company", noticing about ongoing issues would be highly apprecaited, i think. there, in short, could be mentioned that important, community visible members of staff are leaving or hired or what you wrote regarding the buzz: tests going on, procedure has been etablished, bids are requested, pondering ways of fixing in field ... so we could rest assured that those things are not forgotten but being worked on (and maybe the wired headset buzzing would have come up again earlier). the heated debates when rasterman left or about the way to handle th buzz fix could maybe have been a lot cooler with a constant flow (or trickle) of information, even if it says "we hear you, but we're not quite sure yet, how to procede". _______________________________________________ Openmoko community mailing list [email protected] http://lists.openmoko.org/mailman/listinfo/community
