[development] should tinymce get a new maintainer tinymce
rob at robshouse.net
Wed Feb 7 16:13:14 UTC 2007
I think that anybody who was critical of drupal-id.com's work to this
point has added the caveat that things could simply resolve favorably if
the communication roadblocks were eradicated. This is fortunately the
case and I think that anybody following the discussion will now gladly
say "welcome back, drupal-id.com", and get on with life.
If there is any lesson to be learned, it is to make sure that you pay
attention to as many channels of communication as possible. The issue
queue, the devel list, and the IRC channel would have all been valuable
sources of early warning to this person that a critical spotlight was
being focused on them. So when you have the chance to offer advice to
new Drupallers, let it be that they need to tune in to as many of the
sources of information as possible.
Sam Tresler wrote:
>> The bad news...
> Ok, I bit my tongue through most of this process, because I didn't
> feel I knew the intricacies involved to comment intelligently, but now
> that its resolving itself it appears that this poor chap had nothing
> wrong but a busy few months, a broken e-mail address, and a little
> difficulty with English.
> Drupal-id deserves a bit in the way of apology - its a contrib module,
> not core, and he took it up when No one else would - it appears just
> to get CVS access to work on things his way - since no one else wanted
> Now that we've spent Many e-mails calling him a poor maintainer in
> public He's ACTIVELY SEEKING HELP - now its 'Bad News'? bad news?!
> Isn't this great news from this thread's perspective?
> Isn't this exactly what a busy 'responsible' module maintainer
> *should* do?
> I ask this in all seriousness as I'm thinking of applying to be a
> co-maintainer of a few 'highly-used' modules and if this is the
> treatment people who try to help get, I might reconsider. I'd rather
> be fully informed in advance though.
More information about the development