Low difficulty

What's your idea?

We can make Drupal more SEO friendly by converting the URL of drupal.org, like - https://drupal.org/node/53933 to https://drupal.org/drupal-theme-problem. We can implement this by using Pathauto module and transferring all number URL to understandable URL.
It is found that when we search drupal issue in google, some other website are come first than Drupal.org.

What are the benefits?

• We will come to drupal.org for Drupal related problem and not go to other websites.
• Increased participation in Drupal forums

What's your idea?

Add user pictures to posts and comments on drupal.org

What are the benefits?

Drupal is a community of people, it would be nice to expose this more. Bringing people to the surface would remind each other that we are human. The issue queue is a stressful place, we should be building relationships not breaking them down.

It would also increase recognition at Drupal meet ups, camps, and drupalcons.

What are the risks?

I'm not sure. Increased bandwidth? We would need to ensure images are cached.

What's your idea?

Lets put a good looking badge on project pages who's maintainers are doing a stellar job with release management. They need to be given the cred they deserve and users will be able to find their projects more easily too.

The #D7CX pledge, http://cyrve.com/d7cx, for modules to be ready for Drupal 7 was quite a success in the sense that a lot of contrib maintainers signed up to it. Unfortunately only a fraction of those projects where ready when Drupal 7 launched, despite the long delay.

What's your idea?

Create an IRC client to be used on Drupal.org, giving users the ability to participate on IRC directly on Drupal.org.

What are the benefits?

Opens up IRC to users who may not know how to access IRC, or even know that it exists. We could maybe set up a way of syncing Drupal.org usernames with IRC.

What are the risks?

Overrun of users on IRC channels.

How can we measure the impact of this idea? (metrics)

Analytics on the embedded chat page.

Who directly benefits from / will use this improvement? (target audiences)

What's your idea?

Add a "Need Maintainers" page on drupal.org. This page would consist of two parts: First part would be written by the drupal core team, and would highlight core components that need maintainers/coordinators; Second part would contain a list of contrib modules that have a "seeking maintainer" status.

What are the benefits?

This would help fill in the gaps, as people join and leave the drupal community. Right now, this information is broadcast through announcements or posts that reach drupal planet, and then go out of sight, and can easily be missed. Directing volunteer developers to contrib modules that need maintainers helps their progress, makes contrib more reliable, and makes a drupal 8 port more likely.

What's your idea?

For anyone who hasn't contributed to any modules or themes but has just participated in Drupal core, their profile page looks pretty empty and it doesn't show any mention about their involvement in core.

I agree with xjm here and quoting again:

A Drupalist's d.o profile is essentially his or her résumé.

What are the benefits?

Attract and motivate more contributors to core.

Who directly benefits from / will use this improvement? (target audiences)

What's your idea?

The community is doing an amazing work maintaining, improving and adding to the *.d.o infrastructure. But it is very much feature focused and where features often are looked at and implemented in isolation and from a technical point of view.

*.d.o has, according to https://drupal.org/home, a cool million users. To provide a great UX for all of them and where they can focus on getting things done is without a doubt a challenge. A challenge I feel isn't really being taken completely serious.

What's your idea?

Make popular projects easier to find from the header-search box. We could add a facet to solr for project usage and adjust that up as a relevancy factor so that items with high usage are higher in search results. When someone filters the facets to Projects we could also ignore whatever sort they have used so far and change it to be by install count.

What are the benefits?