But what happens in the absence of bouncers? Is the information even written down at all? (IME: often no). If the information ends up on a mailing list or issue tracker, is that any more accessible to other people than IRC history? (IME: again no).
Rather than try to get people to change their habits, it would be better to produce tooling that supports the use strategies people have evidently found effective:
* Public, indexed/searchable chat logs in a place that's easy for newcomers to find them (many OSS projects do this already)
* Chat systems where you don't have to do some complex bouncer setup to be able to participate on the same level as the core contributors (e.g. Slack or Gitter, where scrollback is available to every user, even newcomers)
* Support for indexing into useful pieces of chat log, or for excerpting parts of a log into a more permanent home. Slack does something a bit like this (persistent snippets in a channel). HipChat offers some level of integration with Atlassian's terrible wiki product. Google wave seemed to have this as part of its idea.
Offer a public quasselcore with your project and allow people to create accounts on it?
> * Support for indexing into useful pieces of chat log, or for excerpting parts of a log into a more permanent home. Slack does something a bit like this (persistent snippets in a channel). HipChat offers some level of integration with Atlassian's terrible wiki product. Google wave seemed to have this as part of its idea.
That’s already possible if at least one of your users is using Quassel as bouncer, as it stores its logs in an SQL database. Supported by default are SQLite and PostgreSQL.
Logs are honestly a pain if you are just trying to keep up with the important things. Lines and lines of join/quit/hi/hello/how's that pasta/I like movies/etc...
I believe the #indiewebcamp channel handles this situation with a wiki. I haven't use it in a while but I think the wiki-bot lets you define wiki entries right from IRC so if something important is discussed then it can be permanently summarized and indexed on the fly.
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.
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.
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's exactly why jargon is useful...to them.
It's not, however, useful to other people. This about keeping the open source projects, you know, open.
Sure, the title is cliched, that's on purpose.
Sure, notification can be an issue, but I think I made it clear that that is a secondary issue. The primary issue is that the use of bouncers results in habits which result in the information being inaccessible to other people, other people who may not yet be able to decode the logs.
In other words, to people who are saying "using a bouncer make my life easier": It's not about you. It's about making a conscious effort to make other people lives easier and make projects more accessible.