Contrib module clean up - Status report

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.co
m/ (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/7
9550  
("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

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/7
9550  
("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