From owner-freebsd-questions@freebsd.org Wed Jul 27 07:05:38 2016 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 26CC1BA569B for ; Wed, 27 Jul 2016 07:05:38 +0000 (UTC) (envelope-from matthew@FreeBSD.org) Received: from smtp.infracaninophile.co.uk (smtp.infracaninophile.co.uk [81.2.117.100]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "smtp.infracaninophile.co.uk", Issuer "infracaninophile.co.uk" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id AC34818D9 for ; Wed, 27 Jul 2016 07:05:37 +0000 (UTC) (envelope-from matthew@FreeBSD.org) Received: from liminal.local (liminal.infracaninophile.co.uk [IPv6:2001:8b0:151:1:3636:3bff:fed4:b0d6]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: m.seaman@infracaninophile.co.uk) by smtp.infracaninophile.co.uk (Postfix) with ESMTPSA id 38AD984F3 for ; Wed, 27 Jul 2016 07:05:29 +0000 (UTC) Authentication-Results: smtp.infracaninophile.co.uk; dmarc=none header.from=FreeBSD.org Authentication-Results: smtp.infracaninophile.co.uk/38AD984F3; dkim=none; dkim-atps=neutral Subject: Re: freeBSD software certification process? To: freebsd-questions@freebsd.org References: From: Matthew Seaman Message-ID: <8d44637c-07e3-302c-8baf-56249a46cf56@FreeBSD.org> Date: Wed, 27 Jul 2016 08:05:28 +0100 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) Gecko/20100101 Thunderbird/45.2.0 MIME-Version: 1.0 In-Reply-To: Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="58PUFAmatpaOND9lTLNbiqN3r5PpNo87E" X-Spam-Status: No, score=-1.2 required=5.0 tests=BAYES_00,SPF_SOFTFAIL autolearn=no autolearn_force=no version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on smtp.infracaninophile.co.uk X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Jul 2016 07:05:38 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --58PUFAmatpaOND9lTLNbiqN3r5PpNo87E Content-Type: multipart/mixed; boundary="HcW53m0HbpKEetkrDxgSjrAbg4FuKVG0w" From: Matthew Seaman To: freebsd-questions@freebsd.org Message-ID: <8d44637c-07e3-302c-8baf-56249a46cf56@FreeBSD.org> Subject: Re: freeBSD software certification process? References: In-Reply-To: --HcW53m0HbpKEetkrDxgSjrAbg4FuKVG0w Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable On 27/07/2016 00:12, Stephane Brunet wrote: > We are a software vendor, and I'm wanting to *certify our software prod= uct > with freeBSD* in order to address some of our prospective customer's wh= o > enjoy freeBSD, but I'm having trouble finding information regarding tha= t > process and its requirements. >=20 > Our software stack consists of a daemon and a kernel module. >=20 > Can you point me in the right direction? Certify in what sense? Unlike, for instance, java, there isn't a third party who would run some tests and issue you with a stamp of approval. Essentially as software authors, you can build your software on FreeBSD, run whatever tests you think necessary to prove a suitable level of functionality and then market your software as 'FreeBSD supported' all on your own recognizance. There are other similar support offerings available in certain circumstances. For instance you can get your FreeBSD based product registered as "Supported" on Microsoft Azure. If you're interested in FreeBSD as a commercial platform, then I'd suggest getting in touch with the FreeBSD Foundation (info@freebsdfoundation.org) just on general principles. Promoting commercial use of FreeBSD is a big part of the Foundation's remit. Cheers, Matthew --HcW53m0HbpKEetkrDxgSjrAbg4FuKVG0w-- --58PUFAmatpaOND9lTLNbiqN3r5PpNo87E Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQJ8BAEBCgBmBQJXmF04XxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQ2NTNBNjhCOTEzQTRFNkNGM0UxRTEzMjZC QjIzQUY1MThFMUE0MDEzAAoJELsjr1GOGkATyEsP/1Yk068F27O2PG4QV2Xd0pVq IZUntJUKJi7HoU2vHMw2mt8HdDmwtoTQaxB3I0f7vmSeSu5IxyAvm0xsxYZiIu9a qBEmrIDPr25Sljk5lAXg+kpPDQFrDQJG1cDbREX3kUHXX1E6KtgTxRPoWYgV0y0d W3uRJn/Qnxgp0NJ8jOcU/1Edm0L+5y2+X6ZzOtPF7KVHT/JdpBWJpdg2KMDUmS7s BHJv5K+yg1vbELRgAaJ6gm1AmRW5GAnsios9CxNw/teUQNzJ+S9Oqh2hFNSDlT6r bsgUUBN8T2sPpTHZ+bKzzTZD6CyaU3vKELcX1BsD6SMnHjApZKQ12zXpkK63zyXr b2HOi30tYQbwF6SegwLQfIXjXapVPSAg+iUEM4KPEUoFYfl3HeIjgWEluVVeVzz5 4ZJmzxeV48K7lUbW/LbgcoUFFAl6P1bYDpw0fW3bbKrFJg9rLlRybqbQk7dzXL7A KDHKJbQ1CgeC10tdQXIbxlfQ+DijoHXlnQysm3CQNN45kxZsWAdg/Pf2YqV9v7lf cMZRt0WQ+Ox5UnpMn1IyLhnNT1irHvqK+pxoXeM46ffjxFEHfZdqEMZG1vsbMFpG tLgxHLTfEndnwrsK8aHxabrBZASiXVtOKgTYSLtfHU+qnW+F41y2FQJIsBdRUxD4 oTnMnSqhm47fRmyeB9dw =8n9P -----END PGP SIGNATURE----- --58PUFAmatpaOND9lTLNbiqN3r5PpNo87E--