Closed (fixed)
Project:
Contrib status
Component:
Miscellaneous
Priority:
Major
Category:
Task
Assigned:
Unassigned
Reporter:
Created:
12 Sep 2011 at 11:54 UTC
Updated:
1 Oct 2015 at 10:15 UTC
Jump to comment: Most recent
Thread to collect feedback on http://drupalcontribstatus.com/. I'll try and spin suggestions off into sub-issues and/or fix them.
Comments
Comment #1
moshe weitzman commentedAdd a 'Last Updated' timestamp somewhere so we can see when you cron job fails :)
Perhaps link to Usage report for each release so one can gauge how usable a given release is.
"32 of 60 projects ported to Drupal 7!". => "32 of 60 projects released for Drupal 7!"
Comment #2
webchickCool, did the first and third one. There wasn't really a great place to put a usage link for each project, and in clicking around, I'm not sure the data is all that helpful. Projects with stable releases have much higher usage than projects without. SHOCK. :)
So instead, I just linked to the main usage stats in the first paragraph, and also added a blurb about how to take over an abandoned project.
Comment #3
effulgentsia commentedAwesome idea to have this site.
What does 32 of 60 refer to? I count 26 rows with checkmarks (full releases) and 37 with a green background (release candidate or full release).
Comment #4
webchickRC is not quite a release, so it doesn't count towards the 32. But it's close enough that people shouldn't be scared of it, so I coloured it green. :)
Comment #5
effulgentsia commentedSo is the code that's generating the number "32" buggy, since I only count 26?
Comment #6
webchickAh! It counts modules moved into core as "released" as well. Which for the most part is accurate, though CCK and Token kind of break that. Hm.
Comment #7
gregglesThe table lists the "Maintainer" which can be misleading. Listing committers from the past year would be ideal, IMO. In case it helps, https://github.com/greggles/epm_project_management has some code for parsing project pages to get things like maintainer count.
The token module is "in core" but the 7.x version is pretty important if you want to get a UI or do fancy stuff with it.
Comment #8
David_Rothstein commentedNeat page!
The "In core" label may be a bit misleading as a binary setting. In addition to the Token module example @greggles mentioned above, there's also:
Maybe there needs to be an "In core (mostly)" label, or something along the same lines but better-worded :)
Comment #9
longwave+1 to greggles' suggestion of improving the Maintainer column (mostly because I co-maintain Ubercart, and Andy_Lowe is listed as maintainer even though he has never made a commit)
Perhaps token and CCK's "in core" text could be linked to separate pages explaining which bits are now in core and which aren't.
Comment #10
mstrelan commentedUh oh, I'm getting an error.
Warning: Division by zero in theme_contrib_status_report() (line 247 of /mnt/www/html/webchick/docroot/sites/all/modules/contrib_status/contrib_status.module).
Comment #11
jami3z commentedGood snapshot, but ive counted the list several times, added it up different ways and I cant make sense of the figures equaling 34 of 61 ??? Also doesn't "ported" mean that it is in someway available in D7, so wouldnt that mean pretty much all of those modules have been ported to D7 ?
Comment #12
webchickSorry about #10. I was dorking around with caching backends. Should be fixed now. :)
For #11, the key could definitely stand to be more clear. Alpha/beta still means "in development," at least to most normal humans. RC does as well, but it's "green" enough for folks to at least start testing in earnest, so the rows are coloured such. However, the only ones that we can really count as fully "ported" are the X.0 releases, the ones with D7 versions that have X.0 releases, and the ones moved into core. This is also not totally precise, but provides a fairly decent picture of the state of things.
So the goal is to move the alpha/beta/rcs in that list of 60 modules to stable releases, because until that happens the wider perception is still going to be that D7 is not "ready." :\
Also, I actually have no idea how that 60 became 61. :P Will have to log in and take a look.
Comment #13
gboudrias commentedThanks for the site, it's neat.
Just wanted to report that I'm still geting the same error as #10.
Comment #14
eli-tJust thought you'd like to know I've just received somewhere around 1000 of:
Notice: Undefined index: in update_xml_parser->end() (line 256 of /mnt/www/html/webchick/docroot/modules/update/update.fetch.inc)
in the message section on each page load.
The rest of the page looks fine.
update error messages have gone now.
Comment #15
webchickhaha, yeah, sorry. I was futzing around with cron and stuff trying to fix the "division by zero" error.
Hopefully all of those weird bugs should be gone now. :) Thanks for the reports!
Comment #16
pcambraNote that Path redirect is Redirect for D7
Comment #17
AdrianB commentedSeems like those last 10 precent will take 90 percent of the time... :)
Two things about drupalcontribstatus.com:
1) drupalcontribstatus.com says Simplenews is 7.x-1.0-rc1 but all I can find is 7.x-1.0-beta2.
2) As pcambra mentions above, Path redirect should be replaced with Redirect (wich is 7.x-1.0-beta4 since last year).
Comment #18
gregglesThe link for metatags blocker issues goes to http://drupal.org/project/issues/search/metatags/?issue_tags=D7+stable+r... but it has been renamed to just metatag, so it should be http://drupal.org/project/issues/search/metatag/?issue_tags=D7+stable+re...
Comment #19
eli-thttp://drupalcontribstatus.com/ is now squatted so I think we can close this :)