Framebuffer policy [ was Re: Linux 2.5.19]

[James Simmons]

> This is about people who think they're god nicking patches from
> the author and maintainer of drivers and bypassing the maintainer
> completely.

Please no fighting. It is clear the problem is the lack of order here.
I understand how Russell feels. Most of the time people send in new fbdev
drivers or good size patches without consulting me or Geert first. I have
to say it has gotten better. So here goes for policy time:

--------------------------------------------------------------------
             Framebuffer driver policy.

1) Basic one or few line fixes for drivers can go straight into the
   kernel. Please don't abuse this.

2) All new drivers must be posted to the fbdev developement list for
   peer review. Me and/or geert have final fword about them going in.
   Please note we do get busy so just harass me about your driver. I
   will not be offended and it pushs me to go do it. I'm the type of
   person if I don't do it right away I will forget.

   [e-mail]

3) Large changes should be posted to both the framebuffer list and the
   kernel mailing list as well to the framebuffer author if they
   are know. Again it is for peer review and wide scale testing. We 
   need to make clear what drivers where effect. And yes if you are the 
   maintainer of a driver you should mail yourself. It makes it easier
   for users to reply to you directly.  

If no one follows these rules then their changes will be ignored. No
exceptions including for myself.

-----------------------------------------------------------------
How does this sound? Again sorry about the confusion.