Request for winetesting volunteers

Dimitrie O. Paun dpaun at rogers.com
Sat May 29 03:05:29 CDT 2004


On Sat, May 29, 2004 at 09:22:02AM +0200, Ferenc Wagner wrote:
> work again.  It would even make more sense now that the dust
> settled.  Have you perhaps got concrete ideas? 

So here is what's left to do:
  1. Finish the metadata-in-winetest patch
  2. Arrange the reports on WineHQ
  3. Maybe add script signing/checking to winrash/service.cgi
     (this is optional, and just a nice-to-have ATM).

I'm sure you know precisely what's required for (1), so I'll
focus on (2). For that, I was thinking we need a page
(http://www.winehq.org/site/status_testing) that is organized
into two sections (just like our home page, with 
"About Wine"/"Latest News").

The first section (let's call this "Wine Testing") would contain 
a short description of our testing framework, what it does, how 
you can sign up to become a tester, pointers to where the tests 
can be downloaded from, etc. This section is obviously hand crafted.

The second section (call it "Test Reports") would contain links to
the various reports generated by dissect/gather. This section would
me automatically generated. Ideally the section would contain the
current and the previous month (in the form of a calendar, as
reported cal(1)), with the applicable days being links to the
reports. At the bottom of the section we should have a link to a
page listing all historical reports (again if possible in the same
cal(1) format).

Looking at this, it now seems better if we arrange these two
sections one besides the other, like "About Wine" and "Weekly Newsletters"
on our home page. Namely, "Wine Testing" will be in the middle,
while "Test Reports" will be a narrow section to the right of
the page, with the month listed one below the other in decressing
order (and BTW, we could display more than 2 months at a time).

How does this sound?


-- 
Dimi.




More information about the wine-devel mailing list