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/000245.html | |
parent | fa5098cf210b23ab4f419913e28af7b1b07dafb2 (diff) | |
download | archives-master.tar archives-master.tar.gz archives-master.tar.bz2 archives-master.tar.xz archives-master.zip |
Diffstat (limited to 'zarb-ml/mageia-marketing/2011-April/000245.html')
-rw-r--r-- | zarb-ml/mageia-marketing/2011-April/000245.html | 174 |
1 files changed, 174 insertions, 0 deletions
diff --git a/zarb-ml/mageia-marketing/2011-April/000245.html b/zarb-ml/mageia-marketing/2011-April/000245.html new file mode 100644 index 000000000..8326cfc25 --- /dev/null +++ b/zarb-ml/mageia-marketing/2011-April/000245.html @@ -0,0 +1,174 @@ +<!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=%3C4D9C62C7.40702%40NorthTech.US%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="000242.html"> + <LINK REL="Next" HREF="000248.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-marketing] Plan - stuff to do pre Beta 1 release</H1> + <B>Bradley D. Thornton</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=%3C4D9C62C7.40702%40NorthTech.US%3E" + TITLE="[Mageia-marketing] Plan - stuff to do pre Beta 1 release">Bradley at NorthTech.US + </A><BR> + <I>Wed Apr 6 14:55:35 CEST 2011</I> + <P><UL> + <LI>Previous message: <A HREF="000242.html">[Mageia-marketing] Plan - stuff to do pre Beta 1 release +</A></li> + <LI>Next message: <A HREF="000248.html">[Mageia-marketing] Plan - stuff to do pre Beta 1 release +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#245">[ date ]</a> + <a href="thread.html#245">[ thread ]</a> + <a href="subject.html#245">[ subject ]</a> + <a href="author.html#245">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>-----BEGIN PGP SIGNED MESSAGE----- +Hash: RIPEMD160 + + + +On 04/06/2011 05:25 AM, Wolfgang Bornath wrote: +><i> 2011/4/6 Patricia Fraser <<A HREF="https://www.mageia.org/mailman/listinfo/mageia-marketing">trish at thefrasers.org</A>>: +</I>>><i> Comments inline: +</I>>><i> +</I>>>>><i> 1. Announcement for forum, blog and mailing lists has/have to be +</I>>>>><i> written (who does this?) +</I>>>><i> +</I>>>><i> Ennael appears to have written the one for Alpha 1. Whether or not +</I>>>><i> she actually wrote it is beside the point. +</I>>>><i> +</I>>>><i> I think she's the logical spokesperson for, lack of a better term, +</I>>>><i> the corporate face of Mageia. +</I>>>><i> +</I>>>><i> Now, having said that, perhaps it is time to bring up how +</I>>>><i> grammatically atrocious the English version of that blog +</I>>>><i> announcement was. It's obvious that even the wind of that release +</I>>>><i> announcement never came through this committee - which is an +</I>>>><i> obvious case in point. +</I>>><i> +</I>>><i> Yep - and the current one's not a lot better. Lots of opportunities +</I>>><i> are also being missed to put a communication-type wrapper around it +</I>>><i> that speaks about what kind of community we are - must be fixed for +</I>>><i> Final, if not for Beta2. +</I>><i> +</I>><i> As I already wrote in this thread: +</I>><i> The current announcement is a simple information to the community of +</I>><i> testers and all interested people that Beta1 is out, +</I> +The 'current announcement' was a public announcement - As Patricia +pointed out, it wasn't much better than the first announcement. As I +pointed out it not even the odor of a draft of this announcement made it +here to this list. + +Finally, it was arbitrarily published, is a hackjob write up, and should +have come through here. + +It doesn't matter who the authors "Think" it is intended for - it is +public, and a reflection of the marcom group - even though we were +blindsighted by it. + + +><i> +</I>>><i> Role account; also advisory to the board on presenting Mageia outside +</I>>><i> the core community. +</I>><i> +</I>><i> That would be nice and important whenever the time allows to ask for +</I>><i> this advice, i.e. in situations where announcements and other docs are +</I>><i> planned some time before they are needed. +</I> + +I think we've waited six months long enough Wolfgang. I do not concur +with your thoughts regarding situations that take longer than six months. +><i> +</I>>><i> Can we have some server space and a CRM, and who do we ask for that? +</I>>><i> What I'd like to be able to tell new marcom people is: go to here +</I> +><i> You can have all the space you need in the existing wiki right now. +</I>><i> Just log in and create it. +</I> +Why yes we can have the server space and a CRM :) Not only that, but +until such time as whomever it is that we keep asking about that +apparently doesn't exist gets around to it and finally does this for us, +I'll create a hosted account for the marcom and other teams since we +can't get a straight answer otherwise. The wiki is [still] temporary I +believe, has uses, but not acceptable for what we've already discussed for. + +Hopefully, someone will get a clue. + +"Who do we ask for????" - "Oh just do this instead". No! That is +cojmpletely unacceptable! If we can't have the answers to the questions, +If the resources we, as a team decided upon, aren't being delivered now +that all of the pieces we've been waiting on have been put in place to +do so, then we just need to not bother asking anymore. + +I haven't worked on this project for months and months and waited for +the bootstrapping process to be completed, just so this team can be +obviated or marginalized by whimsical and arbitrary decision making +contrary to how this organization is established. + +NO. We'll just do it ourselves and when this invisible and anonymous +person who has the power to set up the tools we've asked for actually +does it, then they can also take a dump of the database we've built and +we can have it hosted at megeia.org when it is mature enough an +infrastructure to host such things. + +"USE THE WIKI" Was NOT not appreciated, nor was it an acceptable answer! + + +- -- +Bradley D. Thornton +Manager Network Services +NorthTech Computer +TEL: +1.760.666.2703 (US) +TEL: +44.702.405.1909 (UK) +<A HREF="http://NorthTech.US">http://NorthTech.US</A> + +-----BEGIN PGP SIGNATURE----- +Version: GnuPG v1.4.10 (GNU/Linux) +Comment: Find this cert at x-<A HREF="hkp://pool.sks-keyservers.net">hkp://pool.sks-keyservers.net</A> + +iQEcBAEBAwAGBQJNnGLHAAoJEE1wgkIhr9j360kIAI6pRQbV+EdUP8145tqL0Ia5 +4aYnVjLWdJiFk+2E1fUnA02yMcECXN2FJnkkFLe1Y2aKPGJe8k6ndON4c4RgnR6I +QOUqWWSMMXiSZpT6j8Ag3EHDW3Mnyb83ezBh8c9CEkelDhCD/b1EuN1ovWb7jACa +3baMPOjUNoRsWPW0OF3MwbAe9cSfhhqWRuAPm75Wjtao9+ded2ExocExFVrvIG6n +JtWQg0HmqD+NGgmsutkLEAS4OAgJBOjuWRVx2gkpaWboeVWwPpisO41KxyCnFBIp +neU5tDTibHGf9F0PkLND2FA2vCBnhqDs0mSimrUQvt+UXmBdeAli0PWfrYWJxJk= +=Abgl +-----END PGP SIGNATURE----- +</PRE> + + + + + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="000242.html">[Mageia-marketing] Plan - stuff to do pre Beta 1 release +</A></li> + <LI>Next message: <A HREF="000248.html">[Mageia-marketing] Plan - stuff to do pre Beta 1 release +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#245">[ date ]</a> + <a href="thread.html#245">[ thread ]</a> + <a href="subject.html#245">[ subject ]</a> + <a href="author.html#245">[ 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> |