I have grown quite weary of individuals with power and privilege who take it upon themselves to make kneejerk reactions presumably in the name of upholding the rules.
At issue today is Tim Pluncket and his decision to use a public post via twitter to share his decision that my recent blog post featured on Drupal Planet was, in his decision, not a valid post for the planet.
My reaction was to remove it immediately as I am a lover of rules.
Upon further review of the link he sited as his reason for deciding that my post was in error, I saw clearly that my post was perfectly fine. I reinstated the DrupalPlanet tag.
On the page listing Content requirements for being added to the Planet: found at http://drupal.org/about/drupal-planet , we see the following criteria:
"Posts about the Drupal community. The people, influencers, issues that concern or thrill you."
My big decision to join a huge company and what plans they have for Drupal clearly meet, at the very least, the criterium listed above.
However, Tim saw it as an opportunity to publicly exact criticism and deem that the post does not belong.
If other moderators agree, then I am en error and will react accordingly by removing the tag again.
My bigger concern is that a process be put in place to avoid the kind of conduct shown by Tim in this situation. To that end I request that such a process be drafted and published so that we all may know what to expect from those with the power and privilege of being a d.o moderator.
Thank you,
- Doug Vann
| Comment | File | Size | Author |
|---|---|---|---|
| #2 | Screen shot 2012-12-09 at 8.59.52 PM.png | 99.86 KB | dougvann |
Comments
Comment #1
dougvann commentedSorry,
I should have posted a link to my blog post which sparked these events:
http://dougvann.com/blog/announcement-i-am-now-working-exact-target
Comment #2
dougvann commentedTim has deleted the twitter post in which he announces my post as invalid.
Here is a screen shot from my phone which oddly is out of date with the web version.
Comment #3
mr.baileysThere is a process in place to object to a post, described http://drupal.org/about/drupal-planet:
The only tweak we could make to that policy is to request that the blog author be contacted privately.
Regarding the content of the post itself: the rules also mention "No hiring posts". There has been a lot of discussion about this rule (for example: #1035184: Form a community consensus on Planet Drupal guidelines), and not everyone agrees with it, but for the moment it *is* part of the "what is not allowed"-section of the guidelines, and as such I agree with tim.plunkett about this post not belonging on Planet Drupal.
You seem to imply that certain individuals are abusing power and privilege. It seems to me you are reading too much in Tim's tweet. Tim did not block or remove the feed from Planet or demote it to Drupal Talk, nor did he claim he was tweeting as a d.o. maintainer. Rather, he followed the policy about getting in touch with the author (granted, an email might have been better).
Comment #4
dougvann commentedWe'll agree to disagree then.
Thank you.
Comment #5
dddave commentedJust for the record: I would very much like to see these restriction on hiring and new jobs somebody got gone. I think it is community relevant when major contributors like dougvann have major changes in their professional live.
#1035184: Form a community consensus on Planet Drupal guidelines is a hot mess filled with personal conflicts and the current situation is that was once decreed his hardly changeable. If somebody knows a good solution please raise your hand.