The CentOS main IRC channel is described elsewhere in greater detail, but a central characteristic of the channel #centos is that it discourages 'spoonfeeding' answers to random people who wander into the channel, and ask a random question.
Such questions may be off topic, and indeed some have no CentOS specific aspect at all. Neither is the channel a new user training venue, as it does not and cannot scale effectively. The CentOS project publishes full documentation for such purposes. Others relate to downstream or broken fork implementations based on CentOS, often seen in virtual server applications.
'In the know' channel regulars reject guessing how to fix random non-CentOS broken content. Teaching good diagnostic skills, partition of problems, reading the documentation [ Read That FINE Manual ], and so forth are demonstrated daily. Tools used to identify broken or non-CentOS installations, and so to avoid potentially harmful haphazard guessing, are listed in part at the IRC request page.
From experience, the result of giving such a 'spoonfed' answer, is that the questioner disappears from the channel, but has not learned how to solve their problem; they often re-appear weeks later, with the same question. Because they were not taught how to research answers, the process recurs. We know, as the channel is continuously logged and monitored by CentOS project members, and we detect such. This boring repetition of simple answers for unprepared questioners has the negative effect (in channels without the #centos approach) of driving channel regulars with strong diagnostic technique and experience away. Think of it as a poor Signal to Noise ratio.
It is no fun for channel regulars to be pounded with the same questions, which a tiny bit of research will readily answer, day after day; some topics are so common that a FAQ type entry is written in this wiki. This may or not make sense with questions with a specific CentOS aspect, because it imposes maintenance load into the future, keeping it up to date. See, e.g., the second part of the java on CentOS article, which rots with great regularity.
Additionally, the Socratic approach of the channel is signaled by the fact that all entering the IRC channel see the '/topic' which carries a link to the ESR writeup about How to Ask Questions the Smart Way. Similar pieces exist by others. Other statements of #centos IRC channel management intent also exist on the main web pages and are worth a read.
Another part of the '/topic' is the strong: DO NOT PASTE IN HERE (unless asked; 1 line MAX) rule, and reference to a pastebin. This distaste for large pastes has been picked up in some channels of related projects. Clearly in a development channel, large pastes in channel are common and proper; but in #centos, it is just a confirmation by the paster that they have disregarded the '/topic'.
The takeaway here is that CentOS has consciously chosen to use a Socratic method approach, that of an informed mentor asking leading questions of a student, to guide a questioner to finding an answer; this has the effect also of making the channel more of an educational tool for 'lurkers'. Of necessity, this also disfavors 'spoonfeeding' answers.
"Give a man a fish and you feed him for a day. Teach him how to fish and you feed him for a lifetime." -- Lao Tzu 老子
"Give a man a fire and he's warm for a day, but set fire to him and he's warm for the rest of his life. "