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
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<TITLE> [Mageia-dev] Art, Logo and Branding
</TITLE>
<LINK REL="Index" HREF="index.html" >
<LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Art%2C%20Logo%20and%20Branding&In-Reply-To=%3C201009250749.50773.yorick_%40openoffice.org%3E">
<META NAME="robots" CONTENT="index,nofollow">
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
<LINK REL="Previous" HREF="000193.html">
<LINK REL="Next" HREF="000198.html">
</HEAD>
<BODY BGCOLOR="#ffffff">
<H1>[Mageia-dev] Art, Logo and Branding</H1>
<B>Graham Lauder</B>
<A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Art%2C%20Logo%20and%20Branding&In-Reply-To=%3C201009250749.50773.yorick_%40openoffice.org%3E"
TITLE="[Mageia-dev] Art, Logo and Branding">yorick_ at openoffice.org
</A><BR>
<I>Fri Sep 24 21:49:50 CEST 2010</I>
<P><UL>
<LI>Previous message: <A HREF="000193.html">[Mageia-dev] Art, Logo and Branding
</A></li>
<LI>Next message: <A HREF="000198.html">[Mageia-dev] Art, Logo and Branding
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#208">[ date ]</a>
<a href="thread.html#208">[ thread ]</a>
<a href="subject.html#208">[ subject ]</a>
<a href="author.html#208">[ author ]</a>
</LI>
</UL>
<HR>
<!--beginarticle-->
<PRE>On Friday 24 Sep 2010 12:38:41 Michael Scherer wrote:
><i> Le vendredi 24 septembre 2010 à 12:04 +1200, Graham Lauder a écrit :
</I>><i> > Who do I talk to about setting up a Marketing Mail list
</I>><i>
</I>><i> We postponed the mls creation until we have a clear delimitation and
</I>><i> understanding about the various sub groups who will need one, and until
</I>><i> we can find what we can offer to those subgroups to collaborate ( ie,
</I>><i> wiki, elgg, or any kind of tools, depending on the need, what is
</I>><i> available and so on ).
</I>><i>
</I>><i> Marketing and communication somehow overlap if we look at the
</I>><i> description on <A HREF="http://mageia.org/wiki/doku.php?id=marketing">http://mageia.org/wiki/doku.php?id=marketing</A> and
</I>><i> <A HREF="http://mageia.org/wiki/doku.php?id=communication,">http://mageia.org/wiki/doku.php?id=communication,</A>
</I>><i> communication and webteam may overlap ( as the web site is
</I>><i> communication ), so could webteam and design, or design and
</I>><i> communication.
</I>><i> And webteam and sysadmin may also overlap too or at least, will require
</I>><i> to discuss.
</I>
My first reaction was "NOOOO, I want my exclusive MARKETING LIST!!"
(note caps and 2, yes two, exclamation marks. So restrained ;) )
But then my consideration is that you are right. We (people) tend to package
things in terms of job descriptions. This is a hangover from our offline work
environment.
Marketing, website, education, documentation, graphic design: all are
communication, so lets put them under a single mail list. The more I think
about it the more i like the synergies that would come out of that.
><i>
</I>><i> So we thought that too much mls in the first place would be ineffective,
</I>><i> as this would get too messy too soon.
</I>
The only problem I have is that important stuff can get buried in noise. For
instance if a group of us were working on a mission statement, the thread
would not be busy and would disappear off the bottom in really short order.
The ideal solution of course would be a Email Subject/title convention, but
noone ever sticks to those in an open source project, it's hard enough to get
them to stop top posting! :D However a single Comms list would mitigate that
to a degree
><i>
</I>><i> I can understand the need to have a list as it somehow act the creation
</I>><i> of the team, but I think we can do better than a ml to do that, except
</I>><i> that we do not have the definite infrastructure for this ( but we are
</I>><i> working hard on it ).
</I>><i>
</I>><i> > I'll set up a pirate pad in any case.
</I>><i>
</I>><i> I have been pondering on installing gobby on the server, because it is
</I>><i> packaged, and wait on <A HREF="https://fedoraproject.org/wiki/Etherpad_FAD">https://fedoraproject.org/wiki/Etherpad_FAD</A> to
</I>><i> adapt the package for our current host ( running Mandriva ), since
</I>><i> etherpad is rumored to be quite complex to setup properly.
</I>
OK, they're horrible bloody things in many ways from a usage pov,
><i>
</I>><i> In the mean time, yes, a piratepad would be a solution.
</I>
I would prefer collaboration on google docs but pirate pads realtime update
is a killer feature at this point and so I'll put up with the other
irritations.
I will have breakfast and get into it
--
Graham Lauder,
OpenOffice.org MarCon (Marketing Contact) NZ
<A HREF="http://marketing.openoffice.org/contacts.html">http://marketing.openoffice.org/contacts.html</A>
OpenOffice.org Migration and training Consultant.
INGOTs Assessor Trainer
(International Grades in Open Technologies)
www.theingots.org
</PRE>
<!--endarticle-->
<HR>
<P><UL>
<!--threads-->
<LI>Previous message: <A HREF="000193.html">[Mageia-dev] Art, Logo and Branding
</A></li>
<LI>Next message: <A HREF="000198.html">[Mageia-dev] Art, Logo and Branding
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#208">[ date ]</a>
<a href="thread.html#208">[ thread ]</a>
<a href="subject.html#208">[ subject ]</a>
<a href="author.html#208">[ author ]</a>
</LI>
</UL>
<hr>
<a href="https://www.mageia.org/mailman/listinfo/mageia-dev">More information about the Mageia-dev
mailing list</a><br>
</body></html>
|
