<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
</head>
<body bgcolor="#ffffff" text="#000000">
Moshe Weitzman wrote:
<blockquote
id="mid_6117a7500805090901m4ba67defmb082860b5bf3960b_mail_gmail_com"
cite="mid:6117a7500805090901m4ba67defmb082860b5bf3960b@mail.gmail.com"
type="cite">
<pre wrap="">I setup such a user called 'unmaintained' a few years ago and dries
blocked him. he did not like this process for dealing with abandoned
modules. see <a class="moz-txt-link-freetext" href="http://drupal.org/node/103968">http://drupal.org/node/103968</a>. i still think it is a good
idea, or at least one that can start delivering usefulness in 5
minutes.</pre>
</blockquote>
Ok, I've pondered my previous comment and here's what I think would be
helpful for end users of the modules and site : <br>
<br>
There has to people other than those who use Drupal.org on a daily
basis as either maintainers or developers to know right away when a
themes or modules are ready for production or in development and either
live or abandoned. <br>
<br>
Right now the first issue, DEV vs PROD, is only taken care of when
looking at the MODULES and THEMES list/index pages in unfiltered mode.
If you filter the page (as I do) based on the version of Drupal you are
working on, the pages loose that very important and time saving visual
cue. And I say that as someone who spent last night 3 hours combing
through the unfiltered modules list. <br>
<br>
Now, here's what I would have LOVED to have seen on that page last
night : <br>
<br>
1. I'd like to see the filtered list of MODULES not lose the distro
information when filtered by Drupal version. <br>
2. I also would like the list of modules broken down into MAINTAINED
and ABANDONED modules. <br>
<br>
If you are not going to use VIEWS to break down the MODULES and THEMES
pages into maintained and abandoned, then why not implement a visual
cue that helps people look at an entry and immediately know whether to
move along or not. Hence the idea of a "stamp", "watermark" or "button"
image saying "ABANDONED" or something to that effect. <br>
<br>
Finally, at the top of both the MODULES and THEMES pages, you can put a
quick disclaimer and/or explanation stating that "ABANDONED" doesn't
mean all is lost but that it's an opportunity for an end-user to bring
in another developer to take on the project, yadda yadda. <br>
<br>
/liza<br>
<br>
<br>
<div class="moz-text-html" lang="x-western"> <font
face="Helvetica, Arial, sans-serif"><br>
<br>
<br>
<br>
<b>Liza Sabater, Publisher<br>
</b><a class="moz-txt-link-freetext" href="http://culturekitchen.com">http://culturekitchen.com</a><br>
<a class="moz-txt-link-freetext" href="http://dailygotham.com">http://dailygotham.com</a><br>
<a class="moz-txt-link-freetext" href="http://lizasabater.com">http://lizasabater.com</a><br>
<br>
</font><font face="Helvetica, Arial, sans-serif"><b>Twitter</b><br>
<a class="moz-txt-link-freetext" href="http://twitter.com/blogdiva">http://twitter.com/blogdiva</a><br>
<br>
<b>FriendFeed</b><br>
<a class="moz-txt-link-freetext" href="http://friendfeed.com/liza">http://friendfeed.com/liza</a><br>
<br>
<b>Facebook<br>
</b><a class="moz-txt-link-freetext"
href="http://www.facebook.com/profile.php?id=502696333">http://www.facebook.com/profile.php?id=502696333</a><b><br>
</b><br>
</font>
</div>
<br>
<br>
<br>
<br>
<br>
</body>
</html>