![Popular open source software is more secure than unpopular open source software, because insecure software becomes unpopular fast. [That doesn't happen for proprietary software.]](../sites/all/themes/drupal4hu/images/bg-center/bg-center_4.png)
Seems the community is overly happy with the git migration and it's right to be. But I would like to quietly remind everyone one part of our success is us being centralized. One part the git migration is beneficial to this because all those projects that went off to github can return home. On another part all these "sandboxes" have a danger of everyone going off into their own little corner. Oh yes, our long time core contributors will still post patches and just play nice but ... maybe not. Last year a project was borne out of frustration of core committing speed. Another example. Someone (some big, big company) shows up with an API their company is using, dumps their core fork with that API into their sandbox "take it or leave it" style and then posts contrib modules using that API? Heaven forbid, good quality, useful modules? So tread carefully, my fellow Drupalers.
Commenting on this Story is closed.
the honesty shared here and hope that others do read and take pause. i came to drupal because of the community. being a newbie in this community i can see some splintering and can only hope that the community stays healthy and vibrant and cooperative. thanks for the friendly reminder :)
Yeah, git empower people, and that's great ;-)
I strongly believe in drupal community cohesion, and I think we will end up with more awesomeness around.
I would really appreciate any suggestion, and will bring it back to git migration team if there is not an issue already opened about it. IMHO moving fast to help people collaborate through d.o is key to the adoption of git, and git phase 3[1] really want to help in that process, so please feel free to communicate any concerns, so we can be aware and we can try to solve them.
1: http://drupal.org/community-initiatives/git/phase-3
The way to prevent that is for git.drupal.org to be a delightful place to do development. We have made strides, but we are quite a bit less delightful than github still. Some awesome features we should provide are fork queue and line by line diff comments. I know that there are open feature requests for these. So what. Vaporware is vaporware.
Further, drupal.org should move to fill in the 'app store' gap. Or else someone else will. At minimum, we should be running a feature server which is easily browsable. drupalmodules.com has existed for years and our project pages are still not as useful as those.
Finally, doing work for drupal.org is a complete pain in the ass. It takes months and months to get patches reviewed and committed to the project modules.
I have advocated for the DA to name a webmaster for each of our sites, including drupal.org. So far, no progress.
Speaking of webmasters, is drupal.org actually based off the "Drupal.org Testing" install profile? If not, could it be updated so that the install profile were the actual canonical source, and so we could contribute patches to the drupal.org site just like we would to a module? Would that make a designated webmaster less needed, given that we could all take a more active part in creating and discussing the evolution of d.o using the familiar format of the issue queue? The person in charge would be less grand-pooba-webmaster-of-all, and more like an install profile maintainer. Plus I think there'd be more involvement in the community in pushing new site features, since we could all contribute in the way that we're used to contributing (patches). Is that crazy-talk?
Also, thanks for the post chx. Personally, these sandboxes are just going to bring me in more, as there's a simple place for me to post my wares and get feedback -- which hopefully will be encouraging :)
Oops. Anonymous? d.o username = patcon