The issue with jargon is only an issue if the the IRC logs are the primary place where information sharing is happening. It goes like this:<p>If leaders™ are using bouncers and that use is reinforcing the habit of having all info exchange in IRC then, because IRC itself encourages the use of jargon (because it is conversational and personal), the logged information for the project will be very jargony.<p>Mailing list postings, which are a bit more considered and more broadcast oriented, are less subject to the shortcutting that leads to jargon. Thus a mailing list posting ought to be easier to digest, at any time, by someone who is not as familiar with the jargon.<p>So the issue here is not that the jargon makes this difficult for those leaders. Certainly they will be able to scan the logs for the hallmarks of the stuff that matters to them. That&#x27;s exactly why jargon is useful...to them.<p>It&#x27;s not, however, useful to other people. This about keeping the open source projects, you know, open.