Before I try a module or theme, I usually check the Issues list to see how stable and/or well-supported it seems to be. But user ratings of people who have tried the projects would also be helpful. It should also be possible to change one's rating if the project improves. Maybe the ratings could be tied to comments on issues in some way. Even just rolling up some basic statistics to the project page, e.g. number of bugs, issues, & feature requests, and mean time to closure of bugs, issues, & feature requests would help.

I've just tried posting a comment & patch to an issue.
Twice I got no result.
The third time I tried a short test comment. My original comment appeared posted.

Now the issue has all three comments on it.

Hi All,

This is probably me doing something incredibly dumb. I created a Theme, got CVS access and uploaded it. I had the first version as Dev release. Made a few changes and then uploaded the official release. No problem. I have since added a few extra features and committed the changes. I added a new tag before committing ( DRUPAL-5--1-3 ). I added a release, selecting this tag and assumed this would show up as a new official release, however, it showed up as a snapshot. I tried it again with the tag DRUPAL-5--1-4, but got the same.

In the near future, installation profiles will be packaged with all of core, and whatever contributed projects they depend on. In designing exactly how this system will work, there are some unanswered questions that I'd like to get feedback from the community about. I've posted each one as a poll in the installation profile group (http://groups.drupal.org/distributions) so that people can both comment and vote on the various alternatives.

• Should the version strings for installation profiles include the exact version of core they contain?
• Should the file that controls packaging for installation profiles be called ".info" or ".pkg"? (Note: all the other polls and discussions are currently written to assume we'll use .info files for installation profiles).
• Should install profile maintainers have control over where contributed projects are included in the packaged tarball?
• Should maintainers be able to place files in arbitrary locations in the installation profile's directory tree?
• What's the best practice for where modules should be located inside an installation profile?

I find myself browsing the "utility" category on the module page over and over again for certain categories of modules, especially the ones specified below. It seems that it (the "utility" cat) is being too much stuffed with modules that are there just because they didn't fit in well to any other category?

Anyway, below is a suggestion for three new categories, along with a list of modules (taken from the the "utility" cat) that could fit into them. These lists are probably incomplete, but could possibly be a good starting point.

• Navigation
  • (Administration Menu Dropdown, Drupal Administration Menu, Hierarchical Select, Imagemenu, Login Menu, Menu Block Split, Menu Page, Menu Subtree Permissions, Menu Trails, pathmenu, Quick Add Child(?), Quick Admin Menus, Submenu Tree, Sympal book menu, UpAPI, ... )
• Automation
  • (Auto Time Zone, Automated Logout, AutoPilot, Autosave, Bot(?), Comment Mail, DB Cron, Drupal Automated Staging Toolkit, Field Actions, HTML2Book, Multiping, Node Auto Term [NAT], OG Actions, Workflow Wordfilter, Workflow-ng ... )
• Performance
  • (Advanced cache, APC - Alternative PHP Cache, Block Cache, Boost, CacheExclude, Coral Defender, fastpath_fscache, File Cache, Memcache API and Integration, PressFlow Preempt Panels, QueryCache, Result cache, Session expire ... )

Hi All,

as the title says, I can't log in to Drupal.org from Opera. I'm writing this post really as a heads up in case this issue is not known. I've done a search but nothing seems relevant to this site here.

The error I get is that my password is not recognised.

A couple more things - Firefox and IE log in to the site fine. Opera has problems with no other sites that I know of - I can log in to my own Drupal dev site fine from the same Opera session ( and FF and IE).