summaryrefslogtreecommitdiffstats
path: root/zarb-ml/mageia-marketing/2012-June/000951.html
blob: 5d237c730a2563e7a9936650d5cab6e864b5aae6 (plain)
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
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
 <HEAD>
   <TITLE> [Mageia-marketing] marcom + artwork + web =&gt; atelier ?
   </TITLE>
   <LINK REL="Index" HREF="index.html" >
   <LINK REL="made" HREF="mailto:mageia-marketing%40mageia.org?Subject=Re%3A%20%5BMageia-marketing%5D%20marcom%20%2B%20artwork%20%2B%20web%20%3D%3E%20atelier%20%3F&In-Reply-To=%3C4FDF2337.5030207%40alice.it%3E">
   <META NAME="robots" CONTENT="index,nofollow">
   <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
   <LINK REL="Previous"  HREF="000945.html">
   <LINK REL="Next"  HREF="000952.html">
 </HEAD>
 <BODY BGCOLOR="#ffffff">
   <H1>[Mageia-marketing] marcom + artwork + web =&gt; atelier ?</H1>
    <B>Marcello</B> 
    <A HREF="mailto:mageia-marketing%40mageia.org?Subject=Re%3A%20%5BMageia-marketing%5D%20marcom%20%2B%20artwork%20%2B%20web%20%3D%3E%20atelier%20%3F&In-Reply-To=%3C4FDF2337.5030207%40alice.it%3E"
       TITLE="[Mageia-marketing] marcom + artwork + web =&gt; atelier ?">marcello.anni at alice.it
       </A><BR>
    <I>Mon Jun 18 14:46:47 CEST 2012</I>
    <P><UL>
        <LI>Previous message: <A HREF="000945.html">[Mageia-marketing] Lets build some excitement!
</A></li>
        <LI>Next message: <A HREF="000952.html">[Mageia-marketing] marcom + artwork + web =&gt; atelier ?
</A></li>
         <LI> <B>Messages sorted by:</B> 
              <a href="date.html#951">[ date ]</a>
              <a href="thread.html#951">[ thread ]</a>
              <a href="subject.html#951">[ subject ]</a>
              <a href="author.html#951">[ author ]</a>
         </LI>
       </UL>
    <HR>  
<!--beginarticle-->
<PRE>Il 09/06/2012 18:27, Romain d'Alverny ha scritto:
&gt;<i> Hi everyone, (xposted on -marketing, -artwork and -webteam; if
</I>&gt;<i> possible, please follow-up in -marketing)
</I>&gt;<i>
</I>&gt;<i> So here's the plan (actually, that's a suggestion of a plan):
</I>&gt;<i>   - we make a new team; which role is to think, design, produce and
</I>&gt;<i> maintain the identity of the project and its declinations in messages,
</I>&gt;<i> graphics, Web and print [1];
</I>&gt;<i>   - this team is named &quot;atelier&quot;;
</I>&gt;<i>   - a new mailing-list is open for that;
</I>&gt;<i>   - it practically merges responsibilities from artwork, web and marcom teams;
</I>&gt;<i>   - it integrates roles as diverse as: design, marketing, graphic
</I>&gt;<i> research and production, copy writing, web design, integration and
</I>&gt;<i> development, curation, etc.
</I>&gt;<i>   - existing web, marcom and artwork lists are kept for archive, but
</I>&gt;<i> locked down and all subscribers are unsubscribed;
</I>&gt;<i>   - will have a say in whatever happens in this team, only those making
</I>&gt;<i> and contributing things (so here, actionable designs, working code,
</I>&gt;<i> graphics or copy, etc.); opinions and feedback from others still
</I>&gt;<i> welcome, but not enough to move forward;
</I>&gt;<i>   - external contributions are a true option; that is, one team peer
</I>&gt;<i> getting in touch/inviting a professional person to propose and work on
</I>&gt;<i> a specific, focused topic, from overall project identity design, down
</I>&gt;<i> to a specific production. It only needs to be stated within the team
</I>&gt;<i> first so that everyone is in sync;
</I>&gt;<i>   - formatting our resources so that one-shot contributions from
</I>&gt;<i> external people are made easier is a true option too (that means
</I>&gt;<i> things easier to grasp, understand and update);
</I>&gt;<i>   - no more meeting, we plan and do things, and update everyone through
</I>&gt;<i> the mailing-list (or other, but asynchronous); so being on IRC is not
</I>&gt;<i> a must, just good to have;
</I>&gt;<i>   - no more than 10 hours a week on Mageia.
</I>&gt;<i>
</I>&gt;<i> Questions:
</I>&gt;<i>   - who's going to lead this?
</I>&gt;<i>   - what's the plan up to Mageia 3? several things at least in several
</I>&gt;<i> regards (identity, print, web, distribution), but that will highly
</I>&gt;<i> depend on who lead(s) the team.
</I>&gt;<i>
</I>&gt;<i> [1] ideally, everything that's the public face of Mageia.Org, the
</I>&gt;<i> Mageia distribution and the Mageia project should go through this
</I>&gt;<i> team; that does not mean that things will not be flexible, but if
</I>&gt;<i> there's one place to discuss, document and synchronize all this work,
</I>&gt;<i> it's here. That, in turn, requires some responsiveness and initiative
</I>&gt;<i> from the team members.
</I>&gt;<i> _______________________________________________
</I>&gt;<i> Mageia-marketing mailing list
</I>&gt;<i> <A HREF="https://www.mageia.org/mailman/listinfo/mageia-marketing">Mageia-marketing at mageia.org</A>
</I>&gt;<i> <A HREF="https://www.mageia.org/mailman/listinfo/mageia-marketing">https://www.mageia.org/mailman/listinfo/mageia-marketing</A>
</I>

ok for this, but for marketing team what is needed is not a new ml, but 
real marketing objectives and people dedicated to them. what should do a 
marketing team is not (at least, only) writing blog post announces and 
things like that, but planning:

- marketing-plan
- balanced scorecard

in plus, we need people from dev and artwork that follow our suggestions 
and our plans (naturally, the plans should be agreed also by them). i 
can help in these areas of long-term view, i cannot follow tasks that 
should be done in a day. the paucity of linux is proper in the missing 
of a long-term view, where all the aspects of the project are taken in 
considerations and priorities are set and done.

Bugzilla 4 is a perfect example of what should do a marketing team 
(atelier, if you prefer) for real. Bugzilla would help qa team work, 
would improve the overall quality of the distro and would allow to 
manage bugs that affect different versions, but instead of porting it, 
we're at mageia 3 specs... useless


cheers,
Marcello
</PRE>


<!--endarticle-->
    <HR>
    <P><UL>
        <!--threads-->
	<LI>Previous message: <A HREF="000945.html">[Mageia-marketing] Lets build some excitement!
</A></li>
	<LI>Next message: <A HREF="000952.html">[Mageia-marketing] marcom + artwork + web =&gt; atelier ?
</A></li>
         <LI> <B>Messages sorted by:</B> 
              <a href="date.html#951">[ date ]</a>
              <a href="thread.html#951">[ thread ]</a>
              <a href="subject.html#951">[ subject ]</a>
              <a href="author.html#951">[ 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>