Differences between revisions 11 and 14 (spanning 3 versions)
Revision 11 as of 2017-05-17 01:03:04
Size: 3018
Editor: PaulWise
Comment: add FSF RYF
Revision 14 as of 2019-01-25 02:50:49
Size: 3398
Editor: PaulWise
Comment: missing whitespace
Deletions are marked like this. Additions are marked like this.
Line 5: Line 5:
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. 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. At some point we'd like to formalize a process.
Line 29: Line 29:
 * DebConf17: [[https://debconf17.debconf.org/talks/70/|BoF]] ([[https://gobby.debian.org/export/debconf17/bof/Hardware-certification-program|notes]])
Line 31: Line 32:
 * Debian derivatives census: [[https://wiki.debian.org/Derivatives/CensusFull?action=fullsearch&context=180&value=title%3ADerivatives%2FCensus%2F+regex%3A%5B%5E%23%5D%5Cs%5C*%5Cshardware%5Cscertification.%5Cshttp&fullsearch=Text|search for hardware certification]]

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. At some point we'd like to formalize a process.

The initial discussion stands as a good starting point on what we want to achieve. To mention some of the points, what Debian needs is:

  • A Hardware Certification 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: may need some legal guidance too, in terms of logo usage.

Final goal

What we aim at, is having a clear (and easy) procedure for hardware vendor to get their hardware (laptop, desktop, servers, etc.) be certified to work with Debian. Once they pass the certification process, they would be allowed to display on their website (and in a more broad way, on all sorts of communications, like emails, brochures, etc.) a logo that displays a compatibility with the Debian operating system.

Why a hardware vendor needs it? How will this benefit Debian?

For some customers, an HCL (Hardware Compatibility List) is a mandatory thing to have in order to start ordering. If hardware vendors aren't capable of displaying a "Debian compatible" log, and ship a Debian HCL, then Debian may simply not be an option for those customers. They will simply look at other operating systems, for which the hardware vendor has been certified.

By having a hardware certification program, Debian may increase its user base, especially the more "corporate" of them.

References