#16763: code.djangoproject.com won't stop emailing me (doesn't abide by
cc/reporter/etc)
-------------------------------------+-------------------------------------
Reporter: ferringb | Owner: nobody
Type: Bug | Status: reopened
Component: Djangoproject.com | Version:
Web site | Resolution:
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 anonymous):
Replying to [comment:17 mlavin]:
> This rant is very colorful but I believe you are incorrect in your
understanding of the law in this case. While I'm not a lawyer, CAN-SPAM
does not apply to transactional content which the Trac updates would fall
under. The law only applies to commercial messages as defined by
>
> > any electronic mail message the primary purpose of which is the
commercial advertisement or promotion of a commercial product or service
>
> which Trac ticket update emails are clearly not. Your frustration is
understandable but your subtle threats against the DSF are not necessary
nor based on fact.
>
> Read the CAN-SPAM rule here: http://ecfr.gpoaccess.gov/cgi/t/text/text-
idx?c=ecfr&sid=a273032f4545305b53bd3b788739f586&tpl=/ecfrbrowse/Title16/16cfr316_main_02.tpl
Shush. It was attempted motivation/shaming, although I should've expected
someone would look up the letter of the law rather than just fixing the
damn configuration ;)
Also, must admit I find it rather interesting that rather than fixing it,
or pruning my address as was offered (and aparently never followed through
with, useful, that), instead someone goes and bans my primary account from
django dev ml- roughly, w/in the last hour or two. While I've not had
much intent on posting to the ml (did have interest to see if a discussion
about this had started however), but I find it rather entertaining- no
problems spamming me, but y'all go to the trouble of banning my account?
Double standard there, albeit a funny one.
Pretty easy to fix this; if devs want to be cc'd on everything, either
create a global list trac mails and have people subscribe to that, or
collect the names and add them to existing tickets cc; this covers the
reasoning given thus far.
Then flip the setting off. Really is that easy, and much more productive
than banning, arguing over CAN-SPAM, or generally leaving the setting in
place to piss further people off.
--
Ticket URL: <https://code.djangoproject.com/ticket/16763#comment:18>
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.
