summaryrefslogtreecommitdiffstats
path: root/zarb-ml/mageia-sysadm/2010-November/000551.html
diff options
context:
space:
mode:
Diffstat (limited to 'zarb-ml/mageia-sysadm/2010-November/000551.html')
-rw-r--r--zarb-ml/mageia-sysadm/2010-November/000551.html201
1 files changed, 201 insertions, 0 deletions
diff --git a/zarb-ml/mageia-sysadm/2010-November/000551.html b/zarb-ml/mageia-sysadm/2010-November/000551.html
new file mode 100644
index 000000000..8d4e237e3
--- /dev/null
+++ b/zarb-ml/mageia-sysadm/2010-November/000551.html
@@ -0,0 +1,201 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
+<HTML>
+ <HEAD>
+ <TITLE> [Mageia-sysadm] Main tasks for the next days
+ </TITLE>
+ <LINK REL="Index" HREF="index.html" >
+ <LINK REL="made" HREF="mailto:mageia-sysadm%40mageia.org?Subject=Re%3A%20%5BMageia-sysadm%5D%20Main%20tasks%20for%20the%20next%20days&In-Reply-To=%3C1289912077.722.327.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="000548.html">
+ <LINK REL="Next" HREF="000552.html">
+ </HEAD>
+ <BODY BGCOLOR="#ffffff">
+ <H1>[Mageia-sysadm] Main tasks for the next days</H1>
+ <B>Michael Scherer</B>
+ <A HREF="mailto:mageia-sysadm%40mageia.org?Subject=Re%3A%20%5BMageia-sysadm%5D%20Main%20tasks%20for%20the%20next%20days&In-Reply-To=%3C1289912077.722.327.camel%40akroma.ephaone.org%3E"
+ TITLE="[Mageia-sysadm] Main tasks for the next days">misc at zarb.org
+ </A><BR>
+ <I>Tue Nov 16 13:54:37 CET 2010</I>
+ <P><UL>
+ <LI>Previous message: <A HREF="000548.html">[Mageia-sysadm] Main tasks for the next days
+</A></li>
+ <LI>Next message: <A HREF="000552.html">[Mageia-sysadm] Main tasks for the next days
+</A></li>
+ <LI> <B>Messages sorted by:</B>
+ <a href="date.html#551">[ date ]</a>
+ <a href="thread.html#551">[ thread ]</a>
+ <a href="subject.html#551">[ subject ]</a>
+ <a href="author.html#551">[ author ]</a>
+ </LI>
+ </UL>
+ <HR>
+<!--beginarticle-->
+<PRE>Le mardi 16 novembre 2010 &#224; 09:01 +0100, Romain d'Alverny a &#233;crit :
+&gt;<i> On Tue, Nov 16, 2010 at 00:55, Michael Scherer &lt;<A HREF="https://www.mageia.org/mailman/listinfo/mageia-sysadm">misc at zarb.org</A>&gt; wrote:
+</I>
+
+&gt;<i> &gt; There is lots of topic that we didn't really discussed about ML setup
+</I>&gt;<i> &gt; like :
+</I>&gt;<i> &gt; - list moderation policy
+</I>&gt;<i>
+</I>&gt;<i> Do you have an example of such a policy?
+</I>
+Nope, but I guess we can find some of them for
+debian/ubuntu/fedora/gentoo.
+
+<A HREF="http://fedoraproject.org/wiki/Hall_Monitor_Policy">http://fedoraproject.org/wiki/Hall_Monitor_Policy</A>
+<A HREF="https://wiki.ubuntu.com/MailingLists">https://wiki.ubuntu.com/MailingLists</A>
+<A HREF="http://www.debian.org/MailingLists/HOWTO_start_list">http://www.debian.org/MailingLists/HOWTO_start_list</A>
+
+( but most research give MLs guideline for users, that we already have )
+
+But this is also related to the creation of a team to take care of that,
+and to the policy of creation. Ie, who decide that list are created or
+not.
+
+And also who take care of the list that are not tied to a team. And who
+can moderate a list, the moderation team alone, the team leader, the
+sysadmin, a combination of them, etc ?
+
+&gt;<i> &gt; - archiving
+</I>&gt;<i>
+</I>&gt;<i> Not sure it makes for all, but, subscriptions to public ml should
+</I>&gt;<i> state that all communications on these lists are archived.
+</I>
+We also need to discuss what will be public and what will not.
+
+And what do we do with thing like gmane ( nntp and public archiving ). A
+automated integration would be nice ( like automatically subscribe to
+their service when we offer a mailing list ), but this would require a
+script I guess.
+
+There is also the topic of ml&lt;-&gt; forum integration.
+
+&gt;<i> &gt; - migration from the old server ( especially for archives migrations )
+</I>&gt;<i>
+</I>&gt;<i> I don't know if we can import Mailman archives into Sympa ones. If
+</I>&gt;<i> not, maybe we should just copy plain archives into a specific place
+</I>&gt;<i> and put redirection rules for existing ones.
+</I>
+Even we do import, we will likely lose links, and therefore we will need
+to change 1) blog posts 2) mailing list archives. So a copy of the
+website should be done indeed. How long should we keep the url is open
+to discussion.
+
+&gt;<i> &gt; - setting a proper spam filter, with greylisting and sympa integration
+</I>&gt;<i>
+</I>&gt;<i> How is it managed at this time with Mailman? Can't this be done after
+</I>&gt;<i> Sympa production setup?
+</I>
+For mailman, this is managed at the smtp server level, and we do not
+have any kind of integration ( but this will likely change as I am quite
+tired of cleaning the queue of some others zarb.org project with 100
+spam per month ).
+
+And by integration, it usually mean &quot;moderation/rejection based on SMTP
+headers&quot;.
+
+For the moment, there is around 1 to 2 spam per day that end in the
+moderation queue for mageia lists. Without spam filtering and
+greylisting, I suspect it will be much more ( greylisting reduced the
+load of spam by 90% the day we deployed it ). And as the one that clean
+the moderation queue quite often, I am not thrilled of having a mail
+server without spam protection :)
+
+But my point is we need a proper ( read with proper filtering and
+redundancy ) smtp server before having a ml server.
+
+&gt;<i> &gt; - web interface setup and requirement
+</I>&gt;<i>
+</I>&gt;<i> Isn't a sympa vanilla install correct for that?
+</I>
+We have to check, and for this, we need to know what we want.
+
+I am quite confident that it can be tweaked to do what we want as it
+offer templating ( with TT2 ) like most of the perl applications we
+deployed.
+
+( and in fact, I also think we should add &quot;template technology used&quot; to
+the list of criteria for selecting application, as I do not think the
+web team will love to have 23 types of languages to learn for this )
+
+But we need to see if there is work needed on this part. I mostly see
+the need to remove some part of the interface for some users, and the
+need for usual theming and navbar.
+
+
+A recurrent problem on AUFML server was that we had a dual admin
+interface : some people were subscribed with drupal and ldap ( and a
+nightly synchronisation script ), and some with mailman.
+
+Yet, people used mailman to unsubcribe ( as this was the logical thing
+to do, and since nothing prevented it on mailman side ), and some people
+were then re subscribed each night, leading to frustration ( and some
+angry mails toward admins ).
+
+
+&gt;<i> &gt;&gt; * we will import a copy of the Mandriva soft/ repository as
+</I>&gt;<i> &gt;&gt; svn.mageia.org/soft-cleaning, and will use this repository to clean
+</I>&gt;<i> &gt;&gt; all projects. Each project when ready will be imported in the new
+</I>&gt;<i> &gt;&gt; soft/ repository (when the new organisation has been decided). The
+</I>&gt;<i> &gt;&gt; soft-cleaning repository will only be used to do the cleaning work
+</I>&gt;<i> &gt;&gt; and will be erased when finished.
+</I>&gt;<i> &gt;
+</I>&gt;<i> &gt; Without history ?
+</I>&gt;<i>
+</I>&gt;<i> Without svn history, this what I thought we agreed on yesterday
+</I>&gt;<i> (checking <A HREF="http://meetbot.mageia.org/mageia-meeting/2010/mageia-meeting.2010-11-15-19.36.html">http://meetbot.mageia.org/mageia-meeting/2010/mageia-meeting.2010-11-15-19.36.html</A>
+</I>&gt;<i> it is).
+</I>
+The lose of history was for the packages, not for soft ( at least,
+that's what I understand, given the fact that &quot;history&quot; is said 5 times
+and all related to packages, not soft/ ).
+
+We all agree that some softwares will need to be cleaned from icons, but
+IMHO, most of them don't. I also think we can do miracles with git-svn
+and history rewriting ( except it may take time ).
+
+But having worked on software without svn history, I can tell you it is
+a source of recurrent frustration. You look at some weird piece of code,
+you do not understand why it was done like this, you do svn blame -&gt;
+&quot;rev 443 admin: import of the old repository&quot;. You are screwed.
+
+&gt;<i> &gt; Because there is software that do not requires cleaning ( like mdvsys or
+</I>&gt;<i> &gt; some software that were fully created by the community ).
+</I>&gt;<i>
+</I>&gt;<i> Not related, but isn't this a supplementary reason to have a separate
+</I>&gt;<i> SVN repository for each project, and not a single one for soft/ (as it
+</I>&gt;<i> is today)?
+</I>
+Yes, it is.
+
+--
+Michael Scherer
+
+</PRE>
+
+
+
+
+
+<!--endarticle-->
+ <HR>
+ <P><UL>
+ <!--threads-->
+ <LI>Previous message: <A HREF="000548.html">[Mageia-sysadm] Main tasks for the next days
+</A></li>
+ <LI>Next message: <A HREF="000552.html">[Mageia-sysadm] Main tasks for the next days
+</A></li>
+ <LI> <B>Messages sorted by:</B>
+ <a href="date.html#551">[ date ]</a>
+ <a href="thread.html#551">[ thread ]</a>
+ <a href="subject.html#551">[ subject ]</a>
+ <a href="author.html#551">[ author ]</a>
+ </LI>
+ </UL>
+
+<hr>
+<a href="https://www.mageia.org/mailman/listinfo/mageia-sysadm">More information about the Mageia-sysadm
+mailing list</a><br>
+</body></html>