Re: Presenting Debian to the user at cloud provider marketplaces
On Sat, Jul 6, 2019 at 4:18 AM Bastian Blank wrote:
> I'd would like some input on how to present Debian at some of the cloud
> providers, namely Microsoft Azure and Amazon Web Services.
This reminds me of a discussion we had recently about guidelines for
Debian presences on social networks:
https://lists.debian.org/msgid-search/e91d87dfb9033844f11c9137bbbc80cf873e4b50.camel@debian.org
> What can and what should we write on such pages?
Probably the same descriptions as what we use on the Debian website
(BTW the web team are working on revamping that), perhaps tweaked for
the cloud audience and for the particular cloud.
> What should we add as links to such pages, esp the Azure one?
I'd refer to them as "Debian for <cloud>".
For the Azure one I would suggest a few specific changes:
Replace "Debian Linux" with either "Debian" or "Debian GNU/Linux".
Remove "Debian GNU/Linux is one of the most popular Linux
distributions", I'm not sure we can claim that right now. It is also
something that changes over time so isn't appropriate for a
description. Probably replace the description entirely.
Replace the wiki link with a "general documentation" link to the
documentation page on the Debian website and the other one to "cloud
documentation" or "Azure documentation".
https://www.debian.org/doc/
Replace the privacy policy link with Debian's Privacy Policy page:
https://www.debian.org/legal/privacy
Remove the pricing information link or otherwise indicate more clearly
that Debian is gratis.
For the AWS one I would suggest a few specific changes:
Replace the description with the one that the website team are
planning to use for the new layout of the website.
Fix the support period description, "supported for the next 5 years"
is a bit simplistic considering the LTS period and the semi-variable
nature of Debian release cycles.
Debian is not a company, so that word shouldn't be in the description
on the Debian seller page.
--
bye,
pabs
https://wiki.debian.org/PaulWise
Reply to: