summaryrefslogtreecommitdiffstats
path: root/zarb-ml/mageia-webteam/2011-January/000204.html
diff options
context:
space:
mode:
Diffstat (limited to 'zarb-ml/mageia-webteam/2011-January/000204.html')
-rw-r--r--zarb-ml/mageia-webteam/2011-January/000204.html144
1 files changed, 144 insertions, 0 deletions
diff --git a/zarb-ml/mageia-webteam/2011-January/000204.html b/zarb-ml/mageia-webteam/2011-January/000204.html
new file mode 100644
index 000000000..ef2ced21c
--- /dev/null
+++ b/zarb-ml/mageia-webteam/2011-January/000204.html
@@ -0,0 +1,144 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
+<HTML>
+ <HEAD>
+ <TITLE> [Mageia-webteam] planet.mageia.org - info/discuss about the installation
+ </TITLE>
+ <LINK REL="Index" HREF="index.html" >
+ <LINK REL="made" HREF="mailto:mageia-webteam%40mageia.org?Subject=Re%3A%20%5BMageia-webteam%5D%20planet.mageia.org%20-%20info/discuss%20about%20the%0A%20installation&In-Reply-To=%3C1296494367.12892.92.camel%40akroma.ephaone.org%3E">
+ <META NAME="robots" CONTENT="index,nofollow">
+ <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
+ <LINK REL="Previous" HREF="000203.html">
+ <LINK REL="Next" HREF="000205.html">
+ </HEAD>
+ <BODY BGCOLOR="#ffffff">
+ <H1>[Mageia-webteam] planet.mageia.org - info/discuss about the installation</H1>
+ <B>Michael Scherer</B>
+ <A HREF="mailto:mageia-webteam%40mageia.org?Subject=Re%3A%20%5BMageia-webteam%5D%20planet.mageia.org%20-%20info/discuss%20about%20the%0A%20installation&In-Reply-To=%3C1296494367.12892.92.camel%40akroma.ephaone.org%3E"
+ TITLE="[Mageia-webteam] planet.mageia.org - info/discuss about the installation">misc at zarb.org
+ </A><BR>
+ <I>Mon Jan 31 18:19:27 CET 2011</I>
+ <P><UL>
+ <LI>Previous message: <A HREF="000203.html">[Mageia-webteam] planet.mageia.org - info/discuss about the installation
+</A></li>
+ <LI>Next message: <A HREF="000205.html">[Mageia-webteam] planet.mageia.org - info/discuss about the installation
+</A></li>
+ <LI> <B>Messages sorted by:</B>
+ <a href="date.html#204">[ date ]</a>
+ <a href="thread.html#204">[ thread ]</a>
+ <a href="subject.html#204">[ subject ]</a>
+ <a href="author.html#204">[ author ]</a>
+ </LI>
+ </UL>
+ <HR>
+<!--beginarticle-->
+<PRE>Le lundi 31 janvier 2011 &#224; 16:50 +0100, Romain d'Alverny a &#233;crit :
+&gt;<i> On Mon, Jan 31, 2011 at 12:30, Michael Scherer &lt;<A HREF="https://www.mageia.org/mailman/listinfo/mageia-webteam">misc at zarb.org</A>&gt; wrote:
+</I>
+&gt;<i> &gt;&gt; And yes, it has to be filtered by the Mageia topic; off-topic stuff
+</I>&gt;<i> &gt;&gt; (regarding the project as a whole, it's not only about technical
+</I>&gt;<i> &gt;&gt; stuff) should not appear in such a feed. And yes, we rely on authors
+</I>&gt;<i> &gt;&gt; benevolence in this regard.
+</I>&gt;<i> &gt;
+</I>&gt;<i> &gt; Well, this has to be clearly said. That's not the same policy on all
+</I>&gt;<i> &gt; planet, and I think that having a tag is not enough ( see Adam W post on
+</I>&gt;<i> &gt; planet Mandriva, some people have seen them too off topic, but it has a
+</I>&gt;<i> &gt; tag Mandriva nonetheless ).
+</I>&gt;<i>
+</I>&gt;<i> How do you suggest to manage it otherwise?
+</I>
+No, I do not say that using a tag is not good on a technical level. I
+say that the definition should be IMHO clearer than &quot;using a tag&quot;. Ie,
+what do we expect on the tag.
+
+&gt;<i> &gt; Marcom, marketing or communication ?
+</I>&gt;<i>
+</I>&gt;<i> Both.
+</I>
+Well, to me, this look like the job of communication more than
+marketing, but maybe I mistake the purpose of the marketing team.
+
+&gt;<i> &gt; Shouldn't the board have the final say ( as one of the duty is conflict
+</I>&gt;<i> &gt; management ) ?
+</I>&gt;<i>
+</I>&gt;<i> The board always has a final say, that's a given. But that should
+</I>&gt;<i> still be exceptional and repeating it over and over won't entrust
+</I>&gt;<i> teams on themselves.
+</I>
+If we entrust the marketing team to do conflict management and editorial
+control, it should be clearly said. If the duty is shared among the
+board, the web team, the communication team, the marketing team, it may
+not be so final say, and I can only foresee potential conflicts.
+
+&gt;<i> &gt; We can hardly call &quot;community feed aggregation&quot; a new field of
+</I>&gt;<i> &gt; experimentation, given the fact that it is a common practice in free
+</I>&gt;<i> &gt; software since years. And we can also take for granted that unspecified
+</I>&gt;<i> &gt; things will likely be interpreted differently.
+</I>&gt;<i>
+</I>&gt;<i> That's the interesting part; to let thing go different.
+</I>
+If we want to be different, then I still have my old proposal of having
+a feed of feeds instead of a feed of articles. But this requires to
+write lots of software, patchs and a protocol ( and not enough space in
+the margin for this )
+
+&gt;<i> Nonetheless, how would you act on this then? (filtering, policy for
+</I>&gt;<i> aggregation, etc.)
+</I>
+Personally, I would not do it. At least, not now. All teams are not
+started, website is still at zarb, blogs also at zarb, catdap is not
+announced ( and would be nice with more polish ), lots of more pressing
+needs ( maintainers db, wiki ), etc.
+
+
+Now, if I wanted to do it, I would still aim for having the minimal
+requirement of maintainability. People ( as long they have a email
+alias, ie are peers ) decide what they blog, how they blog, etc. Some
+kind of wiki way applied to feed aggregations. I would even push to
+delegate the feeds in ldap so people can change themselves without
+anyone intervention.
+
+
+But let's pretend we should have to decide and what to filter ( because
+i am pretty sure that the free-for-all POV is not universally shared ).
+
+First, I would try to clearly articulate the goal of the website. Having
+&quot;a regular stream of news about Mageia&quot; is not the same as &quot;discovering
+the life of contributors&quot;. For example, the aforementioned chocolate
+cake pictures is likely not ok if the goal is to speak only of Mageia.
+
+Getting the target audience is also important, and anticipate where it
+should be displayed.
+
+This allows to know if we want someone see the word fuck or not. We may
+not want to have strong political comments on the frontpage of the
+project ( As said, I personally wouldn't care, but I guess that's not a
+universal view ).
+
+The rest will then come by itself after that.
+
+--
+Michael Scherer
+
+</PRE>
+
+
+<!--endarticle-->
+ <HR>
+ <P><UL>
+ <!--threads-->
+ <LI>Previous message: <A HREF="000203.html">[Mageia-webteam] planet.mageia.org - info/discuss about the installation
+</A></li>
+ <LI>Next message: <A HREF="000205.html">[Mageia-webteam] planet.mageia.org - info/discuss about the installation
+</A></li>
+ <LI> <B>Messages sorted by:</B>
+ <a href="date.html#204">[ date ]</a>
+ <a href="thread.html#204">[ thread ]</a>
+ <a href="subject.html#204">[ subject ]</a>
+ <a href="author.html#204">[ author ]</a>
+ </LI>
+ </UL>
+
+<hr>
+<a href="https://www.mageia.org/mailman/listinfo/mageia-webteam">More information about the Mageia-webteam
+mailing list</a><br>
+</body></html>