Say Hello To My Little Friend (or How To Abandon a Module)
Hi, Sometimes modules get abandoned because they are no longer needed or no longer make sense. Features get added to core, CCK+Views come along and deprecate whole swaths of modules, etc. People need to know that a module has been abandoned, which is usually best communicated on the project node itself. But, if you've done that and want to make it more clear (and, maybe, stop getting contacted to help with the module) what can you do? http://drupal.org/user/291168 The "Abandoned Modules" user. He's too busy sunning himself in Antigua to care about his modules. He's unemployed and loving it. Give him your dead modules, won't you? If you are the author of a module and would like it to be assigned to this user and can't do it yourself, file an issue about it: http://drupal.org/project/issues/webmasters Note: except in rare situations, this is not for just modules that need a new maintainer. You should find that some other way. The "Abandoned Module" owner is like a graveyard. Thanks, Greg -- Greg Knaddison Denver, CO | http://knaddison.com World Spanish Tour | http://wanderlusting.org/user/greg
Brilliant! With great euphoria I have ditched all of my abandoned modules. Hopefully this will speed their uptake by their future new maintainers. Robert Douglass On May 9, 2008, at 5:34 PM, Greg Knaddison - GVS wrote:
Note: except in rare situations, this is not for just modules that need a new maintainer. You should find that some other way. The "Abandoned Module" owner is like a graveyard.
I agree, mostly. I think it is a good enough place for any module where the maintainer honestly doesn't ever intend to do anything with the modules. The only problem is that to the anonymous user it doesn't show which modules the user maintains. Is this a project module permission that can be updated?
Actually, I'm seeing now that there is no way to see which modules belong to Abandoned Modules. Maybe I need to go get my orphans back.
There is a way to see the modules that belong to Abandoned Modules: http://drupal.org/user/291168/track Since Mister Abandoned Modules is very unlikely to be active in any forum or issue queue, nothing else will show up in his tracker. On Fri, May 9, 2008 at 8:47 AM, Robert Douglass <rob@robshouse.net> wrote:
Actually, I'm seeing now that there is no way to see which modules belong to Abandoned Modules. Maybe I need to go get my orphans back.
On 09.05-08:59, Florian Loretan wrote: [ ... ]
Since Mister Abandoned Modules is very unlikely to be active in any forum or issue queue, nothing else will show up in his tracker.
bit sexist making "it" a man, isn't it? ... but next time you chat mention that if he has a spare room in antuiga then i'll bring beer.
Florian Loretan wrote:
There is a way to see the modules that belong to Abandoned Modules: http://drupal.org/user/291168/track Since Mister Abandoned Modules is very unlikely to be active in any forum or issue queue, nothing else will show up in his tracker.
Even better: http://drupal.org/project/user/291168
On Fri, May 9, 2008 at 6:20 PM, Earl Miles <merlin@logrus.com> wrote:
Florian Loretan wrote:
There is a way to see the modules that belong to Abandoned Modules: http://drupal.org/user/291168/track Since Mister Abandoned Modules is very unlikely to be active in any forum or issue queue, nothing else will show up in his tracker.
Even better: http://drupal.org/project/user/291168
Added this link to the users' bio :) Gabor
Even better: http://drupal.org/project/user/291168
I even didn't know that anyone can access this view. Interesting... ;) However, we really should consider adding a maintenance status to projects: http://drupal.org/node/99466 Setting a taxonomy term on projects does not involve actions by d.o Webmasters.
This is handy - but it also made it obvious that at least one project is there which has a 'recommended for 5.x' release. The release system has flags for 'unsupported' now - so at a minimum these projects need to be marked with that in addition to being reassigned. Update status won't care if the project node owner changes so it's not that much use by itself. Nat PS. On a similar note, http://drupal.org/node/252105 - removing all 4.7 only modules from the main project listings. +1 etc. On Fri, May 9, 2008 at 5:52 PM, Daniel F. Kudwien
Even better: http://drupal.org/project/user/291168
And these suggestions should be added to that documentation mentioned previously. These steps should be taken _before_ a request is made to the infrastructure team to re-assign the module. Steven On Fri, May 9, 2008 at 11:41 AM, catch <catch56@googlemail.com> wrote:
This is handy - but it also made it obvious that at least one project is there which has a 'recommended for 5.x' release. The release system has flags for 'unsupported' now - so at a minimum these projects need to be marked with that in addition to being reassigned. Update status won't care if the project node owner changes so it's not that much use by itself.
Nat
PS. On a similar note, http://drupal.org/node/252105 - removing all 4.7 only modules from the main project listings. +1 etc.
On Fri, May 9, 2008 at 5:52 PM, Daniel F. Kudwien
Even better: http://drupal.org/project/user/291168
On May 9, 2008, at 9:52 AM, Daniel F. Kudwien wrote:
However, we really should consider adding a maintenance status to projects: http://drupal.org/node/99466
... On May 9, 2008, at 11:41 AM, catch wrote:
The release system has flags for 'unsupported' now - so at a minimum these projects need to be marked with that in addition to being reassigned. Update status won't care if the project node owner changes so it's not that much use by itself. ...
Right. Big -1 on this abandoned user hack. update_status even has support for per-project status terms, not only the per-release terms. There's just no server-side code for this yet, since #99466 has languished due to Dries wanting to hold up the basics until all the UI bling was done, then losing interest and abandoning the issue when the rest of us replied. ;) Busy man, that Dries... Anyway, #99466 is the right way to deal with this, on so many levels. On May 9, 2008, at 9:20 AM, Earl Miles wrote:
Even better: http://drupal.org/project/user/291168
For no particularly good reason (other than it's never been a high prio and I haven't had time) this doesn't work for anonymous users. Cheers, -Derek (dww)
On Fri, May 9, 2008 at 4:55 PM, Derek Wright <drupal@dwwright.net> wrote:
Right. Big -1 on this abandoned user hack.
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 -- Greg Knaddison Denver, CO | http://knaddison.com World Spanish Tour | http://wanderlusting.org/user/greg
On Fri, May 9, 2008 at 1:20 PM, Greg Knaddison - GVS <Greg@growingventuresolutions.com> wrote:
On Fri, May 9, 2008 at 4:55 PM, Derek Wright <drupal@dwwright.net> wrote:
Right. Big -1 on this abandoned user hack.
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.
I'll throw in my two cents. It sounds like #99466 would work too but looking at the create date on that issue shows that this problem has been looking for a solution for over a year and a half. As Voltaire said, "the perfect is the enemy of the good". We shouldn't keep this functionality from users while waiting on some "correct" way of doing it. andrew
On May 9, 2008, at 1:45 PM, andrew morton wrote:
We shouldn't keep this functionality from users while waiting on some "correct" way of doing it.
I agree, which is why I think I'm going to impose a statute of limitations on Dries's objections to something I want to get done. ;) If he doesn't like something, he gets (say) 1 month of "languish" time in the issue queue, then I'm just going to move forward, regardless... -Derek (dww) p.s. Says the man who's been AWOL from the project* issue queue for far too long and has plenty of issues that have been languishing without attention, including some goodies from drewish himself. ;)
On Fri, 9 May 2008, Robert Douglass wrote:
Actually, I'm seeing now that there is no way to see which modules belong to Abandoned Modules. Maybe I need to go get my orphans back.
http://drupal.org/user/291168/track --
From the mailer of |_|0|_| B R A N D O N B E R G R E N |_|_|0| T e c h n i c a l |0|0|0| G e n e r a l i s t ( C S )
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 http://drupal.org/node/103968. i still think it is a good idea, or at least one that can start delivering usefulness in 5 minutes. On Fri, May 9, 2008 at 11:34 AM, Greg Knaddison - GVS <Greg@growingventuresolutions.com> wrote:
Hi,
Sometimes modules get abandoned because they are no longer needed or no longer make sense. Features get added to core, CCK+Views come along and deprecate whole swaths of modules, etc. People need to know that a module has been abandoned, which is usually best communicated on the project node itself. But, if you've done that and want to make it more clear (and, maybe, stop getting contacted to help with the module) what can you do?
The "Abandoned Modules" user. He's too busy sunning himself in Antigua to care about his modules. He's unemployed and loving it. Give him your dead modules, won't you? If you are the author of a module and would like it to be assigned to this user and can't do it yourself, file an issue about it: http://drupal.org/project/issues/webmasters
Note: except in rare situations, this is not for just modules that need a new maintainer. You should find that some other way. The "Abandoned Module" owner is like a graveyard.
Thanks, Greg
-- Greg Knaddison Denver, CO | http://knaddison.com World Spanish Tour | http://wanderlusting.org/user/greg
I'm hoping that Dries doesn't block this user, as previously happened with 'unmaintained' - unless an alternative is available right now. In fact I'm waiting to hear from him before I assign a couple of modules to it :) It really is quite helpful and a very simple solution until something better is available.
This is very useful IMHO. I've already taken over one of the listed. On Wed, May 14, 2008 at 11:14 PM, Simon Hobbs <simon@emspace.com.au> wrote:
I'm hoping that Dries doesn't block this user, as previously happened with 'unmaintained' - unless an alternative is available right now. In fact I'm waiting to hear from him before I assign a couple of modules to it :)
It really is quite helpful and a very simple solution until something better is available.
Was this, I don't know, discussed on the infrastructure list or IRC? On Fri, May 9, 2008 at 8:34 AM, Greg Knaddison - GVS <Greg@growingventuresolutions.com> wrote:
Hi,
Sometimes modules get abandoned because they are no longer needed or no longer make sense. Features get added to core, CCK+Views come along and deprecate whole swaths of modules, etc. People need to know that a module has been abandoned, which is usually best communicated on the project node itself. But, if you've done that and want to make it more clear (and, maybe, stop getting contacted to help with the module) what can you do?
The "Abandoned Modules" user. He's too busy sunning himself in Antigua to care about his modules. He's unemployed and loving it. Give him your dead modules, won't you? If you are the author of a module and would like it to be assigned to this user and can't do it yourself, file an issue about it: http://drupal.org/project/issues/webmasters
Note: except in rare situations, this is not for just modules that need a new maintainer. You should find that some other way. The "Abandoned Module" owner is like a graveyard.
Thanks, Greg
-- Greg Knaddison Denver, CO | http://knaddison.com World Spanish Tour | http://wanderlusting.org/user/greg
On Fri, May 9, 2008 at 2:12 PM, Steven Peck <sepeck@gmail.com> wrote:
Was this, I don't know, discussed on the infrastructure list or IRC?
Yes. In IRC. Thanks, Greg -- Greg Knaddison Denver, CO | http://knaddison.com World Spanish Tour | http://wanderlusting.org/user/greg
If this is or ends up an _official_ way to deal with this subject, then please add a handbook page in the the project/module maintainers guide. An email to the list i sto transitory. Steven On Fri, May 9, 2008 at 11:34 AM, Greg Knaddison - GVS <Greg@growingventuresolutions.com> wrote:
On Fri, May 9, 2008 at 2:12 PM, Steven Peck <sepeck@gmail.com> wrote:
Was this, I don't know, discussed on the infrastructure list or IRC?
Yes. In IRC.
Thanks, Greg
-- Greg Knaddison Denver, CO | http://knaddison.com World Spanish Tour | http://wanderlusting.org/user/greg
On Fri, May 9, 2008 at 12:12 PM, Steven Peck <sepeck@gmail.com> wrote:
Was this, I don't know, discussed on the infrastructure list or IRC?
This started because I needed to figure out what to do with the project pages I recreated. I was going to assign them back to the now blocked maintainer to get them out of my queue but then Greg came up with this way, which works fine for me. It may not be the ideal solution but it at least works for now until a better one comes along. Michelle
Why a user for abandoned modules and why not one for "needs new maintainer"? Sorry but while this was a quick solution I think a status field would be more appropriate. A project status would handle most all cases would it not? Greg Knaddison - GVS wrote:
Note: except in rare situations, this is not for just modules that need a new maintainer. You should find that some other way. The "Abandoned Module" owner is like a graveyard.
participants (18)
-
andrew morton -
Ben -
Brandon Bergren -
catch -
Daniel F. Kudwien -
Derek Wright -
Earl Miles -
Florian Loretan -
Greg Knaddison - GVS -
Gábor Hojtsy -
Jerad Bitner -
Liza Sabater -
Michelle Cox -
Moshe Weitzman -
Robert Douglass -
Simon Hobbs -
Steven Peck -
ttw+drupal＠cobbled.net