| |||||||||||||
ELC: Android and the communityELC: Android and the communityPosted Apr 15, 2010 22:05 UTC (Thu) by cdibona (subscriber, #13739)In reply to: ELC: Android and the community by Trelane Parent article: ELC: Android and the community
Nope, but it is hard to address the concerns of people about the lack of community when in fact there is one. It is difficult to even converse about it when one persons community looks like drupal, while another like samba, while still another like the kernel.
(Log in to post comments)
ELC: Android and the community Posted Apr 15, 2010 22:25 UTC (Thu) by dlang (✭ supporter ✭, #313) [Link]
the common thing about all those communities is that they do more than just code dumps at every release.
they allow people who are not yet part of the project to see what they are doing, including how and why something is done.
if you only do one checkin per release, then you may as well just publish tarballs, a VCS is of limited help.
This is one huge portion of the problem that is being called out.
ELC: Android and the community Posted Apr 16, 2010 2:44 UTC (Fri) by Trelane (subscriber, #56877) [Link]
Plus, it's hard to winnow out which particular commit broke something; you're stuck with a ginormous monolithic patch. And sadly, not the 2001 type.
It's not quite as bad as tarballs (in the kernel, you'd have to first generate the patch) but it's not far off.
And then the other thing of there are people interested in using the tech in other places (the supercomputing thing in the article above) but are stopped by Google's foot-dragging. This is hardly ideal.
It may be the minimum required, but do you want to just have the minimum pieces of flair?
|
|||||||||||||