Posted by senpai on April 23, 2012 at 8:11pm
Could someone easily roll out the "Don't send notifications for this edit" on this site, or is it a really complicated and involved process?
Categories: support & ticketing
Could someone easily roll out the "Don't send notifications for this edit" on this site, or is it a really complicated and involved process?
Comments
Never mind. Old habits die hard.
Never mind, I posted this in the wrong place. Moving it to http://drupal.org/node/1543866
Joel Farris | my 'certified to rock' score
Transparatech
http://transparatech.com
619.717.2805
Yes, please!Here are the
Yes, please!
Here are the issues for this:
(削除) For the love of all that is holy, stop sending people e-mail notifications on edit! (削除ここまで)https://drupal.org/node/1193360
Optionally send notifications for only the first comment edit
https://drupal.org/node/780842
In general, I think getting anything done on this site has been a really complicated and involved process. Fortunately, there are more volunteers now than there were when these issues were posted.
In general, I think getting
We started the gdo queue almost a year after taking over the site, basically 2 years ago. In the time since that queue was created almost 500 issues were closed. That seems like something got done.
It's true that getting things done on drupal.org in general was and is complicated. In 2011, after a relatively long effort to improve the process, webchich posted how you can make drupal.org awesome detailing why it's been so hard and some recent successes in making it easier for people to work on these sites.
In the case of the issues you linked to they are bugs in the underlying modules in use on this site that have not been fixed in those underlying modules. A d.o sandbox site or g.d.o admin permissions were not necessary to work on them. What do you think could have been done differently to get that solved? Your comment about new volunteers (there are not more, just different people) makes it seem like you think that it is the responsibility of the site maintainers to fix it. I personally had been waiting for the module maintainers OR someone affected by the bug to work on it. It didn't frustrate me personally.
I would have loved to do even more work improving the site. Unfortunately, much of my volunteer-time was spent elsewhere. One example of volunteer-time I wish I could have allocated to bugfixes was investigating what happened from the time you misappropriated content and then deleted revisions to hide your actions.
knaddison blog | Morris Animal Foundation
I'm not sure why my comment
I'm not sure why my comment was downvoted. There isn't anything negative or controversial in my comment and it sounds like you agree with what I wrote when you said:
More to the point, it appears that I'm being downvoted not because what I said but because it was me who said it:
What's the basis of that statement, Greg? It takes less than a minute to click on a group's "Moderation" tab and read the history. "Hiding my actions" was never my intention, nor do I think it's even possible. In your own words, you've said it isn't a big deal if a group is approved by the same person that submitted it. That's essentially what I did.
Isn't it up to the groups.drupal.org site maintainers to operate and update the site and provide guidance and support when necessary? These things appear to me to be happening more now that there are additional volunteers who are site admins.
To me, this is a very welcome change to groups.drupal.org's SOP and I thought your announcement at https://drupal.org/node/1529948 was a great call to action and introduction to the new members of the team.
It takes less than a minute
That is not what you originally did. You took the Lithuanian group, re-titled it, and deleted revisions. To discover the history I had to find a database backup, download it, load it up, and run queries to look at the history of the node from before you deleted the revisions.
knaddison blog | Morris Animal Foundation