<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
</head>
<body bgcolor="#ffffff" text="#000000">
As an end user who deals with LOTS of modules, may I suggest one giant
ribbon/sticker image on the module's project that says "UNSUPPORTED"
... kind of like a "winner" ribbon but for the opposite intent and
meaning. <br>
<br>
I know, I know, it is the least techie solution but ... <br>
<br>
/ liza<br>
<br>
<br>
<br>
<br>
<br>
Greg Knaddison - GVS wrote:
<blockquote
id="mid_3861c6770805091320v6e557ca2gb8dcd1b98e48dbdb_mail_gmail_com"
cite="mid:3861c6770805091320v6e557ca2gb8dcd1b98e48dbdb@mail.gmail.com"
type="cite">
<pre wrap="">On Fri, May 9, 2008 at 4:55 PM, Derek Wright <a class="moz-txt-link-rfc2396E" href="mailto:drupal@dwwright.net"><drupal@dwwright.net></a> wrote:
</pre>
<blockquote id="StationeryCiteGenerated_1" type="cite">
<pre wrap="">Right. Big -1 on this abandoned user hack.
</pre>
</blockquote>
<pre wrap=""><!---->
I agree with you and catch that the releases for these projects should
also be marked as unsupported and/or unpublished in addition to giving
more UI to end users letting them know that it's unsupported.
But, there are two goals with this change:
1) A visual cue to the user. This was an afterthought and not nearly
as important in the motivation for this "hack" as
2) Helping people who, at one point for reasons that made sense at
that time, have a project page assigned to them and no longer want to
have it assigned to them. I think that we should let our maintainers
off the hook if they find themselves in that position.
I wanted to solve problem 2 and don't see how #99466 gets us there.
Regards,
Greg
</pre>
</blockquote>
<br>
</body>
</html>