#16763: code.djangoproject.com won't stop emailing me (doesn't abide by
cc/reporter/etc)
-------------------------------------+-------------------------------------
Reporter: (removed) | Owner: nobody
Type: Bug | Status: closed
Component: Djangoproject.com | Version:
Web site | Resolution: fixed
Severity: Normal | Triage Stage: Accepted
Keywords: | Needs documentation: 0
Has patch: 0 | Patch needs improvement: 0
Needs tests: 0 | UI/UX: 0
Easy pickings: 0 |
-------------------------------------+-------------------------------------
Comment (by ferringb):
Replying to [comment:20 kmtracey]:
> So now everyone who has been working with this trac for years and gotten
used to the behavior of its auto-notifying them of changes to tickets they
have commented on has to be re-educated that in order to get updates to
tickets they must add themselves to cc list? That seems more broken than
the old behavior to me.
Not an answer you'll like, but frankly you'll get used to it and it's far
more powerful having that setting off. Couple of years back I was fairly
active with django- even then, the behaviour was proving worthless since
(like all other sites) I was using CC's to track what I cared about- which
could, and did change; simplest example, I cared fairly heavily about
template engine speed, thus was tracking a lot of tickets for that.
Switched to jinja, was happy, thus no longer cared about the templating
tickets, nor wanted that email- yet it persisted in mailing, screwing up
my signal/noise tracking of the project. That sort of behaviour for folks
tracking multiple projects makes one rather disinclined to interact w/
djangos trac. As is, there are some things I still would be interested in
tracking, but w/ the proceeding behaviour my option was only to just level
a full on ban of all incoming django mail to suppress the noise (tracking
a ticket or two wasn't worth the noise specifically).
CC being abided by gives you far more power than the broken previous
behaviour, and like it or not, it /was/ spamming. Definitely well
intentioned spam, but spam none the less. I realize it may be a pita in
for the minority who were relying on it, but for everyone else (who used
CC correctly, if in doubt look at people manipulating CC on tickets) it
was an ongoing annoyance.
Either way, thank you Adrian for correcting the setting; also pardon the
level of ass-hattery ultimately deployed trying to force people to abide
by standards- unfortunately pissed off folks a fair bit more than was the
intent.
--
Ticket URL: <https://code.djangoproject.com/ticket/16763#comment:21>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
