One of the culture change issue we ran into when requesting a centralized wiki for the Android community was that we asking if Google had any plans so as not to duplicate them..
But we got some slience, not due to the Engineers but obviously peoel above the engineers. Change in community involvement/engement in community often has to happen from the top down as far as big corporations go.. Some time ago Burce Prenes wrote aobut thi swhen the open source adovcate whiel at HP. On Fri, Apr 3, 2009 at 1:02 PM, Mark Murphy <[email protected]> wrote: > > JP wrote: > >> On the "community built" front...let's just say that there's a long road > >> ahead of us for Android. > > Well the question then: is a bus coming? We are in it for a year now > > and there are still no signs there will. > > It's been a year since last fall's source release? > > Damn, I missed a few months there. > > ;-) > > Seriously, expecting collaborative software development before there is > software to collaborate upon is asking a wee bit much. > > > As Muthu points out, front > > line engineers are working their butts off, but effective community > > engagement is not in sight. Instead, we get a continuing string of > > fiasco's as we are kept perpetually in the dark. A big bummer to me - > > the Android team could really differentiate itself - from Apple in > > particular - by engaging the developer community in an earnest way. > > Absolutely. > > > 2009, there should be > > no question that the dynamics of OSS projects weren't understood, so > > one would assume that years of explorations could be skipped and > > Google could go straight to handling this more seriously. > > IMHO, the issue is one of culture change. That does not happen as easily > as flipping a light switch. > > I want it to be happening faster. You want it to be happening faster. > Lots of people want it to be happening faster. What I am trying to > determine is how we can *help* it happen faster. > > >> In another example, Google's GWT took the slow > >> boat to true collaborative development, but things are humming along > >> better now AFAICT. > > Things have always been calmer over at GWT because the target platform > > (browsers) are a known quantity w/o central control of the user base > > by opaque Google/carrier teams. > > Which is why I brought them up. Again, IMHO, the issue was culture > change. It took a year or so for them to switch to a public repository, > and longer still to accept patches from the community. By your argument, > GWT should have been "handling this more seriously" from the > outset...but didn't. My guess is that it's a question of culture. > > -- > Mark Murphy (a Commons Guy) > http://commonsware.com | http://twitter.com/commonsguy > > _The Busy Coder's Guide to Android Development_ Version 2.0 Available! > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Discuss" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
