# Community Guidelines Feedback on "1/n"

**URL:** <https://discuss.python.org/t/community-guidelines-feedback-on-1-n/58669>\
**Category:** Discourse Feedback\
**Created:** [July 19, 2024, 2:27pm UTC](https://discuss.python.org/t/community-guidelines-feedback-on-1-n/58669 "2024-07-19T14:27:08Z")\
**Posts on this page:** 12\
**Page:** 1

<div class="post-metadata">

**Author:** ![notatallshaw](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/notatallshaw/32/10861_2.png) [@notatallshaw](https://discuss.python.org/u/notatallshaw)\
**Post date:** [July 19, 2024, 2:27pm UTC](https://discuss.python.org/t/community-guidelines-feedback-on-1-n/58669/1 "2024-07-19T14:27:08Z")

</div>

I don’t want to start a broad topic on feedback of the community guidelines, I just want to point out this line seems very odd to me:

> The best conversations allow for all participants to chime in. In a group of `n` people, try to use up `1/n` space in terms of both the volume of posts and their size. Some of us only have time to respond once or twice per day.

**Scenario** : Two people are having a long discussion on discourse as they are both experts in the relevant field. They are therefore roughly taking up 1/2 of the conversation space. I want to make 1 small comment I find relevant, but I do not want, or need to, participate in the conversation at large.

In this scenario I am now taking up close to 0 of the discussion, I certainly do not want to take up “1/3” of the discussion. And now these users are way over the “1/3” of their space, will they be penalised?

In my experience, this kind of input to long running healthy discussions is normal, that there are some “core” people, as they are most invested or expertized in the conversation, and then “single issue” people who want to raise a point about a single issue.

Conversely, in my experiences, discussions where almost everyone feels they need to keep replying, and there are these close to “1/n” numbers, tend to be fraught conversations where people are very divided and points are being recycled and little usefulness is being made. They are therefore certainly not the “best” conversations.

Also is “Some of us only have time to respond once or twice per day.” a non-sequitur? I don’t understand how it’s relevant, in a healthy conversation that is making a lot of ground on a topic, what does it matter how many times someone posts? Maybe it’s that I mostly read a discussion, rather than respond to one, or maybe it’s because this sentence assumes the conversation is divisive? If so, it doesn’t state it, which makes the point very confusing.

---

<div class="post-metadata">

**Author:** ![jamestwebber](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/jamestwebber/32/12799_2.png) [@jamestwebber](https://discuss.python.org/u/jamestwebber)\
**Post date:** [July 19, 2024, 2:30pm UTC](https://discuss.python.org/t/community-guidelines-feedback-on-1-n/58669/2 "2024-07-19T14:30:03Z")

</div>

> [@notatallshaw](#):
>
> In this scenario I am now taking up close to 0 of the discussion, I certainly do not want to take up “1/3” of the discussion. And now these users are way over the “1/3” of their space, will they be penalised?

I didn’t get any impression that this is a _rule_ that will be enforced in any way. That whole section reads as “how to be a normal person in a forum” \[1\]

* * *

1. something that I am currently flunking…I’ll get back to work as soon as the coffee works

---

<div class="post-metadata">

**Author:** ![ambv](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/ambv/32/25884_2.png) [@ambv](https://discuss.python.org/u/ambv)\
**Post date:** [July 19, 2024, 2:39pm UTC](https://discuss.python.org/t/community-guidelines-feedback-on-1-n/58669/3 "2024-07-19T14:39:20Z")

</div>

> [@notatallshaw](#):
>
> I certainly do not want to take up “1/3” of the discussion

The `1/n` rule is a rule of thumb. It’s not worth worrying about detailed numbers, it’s more about cases where a single person posts 50 times in a topic of 180 messages total, overwhelming the discussion for everybody else.

---

<div class="post-metadata">

**Author:** ![notatallshaw](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/notatallshaw/32/10861_2.png) [@notatallshaw](https://discuss.python.org/u/notatallshaw)\
**Post date:** [July 19, 2024, 2:42pm UTC](https://discuss.python.org/t/community-guidelines-feedback-on-1-n/58669/4 "2024-07-19T14:42:44Z")

</div>

> [@ambv](#):
>
> The `1/n` rule is a rule of thumb. It’s not worth worrying about detailed numbers, it’s more about cases where a single person posts 50 times in a topic of 180 messages total, overwhelming the discussion for everybody else.

Ah “overwhelming the discussion” makes a lot more sense.

If it’s not worth worrying about detailed numbers, could you reword this to not use a specific number? i.e 1/n

Someone could easily be **way** over 1/n and not overwhelming the discussion.

---

<div class="post-metadata">

**Author:** ![MegaIng](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/megaing/32/16162_2.png) [@MegaIng](https://discuss.python.org/u/MegaIng)\
**Post date:** [July 19, 2024, 2:52pm UTC](https://discuss.python.org/t/community-guidelines-feedback-on-1-n/58669/5 "2024-07-19T14:52:00Z")

</div>

A very obvious example of this is in #Python Help , where that one person is OP asking a question and a large variety of different people are chiming in trying to help them. It is not surprising if OP in that case takes about ~1/2 of messages and everyone else together the other half.

---

<div class="post-metadata">

**Author:** ![tim.one](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/tim.one/32/282_2.png) [@tim.one](https://discuss.python.org/u/tim.one)\
**Post date:** [July 19, 2024, 6:06pm UTC](https://discuss.python.org/t/community-guidelines-feedback-on-1-n/58669/6 "2024-07-19T18:06:00Z")

</div>

Echoing what appears to be the general consensus: consider the context and generally don’t fret over it. `1/n` isn’t part of the CoC. I routinely see that “helpful suggestion” in, e.g. topics about floating-paint behavior in Python. I’m usually the only actual expert in such topics, and am usually very patient about trying to answer questions, so my posts can utterly dominate the topic for days on end. I’m not trying to hog attention - I’m typically the only one who _can_ give reliable answers in such cases.

Similarly, e.g. for the “helpful suggestions” like (paraphrasing) “the link you’re adding was already supplied in some other post - are you sure you want to add it again?”. The answer to which is almost always “yes”. I recall one time the answer was “no”. The link was pretty useless anyway 😉.

---

<div class="post-metadata">

**Author:** ![thejcannon](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/thejcannon/32/23759_2.png) [@thejcannon](https://discuss.python.org/u/thejcannon)\
**Post date:** [July 19, 2024, 6:43pm UTC](https://discuss.python.org/t/community-guidelines-feedback-on-1-n/58669/7 "2024-07-19T18:43:42Z")

</div>

Maybe it’s a typo and “try to use up” should be “try to use up to”? So, a recommended _maximum_ of 1/N?

Edit: wait no that sounds like it’d be encouraging taking up more space 🤦‍♂️ so “try to use no more than”, but now we’re outside “it was a typo” territory

---

<div class="post-metadata">

**Author:** ![jamestwebber](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/jamestwebber/32/12799_2.png) [@jamestwebber](https://discuss.python.org/u/jamestwebber)\
**Post date:** [July 19, 2024, 7:14pm UTC](https://discuss.python.org/t/community-guidelines-feedback-on-1-n/58669/8 "2024-07-19T19:14:23Z")

</div>

I don’t think the authors expected the `1/n` metric to be scrutinized as heavily as this, which in retrospect was an obvious mistake given the audience. 😂

---

<div class="post-metadata">

**Author:** ![notatallshaw](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/notatallshaw/32/10861_2.png) [@notatallshaw](https://discuss.python.org/u/notatallshaw)\
**Post date:** [July 19, 2024, 7:31pm UTC](https://discuss.python.org/t/community-guidelines-feedback-on-1-n/58669/9 "2024-07-19T19:31:18Z")

</div>

> [@thejcannon](#):
>
> Maybe it’s a typo and “try to use up” should be “try to use up to”? So, a recommended _maximum_ of 1/N?

To clarify on this though, IMO in a healthy conversation 1/N is a bad maximum.

For example, in this discussion, at the time of this post there are 6 unique authors, and 9 posts, I have made 3 of those posts (including this one), so I am currently at 2/N (Where N is 6). In terms of word volumne I am even more in breach of this guideline.

I hope, however, no one thinks I am overwhelming this discussion.

---

<div class="post-metadata">

**Author:** ![effigies](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/effigies/32/35835_2.png) [@effigies](https://discuss.python.org/u/effigies)\
**Post date:** [July 19, 2024, 7:36pm UTC](https://discuss.python.org/t/community-guidelines-feedback-on-1-n/58669/10 "2024-07-19T19:36:50Z")

</div>

Okay, we need a formula \phi(n\_{posts}, N\_{posters}) that asymptotically approaches \frac n N as n \to\infty, as well as a strict upper bound \Phi(n\_{posts}, N\_{posters}) that triggers auto-moderation.

---

<div class="post-metadata">

**Author:** ![stoneleaf](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/stoneleaf/32/88_2.png) [@stoneleaf](https://discuss.python.org/u/stoneleaf)\
**Post date:** [July 19, 2024, 7:56pm UTC](https://discuss.python.org/t/community-guidelines-feedback-on-1-n/58669/11 "2024-07-19T19:56:38Z")

</div>

> [@effigies](#):
>
> Okay, we need a formula […]

I have no idea what you said, but I wholeheartedly agree!

---

<div class="post-metadata">

**Author:** ![davidism](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/davidism/32/3295_2.png) [@davidism](https://discuss.python.org/u/davidism)\
**Post date:** [July 19, 2024, 8:38pm UTC](https://discuss.python.org/t/community-guidelines-feedback-on-1-n/58669/12 "2024-07-19T20:38:10Z")

</div>

Thanks for the feedback, we agree the wording was unclear. I’ve changed that paragraph to the following:

> Avoid overwhelming a conversation and leave room for other voices. Be aware of the number, length, and frequency of your posts compared to others in the thread. It can be difficult for others to participate if a few voices take up the majority of a thread.
