Remove 4.7-only modules from public view

-1, at least until we do not have separate views for Drupal users and developers. There are 4.7.x modules that have not been ported yet, but may be useful for a developer, because most modules are not that hard to port.

+1.. I don't think any modules which haven't yet been ported from 4.7 will EVER be ported from 4.7... I would say leave them in CVS and leave clear instructions on how to get them from there for people who still need access to those modules for one reason or another.

I think anything which reduces the clutter/confusion on the modules list is good.

@beeradb: I'm currently messing with a trying to port a 4.6 module, and I believe the FOAF module hasn't been ported for 5.x but that James have agreed that it is time to bring it back for D6. And I'm sure there are other modules out there skipping 5.x (isn't Creative Commons doing this? I believe there was at least one of the other modules I (used to) keep track on that did/does this...).

Anyway, +1 for removing from default listing. But it would be nice if they were still accessible from the drop-down.

I'm also -1. There are still 4.x sites that may wish to obtain additional modules for their long running production sites, and there may be many other reasons to put togther a 4.x system to provide historical functionality. Maybe a file got corrupted or patched badly and needs to be restored.

I don't care if they are invisible on the modules page, but they should be obtainable. However, the modules page is the best place for them. Those recovering a hosed production site are going to be in a hurry and will curse you if you make it too hard to get their site back to life.

-1 for removal.

Old module can be taken over by those who need them, or provide starting points to more current modules.

CVS alone is not visible/accessible to the vast majority of people, and having the projects listed provides the visibility needed for those looking for starting points and such ...

There's plenty of reasons for people to need modules for old 4.7 sites or want to revive them. However, these are less than the reasons for hiding them from those default listings - those categories and the main module list are massive, and removing modules that have no relevance to 99% of Drupal sites is low hanging fruit compared to other ways of dealing with the same issues (module ratings etc.).

So let's remove them from the default listings but keep the project/release nodes published - then there can be an unfiltered list linked from the handbook etc. Is there an easy way to do this though?

Queue Cleanup

It seem that the API filter on the project release pages takes care of this. Marking as fixed as the 4.7 releases aren't in public view anymore.