For me, I view Users as a general purpose place for people programming
in Python. Maybe that was not The Plan, but the description says:
General discussion forum for the Python programming language.
All welcome.
And that is a great description for the top category!
I’d consider that roughly the same audience as the python-list mailing
list. Certainly I’d expect anyone using Python who has a question to
come here if there isn’t a pretty obvious better place to go.
The list of categories has some pretty clear sections at the top (Users,
Ideas, etc), and there’s no direct equivalent to the “tutor” mailing
list for beginners. So they should come to “Users” as well.
So I expect anyone with a Python programming question to land here. If
their question is quite specific to something specialised like numpy etc
the should be welcomed, and pointed to the better forum. But if there’s
someone here with knownledge in that domain, I’ve no objection to to the
discussion happening here.
We can clearly stick links in the category descriptions. Maybe Users
could do with a single terse link to a separate page on Python resources
(area specific lists and forums, etc). But I also think it would
diminish that great concise welcoming description.
In my experience, no amount of “focus” in the description will prevent
misfiled posts - the best we can do is what I see: Users at the top as a
catch-all and a bunch of obviously somewhat specialised categories below
it.
Many mailing lists send an intro email when people subscribe. My
experience is that this does not prevent posts which should go elsewhere
or be formed differently. And the more information there is in such an
intro, I suspect the less it gets read.
So my opinion is that:
-
do not focus the “Users” category on the stdlib in any formal way
- greet specialised nonstdlib questions either with specific advice or a
suggestion of a better list/forum, accompanied with the context that
this forum is mostly around the stdlib, or mostly populated by
generalists
- I’m against telling people to go away because they’re asking something
specialised without a helpful link to better help
- I’m against telling people to go away because they’re asking something
specialised in any kind of “brush them off” dismissive tone; I would
rather their query went unanswered than that they were made to feel
unwelcome
- we’ve got topics in the Categories, just like mailing list subject
lines - we can all ignore what we’re not interested in; aside: can
people mute topics?
For context:
- I hate forums; I interact with discourse via email - to me that is a
major feature of discourse, that I have this choice
- I’m on a lot of lists, and I have my mail system file them in a far
smaller number of mail folders, so I’ve got quite a few lists all
mixed into my “python” folder, including the discourse forums - all of
them to which I subscribe
So my “python” folder has: python-list, tutor, Users and a bunch of
other things. They’re labelled, and I expect to pay a bit of attention
to that context. There’s only one line per topic/subject, and the most
recent stuff is at the top. For me, this works.
How is this relevant?
The Users category is inherently going to get something of everything.
We should expect that category to be a big mix, and expect to divert
people to better places when those places are better (and there’s nobody
here who can help).
I’m fine with expecting to help with the stdlib in users and
occasionally or as convenient helping with other things. We’re always
going to get the beginners, either outright on in whatever new domain
they’re using. We’re always going to get people in specialised domains
(eg numpy) where users have come here because it is an obvious place to
start.
Specialist lists can be confronting - there’s the whole “imposter
syndrome” where you don’t feel competent enough to join and ask your
question. But a forum for “Python Users”? That’s where you go to start.
So I’m ok with the informal focus on the stdlib - that’s what all Python
users have in common. But I’m against formal focus on the stdlib.
If a question’s not for you, you should ignore it and move on. That’s
what I do, even on topics I’m interested in, if others have covered off
what I’d have tried to say.
Cheers,
Cameron Simpson cs@cskk.id.au