CommunityWikiCrisis

You can feel it, the pulse that Epoch 2020 started is slowly getting weaker and weaker. There are less edits now.

It has been mentioned on WikiMeet 2021-02-06: the community will die again unless a lot of new people with fresh energy appear from somewhere.

TimurIsmagilov invited many people to contribute here. As you can see, only DanInSpace has shown up. This case proves that not many people want to do wiki-stuff.

What do we do? Decay slowly, or miraculously phoenix ourselves, or get more people?

new: 2021-02-25 20:31 UTCLionKimbro:

Yeah. Work priorities and StarCommunity priorities and relationships have asserted themselves. My vaccination is complete. I’ve been focused on my own exploration of the Python package distribution ecology, and getting myself set up for working more publicly, rather than in my own constructed (and unfortunately, private) ecology. I’ve given a couple of hours each week to the UniversityOfBayes? community. I’m treading water with 漢字 studies. I’ve been interacting with the TreeLineOutliner? community, and am looking at extending that project with a SmolNet of its own. I’ve also been working on AggregatedInformation locally. My programming work is presently on building up the infrastructure towards doing that work more publicly.

Python package management and preparation is (if I may put it crudely: ) …, let’s say: “high maintenance.” It’s great, but, is constantly demanding things. The “working publicly” package ecology is – an absolute nightmare, to my thinking. It’s like all the things I dislike about the node.js ecology came and landed into the Python ecology. Of course, it’s not JS’s fault – Python just worked very very incrementally towards creating its package management system, and – it totally shows. Actually, now that I think of it – it’s not just the package management system, it’s the entire ecology of working publicly. Testing systems, version numbers, workflow, virtual environment, task execution, project templates, hooking up command line tools, coding conventions, documentation systems, managing github and PyPI?, misnamed “continuous integration” (more like: automated testing and de-linting,) … – it adds up to a heap of disorganized things, and then a heap of organizers to organize the disorganized things – like Hatch and Poetry and such. If Python public development were a programming language, it’d be old-style PHP. The space of working publicly feels like a free-for-all, and it may continue to be so for another two decades. This has taken up so much of my time, non-productively, just trying to sort out how to get something that works. I think I may write an entire article on the PublicSoftwareBricolage?, or something like that.

I’m sad to have “missed” DanInSpace. I said I’d be involved, and instead, I dropped out. I’m sorry Dan.

new: 2021-02-26 10:09 UTCDanInSpace: LionKimbro it is okay, your work is very important for python community. As part of it i can agree with this situation and hope, you can find solution.

new: 2021-02-25 20:31 UTCLionKimbro: Uh, wait, what?

I appreciate the thought, but just so you know — I don’t think I’ve done anything for the Python community at all really; I have no name in the Python world, and I haven’t contributed to it.

I’d like to contribute ideas to the world of software, but I think that’s a long way off, if it will ever be a thing.

My life is focused on StarCommunity presently. I explore ideas in software and programming with a vague hope that someone might find something interesting and do something bigger with it. But I don’t think I will have a bigger impact.

(CommunityWikiFooter)

Define external redirect: UniversityOfBayes TreeLineOutliner PublicSoftwareBricolage PyPI

Languages: