« Return to Thread: [Cooker] Mandriva HCL testing
Re: [Cooker] Mandriva HCL testing
by Romain d'Alverny | Mandriva
::
Rate this Message:
Hi,
Le 8 août 08 à 13:51, Bruno Cornec a écrit :
> Romain d'Alverny|Mandriva said on Tue, Jul 29, 2008 at 07:22:35PM
> +0200:
>> You will not see that many interesting reports at first. One goal
>> of this
>> review precisely is: you check if you have hosts registered
>> already, and
>> then you do comment/rank them.
>
> And what does it bring to have a host registered in it without
> comment ?
Nothing. We may as well not show these (see below).
> For example, I was looking at HP products, found a server I know well
> (dl360 g5) And had that result: [...]
>
> How is it useful to someone, I don't really understand.
> At the minimum, I wold expect a OK/NOK box somewhere, and then for
> those
> interested the details per component.
The OK/NOK status comes from two sources:
* people whose machine has been registered and who have ranked
their system (one needs to login for that purpose; it may not be
obvious at all for now);
* Mandriva QA labs; that's step two.
At the moment, I have 6 reports in db about 6 distinct systems. I
expected this beta preview to have people rank their own systems, but
it appears almost no one does. Again, that may be not that obvious.
Actually, if users do not report on their system, it won't get any
more useful.
As for the details per component, you may get these, but coming from
a system (click on the component name). We do not make components
available as a result of a search query, for now.
>> The key questions afterwise are: is it useful? is it simple to
>> understand/use? what can be scratched out already? what is missing?
>
> Currently, I don't find it useful. Isn't it a duplication of work
> already done elswhere by other distros ? Shouldn't this topic be
> brought
> to the LinuxFundation Distributions ML level and try to work on a
> common
> set ?
Well, I believe so. Still, my assignment to this point is to roll
this one out and working first.
> Also you really need to standardize stuff: HP (not hp, hewlett-
> packard,
> ..) everything uppercase e.g., get the name from dmidecode/lshw, (and
> add the lshw content to the web page), ...
All the data we have is extracted from dmidecode and lshw already. So
most issues about that should be fixed upstream as well, although we
are working on making this better on the web side.
> Sorry to sound negative, I think the initiative is extremely
> useful, but
> the current status is not what you should release.
It's a beta, that's really why I posted it as such and want to hear
comments as yours and upgrade http://wiki.mandriva.com/en/
Hardware_Compatibility_List .
thanks! :-)
romain.
Le 8 août 08 à 13:51, Bruno Cornec a écrit :
> Romain d'Alverny|Mandriva said on Tue, Jul 29, 2008 at 07:22:35PM
> +0200:
>> You will not see that many interesting reports at first. One goal
>> of this
>> review precisely is: you check if you have hosts registered
>> already, and
>> then you do comment/rank them.
>
> And what does it bring to have a host registered in it without
> comment ?
Nothing. We may as well not show these (see below).
> For example, I was looking at HP products, found a server I know well
> (dl360 g5) And had that result: [...]
>
> How is it useful to someone, I don't really understand.
> At the minimum, I wold expect a OK/NOK box somewhere, and then for
> those
> interested the details per component.
The OK/NOK status comes from two sources:
* people whose machine has been registered and who have ranked
their system (one needs to login for that purpose; it may not be
obvious at all for now);
* Mandriva QA labs; that's step two.
At the moment, I have 6 reports in db about 6 distinct systems. I
expected this beta preview to have people rank their own systems, but
it appears almost no one does. Again, that may be not that obvious.
Actually, if users do not report on their system, it won't get any
more useful.
As for the details per component, you may get these, but coming from
a system (click on the component name). We do not make components
available as a result of a search query, for now.
>> The key questions afterwise are: is it useful? is it simple to
>> understand/use? what can be scratched out already? what is missing?
>
> Currently, I don't find it useful. Isn't it a duplication of work
> already done elswhere by other distros ? Shouldn't this topic be
> brought
> to the LinuxFundation Distributions ML level and try to work on a
> common
> set ?
Well, I believe so. Still, my assignment to this point is to roll
this one out and working first.
> Also you really need to standardize stuff: HP (not hp, hewlett-
> packard,
> ..) everything uppercase e.g., get the name from dmidecode/lshw, (and
> add the lshw content to the web page), ...
All the data we have is extracted from dmidecode and lshw already. So
most issues about that should be fixed upstream as well, although we
are working on making this better on the web side.
> Sorry to sound negative, I think the initiative is extremely
> useful, but
> the current status is not what you should release.
It's a beta, that's really why I posted it as such and want to hear
comments as yours and upgrade http://wiki.mandriva.com/en/
Hardware_Compatibility_List .
thanks! :-)
romain.
« Return to Thread: [Cooker] Mandriva HCL testing
| Free embeddable forum powered by Nabble | Forum Help |
