# Community norms for unsolicited communication

**URL:** <https://discourse.julialang.org/t/community-norms-for-unsolicited-communication/7539>\
**Category:** Community\
**Created:** [December 5, 2017, 9:59am UTC](https://discourse.julialang.org/t/community-norms-for-unsolicited-communication/7539 "2017-12-05T09:59:57Z")\
**Posts on this page:** 9\
**Page:** 2

<div class="post-metadata">

**Author:** ![ChrisRackauckas](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/chrisrackauckas/32/77_2.png) [@ChrisRackauckas](https://discourse.julialang.org/u/ChrisRackauckas)\
**Post date:** [December 7, 2017, 5:06pm UTC](https://discourse.julialang.org/t/community-norms-for-unsolicited-communication/7539/21 "2017-12-07T17:06:34Z")

</div>

> [@mkborregaard](#):
>
> There’s a “but”: good user feedback and discussion is a really useful resource for package maintainers. If people talk about my package, I would like to know. I’m perfectly capable of ignoring a ping if I’m not interested, and generally I appreciate getting pinged on something interesting. I think a better general rule is that the more people are likely to ping a given person, the better a reason you should have to do it.

Yeah, that’s another good point. I’m happy @mohamed82008 pinged me in the other thread. I think some of that has to do with personal tolerance as well. All of these “rules” are very rough on the boundaries, so again it just comes back to common sense.

---

<div class="post-metadata">

**Author:** ![dlfivefifty](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/dlfivefifty/32/1959_2.png) [@dlfivefifty](https://discourse.julialang.org/u/dlfivefifty)\
**Post date:** [December 7, 2017, 8:47pm UTC](https://discourse.julialang.org/t/community-norms-for-unsolicited-communication/7539/22 "2017-12-07T20:47:26Z")

</div>

I think the issue is a software issue, not a human behaviour issue: GitHub/Discourse co-opting Twitters @ syntax to mean something slightly different. Perhaps the solution is to modify Discourse site to add a checkbox whether @ mentions should be contacted?

---

<div class="post-metadata">

**Author:** ![greg\_plowman](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/greg_plowman/32/8100_2.png) [@greg\_plowman](https://discourse.julialang.org/u/greg_plowman)\
**Post date:** [December 7, 2017, 11:56pm UTC](https://discourse.julialang.org/t/community-norms-for-unsolicited-communication/7539/23 "2017-12-07T23:56:33Z")

</div>

> [@dlfivefifty](#):
>
> Perhaps the solution is to modify Discourse site to add a checkbox whether @ mentions should be contacted?

Does enclosing an @ mention in backticks suppress notification? (e.g. `@dlfivefifty`)

If so, this could be used in cases where one wants to acknowledge or reference someone without notifying them.

---

<div class="post-metadata">

**Author:** ![ChrisRackauckas](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/chrisrackauckas/32/77_2.png) [@ChrisRackauckas](https://discourse.julialang.org/u/ChrisRackauckas)\
**Post date:** [December 8, 2017, 12:43am UTC](https://discourse.julialang.org/t/community-norms-for-unsolicited-communication/7539/24 "2017-12-08T00:43:35Z")

</div>

> [@greg\_plowman](#):
>
> Does enclosing an @ mention in backticks suppress notification? (e.g. @dlfivefifty)

yes, though quoting breaks that 🙂

---

<div class="post-metadata">

**Author:** ![PetrKryslUCSD](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/petrkryslucsd/32/215825_2.png) [@PetrKryslUCSD](https://discourse.julialang.org/u/PetrKryslUCSD)\
**Post date:** [December 8, 2017, 1:05am UTC](https://discourse.julialang.org/t/community-norms-for-unsolicited-communication/7539/25 "2017-12-08T01:05:49Z")

</div>

Just break the “at”: @-greg\_plowman

---

<div class="post-metadata">

**Author:** ![dlfivefifty](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/dlfivefifty/32/1959_2.png) [@dlfivefifty](https://discourse.julialang.org/u/dlfivefifty)\
**Post date:** [December 8, 2017, 11:30pm UTC](https://discourse.julialang.org/t/community-norms-for-unsolicited-communication/7539/26 "2017-12-08T23:30:04Z")

</div>

My point was make it opt in communicate, not opt out. Expecting new users to put ticks is not realistic

---

<div class="post-metadata">

**Author:** ![kevbonham](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/kevbonham/32/216165_2.png) [@kevbonham](https://discourse.julialang.org/u/kevbonham)\
**Post date:** [December 13, 2017, 3:23am UTC](https://discourse.julialang.org/t/community-norms-for-unsolicited-communication/7539/27 "2017-12-13T03:23:02Z")

</div>

For the record, i don’t have any objecting to people @ing me at any time for any reason… This is probably because there are few that would think to do so, and after reading this thread I realize I am probably guilty of over @ing …

Sorry 😣

---

<div class="post-metadata">

**Author:** ![ihnorton](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/ihnorton/32/26_2.png) [@ihnorton](https://discourse.julialang.org/u/ihnorton)\
**Post date:** [December 13, 2017, 4:30am UTC](https://discourse.julialang.org/t/community-norms-for-unsolicited-communication/7539/28 "2017-12-13T04:30:36Z")

</div>

FWIW, on reflection I think what I said above was stated a bit too strongly. As many others here have said quite well: just try to be considerate. (and similarly, be considerate when responding to a meta-request/suggestion made publicly or otherwise)

---

<div class="post-metadata">

**Author:** ![ScottPJones](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/scottpjones/32/146_2.png) [@ScottPJones](https://discourse.julialang.org/u/ScottPJones)\
**Post date:** [December 14, 2017, 1:25pm UTC](https://discourse.julialang.org/t/community-norms-for-unsolicited-communication/7539/29 "2017-12-14T13:25:12Z")

</div>

Ping me whenever you want also! 🙂

[Previous page](https://discourse.julialang.org/t/community-norms-for-unsolicited-communication/7539.md?page=1)
