From 1be510f9529cb082f802408b472a77d074b394c0 Mon Sep 17 00:00:00 2001 From: Nicolas Vigier Date: Sun, 14 Apr 2013 13:46:12 +0000 Subject: Add zarb MLs html archives --- zarb-ml/mageia-marketing/2011-June/000441.html | 80 ++++++++++++++++++++++++++ 1 file changed, 80 insertions(+) create mode 100644 zarb-ml/mageia-marketing/2011-June/000441.html (limited to 'zarb-ml/mageia-marketing/2011-June/000441.html') diff --git a/zarb-ml/mageia-marketing/2011-June/000441.html b/zarb-ml/mageia-marketing/2011-June/000441.html new file mode 100644 index 000000000..daf7c7f0c --- /dev/null +++ b/zarb-ml/mageia-marketing/2011-June/000441.html @@ -0,0 +1,80 @@ + + + + [Mageia-marketing] Advertise Mageia in upstream websites + + + + + + + + + +

[Mageia-marketing] Advertise Mageia in upstream websites

+ Romain d'Alverny + rda at mageia.org +
+ Tue Jun 28 11:25:23 CEST 2011 +

+
+ +
Hi,
+
+On Tue, Jun 28, 2011 at 09:58, Samuel Verschelde <stormi at laposte.net> wrote:
+> There are upstream websites that explain how to install their software in
+> various distributions. A simple way to help Mageia to be known would be to
+> contact those upstream projects one by one
+>
+> Things will be better once we have Mageia App Db because then we will be able
+> to point them at a permanent URL for their software, but maybe we could start
+> already ?
+> What do you think ?
+
+Yes! For one given project, we need to:
+ 1. have the software packaged,
+ 2. contact the project website to notify them and have them tell about it:
+     - citing the distribution (Mageia) and using the logo,
+     - giving the process to install the softwarer (ideally, just
+urpmi <software> or package manager => install => <software>) ?
+ 3. a documented process in the wiki or elsewhere
+ 4. people to do it
+
+Or should something else/different be done?
+
+Romain
+
+ + + +
+

+ +
+More information about the Mageia-marketing +mailing list
+ -- cgit v1.2.1