Vote for the next feature

Screenshots: Bah, lots of projects aren't visual projects.

Versions: Call them Releases and yeah, this isn't a bad idea.

Platforms: Not a bad idea.

Categorization: That's what tabs are for. But really, if you want to, just make some special tags like '@db' or '@db::front-ends' or something like that.

Advanced Project Search: Barring problems with how projects can be classified incorrectly if they have dependent files (say, clients in multiple languages)... also not a bad idea.

But really, please allow us to specify some files to NOT count... it not only lets us better shape how our project is viewed, but also removes some processing strain for files we don't want considered as part of our project like bundled dependencies.

Would it be an option to use CVS tags to identify different releases?

What about darcs and mercurial support? Seriously, that's what everybody is waiting for!

+1 for darcs/mercurial - there are too many projects out there that Ohloh doesn't track.

Also, tracking of branches (on top of trunk) has been a very popular request (and much more urgent than, say, project categorization IMO). Once Ohloh is capable of multiple branch tracking, using tags for automatically identify releases sounds ike the natural thing to do.

+1 for screenshots, for projects that are visual, it's the #1 thing people click on.

What about building custom stacks? Maybe someone of them can be shared. I'd like also to view Code analysis on them.

Just my 2 cents...

Hi Jason, with Code analysis I mean what you see by clicking on Code analysis for a single project (line counts, language pie chart and such).

I don't know if it is easy or not (or ever if it is possible) to join the code analisys data of all the projects on a stack... anyway this was my suggestion.

Following up on the idea of project releases, it would be great to handle this like freshmeat does and aggregate a list of recently released software on the frontpage. It would also be a nice way to get more developers involved.

Specifying platforms, etc. could maybe be done with default tags.

That way, projects would have predefined tags and freeform tags, and we would no longer see projects with "macosx, mac osx, osx, mac" but simply one selectable "macosx" tag.

This also wouldn't restrict developers to having to define their projects the way you lay out.

It would just make the tags saner the soft way: "You can choose any tag, but we recommend selecting among the following ones: ... "

Then the developers could add special tags for their subcommunities, but the general tags would fit better.

Also it might be useful to aggregate very similar tags at the time when you create a default tag (and allow developers to add the old tags again, if they really prefer the nonstandard tags).

Example: When you create the default tag "macosx", all similar tags like "mac osx, osx" could just be changed to it.

(beware though that "mac" could mean "mac os 9" "mac os 8" or "macosx")