Low difficulty

What's your idea?

All module maintainers to define related projects on projects.

Use this data to populate the "Related projects" block using these and any back links from other projects "Related projects" fields grouped by # references and order # ref descending.

If none found, then fallback to the automated one.

What are the benefits?

To actually make this block useful.

Two existing examples that show the maintainers suggestions beside the related projects block.

Menu Node API - https://drupal.org/project/menu_node

What's your idea?

Changing the Tab names or Moving the sign up button on Top?

What are the benefits?

At first glance if i want to sign up i click the TAB believing it to be a link to sign up.

And seeing there's no sign up button in the "Sign Ups" Tab i figured it's a closed event and move on.

What are the risks?

NONE clearer understanding on how the tab works.

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

Non-Drupal users ease of sign up and want to skip reading the details.

What's your idea?

I can't believe I didn't think to mention this one already...

Drupal 8 is making extensive use of 3rd party components, pulled in via Composer from Packagist.org. This is good.

Drupal 8 is checking all 3rd party components into our main repository, including the generated Composer files. This is bad. It's directly contrary to all Composer best practices, and makes any attempt to update our dependencies consist of 500 KB patches at least. This is not how it should work.

Why are we still doing that? Well, because

What's your idea?

Force full project review for ALL projects, not one time only per user.
Today if a user gets a project approved to be a full project the user gets a role which can promote ANY project in the future without review.

This should be changed force reviewing ALL new projects, instead of giving this role to the user.

What's your idea?

Currently, projects get assigned their final namespace during the 'promote to full project' operation.

This proposal suggests that the 'shortname' field be exposed on sandbox projects, where it be made editable by the project owner but read-only to all other users. Validation logic on this field would ensure that the chosen shortname does not conflict with any previously established "full" projects, and could potentially also warn users about namespace conflicts with other sandbox projects (but still allow the field to be saved).

What's your idea?

We have to create drupal.org search more powerful and relavant.

I have noticed when we search for module - Google search result is more accurate than drupal.org website inbuild search.

For Example - Lets serch for Insert Module - In drupal.org, you can see many insert modules are coming, but only "Insert" module is coming after many modules. But in Google, the first one is only "Insert" module.

Now, if you click on modules tab, we are seeing sort by Relevance. Now change it to sort by Most Installed. Still the insert module is not coming in the first.

What's your idea?

There are a number of projects that have NO release, NO activity and are years old that should either be moved to a sandbox, or outright deleted. These were created pre-sandbox days, although some have been created recently.