Time to update Wine's status?

[Adam Petaccia]

http://winehq.org/site/status is the website showing Wine's status on
implementing various DLLs, but it hasn't been updated in almost a year!
The information is not only old, but Wine has added new DLLs that aren't
listed. With Wine approaching its 1.0 release, perhaps it should be
decided to update or remove the page.

My vote would be for updating, but I'm not sure where those stats come
from, and that may take away from time better spent on bug hunting.

[Scott Ritchie]

Adam Petaccia wrote:
> http://winehq.org/site/status is the website showing Wine's status on
> implementing various DLLs, but it hasn't been updated in almost a year!
> The information is not only old, but Wine has added new DLLs that aren't
> listed. With Wine approaching its 1.0 release, perhaps it should be
> decided to update or remove the page.
>
> My vote would be for updating, but I'm not sure where those stats come
> from, and that may take away from time better spent on bug hunting.

I propose we get rid of the page altogether, it's pretty much useless
for figuring out how good Wine is.  This is unfortunate, since it's
often the first place people click.

Thanks,
Scott Ritchie

[Edward Savage]

> I propose we get rid of the page altogether, it's pretty much useless
> for figuring out how good Wine is.  This is unfortunate, since it's
> often the first place people click.
>
> Thanks,
> Scott Ritchie

I found it very handy to track down details on mswsock the other day.

I suggest if it is to be removed instead dull it down by turning it in
to a list of dlls wine has and all available information in the form
of links for each dll is listed so that people can speedily find say
the msdn page or relevant wiki pages.  That way it would still be a
handy resource without being a pain to answer to users why a dll is
only 96.23% complete on an out dated page.

[Scott Ritchie]

Edward Savage wrote:
> > I propose we get rid of the page altogether, it's pretty much useless
> > for figuring out how good Wine is.  This is unfortunate, since it's
> > often the first place people click.
> >
> > Thanks,
> > Scott Ritchie
>
> I found it very handy to track down details on mswsock the other day.
>
> I suggest if it is to be removed instead dull it down by turning it in
> to a list of dlls wine has and all available information in the form
> of links for each dll is listed so that people can speedily find say
> the msdn page or relevant wiki pages.  That way it would still be a
> handy resource without being a pain to answer to users why a dll is
> only 96.23% complete on an out dated page.

Why not just move the whole thing into the wiki then?

Thanks,
Scott Ritchie

[Paul Vriens]

Scott Ritchie wrote:
> Edward Savage wrote:
> > > I propose we get rid of the page altogether, it's pretty much useless
> > > for figuring out how good Wine is.  This is unfortunate, since it's
> > > often the first place people click.
> > >
> > > Thanks,
> > > Scott Ritchie
> >
> > I found it very handy to track down details on mswsock the other day.
> >
> > I suggest if it is to be removed instead dull it down by turning it in
> > to a list of dlls wine has and all available information in the form
> > of links for each dll is listed so that people can speedily find say
> > the msdn page or relevant wiki pages.  That way it would still be a
> > handy resource without being a pain to answer to users why a dll is
> > only 96.23% complete on an out dated page.
>
> Why not just move the whole thing into the wiki then?
>
> Thanks,
> Scott Ritchie

That still leaves the question, who decides how 'good' a dll is?

Can't we come up with some guesstimate? We know how many functions there are for 
a given dll, we know how much is implemented, we (could) know how much is tested 
and we know how much of those tests are todo's.

Asking a developer to give the status of a dll is possible but that's against 
the current knowledge. If a new app comes out tomorrow and it uses a whole new 
set of (not 100% implemented) API's the status drops.

[Adam Petaccia]

On Thu, 2008-06-12 at 13:56 -0700, Scott Ritchie wrote:
> > I found it very handy to track down details on mswsock the other day.
> >
> > I suggest if it is to be removed instead dull it down by turning it in
> > to a list of dlls wine has and all available information in the form
> > of links for each dll is listed so that people can speedily find say
> > the msdn page or relevant wiki pages.  That way it would still be a
> > handy resource without being a pain to answer to users why a dll is
> > only 96.23% complete on an out dated page.
>
> Why not just move the whole thing into the wiki then?

I don't really think its wiki material, but could probably be run from a
script for each Wine release. Unless I misunderstand, the numbers are
available from http://source.winehq.org/WineAPI/  (like GdiPlus is 46%
implemented with no documentation, see
http://source.winehq.org/WineAPI/gdiplus.html ). Of course this would
over state our progress as functions that just print a FIXME and return
would be included, but that seems like the more reasonable option.
> Thanks,
> Scott Ritchie