summaryrefslogtreecommitdiffstats
path: root/zarb-ml/mageia-marketing/attachments/20120617/f8b3394f/attachment-0001.html
diff options
context:
space:
mode:
Diffstat (limited to 'zarb-ml/mageia-marketing/attachments/20120617/f8b3394f/attachment-0001.html')
-rw-r--r--zarb-ml/mageia-marketing/attachments/20120617/f8b3394f/attachment-0001.html16
1 files changed, 16 insertions, 0 deletions
diff --git a/zarb-ml/mageia-marketing/attachments/20120617/f8b3394f/attachment-0001.html b/zarb-ml/mageia-marketing/attachments/20120617/f8b3394f/attachment-0001.html
new file mode 100644
index 000000000..04379a378
--- /dev/null
+++ b/zarb-ml/mageia-marketing/attachments/20120617/f8b3394f/attachment-0001.html
@@ -0,0 +1,16 @@
+<div dir="ltr">So...<br>Did this initiative die, or what?<br><br><div class="gmail_quote">On Tue, Jun 12, 2012 at 1:39 AM, Max Quarterpleen <span dir="ltr">&lt;<a href="mailto:bogusman222@gmail.com" target="_blank">bogusman222@gmail.com</a>&gt;</span> wrote:<br>
+<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="im"><blockquote style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex" class="gmail_quote">
+We should probably leave this discussion for now and focus on founding<br></blockquote>
+</div><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
+the new group.<br><br></blockquote><div><br>I agree.<br>The way I see it we should have one group (never mind the name) with three virtual task forces.<br>The task forces will not be real, just a sort of legacy issue for people from the old teams to have some initial direction in the new team. Ideally, everybody will contribute where he or she can.<br>
+
+These three virtual task forces should, however, have a real coordinator. One person who is in charge of looking out for a specific field. Aside from that there should be a team leader, who should be one of the task force leaders.<br>
+
+This way we have a sort of hierarchical structure: Someone willing to work on web design or a marketing poster or whatnot turns to the appropriate task coordinator. He or she then discusses with the other two what needs to be done for this by which task force, then one of these three (it doesn&#39;t really matter who) propagates that information back down to everybody else.<br>
+
+It will work the same way in reverse. The three coordinators come up with the final list of things that need to be done for Mga3 (with considerable input and discussion from everybody, of course) and then coordinate the tasks.<br>
+
+I think that this allows for maximum communication and we don&#39;t end up with the left hand not knowing what the right hand is doing.<br>Furthermore, this allows for individual people to come up with their own ideas, plans, projects and whatnot and then act upon them as part of the group. Even if in the end they are working alone, the whole group is aware of what is going on.<br>
+
+</div></div></div>
+</blockquote></div><br></div>