<?xml version="1.0" encoding="utf-8"?>
<?xml-stylesheet type="text/xsl" href="../assets/xml/rss.xsl" media="all"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Moderate Realism (Posts about Community)</title><link>http://ramblings.tjg.org.uk/</link><description></description><atom:link href="http://ramblings.tjg.org.uk/categories/community.xml" rel="self" type="application/rss+xml"></atom:link><language>en</language><copyright>Contents © 2021 &lt;a href="mailto:mail@timgolden.me.uk"&gt;Tim Golden&lt;/a&gt; </copyright><lastBuildDate>Sun, 31 Oct 2021 11:26:50 GMT</lastBuildDate><generator>Nikola (getnikola.com)</generator><docs>http://blogs.law.harvard.edu/tech/rss</docs><item><title>Following up from stepping back</title><link>http://ramblings.tjg.org.uk/posts/following-up-from-stepping-back/</link><dc:creator>Tim Golden</dc:creator><description>&lt;div&gt;&lt;p&gt;Thank you to those who responded to &lt;a class="reference external" href="http://blog.tjg.org.uk/posts/stepping-back-a-bit-from-pythonorg/"&gt;my previous post&lt;/a&gt;
with thanks and words of encouragement. Just to be clear, I'm not stepping back from Python
altogether; far from it. I'm simply giving up certain background responsibilities
which I've found difficult to sustain. I realise that, by doing so, I've left the others who continue to manage those
tasks more burdened than before. So, again, I encourage you to offer
to help on whatever basis you think you can manage.&lt;/p&gt;
&lt;p&gt;Python has grown. When I entered the community
about 20 years ago, it was a moderate-sized mostly technical language
community. It's always been growing in popularity, but over the last 10 years
it's reached the point where it's used and relied on -- directly or indirectly --
by millions of people around the world. Indirectly by virtue of its use in
some very big-name companies. Directly because it's become the go-to language
for science and data projects. And it's the text-based programming language
most likely to be taught in secondary schools in the UK and maybe elsewhere, especially with
the encouragement of the &lt;a class="reference external" href="http://ramblings.tjg.org.uk/posts/following-up-from-stepping-back/raspberrypi.org"&gt;Raspberry Pi foundation&lt;/a&gt; and its resources. The audience is huge.&lt;/p&gt;
&lt;p&gt;Because of its size and significance, many people assume that there's a
commercial organisation running things. Or at least a well set-up NGO or institute
or something. But there isn't. There is a series of semi-detached volunteer
teams who typically only interact because one or more people on one of the teams
are also on one or more of the other teams.&lt;/p&gt;
&lt;p&gt;The webmaster@ address is the fallback communication point for the
Python community. It handles all sorts of queries. There are general requests for help;
requests from official bodies for us to complete some complicated export license
document; more questions about the cost of licenses than I care to think about
("No really, it's free; yes you can get a bulk discount of 100% because IT'S FREE");
questions about copyright and logo use; technical questions; questions from
school administrators who don't grok the new Python Windows installers;
people who've bought a car security system with the brand name "Python".
And all those queries are fielded by about three people (now about two people!)
working with whatever time they have available.&lt;/p&gt;
&lt;p&gt;The &lt;a class="reference external" href="https://mail.python.org/mailman/listinfo/python-list"&gt;Python mailing list&lt;/a&gt;
(also &lt;a class="reference external" href="news:comp.lang.python"&gt;comp.lang.python&lt;/a&gt; newsgroup) is the
"official" general-purpose communication channel for questions
about Python. But it's a mailing list / newsgroup, both of which are
slightly ageing concepts. Its origin as the forum of discussion around
a mostly technical audience still informs its general attitude. And, by
its nature, it assumes that you're interested in joining a community and
not simply asking a drive-by question. There's some experimentation going on
at the moment about using a &lt;a class="reference external" href="https://discuss.python.org/"&gt;Discourse&lt;/a&gt;
or a &lt;a class="reference external" href="https://python.zulipchat.com"&gt;Zulip&lt;/a&gt; instance or both, which
I think might be a move in the right direction for the wider casual audience.&lt;/p&gt;
&lt;p&gt;People raise issues on &lt;a class="reference external" href="https://bugs.python.org"&gt;https://bugs.python.org&lt;/a&gt; asking
questions about &lt;a class="reference external" href="https://pypi.python.org"&gt;https://pypi.python.org&lt;/a&gt;; they write to &lt;a class="reference external" href="mailto:webmaster@python.org"&gt;webmaster&lt;/a&gt; querying why they
haven't received a confirmation email when they signed up on the &lt;a class="reference external" href="https://python.org"&gt;https://python.org&lt;/a&gt;
website; they write to &lt;a class="reference external" href="mailto:docs@python.org"&gt;mailto:docs@python.org&lt;/a&gt; when downloads aren't available on
&lt;a class="reference external" href="https://docs.python.org"&gt;https://docs.python.org&lt;/a&gt; for the latest version of the documentation; and they raise an issue on the
&lt;a class="reference external" href="https://github.com/python/pythondotorg/issues"&gt;website tracker&lt;/a&gt; when there's a spelling mistake in the online documentation.
And although I've put those examples forward as mistakes, it may not even
be obvious to you &lt;em&gt;why&lt;/em&gt; those are mistakes. python.org contains quite a few
silos.&lt;/p&gt;
&lt;p&gt;The easy majority of volunteers behind these various forums are technical
people who've stepped up to help. Which is clearly very much to their credit.
Back in the day, most people
posting through Python forums would also have been those with a technical
background who'd chosen to use Python: students, professional programmers &amp;amp;c.
So there was an easier meeting of minds when it came to answering questions and
giving advice. Nowadays they might be, for example,
schoolteachers or data scientists who use Python as a tool (for teaching or analysis)
but who have no knowledge of or, really, interest in the underlying mechanics
of the language or its community. Or even schoolchildren looking for help with
their homework or with a personal project. So there can be a mismatch between the
people asking questions and those answering.&lt;/p&gt;
&lt;p&gt;On top of all that, we're increasingly in a world where &lt;a class="reference external" href="https://www.python.org/psf/codeofconduct/"&gt;Codes of Conduct&lt;/a&gt; are
needed, if only as a reference answer to "Who says I can't do that?". But that
puts a significant burden on list owners and forum volunteers who, in
their spare time and often without much guidance, need to respond authoritatively to complaints and responses.&lt;/p&gt;
&lt;p&gt;What am I suggesting? Whatever I suggest runs the risk of sounding like "We really
should be doing..." when I've just announced that I'm stepping back from doing
things. However, in a spirit of constructive criticism I think I'm suggesting:&lt;/p&gt;
&lt;p&gt;That the PSF take an holistic view of the different public-facing python.org properties (including
bugs.python.org, pypi.python.org, python.org itself, the more public Mailman2/3 lists on python.org,
planet.python.org, &lt;a class="reference external" href="mailto:webmaster@python.org"&gt;webmaster@python.org&lt;/a&gt;) with a view to creating
a common understanding of the roles and responsibilities of those volunteer
teams who manage those resources, including cross-fertilisation of ideas and
a common meta-forum for dealing with misdirected enquiries and CoC issues. Perhaps even synthesising
a single team to handle requests coming in through all of those and other channels.&lt;/p&gt;
&lt;p&gt;Just as I was backing away from my python.org responsibilities, I think there
may have been the beginnings of something like this: a meta-list for list admins.
If there was, then I think that's a step in the right direction. Without question,
there are wider technical issues which &lt;em&gt;could&lt;/em&gt; be addressed given time and
resources (eg the number of accounts needed to operate on different python.org
properties). But I recognise that there are technical and even political challenges to making
that work to everyone's satisfaction.&lt;/p&gt;
&lt;p&gt;I don't know what's in store for Python in the future. Maybe it will continue
to grow and evolve; maybe it will be overtaken by a new kid on the block. I'm
not saying that it doesn't matter. But what matters more is what Python
can offer &lt;em&gt;now&lt;/em&gt; for the many, many people who find it useful, or who merely
find themselves using it, and want support from its community.&lt;/p&gt;&lt;/div&gt;</description><category>Community</category><category>Python</category><guid>http://ramblings.tjg.org.uk/posts/following-up-from-stepping-back/</guid><pubDate>Mon, 15 Oct 2018 05:02:22 GMT</pubDate></item><item><title>Stepping back a bit from python.org</title><link>http://ramblings.tjg.org.uk/posts/stepping-back-a-bit-from-pythonorg/</link><dc:creator>Tim Golden</dc:creator><description>&lt;div&gt;&lt;p&gt;The fact that you hadn't noticed is a testament to the number of people working
behind the scenes at various facets of python.org. For some years I've been part
of a number of teams who sit behind things like the &lt;a class="reference external" href="mailto:webmaster@python.org"&gt;webmaster@python.org&lt;/a&gt; address or
planet.python.org. Or the &lt;a class="reference external" href="mailto:python-list@python.org"&gt;python-list@python.org&lt;/a&gt; mailing list
(mirrored to the comp.lang.python newsgroup). Plus a bunch of other lists including
python-uk, python-win32, python-announce, core-mentorship, python-checkins, speed
and a couple I can't even remember right now! Plus I'm an admin on the python.org website.&lt;/p&gt;
&lt;p&gt;I took on those roles because I felt they were ways I could contribute to the community
without too much commitment of time. Like most people, I have a full-time job (not Python-related)
and some serious commitments outside work. And I rarely have the concentrated spell of time
available to me which I need to do, say, core development work for Python. But most
of those roles only require answering or dealing with the occasional email, sorting out
the odd admin task, or approving a github PR. I can do each thing usually within
a few minutes of receiving the email, even if I'm at work. So I felt that I could
help the Python community without disrupting my life.&lt;/p&gt;
&lt;p&gt;And I could. I stepped up to those roles at different times, but I've been helping
out in that way for between 3 and about 10 years. As have other people, obviously.
Sometimes because I or others have put out a call for help; sometimes, they've just
volunteered spontaneously. In most of those roles I've been part of a small team
which doesn't require much intervention or coordination.&lt;/p&gt;
&lt;p&gt;But recently several things have happened more or less at once: a heavier workload
in my dayjob; a move to a greater out-of-work commitment; some complications with one particular
of those python.org responsibilities which required a much greater input of time and thought.
And I realised: you don't have to do this. I'd done that thing where I felt responsible
for helping out a community to such a great extent that I'd over-extended myself.&lt;/p&gt;
&lt;p&gt;I'd intended
to  scale back gradually what I was doing on python.org, but once I started, it became
easier to just step back from everything. In all but about two cases I was part of a (small)
team so I was able to let them know I was stepping down and leave the situation in good hands.
In a couple of cases I had to reach out to someone else who was or had been involved to ask
them to take over a certain task.&lt;/p&gt;
&lt;p&gt;What surprised me, although it shouldn't have, was the effect on my Inbox. Suddenly, I
was getting no emails for hours on end. I actually thought there was a problem with the
mailserver at first; it was such an unfamiliar sensation. I think the fact that I found it
a relief was a clear sign that I'd made the right choice.&lt;/p&gt;
&lt;p&gt;Let me be clear about this: I stepped back because I needed to, not because of any sour
grapes or misgivings about python.org activities. Or any personal clashes with anyone.
Or any other reason other than: I felt I'd done my stint. &lt;em&gt;Cursum consummavi&lt;/em&gt; and all that.
As I said at the beginning: the fact that you had no idea I had stepped down, nor
that I had even stepped up in the first place is a testament to the unsung work which
goes on in every community, the Python community no less than others.&lt;/p&gt;
&lt;p&gt;So... first, let me thank every person working behind the scenes in the Python community
just to oil the wheels to make everything work which people take for granted. And secondly,
let me invite any of you to offer your services on whatever basis suits you to help out
in some way.&lt;/p&gt;&lt;/div&gt;</description><category>Community</category><category>Python</category><guid>http://ramblings.tjg.org.uk/posts/stepping-back-a-bit-from-pythonorg/</guid><pubDate>Sun, 14 Oct 2018 16:46:54 GMT</pubDate></item></channel></rss>