Documentation fix patches

Magnus Melin mkmelin+mozilla at iki.fi
Mon Jun 13 18:44:45 UTC 2016


Sounds pretty ok to me. We could have a metabug kind of thing that we 
link all the commits to though. Otherwise you have nowhere to discuss 
(after the fact) if someone lands wrong documentation.

  -Magnus

On 11.06.2016 00:12, R Kent James wrote:
> As I discuss various issues in bugs, I continually notice the lack of
> documentation in so much of our internal code (Mozilla culture in
> general does not support good code documentation per my standards, but
> that is another issue. New code is routinely landed with no description
> of the purpose of files or modules, for example).
>
> Might I propose a new review rule, applying at least for anything under
> c-c/mailnews and perhaps under other directories? That would be to allow
> anyone who is a module owner or peer under c-c to provide a
> documentation-only patch without review, landed with DONTBUILD? That way
> we could reduce the friction in improving documentation. I actually
> think there is a similar rule in existence in m-c  Does anyone know that
> rule and what is entered for r= or a= to allow it?
>
> :rkent
>
> _______________________________________________
> tb-planning mailing list
> tb-planning at mozilla.org
> https://mail.mozilla.org/listinfo/tb-planning



More information about the tb-planning mailing list