I hate to chime in with negativity here, but I think the archive as it stands is a really bad idea. To summarize, the only extensions shown there are:
* Ones that *only* had the Joomla 1.5 tag
* No reviews/ratings are shown
Those two things combine to basically have:
* Some of the worst, most unsupported extensions being the only ones listed
* Anyone viewing the archive won't realize how bad some of those extensions are
Simply because an extension supports Joomla 2.5+, doesn't mean it shouldn't be listed in the 1.5 archive. Generally speaking (masterchief's specific example of his backported 1.6 redirect extension and Flexicontent possibly being *the* exceptions that proves the rule), the 1.5-only extensions are likely un/under-supported and likely fully abandoned. The extensions that still support J1.5: K2, Community Builder, our stuff, and many more are specifically excluded.. which means, if you want, for example, a social community, the options are pretty paltry or in some cases (if you're familiar with them), comical:http://archive.extensions.joomla.org/ex ... ommunities
Now, I know that people shouldn't really be looking for 1.5 Community extensions, but if for some reason they are, and that's what they're presented with, it's going to be bad. I'm not the biggest fan of Community Builder, but it is still fully supported on J1.5 and would be a good recommendation for someone needing a community extension, especially over some of the ones now 'promoted' on the archive.
In the scheme of things though, this will be the best method to get people to want to upgrade to J2.5+
To avoid being only negative, my suggestion would probably be to show all extensions that support 1.5, regardless of whether they have 2.5+ support. That way, users can at least see everything that is 'likely' still available for J1.5, not just the stuff that never made it off the 1.5-train.
Just my opinion. For disclosure, we do still support our users on Joomla 1.5 with the last version we released for J1.5 (at the end of 2012), but our newest releases are 2.5+. So, we're in a limbo-y territory of supporting/bug-fixing as necessary, but not developing. Our extensions would be included if my suggestion above was taken, but my reasoning above is still sound (imo at least).
Definitely appreciate all the hard work and thought that has gone into this, and thanks for listening to all the feedback,
Alex Andreae | SourceCoast Web Development
Developers of JFBConnect - The easy Facebook integration suite that's used
on the JED!https://www.sourcecoast.com/