summaryrefslogtreecommitdiffstats
path: root/zarb-ml/mageia-marketing/attachments/20120317/2b67843b/attachment.html
blob: bb2bac17ca1798a070c0ad020d7002f51a11136b (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
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
    <title></title>
  </head>
  <body text="#000000" bgcolor="#ffffff">
    I think Max's email explains it very well. <br>
    <br>
    Just want to add the council representative is usually the leader or
    deputy leader depending on the meeting it seems for Mageia teams,
    however I think for Mageia teams that it would be good if both the
    leader and deputy leader could be this together at council meetings
    together for example.<br>
    <br>
    On 17/03/12 18:43, Max Quarterpleen wrote:
    <blockquote
cite="mid:CABN=Kyisy5BJH0o5FcuGknGHkYGcgYMwS7ha6LokLfa1kF8Fbg@mail.gmail.com"
      type="cite">
      <div dir="ltr">Think of it this way: both artwork and marcom are
        concerned with the appearance of Mageia. It's all about how we
        present ourselves to the world. Whether it's a shiny desktop,
        eye catching posters or good content on podcasts. It all boils
        down to the same thing: how we look to the outside world.<br>
        One of main problems we have with this is good communication.
        It's not just this one project where the two teams need to work
        together, but it's many projects. Thinking back for a few
        seconds I recall the booth setup for FOSDEM, the posters, the
        disc covers and a few other projects where both teams needed to
        work together.<br>
        Aside from the lack of cooperation <i>within</i> the team,
        there was bad communication <i>between</i> teams. Efforts have
        been made in the past to try and amplify the cooperation, by
        staggering IRC meetings, by having people sign up for both
        mailing lists... but they never worked well. Most recently when
        we tried to collaborate we had many double posts on both lists,
        many redundant threads and many people being left out of the
        loop. Why? Because we were trying to communicate across two
        different lists and more or less the same people.<br>
        Now, to clarify: the proposal isn't to merge the actual teams,
        just the communication channels. There will be (under the new
        proposal) one mailing list and one IRC channel. But essentially
        both teams will function as before. Each team will have one
        leader and one council representative (probably the same person
        for each team) and one deputy. This way both teams can function
        as a single unit when it comes to cross-communication and idea
        sharing (which happens a lot), but each team retains its
        autonomy.<br>
      </div>
      <pre wrap="">
<fieldset class="mimeAttachmentHeader"></fieldset>
_______________________________________________
Mageia-marketing mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Mageia-marketing@mageia.org">Mageia-marketing@mageia.org</a>
<a class="moz-txt-link-freetext" href="https://www.mageia.org/mailman/listinfo/mageia-marketing">https://www.mageia.org/mailman/listinfo/mageia-marketing</a>
</pre>
    </blockquote>
    <br>
  </body>
</html>