https://www.drupal.org/project/project_drupalorg?f[0]=&f[1]=&f[2]=&f[3]=...
has lots of sandboxes, which aren't 'Drupal.org project'.

Remaining tasks:

  • Make a list of all sandboxes which need to be move, the list should include project id and content type it needs to be switched to.
  • Move projects via db query

Original report

http://drupal.org/project/drupal.org%20projects?filters=bs_project_sandb... shows a ton of modules that don't belong here, eg Commerce SecurePay, jQuery UI selectmenu, and so on.

Comments

lisarex’s picture

lisarex CreditAttribution: lisarex commented

Agree! It's just a simple case if mistagging.

Ones to remove:
http://drupal.org/project/maintenance_theme
http://drupal.org/project/permission_watch
http://drupal.org/project/selectmenu
http://drupal.org/sandbox/jazzlegs/1085566

etc etc.

There's also an issue for creating an "Other" category for things that aren't falling into an exact category:
#322626: META: Package and version non-modules for download

lisarex’s picture

lisarex CreditAttribution: lisarex commented

I also propose we rephrase the label 'drupal.org project' to '*.drupal.org site project' to see if that clears things up?

joachim’s picture

joachim CreditAttribution: joachim commented

BTW, I'm not sure how project node authors are managing to mis-tag these in the first place -- I tried editing one of my project nodes and didn't see that tag!

Damien Tournoud’s picture

Damien Tournoud CreditAttribution: Damien Tournoud commented

I just did a couple of those. Still a long way to go :)

lisarex’s picture

lisarex CreditAttribution: lisarex commented

@joachim, it's actually the thing they select when they create a project. Editing is probably a permissions thing (Damien and I are admins).

Thanks Damien, I'll reclassify some of the ones that are definitely modules.

http://drupal.org/sandbox/liorkesos/1126176 and others like that should get the 'Other' classification, when we get consensus on it.

joachim’s picture

joachim CreditAttribution: joachim commented

Ohhh right! I see it too when I create a project, but I can't change it on existing projects.

In that case, it could definitely do with a label tweak. '*.drupal.org site project' sounds good to me. I wonder if we can use the d.org customizations module to add description text to that radio button saying 'only use this for code that runs on one of the d.org sites'?

joachim’s picture

joachim CreditAttribution: joachim commented

I've filed a patch for that here: #1241788: Hide the 'Drupal.org projects' project type on the create project node form

lisarex’s picture

lisarex CreditAttribution: lisarex commented
Status: Active » Needs work

I've cleaned up a few more. We'll keep this open til the other issue referenced in #7 is done. :)

apaderno’s picture

apaderno
he/him
Primary language Italian
Location Brescia, 🇮🇹 🇪🇺
CreditAttribution: apaderno commented
Title: remove the 'drupal.org project' category from modules that shouldn't have it » Remove the 'drupal.org project' category from modules that shouldn't have it
Category: bug » task

I notice that there are many sandbox project that use/used that taxonomy term.
Should not we consider blocking that taxonomy term for some roles? I am sure that most of the users who use it should not, and it should be limited to specific roles. Considering that there is rarely the need to use it, maybe only site maintainers should set it.

joachim’s picture

joachim CreditAttribution: joachim commented

That's the aim of the new patch I've just filed at #1241788: Hide the 'Drupal.org projects' project type on the create project node form :)

John_B’s picture

John_B CreditAttribution: John_B commented

This is interesting to me as I am relatively new here. This move would remove some confusion. There is one module I like a lot, but it is so small and simple and I have no idea why it qualifies as a project.

However, some people are going to be disappointed. I have been hanging around on the site, and attended Drupal con, but there is no way to work out easily how decisions are made.

It looks like there are some admins who can make decisions, and there are respected core & major module developer, people who have earned respect, who will be listened to. But now Drupal is so big, with would-be newcomers like me, it would be really helpful to have a quick way to find out who are the decision makers, and how to have a predictable channel of communication.

