Differences between revisions 2 and 3
Revision 2 as of 2017-05-16 05:59:55
Size: 1522
Editor: rrs
Comment:
Revision 3 as of 2017-05-16 06:00:28
Size: 1527
Editor: rrs
Comment:
Deletions are marked like this. Additions are marked like this.
Line 9: Line 9:
* A '''Hardware Cerfitication Testsuite''' in place, which could be used by Hardware vendors and provide Debian with the results.
* As a project, we need to form a team/committee to oversee the certification process
* We need a '''tech team''' to formulate '''Certification Verification and Validation''' criteria
* What should be the certification approach ? Very closely tied to every bit of Hardware (which could result in an enormous database). Or should we push certification to a lower/higher level ? Ultimate goad needs to be that a Debian Certified hardware should work proper.
* Attribution: As Paul/Thomas mentioned, this may need some legal guidance too, in terms of logo usage.
 * A '''Hardware Cerfitication Testsuite''' in place, which could be used by Hardware vendors and provide Debian with the results.
 * As a project, we need to form a team/committee to oversee the certification process
 * We need a '''tech team''' to formulate '''Certification Verification and Validation''' criteria
 * What should be the certification approach ? Very closely tied to every bit of Hardware (which could result in an enormous database). Or should we push certification to a lower/higher level ? Ultimate goad needs to be that a Debian Certified hardware should work proper.
 * Attribution: As Paul/Thomas mentioned, this may need some legal guidance too, in terms of logo usage.

The purpose of this page is to define a Certification Process for Debian. To start with, this may be focused on Hardware Certification, but later could also include Software Certification.

We have had recent conversation on this topic and have interest to have such a process in place. For now, this page intends to capture summary of these conversations. Hopefully, at DC17, we'd like to have a BoF around this topic and formalize a process.

This thread [1] stands as a good starting point on what we want to achieve. To mention some of the points, what Debian needs is:

  • A Hardware Cerfitication Testsuite in place, which could be used by Hardware vendors and provide Debian with the results.

  • As a project, we need to form a team/committee to oversee the certification process
  • We need a tech team to formulate Certification Verification and Validation criteria

  • What should be the certification approach ? Very closely tied to every bit of Hardware (which could result in an enormous database). Or should we push certification to a lower/higher level ? Ultimate goad needs to be that a Debian Certified hardware should work proper.
  • Attribution: As Paul/Thomas mentioned, this may need some legal guidance too, in terms of logo usage.

[1] https://lists.debian.org/debian-project/2017/05/msg00016.html

Additional References https://access.redhat.com/documentation/en/red-hat-enterprise-linux-hardware-certification/ https://certification.ubuntu.com/