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
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<TITLE> [Mageia-artwork] [Mageia-marketing] Proposal to merge with artwork
</TITLE>
<LINK REL="Index" HREF="index.html" >
<LINK REL="made" HREF="mailto:mageia-artwork%40mageia.org?Subject=Re%3A%20%5BMageia-artwork%5D%20%5BMageia-marketing%5D%20Proposal%20to%20merge%20with%0A%09artwork&In-Reply-To=%3C4F62780A.6090007%40gmx.com%3E">
<META NAME="robots" CONTENT="index,nofollow">
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
<LINK REL="Previous" HREF="001103.html">
<LINK REL="Next" HREF="001106.html">
</HEAD>
<BODY BGCOLOR="#ffffff">
<H1>[Mageia-artwork] [Mageia-marketing] Proposal to merge with artwork</H1>
<B>Sebastian sebsebseb</B>
<A HREF="mailto:mageia-artwork%40mageia.org?Subject=Re%3A%20%5BMageia-artwork%5D%20%5BMageia-marketing%5D%20Proposal%20to%20merge%20with%0A%09artwork&In-Reply-To=%3C4F62780A.6090007%40gmx.com%3E"
TITLE="[Mageia-artwork] [Mageia-marketing] Proposal to merge with artwork">sebsebseb_mageia at gmx.com
</A><BR>
<I>Fri Mar 16 00:15:22 CET 2012</I>
<P><UL>
<LI>Previous message: <A HREF="001103.html">[Mageia-artwork] [Bug 261] UPS icon hardcodes english word "UPS"
</A></li>
<LI>Next message: <A HREF="001106.html">[Mageia-artwork] [Mageia-marketing] Proposal to merge with artwork
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#1105">[ date ]</a>
<a href="thread.html#1105">[ thread ]</a>
<a href="subject.html#1105">[ subject ]</a>
<a href="author.html#1105">[ author ]</a>
</LI>
</UL>
<HR>
<!--beginarticle-->
<PRE>
><i> I wouldn't merge the teams per se (with their leads), but I would make
</I>><i> a default common channel of communication, both IRC and mailing-list.
</I>><i> So that communication/sync within teams is easier. But it's important
</I>><i> that both teams keep a separate seat at the Council.
</I>>><i> I think it makes sense to merge them. Maybe MArtCom team? ;-)
</I>><i> Oliver suggested martkomm :)
</I>As Trish already knows I think merging the marketing and communications,
and artwork team together is a good idea.
I seem to pretty much agree with rda or nearly and I like Josh's name
suggestion more so than Oliver's.
I think MArtCom should be created, a IRC channel and mailing list. For
the IRC channel I am willing to register it and set it up as in giving
leaders and deputy leaders ops for example.
We could also drop two Mageia IRC channels that's marcom and artwork and
replace them with martcom. It also seems that marcom and artwork aren't
even registered on the Freenode network, or they are, but not set up in
the normal way.
As for the mailing list currently marketing and artwork have the mailing
lists on mailman: <A HREF="https://www.mageia.org/mailman/listinfo/">https://www.mageia.org/mailman/listinfo/</A> For some
reason the newer mailing lists get listed at
<A HREF="https://ml.mageia.org/l/home">https://ml.mageia.org/l/home</A> instead. It also seems going by a docs team
meeting that I was in, that the older mailing lists are likely to
eventually move over to the newer set up. With the newer set up unlike
the old, a Mageia Identify account is also required to be on the mailing
lists.
We could still keep the separate team IRC channels and mailing lists,
but I think it makes much more sense to do a proper merge and stop using
them.
As for old emails to the mailing lists, they can either stay where they
are in the archives for the old mailing lists and people stop sending to
that list, or sending to is disabled. The messages could also be
archived some where else publicly.
As for the meeting IRC logs they can stay in there sections at
<A HREF="http://meetbot.mageia.org">http://meetbot.mageia.org</A> for the old channels, and I expect they can
also be pointed to from a new martcom IRC channel section.
As for the team leader and deputy team leader positions, I agree with
rda or pretty much it seems. I think Trish should instantly become the
leader of the new MArtCom, and I become the deputy leader, since I won
the vote for becoming that recently for marketing. However Trish and
myself would be mainly the marketing side of the MArtCom team, and
leader-wise we need the artwork as well, and so Max for example could
become the other deputy leader or leader. Like rda suggested and I 100%
agree with him, the team should have two seats at the council. Well
actually maybe it should have more than that depending on how things go
in the future.
I would probably want Max to be the deputy leader or leader of a new
MArtCom team on the artwork side. TeaAge it seems has been away for a
long time, and I think the artwork team should have a vote like other
teams have been doing on who should be leader and deputy leader. Or
members of a new MArtCom team can vote (if we start that team) for who
should be the leader and deputy leader on the artwork side.
From Sebastian sebsebseb
</PRE>
<!--endarticle-->
<HR>
<P><UL>
<!--threads-->
<LI>Previous message: <A HREF="001103.html">[Mageia-artwork] [Bug 261] UPS icon hardcodes english word "UPS"
</A></li>
<LI>Next message: <A HREF="001106.html">[Mageia-artwork] [Mageia-marketing] Proposal to merge with artwork
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#1105">[ date ]</a>
<a href="thread.html#1105">[ thread ]</a>
<a href="subject.html#1105">[ subject ]</a>
<a href="author.html#1105">[ author ]</a>
</LI>
</UL>
<hr>
<a href="https://www.mageia.org/mailman/listinfo/mageia-artwork">More information about the Mageia-artwork
mailing list</a><br>
</body></html>
|
