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/2012-March/000660.html | |
| 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/2012-March/000660.html')
| -rw-r--r-- | zarb-ml/mageia-marketing/2012-March/000660.html | 103 |
1 files changed, 103 insertions, 0 deletions
diff --git a/zarb-ml/mageia-marketing/2012-March/000660.html b/zarb-ml/mageia-marketing/2012-March/000660.html new file mode 100644 index 000000000..ea4d2b146 --- /dev/null +++ b/zarb-ml/mageia-marketing/2012-March/000660.html @@ -0,0 +1,103 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Mageia-marketing] Proposal to merge with artwork + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:mageia-marketing%40mageia.org?Subject=Re%3A%20%5BMageia-marketing%5D%20Proposal%20to%20merge%20with%20artwork&In-Reply-To=%3C4F64E46E.8080004%40gmx.com%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="000658.html"> + <LINK REL="Next" HREF="000654.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-marketing] Proposal to merge with artwork</H1> + <B>Sebastian sebsebseb</B> + <A HREF="mailto:mageia-marketing%40mageia.org?Subject=Re%3A%20%5BMageia-marketing%5D%20Proposal%20to%20merge%20with%20artwork&In-Reply-To=%3C4F64E46E.8080004%40gmx.com%3E" + TITLE="[Mageia-marketing] Proposal to merge with artwork">sebsebseb_mageia at gmx.com + </A><BR> + <I>Sat Mar 17 20:22:22 CET 2012</I> + <P><UL> + <LI>Previous message: <A HREF="000658.html">[Mageia-marketing] Proposal to merge with artwork +</A></li> + <LI>Next message: <A HREF="000654.html">[Mageia-marketing] Proposal to merge with artwork +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#660">[ date ]</a> + <a href="thread.html#660">[ thread ]</a> + <a href="subject.html#660">[ subject ]</a> + <a href="author.html#660">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>I think Max's email explains it very well. + +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. + +On 17/03/12 18:43, Max Quarterpleen wrote: +><i> Think of it this way: both artwork and marcom are concerned with the +</I>><i> appearance of Mageia. It's all about how we present ourselves to the +</I>><i> world. Whether it's a shiny desktop, eye catching posters or good +</I>><i> content on podcasts. It all boils down to the same thing: how we look +</I>><i> to the outside world. +</I>><i> One of main problems we have with this is good communication. It's not +</I>><i> just this one project where the two teams need to work together, but +</I>><i> it's many projects. Thinking back for a few seconds I recall the booth +</I>><i> setup for FOSDEM, the posters, the disc covers and a few other +</I>><i> projects where both teams needed to work together. +</I>><i> Aside from the lack of cooperation /within/ the team, there was bad +</I>><i> communication /between/ teams. Efforts have been made in the past to +</I>><i> try and amplify the cooperation, by staggering IRC meetings, by having +</I>><i> people sign up for both mailing lists... but they never worked well. +</I>><i> Most recently when we tried to collaborate we had many double posts on +</I>><i> both lists, many redundant threads and many people being left out of +</I>><i> the loop. Why? Because we were trying to communicate across two +</I>><i> different lists and more or less the same people. +</I>><i> Now, to clarify: the proposal isn't to merge the actual teams, just +</I>><i> the communication channels. There will be (under the new proposal) one +</I>><i> mailing list and one IRC channel. But essentially both teams will +</I>><i> function as before. Each team will have one leader and one council +</I>><i> representative (probably the same person for each team) and one +</I>><i> deputy. This way both teams can function as a single unit when it +</I>><i> comes to cross-communication and idea sharing (which happens a lot), +</I>><i> but each team retains its autonomy. +</I>><i> +</I>><i> +</I>><i> _______________________________________________ +</I>><i> Mageia-marketing mailing list +</I>><i> <A HREF="https://www.mageia.org/mailman/listinfo/mageia-marketing">Mageia-marketing at mageia.org</A> +</I>><i> <A HREF="https://www.mageia.org/mailman/listinfo/mageia-marketing">https://www.mageia.org/mailman/listinfo/mageia-marketing</A> +</I> +-------------- next part -------------- +An HTML attachment was scrubbed... +URL: </pipermail/mageia-marketing/attachments/20120317/2b67843b/attachment-0001.html> +</PRE> + + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="000658.html">[Mageia-marketing] Proposal to merge with artwork +</A></li> + <LI>Next message: <A HREF="000654.html">[Mageia-marketing] Proposal to merge with artwork +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#660">[ date ]</a> + <a href="thread.html#660">[ thread ]</a> + <a href="subject.html#660">[ subject ]</a> + <a href="author.html#660">[ 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> |