> If the support is intentionally removed with the goal of keeping out people, then it's both.
No it isn't. Stating it is doesn't make it so.
If I expect you to follow a particular procedure and not support another (which is deemed initially friendly) that is perfectly valid. If it keeps people out that wouldn't otherwise be able to follow it, that is a positive, not negative.
It can gatekeep and be authoritative.
> That was the premise accepted by both of the comments above mine, hence my comment working from that premise.
And the premise is incorrect. Thus my comment.
There are also other reasons. Like having two version of the documentation causes confusion in itself.
> Everyone is a noob at some point, so getting rid of documentation is only a means to prevent someone from learning.
Not if the "noob" documentation obscures knowledge by letting people skip important parts of understanding the process.
> There is no cost to anyone if someone installs Arch without being an expert in the CLI.
Yes there is. That person will quiz people in discord, forums, voice chats, reddit etc when they will invariably be presented with an issue that they cannot resolve. Similarly that why people distro-hop.
RTFM response actually trains people to solve their own problems and is the correct way, by first following the process and then only asking when the process doesn't work.
> Where are you getting this from? The whole conversation was newcomers making changes. Code contributions (i.e. changes) are explicitly the "dues" that OSS devs 'pay'.
I was talking about the benefits of gate-keeping in general. I never said anything about specific about code contributions.
BTW, these people will affect code contributions. Much of the Linux desktop is a clone of other systems (typically Windows) to appease users that expect that UI. This actually dominated the conversation for about 15 years in linux.
If we are talking about the newbies. They have to prove they can follow the documentation provided i.e. RTFM.
> If enough of the congregation feels it needs to change, it will (or it will die out). Modern versions of religions look nothing like they did hundreds of years ago, and not all the changes happened due to schisms/ forks. Everything changes, or it dies.
Every group is lead by a minority. The minority in every group, set the agenda, not the majority. That is fact of life, if you think otherwise you are mistaken. Even revolts are usually led by people who are part of disgruntled minority. Every one of those changes would have been made either by someone important in the Church or the state (as the state and the church was typically tied).
Every single one of those changes were made by elites or governments at the time. Not the majority of the congregation. BTW many of the Churches in England and Europe didn't change that much, that why loads of these people migrated in the first place to the US.
BTW many young converts are going to the Orthodox Church because they see it as the most "OG" version of the Church, because some people crave what they believe to be the authentic experience.
I don't think anything you said is explicitly wrong, but I think there is a lot more nuance and that's where the conversation is breaking down.
Such as "RTFM". You're right. People do need to learn to train themselves. That's the most important skill. But the major problem is that noobs are at the beginning. They don't know where to look. They don't know what questions to ask.
The struggle is important, but it can also be too much at times. A senior shouldn't do everything for the junior, but neither should they let them struggle too much. The trick is in the balance. Let them struggle, but pull them back if they stray too far.
If you don't reign them in, then most of them just go far off course. Most of them just get lost and never return. That's not a good situation for anyone. Most wizards come from them not getting too lost while going on this confusing journey. It's more that we just ended up in similar places. But a lot of luck was involved with that. We know the journey itself is important, but you can't tell me that there weren't times that you tripped and fell and they didn't do anything to help you get where you are now (other than learning resilience). We can make things better.
So don't tell a noob to RTFM, they don't even know what the manual is! Point them to the manual, point them to the right section. Say "hey, give this a shot. Let us know how it goes. If you're still stuck we'll probably need to know what <xyz> is". Your "xyz" should always be a hint as to what your guess to the solution is. Gets them thinking about a certain thing they might not have. This still puts everything on them, lets them struggle, but helps prevent them from getting lost. That's not "RTFM" that's "HTM" (Here's the manual)
No it isn't. Stating it is doesn't make it so.
If I expect you to follow a particular procedure and not support another (which is deemed initially friendly) that is perfectly valid. If it keeps people out that wouldn't otherwise be able to follow it, that is a positive, not negative.
It can gatekeep and be authoritative.
> That was the premise accepted by both of the comments above mine, hence my comment working from that premise.
And the premise is incorrect. Thus my comment.
There are also other reasons. Like having two version of the documentation causes confusion in itself.
> Everyone is a noob at some point, so getting rid of documentation is only a means to prevent someone from learning.
Not if the "noob" documentation obscures knowledge by letting people skip important parts of understanding the process.
> There is no cost to anyone if someone installs Arch without being an expert in the CLI.
Yes there is. That person will quiz people in discord, forums, voice chats, reddit etc when they will invariably be presented with an issue that they cannot resolve. Similarly that why people distro-hop.
RTFM response actually trains people to solve their own problems and is the correct way, by first following the process and then only asking when the process doesn't work.
> Where are you getting this from? The whole conversation was newcomers making changes. Code contributions (i.e. changes) are explicitly the "dues" that OSS devs 'pay'.
I was talking about the benefits of gate-keeping in general. I never said anything about specific about code contributions.
BTW, these people will affect code contributions. Much of the Linux desktop is a clone of other systems (typically Windows) to appease users that expect that UI. This actually dominated the conversation for about 15 years in linux.
If we are talking about the newbies. They have to prove they can follow the documentation provided i.e. RTFM.
> If enough of the congregation feels it needs to change, it will (or it will die out). Modern versions of religions look nothing like they did hundreds of years ago, and not all the changes happened due to schisms/ forks. Everything changes, or it dies.
Every group is lead by a minority. The minority in every group, set the agenda, not the majority. That is fact of life, if you think otherwise you are mistaken. Even revolts are usually led by people who are part of disgruntled minority. Every one of those changes would have been made either by someone important in the Church or the state (as the state and the church was typically tied).
Every single one of those changes were made by elites or governments at the time. Not the majority of the congregation. BTW many of the Churches in England and Europe didn't change that much, that why loads of these people migrated in the first place to the US.
BTW many young converts are going to the Orthodox Church because they see it as the most "OG" version of the Church, because some people crave what they believe to be the authentic experience.