Re: PR backlog (was: [RFC] Deprecation and removal of the drm2 driver)

2018-06-01 Thread Mark Linimon
On Thu, May 31, 2018 at 09:04:25PM -0700, K. Macy wrote: > This is where culling older bug reports comes in. Well, even with doing that, the sheer number really doesn't help the S/N that much. It may make someone a bit neurotic like me feel a bit better, but that's all. > However, when I've

Re: PR backlog (was: [RFC] Deprecation and removal of the drm2 driver)

2018-06-01 Thread Mark Linimon
On Thu, May 31, 2018 at 10:25:10PM -0500, Matthew D. Fuller wrote: > because the incentives are rigged. A bad outside contribution brought > into ports more often yields "hey, you should have noticed" to the > committer and more opprobrium back to the submitter. I believe you're missing two

Re: PR backlog (was: [RFC] Deprecation and removal of the drm2 driver)

2018-05-31 Thread K. Macy
> > I wrote up a couple more paragraphs about why I think it happens and > what we'd need to do to import more of that sense over into src. But > it was way longer than it needs to be. We get a lot more man-hours in > ports/ acting as conduits for the "outside patches -> svn" pipeline > because

Re: PR backlog (was: [RFC] Deprecation and removal of the drm2 driver)

2018-05-31 Thread Matthew D. Fuller
On Thu, May 31, 2018 at 03:49:46PM -0500 I heard the voice of Mark Linimon, and lo! it spake thus: > > We do slightly better turning over ports PRs -- due to the fact that > we attach a maintainer field to each port. This doesn't completely > solve the problem, but it goes some distance. >From

Re: PR backlog (was: [RFC] Deprecation and removal of the drm2 driver)

2018-05-31 Thread Mark Linimon
Straying off-topic from the Subject line ... On Thu, May 31, 2018 at 11:34:18AM -0400, Joe Maloney wrote: > Technically since I was using PC-BSD, and was a committer for that > project I had no real dire need to reach out to FreeBSD about the > [wireless driver issue]. I was simply trying to