I think about contributing more. But If one admin takes a decision on a pet project / sandbox / etc which I don't like, there is nothing I could do about it. They might be right, but sometimes there are going to be bad judgements, and occasionally there are sure to be personal politics. It surely worked with a small community where you can earn you way to the inner circle fairly quickly. With a mature and large community like Drupal, a more transparent structure would help it to grow.

I get it that decisions makers are volunteers, and have earned their position many times over. But when someone in the outer circle is upset by a decision, it can look arbitrary, like, 'That's my decision, take it or leave it, and if you don't like it go away, I don't have time to keep talking.' Nobody is going to like losing Project status, but they will be more accepting if it's obvious that there is a fair and functional system of principles, and of getting a second opinion. That is ultimately good for Drupal, and good for everyone including (especially) those at the heart of this hugely growing community.

BTW thanks to anyone reading who has worked to build the fantastic Drupal project and product :-)

joachim’s picture

joachim CreditAttribution: joachim commented

I think you may be confusing the 'Drupal.org project' term with something it's not...

When you go to create a project, you can mark it as being a module or a theme. There are other categories too, and one is 'Drupal.org project'. This is intended for projects which are specifically to do with running the d.org site -- custom code for this site, basically.

The problem is that a lot of projects which are just modules have been categorized incorrectly as this because people don't understand the meaning of that term.

You're still welcome to contribute on any of the d.org projects; they remain public. But you won't be able to create one (and nor will I for that matter). But then I wouldn't need to; if you need to create a new project for d.org code, then you probably are a person who has access to *put* code on the d.org servers...

Just to clarify: nobody is losing project status! :) This is about projects being correctly classified, and most projects people create here should be 'module' or 'theme'.

greggles’s picture

greggles
he/him
Primary language English
Location Denver, Colorado, USA
CreditAttribution: greggles commented

@John_B - http://drupal.org/node/1293124 may be interesting to you on the topic of how change to drupal.org is made.

lisarex’s picture

lisarex CreditAttribution: lisarex commented

I've filed #1982692: Create a separate 'project type' tag for Community related matters to deal with the ones that aren't code but aren't *.d.o.

I've cleaned a few more out:
http://drupal.org/project/node_webform_access
http://drupal.org/sandbox/madmatter23/1253382
http://drupal.org/sandbox/bryrock/1278222

But there's still quite a few more.

lisarex’s picture

lisarex CreditAttribution: lisarex commented
Issue summary: View changes

Per tvn, there are different content types for different project type, so it's not easy to reclassify them anymore. Instead, you'd have to create new project of a proper type, move code there and delete old one. I'm asking project authors to do this.

drumm’s picture

drumm
he/him
Location NY, US
CreditAttribution: drumm commented

This issue should be merged into #1166546: Projects are assigned to the wrong category

tvn’s picture

tvn CreditAttribution: tvn commented
Title: Remove the 'drupal.org project' category from modules that shouldn't have it » Change category for 'drupal.org project' sandboxes that shouldn't have it
Project: Drupal.org site moderators » Drupal.org infrastructure
Component: Site organization » Other
Issue summary: View changes

#1166546: Projects are assigned to the wrong category fixed full projects, which were wrongly created as D.o projects. We still have 270 'd.o projects' sandboxes. To clean them up someone needs to create a list like here: https://www.drupal.org/node/1166546#comment-9106769

irinaz’s picture

irinaz CreditAttribution: irinaz as a volunteer and at Fibonacci Web Studio commented

@tvn, what needs to be done to create this list of 270 'd.o projects' sandboxes? thanks, Irina

drumm’s picture

drumm
he/him
Location NY, US
CreditAttribution: drumm at Drupal Association commented
Status: Needs work » Fixed

I think since #1166546: Projects are assigned to the wrong category did a deeper clean, we can call this done. Any future projects that should be moved should have a fresh issue opened for them.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.