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/2011-April/000247.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/2011-April/000247.html')
| -rw-r--r-- | zarb-ml/mageia-marketing/2011-April/000247.html | 166 |
1 files changed, 166 insertions, 0 deletions
diff --git a/zarb-ml/mageia-marketing/2011-April/000247.html b/zarb-ml/mageia-marketing/2011-April/000247.html new file mode 100644 index 000000000..592e3a537 --- /dev/null +++ b/zarb-ml/mageia-marketing/2011-April/000247.html @@ -0,0 +1,166 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Mageia-marketing] Plan - stuff to do pre Beta 1 release + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:mageia-marketing%40mageia.org?Subject=Re%3A%20%5BMageia-marketing%5D%20Plan%20-%20stuff%20to%20do%20pre%20Beta%201%20release&In-Reply-To=%3CBANLkTikdue75bgSnnwTfC_gxemHzUha2XA%40mail.gmail.com%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="000243.html"> + <LINK REL="Next" HREF="000252.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-marketing] Plan - stuff to do pre Beta 1 release</H1> + <B>Romain d'Alverny</B> + <A HREF="mailto:mageia-marketing%40mageia.org?Subject=Re%3A%20%5BMageia-marketing%5D%20Plan%20-%20stuff%20to%20do%20pre%20Beta%201%20release&In-Reply-To=%3CBANLkTikdue75bgSnnwTfC_gxemHzUha2XA%40mail.gmail.com%3E" + TITLE="[Mageia-marketing] Plan - stuff to do pre Beta 1 release">rdalverny at gmail.com + </A><BR> + <I>Wed Apr 6 15:32:10 CEST 2011</I> + <P><UL> + <LI>Previous message: <A HREF="000243.html">[Mageia-marketing] Plan - stuff to do pre Beta 1 release +</A></li> + <LI>Next message: <A HREF="000252.html">[Mageia-marketing] Plan - stuff to do pre Beta 1 release +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#247">[ date ]</a> + <a href="thread.html#247">[ thread ]</a> + <a href="subject.html#247">[ subject ]</a> + <a href="author.html#247">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>On Wed, Apr 6, 2011 at 14:26, Bradley D. Thornton <<A HREF="https://www.mageia.org/mailman/listinfo/mageia-marketing">Bradley at northtech.us</A>> wrote: +><i> I believe that we can whip out a convention for the creation of the +</I>><i> email aliases to delegate to the council since they've seemingly taken +</I>><i> over the sysadmin team's job too +</I> +That's a joke. Just ask sysadmin about that. :-D + +><i> and we'll see if they actually act on it, or pass it by like the forum/email +</I>><i> list integration listed below as a priority a few months ago. +</I> +Nonsense. This has never been said as a priority (or find me a quote +about that) but as a "nice-to-have, provided someone stands up to +properly integrate this in our setup". It did not happen. + +><i> We need a bit of reciprocity here. We can't be waiting on the horse for +</I>><i> the cart and be expected to deliver the grain before the horse arrives +</I>><i> to pull us along. +</I>><i> +</I>><i> There's a lot of infrastructure we requested and decided upon having +</I>><i> here, and yet await. +</I> +References? + +><i> Yes that was discussed at length, Wolfgang brought up the significance +</I>><i> of syncing the forums and the email lists so that two disparate groups +</I>><i> didn't begin to emerge independant of each other due to the lack of +</I>><i> preference for one medium over the other. +</I>><i> +</I>><i> A simple technical detail that I'm wholly in favor of, although I myself +</I>><i> prefer to use email lists themselves :) +</I> +There has never been a designed plan to actually make such a sync +between the official forums and the mailing-lists. The ml/forum bridge +has been provided by a third party advocating for it (good) but that +has not answered on details for joining the sysadmin team to help +spec'ing and setting this up for good. + +So better leave this aside as long as no one takes this tasks. + +><i> That discussion is archived (Don't tell me if we don't archive this +</I>><i> Mailman list - that would be very bad and I would rather not know if +</I>><i> that were the case) on this list - the particular discussion being +</I>><i> spawned on 24 January 2011. +</I> +<A HREF="http://mageia.org/mailman/">http://mageia.org/mailman/</A> - help yourself. + +><i> We've waited for about six months now as a team, and suddenly the +</I>><i> 'council' is arbitrarily creating lists and contact points without input +</I>><i> or direction, or researching what has already been prepared and waiting +</I>><i> on their actual formation? +</I> +You must be kidding. There has been a regular, permanent marcomm' team +in the past six months with regular meetings and actions? + +I am not saying that there was not one. Patricia, you, a few others +were here from time to time. But in no way as much active as a few +other teams in the project (web, artwork or even more, packagers, +translators, sysadmins to name a few). + +I am not blaming anyone/anything here. But pretending that the marcom +team has been waiting the past six months is pure nonsense when most +that was expected from the team was setting up and organizing, and +opening wide ears and eyes to all the people and activity within the +project to start to bring how it can help and improve things. + +><i> I did run over and throw a few posts out just to help in filling the +</I>><i> forums with some kruft and content so it can get going. +</I> +Just. Don't. Do. That. + +Better have a slowly taking forum with good content than cruft. Really. + +><i> frustrated that many of the things that appeared to be resolved on the +</I>><i> list here were seemingly disregarded when it came time to implement, and +</I>><i> simply arbitrarily taken on as a task by the 'council' and some +</I>><i> 'founders'  w/o input, approval, or direction from this team. +</I> +Wait. You seem to misunderstand how things are done so far and how we +can improve them. + +That was not "arbitrarily" taken by the council/board, that was done +as we used to do so far, without having a communication team/process +in place; that is, with some hurry and difficulty to spread the useful +info here and there before the release: that always happen like that, +take that for _granted_; the only thing we can do is: improve. + +The goal of each team is _not_ to have a veto on how things go here +and there. A potential veto could come from the Council, or the Board. +Not much more. Of course, in the long term, we'd like to have the +communication team take the hand for +copywriting/proofreading/counselling and providing direction elements +- but for that, a clear and working timeplan has to be set and +followed by coordinated team members, and these have to be available +when required, especially at release time. + +Someone is not available? So, unfortunately, she would have a hard +time complaining because things did not go how she expected/planned +them to. I know this can sound like nonsense if one comes from a +corporate environment - but it's not the same environment here - no +one is paid/ordered to contribute. + +As ennael pointed out, the team better focus on how to build tools and +processes within the project, especially the release/communication +plan for finale, and advocate for it in the Council and through the +project (and "advocating" doesn't mean "forcing/patronizing") and help +everyone prepare to put this in motion. + +Cheers, + +Romain +</PRE> + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="000243.html">[Mageia-marketing] Plan - stuff to do pre Beta 1 release +</A></li> + <LI>Next message: <A HREF="000252.html">[Mageia-marketing] Plan - stuff to do pre Beta 1 release +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#247">[ date ]</a> + <a href="thread.html#247">[ thread ]</a> + <a href="subject.html#247">[ subject ]</a> + <a href="author.html#247">[ 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> |