From dev-return-18348-apmail-couchdb-dev-archive=couchdb.apache.org@couchdb.apache.org Mon Oct 3 13:52:32 2011 Return-Path: X-Original-To: apmail-couchdb-dev-archive@www.apache.org Delivered-To: apmail-couchdb-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id DDF3E9DCF for ; Mon, 3 Oct 2011 13:52:31 +0000 (UTC) Received: (qmail 89687 invoked by uid 500); 3 Oct 2011 13:52:31 -0000 Delivered-To: apmail-couchdb-dev-archive@couchdb.apache.org Received: (qmail 89639 invoked by uid 500); 3 Oct 2011 13:52:31 -0000 Mailing-List: contact dev-help@couchdb.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@couchdb.apache.org Delivered-To: mailing list dev@couchdb.apache.org Received: (qmail 89631 invoked by uid 99); 3 Oct 2011 13:52:31 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 03 Oct 2011 13:52:31 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of bchesneau@gmail.com designates 209.85.215.180 as permitted sender) Received: from [209.85.215.180] (HELO mail-ey0-f180.google.com) (209.85.215.180) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 03 Oct 2011 13:52:23 +0000 Received: by eyb6 with SMTP id 6so3757212eyb.11 for ; Mon, 03 Oct 2011 06:52:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=omynmWSBAMZONabloz1NT4YcoiNLNKT2TU1XIU5obL8=; b=tAVTZE81LHQpMRVlowFx4xvyJo5GUWmUFXaz9jXcqukKcj33qz2BnpJnU3gx0E9+1O rPHdPZa7JFTrlhG0o+Qrf39Ol0GbSI4UbJqdt+KFTH0m0N1uMA8RwUUR2lMdU1Qk1fWt JerpiWuQ38B1vV2vFVI6okBlcBGO74WUg46AI= MIME-Version: 1.0 Received: by 10.213.98.76 with SMTP id p12mr788610ebn.39.1317649923606; Mon, 03 Oct 2011 06:52:03 -0700 (PDT) Received: by 10.213.19.129 with HTTP; Mon, 3 Oct 2011 06:52:03 -0700 (PDT) In-Reply-To: <5C9091D0-D882-4B9E-8B87-E6A4EB774E70@apache.org> References: <5C9091D0-D882-4B9E-8B87-E6A4EB774E70@apache.org> Date: Mon, 3 Oct 2011 15:52:03 +0200 Message-ID: Subject: Re: CIA.vc notifications in IRC From: Benoit Chesneau To: "dev@couchdb.apache.org" Content-Type: multipart/alternative; boundary=0015174c1666a28adf04ae65472c X-Virus-Checked: Checked by ClamAV on apache.org --0015174c1666a28adf04ae65472c Content-Type: text/plain; charset=ISO-8859-1 On Monday, October 3, 2011, Noah Slater wrote: > I'd have a chat with the CIA.vc guys, to see what they say. We're obviously not the first people wanting notifications for a Git repository. I would avoid writing our own IRC bot at almost any cost. it's possible for sure. the github cia.vc service works like you described. > > On 3 Oct 2011, at 08:31, Paul Davis wrote: > >> Randall remind me that I haven't implemented IRC notifications for >> commits yet so I started looking at CIA.vc's GIT support. The more I >> look the less I think its a good fit for Git. This is mostly tied to >> the fact that lots of old VCS hooks are written with an assumption of >> "one push is one commit." >> >> So with CIA.vc (unless I'm missing the docs, which includes reading >> the source to the recommended git hook) we have to think about things >> like, one IRC notification per commit, per branch, or per push. IOW, I >> don't see a good way for messages like "davisp updated refname [hash1 >> ... hash2] " type notifications. >> >> Alternatively, I can write a short script that just does the IRC >> notifications which isn't too hard. Its a bit hackish, but we use >> similar things at work and it seems to be more robust than even >> GitHub's IRC bot. >> >> Anyway, input is requested so I know what I should be looking at. > > --0015174c1666a28adf04ae65472c--