I'm not sure if there is a common name for this particular source of discomfort, but that quote definitely contains a lot of it. I'm a historical contributor to the Python source repository, but something about the social structure of the project has changed significantly in recent years that would dissuade me from submitting changes in future. The focus in the statement above no longer feels like it is on the actual productive output of the project itself, and in previous years it wasn't like that, nor needed to be like that.
Reminds me of something like the minutes of a professional schmoozer's business lunch, rather than a technical meeting, or something like that. If you have ever seen a stray engineer at an event like this (or had the misfortune of being that engineer), this feeling probably captures the problem well. Whatever it is, I'd love to see less of it.
I don’t believe you. Python was never like this in the past, and has a long history of rejecting objectively good performance enhancements because the BDFL and friends wanted the implementation to remain a simple teaching example for students.
I don't think anyone would deny Python has changed since then, I think most notably in the years following the release of Django, Python becoming a go-to web language, and the size of the community exploding.
They are good at self-promotion and corporate backed. Real work in the Python world is done by the quieter types who don't strive to "be in charge".
I'm rather interested in why you feel that way however. Do you think your work, or the work of some specific project/person hasn't received the recognition it deserves ? Or that the attention of the community diverted from important work toward subjects that are more eye catching ?
I'm struggling to find that in the quote. What is the fraternity in question?
Much to the opposite, just like many other big and important open source projects, they are actively trying to recruit, mentor and urge people to come as far "in" as possible. It takes a lot of work and dedication to get acquainted with a code base.
The choice of the word "fraternity" by the poster above was deliberate and seems to be being used to imply a more severe exclusion of others.
However, I've just looked it up in Merriam Webster, and it looks like this term can include female members, too, even thought the word and the related adjective have strong masculine associations. Wikipedia basically says the same, "Although membership in fraternities was and mostly still is limited to men, ever since the development of orders of Catholic sisters and nuns in the Middle Ages and henceforth, this is not always the case. There are mixed male and female orders, as well as wholly female religious orders and societies, some of which are known as sororities in North America."
We don't even have to argue anyway. From a dictionary:
> [treated as singular or plural] a group of people sharing a common profession or interests: e.g. “members of the hunting fraternity”.
Frankly it’s very easy to google.
The situation is even worse now.
But why are you using a throwaway account ? And that you that have been answering the other comments with also newly created accounts ?
I don’t have anything about a community being an old boys’ club (would be nice to be in one some day, I reckon it’s what older people’s equivalent of a “safe space” is), it’s that they try hard to pretend they are something else that irks me.
But for the life of me I couldn’t find “python” and “minibosses” mentioned in the same document on the internet, except for an integration testing package and a computer game. So I think the story alluded to is bogus.
There’s a minuscule likelihood of it all being a twitter drama with key characters then nuking their tweets or deleting their accounts, but if it was of any significance some blog would have echoed it.
> I'd prefer if you didn't feel the need to play miniboss on the Python project
Disclosure: I am a current core dev
"On a personal level, we are impressed by Sam’s work so far and invited him to join the CPython project. I’m happy to report he is interested, and to help him ramp up to become a core developer, I will be mentoring him. Guido and Neil Schemenauer will help me review code for the interpreter bits I’m unfamiliar with."