Status of the Status pages?

[Tomas -]

The status pages in general seems to have been at a standstill since around 2007. The exception is the "API Stats" page, but now this page hasn't been updated since May 22.
Is there any plans/ideas on what to do with the status pages?

[Scott Ritchie]

Tomas - wrote:
> The status pages in general seems to have been at a standstill since
> around 2007. The exception is the "API Stats" page, but now this page
> hasn't been updated since May 22.
>
> Is there any plans/ideas on what to do with the status pages?

My overall goal for them is to replace them with dynamically generated
statistics based.  Some possible things to use:
 - Bugzilla stats, especially a chart of open 1.2 bugs and total New bugs
 - Winetest coverage (based on gcov)
 - Winetest results
 - Austin's test suite results (especially if we get a good number of
tests for apps that aren't yet working)
 - AppDB stats

I'll work on some of this after I go through the rest of the WineHQ.org
pages (eg the About page), which also need cleanup.

Thanks,
Scott Ritchie

[Steven Edwards]

On Tue, Jul 21, 2009 at 8:02 AM, Scott Ritchie wrote:
> My overall goal for them is to replace them with dynamically generated
> statistics based.  Some possible things to use:
>  - Bugzilla stats, especially a chart of open 1.2 bugs and total New bugs
>  - Winetest coverage (based on gcov)
>  - Winetest results
>  - Austin's test suite results (especially if we get a good number of
> tests for apps that aren't yet working)
>  - AppDB stats
>
> I'll work on some of this after I go through the rest of the WineHQ.org
> pages (eg the About page), which also need cleanup.

I would add it would be nice to show how much of the API is documented
vs exported. We could keep a similar structure to the page we have now
but pull data from

http://source.winehq.org/WineAPI/

and show how well documented the functionality we export is covered.

Thanks