project module

I have just re-discovered the http://drupal.org/project/issues/statistics in d.o's user menu. Below of the overall project statistics you get a nice overview of total issues by project and status. After clicking through the pages and changing the table sorting to Total, and while still looking at rather meaningless statistics, this idea crossed my mind:

The giants of the project module and Drupal.org's CVS/packaging system (dww, hunmonk, aclight) plan to add the ability of installation profiles to have their modules packaged with them, I understand. This will be a huge step forward for their value to end users.

A new website just opened to the public today called DrupalModules.com. Go check it out!

There are some very cool features, something that the Community has needed for a while.

http://drupalmodules.com/

Hi there,

I am working on a drupal project and need help from an expert drupal developer. The idea is to create a number of custom modules. I would like to work together with some one that has good experience and knows the drupal framework very well. This is a side project, not a full time project. The project has huge growing potential. I will explain all the details in person.

If someone is interested please contact me via my personal contact form at http://groups.drupal.org/user/15781/contact.

Thanks

Project "Give" is a concept for a social networking site that allows users to trade services and goods with other users. Users are rated by their contributions and rewarded by their peers via a wish list.

Key components:

1. Rich user profile and permissions
2. User groups
3. Geo-caching of wish list items as well as services and goods donated to the collective.
4. An auction bidding system
5. User ratings

Special consideration given to those with a secondlife.com avatar.
This IS a PAYING job.

Some of you may have seen Kieran Lal's pitch to the Drupal community to help get Derek Wright (dww) and Chad Phillips (hunmonk) to DrupalCon Boston to work on the crucial Project* modules, and many of you chipped in to help Derek and Chad reach their goals. But the project* team can still use your help!

Adam Light (aclight on Drupal.org) is also trying to get to DrupalCon to work on Project*, and trust me, it will be worth ten times whatever you can give. I have only had limited interactions with Adam, who I don't know personally, but even those limited interactions have blown my socks off. Adam was a tireless volunteer for the GHOP program, and his work with these students was truly out of this world (take a look at any of the GHOP issues that Adam helped out with and you'll see what I'm referring to). As Webchick noted on her blog post asking for help for Adam and Jimmy "boombatower" Berry: "Adam was the one primarily carrying the torch during the latter half of the GHOP program, and was critical to ensuring its success."

I happened upon a blog post Adam wrote in which he requested assistance on the DrupalCon Boston feed, and I think that Adam is a bit too modest to post his request here, so that's why I'm writing this. Here's how Adam describes his contributions to Drupal:

I found this coming in from Drupal planet http://www.tech-wanderings.com/drupal-nofollowed-too-pervasive.

Greg Holsclaw talks about how nofollow attributes could be hurting Drupal (rel=nofollow being a well intentioned way of deterring spam. Something that has managed to keep the ratio of spam to real content on the web down to a respectable 10:1 :P) Basically, he points out that most internal links on drupal.org get the nofollow attribute attached to them.

Greg makes a number of good points, but I think the two most important are:

I've been evaluating solutions for Project management (for the duration of this post, that includes what i describe as project, issue, ticketing, case tracking, and pretty much anything that falls in that category) solutions with Drupal, over a year actually. I keep being enticed by the features of each individual solution, and new promises that are announced for each module(s) and trying them out and coming to the same conclusion with each of them. And yes, all of them seem to have the same problems that I'm hitting repeatedly.

I've been spending most of the last week working on the project_usage.module. I got a copy of the usage data that's been reported to Drupal.org and spent some time fixing bugs (#167074) and making some small improvements (#167079, #167048). My big goal has been to get some code together to make the usage data visible (#165380). I've attached a few screen shots to show how it works.

As of about 2pm PDT Drupal.org has been tracking the module usage. #128827 has been committed to the project module and installed on d.o. There's a follow up issue to make this usage data visible to users (#165380). I've added support to the metrics module to factor that into the score.
I'm not sure if the metrics module will be installed on d.o until the current database troubles resolved.