[RFCv2 1/2] doc: Add statistics page for v2022.07

[Heinrich Schuchardt]

Am 12. Juli 2022 18:10:08 MESZ schrieb Tom Rini <trini at konsulko.com>:
>On Tue, Jul 12, 2022 at 06:01:58PM +0200, Heinrich Schuchardt wrote:
>> On 7/12/22 17:55, Tom Rini wrote:
>> > On Tue, Jul 12, 2022 at 05:42:31PM +0200, Heinrich Schuchardt wrote:
>> > > On 7/12/22 17:32, Tom Rini wrote:
>> > > > These tables are generated by gitdm, patched to generate an rST .. table
>> > > > directive and then
>> > > > with the header, orphan tag and stats summary added manually.
>> > > > 
>> > > > Cc: Heinrich Schuchardt <xypron.glpk at gmx.de>
>> > > > Signed-off-by: Tom Rini <trini at konsulko.com>
>> > > > ---
>> > > > Changes in v2:
>> > > > - Include :orphan: this time
>> > > > - Use .. table and auto-width as suggested by Heinrich
>> > > > ---
>> > > >    .../statistics/u-boot-stats-v2022.07.rst      | 806 ++++++++++++++++++
>> > > >    1 file changed, 806 insertions(+)
>> > > >    create mode 100644 doc/develop/statistics/u-boot-stats-v2022.07.rst
>> > [snip]
>> > > > +
>> > > > +.. table:: Employers with the most signoffs (total 266)
>> > > > +   :widths: auto
>> > > > +
>> > > > +   =========================  ==========
>> > > > +   Name                       Changesets
>> > > 
>> > > %s/Changesets/Signoffs/
>> > > 
>> > > The column heading of column 2 should depend on the table.
>> > 
>> > The code to generate these is pretty basic.  Changesets isn't quite
>> > right for code added/removed either.  I'll go take a pass at passing in
>> > a "what" rather than hard-coding Changesets, but would it be OK to just
>> > say "Quantity" or "Amount" for each table instead?
>> 
>> "Count" should always fit.
>
>That's an easy one.  With that, are you OK with the tables and how
>they'll be referenced?  If so I'll get started on the follow-up patch to

Otherwise things looked ok.

You can render the page in a Python virtual environment using doc/sphinx/requirements.txt to check for correct formatting.

Best regards

Heinrich 

>add that data in.  I'm doing that as another commit since it's going to
>be too big to meaningfully review other content with.
>