[3422] in BarnOwl Developers
Re: barnowl-dev Github account, and notifications
daemon@ATHENA.MIT.EDU (Jason Gross)
Mon May 20 13:35:55 2013
In-Reply-To: <alpine.DEB.2.00.1305201011430.12782@dr-wily.mit.edu>
From: Jason Gross <jasongross9@gmail.com>
Date: Mon, 20 May 2013 13:35:22 -0400
To: Geoffrey Thomas <geofft@ldpreload.com>
Cc: barnowl-dev@mit.edu
--089e0111d7eeaac79204dd29c3fd
Content-Type: text/plain; charset=ISO-8859-1
I've updated https://barnowl.mit.edu:444/wiki/code-review and
https://barnowl.mit.edu:444/wiki/Contributing. For the moment, I've worded
it so that github pull requests are on par with email discussion.
Note that, at least for me, github emails show up, at least some of the
time, as being from notifications@github.com and to
barnowl@noreply.github.com; if you have been filtering on
barnowl-dev@mit.edu, you might want to update your filters.
Additionally, geofft, if I'm reading blanche -l barnowl-locker correctly,
the only people on barnowl-locker are you and adehnert.
-Jason
On Mon, May 20, 2013 at 1:19 PM, Geoffrey Thomas <geofft@ldpreload.com>wrote:
> 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
>
--089e0111d7eeaac79204dd29c3fd
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr">I've updated=A0<a href=3D"https://barnowl.mit.edu:444/=
wiki/code-review">https://barnowl.mit.edu:444/wiki/code-review</a>=A0and=A0=
<a href=3D"https://barnowl.mit.edu:444/wiki/Contributing">https://barnowl.m=
it.edu:444/wiki/Contributing</a>. =A0For the moment, I've worded it so =
that github pull requests are on par with email discussion.<div>
<br><div><div>Note that, at least for me, github emails show up, at least s=
ome of the time, as being from <a href=3D"mailto:notifications@github.com">=
notifications@github.com</a> and to <a href=3D"mailto:barnowl@noreply.githu=
b.com">barnowl@noreply.github.com</a>; if you have been filtering on <a hre=
f=3D"mailto:barnowl-dev@mit.edu">barnowl-dev@mit.edu</a>, you might want to=
update your filters.</div>
</div></div><div><br></div><div style>Additionally, geofft, if I'm read=
ing=A0blanche -l barnowl-locker correctly, the only people on barnowl-locke=
r are you and=A0adehnert.</div><div style><br></div><div style>-Jason</div>
</div><div class=3D"gmail_extra"><br><br><div class=3D"gmail_quote">On Mon,=
May 20, 2013 at 1:19 PM, Geoffrey Thomas <span dir=3D"ltr"><<a href=3D"=
mailto:geofft@ldpreload.com" target=3D"_blank">geofft@ldpreload.com</a>>=
</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">As you might have noticed, I've created =
a Github account named "barnowl-dev" with email address <a href=
=3D"mailto:barnowl-dev@mit.edu" target=3D"_blank">barnowl-dev@mit.edu</a>, =
and set it to "follow" the barnowl repository. This means that no=
tifications relating to the repository -- pull requests and bugs, mostly --=
get copied to the entire mailing list, as opposed to just folks with Githu=
b accounts who have happened to follow the repo, e.g., by having commit acc=
ess.<br>
<br>
By default, this will mean that those of you already receiving notification=
s may receive multiple copies. MIT Cyrus and Gmail seem to dedup them corre=
ctly, 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 whethe=
r you have commit access.)<br>
<br>
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 pl=
ace where only the committers and folks who have bothered to set up notific=
ations will see them. Subscribing to barnowl-dev should be sufficient, by i=
tself. One particular mechanical effect is that pull requests now count as =
reaching barnowl-dev in the code review policy, which specifically allows b=
ranches 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 recom=
mend Github pull requests as workflow, but this now allows us to be consist=
ent with the spirit of the existing policy and not leave interested folks o=
ut of the discussion loop.<br>
<br>
The password for the account is something random, which I'll send to th=
e folks on barnowl-locker later today.<span class=3D"HOEnZb"><font color=3D=
"#888888"><br>
<br>
-- <br>
Geoffrey Thomas<br>
<a href=3D"http://ldpreload.com" target=3D"_blank">http://ldpreload.com</a>=
<br>
<a href=3D"mailto:geofft@ldpreload.com" target=3D"_blank">geofft@ldpreload.=
com</a><br>
</font></span></blockquote></div><br></div>
--089e0111d7eeaac79204dd29c3fd--
