+1. Check out ASFBot for logging IRC, along with other integrations.[1] ASFBot can also be used for record keeping for IRC meetings (example [3]) which can automatically be sent to the appropriate apache mailing list. All other logs are archived online. [4] It’d easy enough to link to those archived logs via the website, etc.
[1] http://wilderness.apache.org/manual.html <http://wilderness.apache.org/manual.html> [3] http://wilderness.apache.org/#meetings <http://wilderness.apache.org/#meetings> [4] http://wilderness.apache.org/channels/#logs-#aurora <http://wilderness.apache.org/channels/#logs-%23aurora> > On Aug 26, 2016, at 11:17 AM, Jason Brown <jasedbr...@gmail.com> wrote: > > +1. How/where will this run? Is there any apache infra that we can make use > of? > > On Fri, Aug 26, 2016 at 10:48 AM, Jake Luciani <jak...@gmail.com> wrote: > >> +1 so long as it filters out the join/leave stuff :) >> >> On Fri, Aug 26, 2016 at 1:42 PM, Jeff Jirsa <jeff.ji...@crowdstrike.com> >> wrote: >> >>> There exists a #cassandra-dev IRC channel that’s historically been used >> by >>> developers discussing the project – while it’s public, it’s not archived, >>> and it’s not a mailing list. The ASF encourages all discussion to be >>> archived, and ideally, archived on a public mailing list. >>> >>> >>> >>> Jake suggested, and I want to propose on the list, that we copy a log of >>> that channel (minus join/part activity) to dev@ either daily or weekly. >>> We’ll need to make sure we comply with Freenode’s IRC logging policy, but >>> the project / developers receives the best of both worlds – fast, real >> time >>> chat but also public archives/visibility for people who aren’t online at >> a >>> given moment. The volume may be a bit higher than most of us have come >>> expect from the list, but it brings the project closer to doing things in >>> The Apache Way, and we can give it an easily-filtered subject for folks >> who >>> don’t want that noise. >>> >>> >>> >>> >>> >> >> >> >> -- >> http://twitter.com/tjake >>
