Re: [development] adoption for 'abandoned' modules?
That comment was supposed to be a little tongue in cheek. Yes I know some of the high profile developers have done that and I can understand why. I think it has to be combined with other factors -- no way to contact them directly + no response to open issues on the queue = a developer whose modules need to get downgraded or adopted. However I do think there is really no reason for new developers who are not so high profile to make themselves unreachable. Anyway, I wasn't really proposing automatic action against anyone whose contact form was disabled. Everyone reacted to my tongue in cheek comment and no one reacted to what I thought was the important idea -- that we provide a place on the project page where you can identify the co-maintainers. Karen ----- Original Message ---- From: Steven Peck <speck@blkmtn.org> To: development@drupal.org Sent: Friday, January 19, 2007 9:31:18 PM Subject: Re: [development] adoption for 'abandoned' modules?
-----Original Message----- From: development-bounces@drupal.org [mailto:development- bounces@drupal.org] On Behalf Of Darren Oh Subject: Re: [development] adoption for 'abandoned' modules?
On Jan 19, 2007, at 11:41 AM, Karen Stevenson wrote:
Also, I would require that anyone listed as a maintainer must have their contact form enabled, otherwise they get de-listed and their project gets put up for adoption on a special adoption page. OK, maybe that last bit is a little strong :-) but whether or not there is a way to contact the maintainer should be another factor in our 'gold star' system.
Not too strong at all. If a person wants to control a project but doesn't want to be contacted, he should maintain the project on his own computer, not on Drupal. Let people who disable their contact forms have CVS access, but find someone who will actually maintain a project to be the maintainer.
Um, and those that out of frustration with people using the contact forum to mail them directly for support instead of using the issue queue? Do we disable their contrib. modules? Site admins can use the contact form. We have the email information and can email directly. Not to put a fine point on it but I know several active module contributors who have disabled their contact modules because of this sort of abuse.
On Sat, 2007-01-20 at 04:12 -0800, Karen Stevenson wrote:
That comment was supposed to be a little tongue in cheek.
Yes I know some of the high profile developers have done that and I can understand why. I think it has to be combined with other factors -- no way to contact them directly + no response to open issues on the queue = a developer whose modules need to get downgraded or adopted.
However I do think there is really no reason for new developers who are not so high profile to make themselves unreachable.
Anyway, I wasn't really proposing automatic action against anyone whose contact form was disabled.
Everyone reacted to my tongue in cheek comment and no one reacted to what I thought was the important idea -- that we provide a place on the project page where you can identify the co-maintainers.
Karen
There is the developers link on the project page.
On Jan 20, 2007, at 1:08 PM, Darrel O'Pry wrote:
There is the developers link on the project page.
That includes even people who contribute translations and don't have access to actually maintain the project.
On Jan 20, 2007, at 6:59 PM, Darren Oh wrote:
That includes even people who contribute translations and don't have access to actually maintain the project.
contrib translations should be separate projects: http://drupal.org/node/105986 this would solve a *ton* of problems with translations, and would solve this, too. -derek
On Jan 20, 2007, at 4:12 AM, Karen Stevenson wrote:
that we provide a place on the project page where you can identify the co-maintainers.
http://drupal.org/node/69556 see also http://drupal.org/node/102532 and yes, there is the "developers" link, as others have pointed out, e.g.: http://drupal.org/project/developers/3281 i'm not opposed to making these better, more visible, etc. specific ideas, screenshots, and (especially) patches are welcome. thanks, -derek p.s. FYI: due to recent changes i've made, once you have CVS access to a project node, you can edit the node to fix settings, descriptions, add releases, etc. so, if you grant CVS access, the new user really now has full rights as co-maintainers. the 1 thing that you can't do unless you own the project node itself is to give out more CVS rights. so, only the owner can add other maintainers, but otherwise, maintainers can do just about anything else. p.p.s. another of my medium term goals (part of what #69556 is about) is that when maintainers are creating or replying to issues, they'd be able to assign issues to anyone else listed as a maintainer of the project, not just themselves vs. unassigned. like the idea? don't reply to this email. http://drupal.org/project/comments/add/69556 ;)
participants (4)
-
Darrel O'Pry -
Darren Oh -
Derek Wright -
Karen Stevenson