|
| 1 | +{ |
| 2 | + "Information for OEMs": "", |
| 3 | + "Give your customers the best experience with elementary OS.": "", |
| 4 | + "Partners & Retailers": "", |
| 5 | + "We offer two ways to be listed as an OEM of elementary OS in <a href=\"https://store.elementary.io\">our store</a>, with differing requirements and benefits.": "", |
| 6 | + "Partner": "", |
| 7 | + "Per-model approval, with each model featured in <a href=\"https://store.elementary.io\">our store</a>.": "", |
| 8 | + "Requirements:": "", |
| 9 | + "Official involvement from elementary, Inc.": "", |
| 10 | + "Negotiable per-device royalty": "", |
| 11 | + "Strict software guidelines": "", |
| 12 | + "Trademark compliance": "", |
| 13 | + "Retailer": "", |
| 14 | + "A link to your website or landing page listed in <a href=\"https://store.elementary.io\">our store</a>.": "", |
| 15 | + "Selling devices with elementary OS": "", |
| 16 | + "Per-device royalty encouraged": "", |
| 17 | + "Resources": "", |
| 18 | + "Installation": "", |
| 19 | + "The elementary OS Installer treats every installation as an OEM installation; step through it to install the OS, then shut down the device and it is ready to be shipped to a customer. Or, to create your own custom image: install the OS, configure any necessary packages or settings using a temporary administrator account, delete the account, and then create an image of the disk. In both cases, Initial Setup will create an end user account upon the customer's first boot.": "", |
| 20 | + "<a href=\"https://github.com/elementary/installer\" target=\"_blank\" rel=\"noopener\" class=\"read-more\">Installer</a>": "", |
| 21 | + "<a href=\"https://github.com/elementary/initial-setup\" target=\"_blank\" rel=\"noopener\" class=\"read-more\">Initial Setup</a>": "", |
| 22 | + "System Settings": "", |
| 23 | + "System Settings offers several advantages to OEMs shipping elementary OS. From its pluggable architecture to easily-provided branding, System Settings was designed with OEMs in mind.": "", |
| 24 | + "Plugs": "", |
| 25 | + "System Settings (codenamed <a href=\"https://github.com/elementary/switchboard\" target=\"_blank\" rel=\"noopener\">Switchboard</a>) uses a concept of “Plugs” to provide pluggable settings for various hardware and software concerns. For example, <a href=\"https://github.com/elementary/switchboard-plug-mouse-touchpad/\" target=\"_blank\" rel=\"noopener\">Mouse & Touchpad settings</a> are provided by a plug.": "", |
| 26 | + "Switchboard": "", |
| 27 | + "OEMs can develop and ship custom plugs if special or unique hardware in the machine requires configuration in addition to what is available by default in elementary OS; for example, special sensors or input methods not present in most hardware. If relevant to a broader set of users, contributing it upstream to the <a href=\"https://github.com/elementary?q=switchboard-plug\" target=\"_blank\" rel=\"noopener\">existing plugs</a> is highly encouraged.": "", |
| 28 | + "Documentation": "", |
| 29 | + "OEM Info in About": "", |
| 30 | + "The <a href=\"https://github.com/elementary/switchboard-plug-about/\" target=\"_blank\" rel=\"noopener\">About</a> plug displays system information to the user and provides several system-wide actions, such as restoring settings, reporting issues, and getting help. In addition to software information (like the OS version), it also provides a space for hardware information. By default, this is filled in with a generic image and the system’s hostname. However, OEMs can provide custom branded data for this section.": "", |
| 31 | + "Switchboard About": "", |
| 32 | + "By providing an <code>oem.conf</code> file, OEMs can fill in the manufacturer name, product name, model number, and manufacturer URL. An image can also be provided which replaces the generic hardware icon.": "", |
| 33 | + "Learn More": "", |
| 34 | + "Third-Party Repositories": "", |
| 35 | + "It is highly discouraged to ship elementary OS with software repositories other than the defaults in elementary OS plus a single repository provided and controlled by the OEM. <strong>Third-party repos effectively give root access and the ability to overwrite any system packages to potentially untrusted third parties.</strong> Even if the party is trustworthy, an OEM’s customer’s security and privacy are now at stake if third parties are compromised, or they reuse their password on multiple services, etc.": "", |
| 36 | + "Further, if a third-party repository ever becomes unmaintained or unpublished, <strong>it may prevent regular OS updates.</strong> This could hold back potentially serious security and stability fixes from reaching the OEM’s customers.": "", |
| 37 | + "News & Announcements": "", |
| 38 | + "We publish frequent updates on development, major announcements, tips for developers, featured apps, and more on our blog.": "", |
| 39 | + "Visit our Blog": "", |
| 40 | + "Brand Resources": "", |
| 41 | + "View the elementary logos, brand usage guidelines, color palette, and community logo. Plus download the official high-resolution and vector elementary logo assets.": "", |
| 42 | + "View Brand Resources": "", |
| 43 | + "Get in Touch": "", |
| 44 | + "Talk directly with the team by sending an email to <a href=\"mailto:[email protected]\">[email protected]</a>. Whether you’re an existing partner or want to explore offering elementary OS, we look forward to chatting.": "", |
| 45 | + "Send an Email": "", |
| 46 | + "Information for OEMs ⋅ elementary": "" |
| 47 | +} |
0 commit comments