1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<TITLE> [Mageia-marketing] Plan - stuff to do pre Beta 1 release
</TITLE>
<LINK REL="Index" HREF="index.html" >
<LINK REL="made" HREF="mailto:mageia-marketing%40mageia.org?Subject=Re%3A%20%5BMageia-marketing%5D%20Plan%20-%20stuff%20to%20do%20pre%20Beta%201%20release&In-Reply-To=%3CBANLkTimGkjFpGzyg7wjCvHn6B5UDswALWQ%40mail.gmail.com%3E">
<META NAME="robots" CONTENT="index,nofollow">
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
<LINK REL="Previous" HREF="000228.html">
<LINK REL="Next" HREF="000230.html">
</HEAD>
<BODY BGCOLOR="#ffffff">
<H1>[Mageia-marketing] Plan - stuff to do pre Beta 1 release</H1>
<B>Romain d'Alverny</B>
<A HREF="mailto:mageia-marketing%40mageia.org?Subject=Re%3A%20%5BMageia-marketing%5D%20Plan%20-%20stuff%20to%20do%20pre%20Beta%201%20release&In-Reply-To=%3CBANLkTimGkjFpGzyg7wjCvHn6B5UDswALWQ%40mail.gmail.com%3E"
TITLE="[Mageia-marketing] Plan - stuff to do pre Beta 1 release">rdalverny at gmail.com
</A><BR>
<I>Tue Apr 5 23:26:40 CEST 2011</I>
<P><UL>
<LI>Previous message: <A HREF="000228.html">[Mageia-marketing] Plan - stuff to do pre Beta 1 release
</A></li>
<LI>Next message: <A HREF="000230.html">[Mageia-marketing] Plan - stuff to do pre Beta 1 release
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#229">[ date ]</a>
<a href="thread.html#229">[ thread ]</a>
<a href="subject.html#229">[ subject ]</a>
<a href="author.html#229">[ author ]</a>
</LI>
</UL>
<HR>
<!--beginarticle-->
<PRE>Hi there,
On Tue, Apr 5, 2011 at 22:38, Patricia Fraser <<A HREF="https://www.mageia.org/mailman/listinfo/mageia-marketing">trish at thefrasers.org</A>> wrote:
><i> You could check out the last time Yorick and the discuss list had a
</I>><i> conversation, to get a really unmistakable feel for this - I should
</I>><i> probably not need to point out that the shrinkage to not-quite-zero
</I>><i> of the marketing team can be traced back to that conversation. A
</I>><i> pity, because we were full of energy and working hard and well.
</I>
Yeah but the direction it was taking at the time was not in sync with
the project state - that is, going too far, too soon. Talking to
non-users as of today (especially those not aware of Mageia or even
Linux) is important, and growing our user-base - although this needs
to scale with regard to the amount of contributors we do need today.
>><i> What is the difference between an announcement to the community and
</I>>><i> one going to the outside world? An Announcement has to say
</I>>><i>  - who announces
</I>>><i>  - what is tha subject of the announcement
</I>><i>
</I>><i> It's all in who you're talking to. If you're talking to a community
</I>><i> of which you're part, you're talking to people who are already on the
</I>><i> inside - there's an existing relationship of a kind, and they know
</I>><i> the context and what's going on and who's who. If you're talking to
</I>><i> people who aren't part of the community yet, you're extending an
</I>><i> invitation. You want to present them with a picture of the community
</I>><i> you're inviting them into (which the community doesn't need),
</I>
I'd say yes, it needs it. Because a community (especially an online
one) has a hard time figuring who/what it is I believe - and that's
where the inviting/human/friendly theme is common to both insiders and
outsiders of the project.
Representing the community to itself properly (far beyond the online
text-only interface we daily use) is a must to aim at. Through
stories, ad-hoc project online/offline activity visibility, and
probably other things.
><i> What I was wondering about, though, was: suppose we're successful in
</I>><i> getting a TV spot? What then?
</I>
We'd do something. Not necessarily the best thing for the very but
something that promotes the core of the project: free software,
collaboration, commons - that's something that everyone can share,
geek or non-geek. Something focused more on the core values driving
the project than on a project specific.
I'm sure we can do it.
Cheers,
Romain
</PRE>
<!--endarticle-->
<HR>
<P><UL>
<!--threads-->
<LI>Previous message: <A HREF="000228.html">[Mageia-marketing] Plan - stuff to do pre Beta 1 release
</A></li>
<LI>Next message: <A HREF="000230.html">[Mageia-marketing] Plan - stuff to do pre Beta 1 release
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#229">[ date ]</a>
<a href="thread.html#229">[ thread ]</a>
<a href="subject.html#229">[ subject ]</a>
<a href="author.html#229">[ author ]</a>
</LI>
</UL>
<hr>
<a href="https://www.mageia.org/mailman/listinfo/mageia-marketing">More information about the Mageia-marketing
mailing list</a><br>
</body></html>
|