diff options
| author | Nicolas Vigier <boklm@mageia.org> | 2013-04-14 13:46:12 +0000 |
|---|---|---|
| committer | Nicolas Vigier <boklm@mageia.org> | 2013-04-14 13:46:12 +0000 |
| commit | 1be510f9529cb082f802408b472a77d074b394c0 (patch) | |
| tree | b175f9d5fcb107576dabc768e7bd04d4a3e491a0 /zarb-ml/mageia-marketing/attachments/20120317 | |
| parent | fa5098cf210b23ab4f419913e28af7b1b07dafb2 (diff) | |
| download | archives-1be510f9529cb082f802408b472a77d074b394c0.tar archives-1be510f9529cb082f802408b472a77d074b394c0.tar.gz archives-1be510f9529cb082f802408b472a77d074b394c0.tar.bz2 archives-1be510f9529cb082f802408b472a77d074b394c0.tar.xz archives-1be510f9529cb082f802408b472a77d074b394c0.zip | |
Diffstat (limited to 'zarb-ml/mageia-marketing/attachments/20120317')
6 files changed, 256 insertions, 0 deletions
diff --git a/zarb-ml/mageia-marketing/attachments/20120317/0b7829f8/attachment-0001.html b/zarb-ml/mageia-marketing/attachments/20120317/0b7829f8/attachment-0001.html new file mode 100644 index 000000000..48693a37f --- /dev/null +++ b/zarb-ml/mageia-marketing/attachments/20120317/0b7829f8/attachment-0001.html @@ -0,0 +1,60 @@ +<!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"> + On 17/03/12, Bradley D. Thornton typed:<br> + <blockquote cite="mid:4F649C63.1030506@NorthTech.US" type="cite"> + <pre wrap="">Anyway, my post won't make any difference +</pre> + </blockquote> + <br> + <style type="text/css">p { margin-bottom: 0.21cm;</style>I think it + already has :). I think that + was a very good message. I do however think that it is a good idea + to + completely merge with the artwork team and how I had suggested in my + email to this mailing list and the artwork. Why? Simple, because + then + as a whole there will be more control, over a team that has been + having problems. <br> + <p style="margin-bottom: 0cm;">The big MArtCom team can be split up + into + sub teams of people who are only or mainly working on specific + tasks, + but members in our team can provide feedback and support for tasks + that are being worked on by other people in the team as well. + For example graphics designers could be working on the installer + slide show images, but also provide feedback about the installer + slide show text from marketing people. Or marketing team people + could be working on reviews, but also provide feedback of the + looks + of the graphics.<br> + <br> + Trish has been working with the artwork team + quite a lot in the last few months or more. I noticed this and + that was why I made sure to join the artwork team mailing list, + and + so the team as well as a result, soon after joining marketing, + even + though not really a graphics designer.<br> + <br> + Something else it seems + the marketing and artwork team IRC meetings have been linked + together + as to when they are for which team. For example one week is + marketing + and the next is artwork and at that time, or that's meant to be + the + idea in general.<br> + <br> + P.S<br> + <br> + Bradley glad you seem to be + feeling better :).<br> + </p> + </body> +</html> diff --git a/zarb-ml/mageia-marketing/attachments/20120317/0b7829f8/attachment.html b/zarb-ml/mageia-marketing/attachments/20120317/0b7829f8/attachment.html new file mode 100644 index 000000000..48693a37f --- /dev/null +++ b/zarb-ml/mageia-marketing/attachments/20120317/0b7829f8/attachment.html @@ -0,0 +1,60 @@ +<!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"> + On 17/03/12, Bradley D. Thornton typed:<br> + <blockquote cite="mid:4F649C63.1030506@NorthTech.US" type="cite"> + <pre wrap="">Anyway, my post won't make any difference +</pre> + </blockquote> + <br> + <style type="text/css">p { margin-bottom: 0.21cm;</style>I think it + already has :). I think that + was a very good message. I do however think that it is a good idea + to + completely merge with the artwork team and how I had suggested in my + email to this mailing list and the artwork. Why? Simple, because + then + as a whole there will be more control, over a team that has been + having problems. <br> + <p style="margin-bottom: 0cm;">The big MArtCom team can be split up + into + sub teams of people who are only or mainly working on specific + tasks, + but members in our team can provide feedback and support for tasks + that are being worked on by other people in the team as well. + For example graphics designers could be working on the installer + slide show images, but also provide feedback about the installer + slide show text from marketing people. Or marketing team people + could be working on reviews, but also provide feedback of the + looks + of the graphics.<br> + <br> + Trish has been working with the artwork team + quite a lot in the last few months or more. I noticed this and + that was why I made sure to join the artwork team mailing list, + and + so the team as well as a result, soon after joining marketing, + even + though not really a graphics designer.<br> + <br> + Something else it seems + the marketing and artwork team IRC meetings have been linked + together + as to when they are for which team. For example one week is + marketing + and the next is artwork and at that time, or that's meant to be + the + idea in general.<br> + <br> + P.S<br> + <br> + Bradley glad you seem to be + feeling better :).<br> + </p> + </body> +</html> diff --git a/zarb-ml/mageia-marketing/attachments/20120317/2b67843b/attachment-0001.html b/zarb-ml/mageia-marketing/attachments/20120317/2b67843b/attachment-0001.html new file mode 100644 index 000000000..bb2bac17c --- /dev/null +++ b/zarb-ml/mageia-marketing/attachments/20120317/2b67843b/attachment-0001.html @@ -0,0 +1,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> diff --git a/zarb-ml/mageia-marketing/attachments/20120317/2b67843b/attachment.html b/zarb-ml/mageia-marketing/attachments/20120317/2b67843b/attachment.html new file mode 100644 index 000000000..bb2bac17c --- /dev/null +++ b/zarb-ml/mageia-marketing/attachments/20120317/2b67843b/attachment.html @@ -0,0 +1,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> diff --git a/zarb-ml/mageia-marketing/attachments/20120317/a47ecfd9/attachment-0001.html b/zarb-ml/mageia-marketing/attachments/20120317/a47ecfd9/attachment-0001.html new file mode 100644 index 000000000..ad454a94c --- /dev/null +++ b/zarb-ml/mageia-marketing/attachments/20120317/a47ecfd9/attachment-0001.html @@ -0,0 +1,7 @@ +<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> diff --git a/zarb-ml/mageia-marketing/attachments/20120317/a47ecfd9/attachment.html b/zarb-ml/mageia-marketing/attachments/20120317/a47ecfd9/attachment.html new file mode 100644 index 000000000..ad454a94c --- /dev/null +++ b/zarb-ml/mageia-marketing/attachments/20120317/a47ecfd9/attachment.html @@ -0,0 +1,7 @@ +<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> |