Contrib module clean up - Status report
I've started at Z and gone through W with the page filter set to "all". I tagged, !--break'd, and cleaned up where I could. These are the remaining issues I see with the modules in those letters: zippy images - Only release is cvs. Needs a better description Z39.50 Search - Last release is 4.6. Ystock - Last release is 4.6. xstatistics - Needs a better description but I don't get the module well enough to write it. workspace - Description makes good teaser, but could use more meat on main page worklog - Has a 4.7 version but default is cvs workflow - Has a 4.7 version but default is cvs worldfilter - Has a 4.7 version but default is cvs wiki404 - Only release is cvs. Last update Apr 2006. Could use a better desc. if it's not abandoned. whatsrelated - Last release is 4.6. Defaults to cvs. wgHTML - Last release is 4.6. weight - Description says "Module now works with both 4.6 and 4.7 (CVS) versions of Drupal." cvs is default. 4.6 version not listed. Weekly node listing - Has 4.7 version but 4.6 is default Webserver Auth - Has 4.7 version but 4.6 is default WebMedia - Only release is cvs. Screenshots require logging in to view. Weblink - Desc says "This module is discontinued after CVS/HEAD" Last version is 4.6. Possibly change that note to be clearer with versions? webcomic - Has a 4.7 version but default is cvs Weather - cvs default. 4.5 only other version. Demo page not found. Project owner email is listed as drupal-devel@drupal.org waypath - Only release is cvs. Last update Apr 2006 A lot of them need the default download changed. I didn't do that because I felt that's something the maintainer should do in case there's a reason it's set as it is. Some of the modules haven't been updated since 4.6 or before. If these have been abandoned, I suggest putting a note as such in the description. If you see any of your modules here, I'd appreciate it if you could either make the change or let me know why it shouldn't be changed. When I get through all the letters, I'll see what modules still have issues and contact the maintainers directly. Thanks, Michelle
Michelle Cox wrote:
A lot of them need the default download changed. I didn't do that because I felt that's something the maintainer should do in case there's a reason it's set as it is.
In most cases the reason probably is "maintainer forgot to set it". Feel free to change it to the latest release, it can easily be changed back.
Some of the modules haven't been updated since 4.6 or before. If these have been abandoned, I suggest putting a note as such in the description.
It is always difficult to guess wether a module is truly abondoned. I myself have modules that don't yet have a 4.7 release since I don't use them myself and there aren't enough patches. But if for example the latest commit is like one year ago on the 4.6 branch and nothing on HEAD since then, it is safe to assume it won't be updated any time soon and maybe never. Adding a note about this will save people from wasting their time with it. Feel free to add such notes, they can also easily be removed. Add something like "this module hasn't been updated in a long time and the author isn't very responsive. It is possible the module is abondoned. The management." Cheers, Gerhard
How difficult would it be to patch project.module to display the date of the last commit and/or release on the teaser page for each module, next to the "Download", "Find out more" links (or next to the module title)? The last release date is shown on the full project page already so it seems like automating this functionality would be best, rather than a one-time update. I will volunteer to code a patch if it would be helpful and/or if Derek is busy. -Chris Gerhard Killesreiter wrote:
Michelle Cox wrote:
A lot of them need the default download changed. I didn't do that because I felt that's something the maintainer should do in case there's a reason it's set as it is.
In most cases the reason probably is "maintainer forgot to set it". Feel free to change it to the latest release, it can easily be changed back.
Some of the modules haven't been updated since 4.6 or before. If these have been abandoned, I suggest putting a note as such in the description.
It is always difficult to guess wether a module is truly abondoned. I myself have modules that don't yet have a 4.7 release since I don't use them myself and there aren't enough patches.
But if for example the latest commit is like one year ago on the 4.6 branch and nothing on HEAD since then, it is safe to assume it won't be updated any time soon and maybe never. Adding a note about this will save people from wasting their time with it. Feel free to add such notes, they can also easily be removed. Add something like "this module hasn't been updated in a long time and the author isn't very responsive. It is possible the module is abondoned. The management."
Cheers, Gerhard
On Thursday 26 October 2006 14:58, Chris Kennedy wrote:
How difficult would it be to patch project.module to display the date of the last commit and/or release on the teaser page for each module, next to the "Download", "Find out more" links (or next to the module title)?
If you click on "View other releases" when on a module's (theme, etc.) home page, you will get a list of all releases along with the "First released" date and the "Last updated" date (if it changed since release. Is that what you are looking for? -- Jason Flatt http://www.oadae.net/ Father of Six: http://www.flattfamily.com/ (Joseph, 13; Cramer, 11; Travis, 9; Angela; Harry, 5; and William, 12:04 am, 12-29-2005) Linux User: http://www.sourcemage.org/ Drupal Fanatic: http://drupal.org/
On Oct 26, 2006, at 2:58 PM, Chris Kennedy wrote:
How difficult would it be to patch project.module to display the date of the last commit and/or release on the teaser page for each module, next to the "Download", "Find out more" links (or next to the module title)?
not terribly hard, but i think http://drupal.org/node/79550 ("Automate gathering of quality metrics") is the way to go (as mentioned by others). which metrics should be displayed in the teaser listings vs. on the project node itself (and how they should all be presented) should be hashed out in that issue, IMO.
I will volunteer to code a patch if it would be helpful and/or if Derek is busy.
y'all can pretty much assume i'm always busy... *sigh* thanks, -derek
participants (5)
-
Chris Kennedy -
Derek Wright -
Gerhard Killesreiter -
Jason Flatt -
Michelle Cox