drupal.org

Just started a discussion about it here:

https://steemit.com/drupal/@develcuy/is-drupal-the-right-tool-for-drupal...

The promise of Drupal vs. the reality

The first thing you read when looking for 'drupal' in google is:

"Drupal is an open source platform for building amazing digital experiences. It's made by a dedicated community"

Are we making Drupal.org an amazing digital experience? You tell me...

The block at https://www.drupal.org/about of "Who's Using Drupal" is in need of a refresh. Do you have any shining examples of Drupal in action that you would like to see listed there? I plan to take your feedback here and work with the Content Working Group to get the block updated with the latest and greatest. Thanks for your feedback. Please comment before October 31.

Hi everyone! We're in the process of redesigning the profile page on Drupal.org, and we need the community's feedback! You can find the issue at: https://www.drupal.org/node/2281763.

Specific feedback needed:

1. Assuming that we're keeping the current theme, does the organization of information make sense on the page?
2. Is there any new information we should be collecting on profiles? Since this will require refactoring several of the data elements in profiles, we have a great opportunity to allow users to show/share more about themselves.

GSoC 2014 application requests our official social media pages. To be honest, it took me several minutes to track them down. Maybe I missed it, but I could not easily find links to the official Drupal twitter, facebook, g+. On another note, who manages these social media accounts and how do we setup a post about GSoC2014?

If you have been on Drupal.org today, you may have noticed something interesting near the bottom of the page. At some point during the past 24 hours, the millionth user joined Drupal.org!

It's worth taking a moment to think about. A million registered users. 228 countries. 181 languages. And counting.

As Dries pointed out in his keynote at Prague, more than 1,600 people have contributed to Drupal 8. That’s nearly double the number of contributors for Drupal 7.

The Drupal community is truly global and it’s always growing, always moving forward, 24 hours a day, 365 days a year.

A little while ago Jacob Singh and Gerhard Killesreiter did some work to gather some growth statistics about drupal.org. Here's that data and some analysis of it (see attached Open Document Spreadsheet for the raw data and some pivot tables of the data).

• We can see a big bump in registrations in January 2011 - Go Drupal 7.

Abstract

The Version Control API is an engine for Drupal integration with a variety of version control systems. It delivers an interface to these systems for use with various development-oriented modules, like Project.

Problem Summary

Currently on Drupal.org, we recommend the very latest release version of Drupal core as the recommended download. But, it often takes Contrib and Docs much longer to catch up to the point where the system is stable and easy to use from an end user (site builder) perspective. Novice or less skilled site bulders who do not realize this and arrive "too early" get extremely frustrated as a result. Contrib developers are placed under extreme stress to have their modules ported as soon as possible, often long before they are ready to do so and with issue queues clogged by angry demands from frustrated users (instead of useful issue reports by more advanced users). Often by the time many users are able to work with the new release to build and upgrade sites, we are halfway through the next major release cycle. This makes it hugely expensive or impossible for many organizations to keep up. Finally, fixing bugs in the new release is very painful due to the necessity to freeze API changes and have strict backporting rules.

This problem causes a great deal of pain and conflict community-wide.

Proposed Solution Summary

This solution is based loosely on the very successful Debian Linux model. Please see the (brief) introduction to this approach at http://wiki.debian.org/DebianReleases#Introduction if you are not familiar with Debian stable/testing/unstable .

To implement this kind of "testing" release for Drupal would be laregly semantics and rethinking how we refer to releases on drupal.org. It would not require extra work or compromise from anybody, nor changes to existing workflow or versioning. In fact, it improves life and reduces stress for contributors.

See the attached doc for more info. I've had this idea back in January, and don't think I'll have time to implement it myself.

It might make an interesting GSoC project (after some fleshing out), if it meets the eligibility rules.

I believe it is even more interesting with the introduction of git.

It would be suited for a student that has some experience with Drupal and ideally drupal.org.

With DrupalCon Chicago over, the ads on the home page are a little less interesting. We could use some graphic design help. The old site had larger size ads, but we have changed the size and style. The style guide is moving to Drupal.org, but the original is a complete source, including branding.