svn commit: r317015 - in head/sys: boot/forth conf crypto/chacha20 dev/random libkern sys

[Mark R V Murray]

> On 16 Apr 2017, at 17:04, Rodney W. Grimes <freebsd at pdx.rh.CN85.dnsmgr.net> wrote:
> So you can understand me being started when any of this arrived?  I am
> on several of the mailling list, and I think -security is probably one
> of them.

I was thoroughly ignored last time I tried to use -security. It was, however,
a while back. I'll try again.

> What watch list is this?  And do we have a watch list that is just "New Phabricator
> created" so we can make just that incident go to some mailling list so people stop
> getting caught off guard by commits that have been reviews that they wish they had
> even known there was a review?  We just need a way for being allerted there is a
> new review that we *might* be interested, or care to participate in without being
> on all the watch lists.

There is 'secteam' on Phabricator.

> And to add my hidden Blue Paint, we need to stop fearing the bike shed, the project
> seems to have stifled the communications process to the point it is becoming a
> closed door shop with everyone working in secret then dumping a commit in once they
> are done.  Yes, bike sheds are a bit time consuming, but so is duplicate work cause
> you had no idea someone else was working in the same area (your LKM suprize is
> an excellent example).

> We must stop working in vacuums and start to communicate, and if that means we
> have a few bike sheds... well.. paints on me (though I reserve the blue for 
> personal use!)

Can't please everybody, but I'll add -security to the list next time.

There is a fair bit of history that predates your return to the project; me getting
attention to folks prepared to do reviews is a sore point. I use Phabricator because
it works for me (I get reviews). I was largely ignored on the mailing lists last time
I had a big commit. 

M
-- 
Mark R V Murray