[3421] in BarnOwl Developers
barnowl-dev Github account, and notifications
daemon@ATHENA.MIT.EDU (Geoffrey Thomas)
Mon May 20 13:19:05 2013
Date: Mon, 20 May 2013 10:19:01 -0700 (PDT)
From: Geoffrey Thomas <geofft@ldpreload.com>
To: barnowl-dev@mit.edu
As you might have noticed, I've created a Github account named
"barnowl-dev" with email address barnowl-dev@mit.edu, and set it to
"follow" the barnowl repository. This means that notifications relating to
the repository -- pull requests and bugs, mostly -- get copied to the
entire mailing list, as opposed to just folks with Github accounts who
have happened to follow the repo, e.g., by having commit access.
By default, this will mean that those of you already receiving
notifications may receive multiple copies. MIT Cyrus and Gmail seem to
dedup them correctly, but if you're seeing multiple copies, you can just
un-follow the repo on Github to suppress your personal copy. (This will
not affect whether you have commit access.)
The purpose of this is to make sure that everyone on the list stays
abreast of discussion about pull requests, and they're not sent off to
some place where only the committers and folks who have bothered to set up
notifications will see them. Subscribing to barnowl-dev should be
sufficient, by itself. One particular mechanical effect is that pull
requests now count as reaching barnowl-dev in the code review policy,
which specifically allows branches to be merged if they haven't received a
reply within seven days. I think Jason is going to update the wiki text to
be clearer and to recommend Github pull requests as workflow, but this now
allows us to be consistent with the spirit of the existing policy and not
leave interested folks out of the discussion loop.
The password for the account is something random, which I'll send to the
folks on barnowl-locker later today.
--
Geoffrey Thomas
http://ldpreload.com
geofft@ldpreload.com
