From 1be510f9529cb082f802408b472a77d074b394c0 Mon Sep 17 00:00:00 2001 From: Nicolas Vigier Date: Sun, 14 Apr 2013 13:46:12 +0000 Subject: Add zarb MLs html archives --- zarb-ml/mageia-sysadm/2010-November/000545.html | 124 ++++++++++++++++++++++++ 1 file changed, 124 insertions(+) create mode 100644 zarb-ml/mageia-sysadm/2010-November/000545.html (limited to 'zarb-ml/mageia-sysadm/2010-November/000545.html') diff --git a/zarb-ml/mageia-sysadm/2010-November/000545.html b/zarb-ml/mageia-sysadm/2010-November/000545.html new file mode 100644 index 000000000..c85dd0646 --- /dev/null +++ b/zarb-ml/mageia-sysadm/2010-November/000545.html @@ -0,0 +1,124 @@ + + + + [Mageia-sysadm] Main tasks for the next days + + + + + + + + + +

[Mageia-sysadm] Main tasks for the next days

+ Michael Scherer + misc at zarb.org +
+ Tue Nov 16 00:55:15 CET 2010 +

+
+ +
Le mardi 16 novembre 2010 à 00:12 +0100, nicolas vigier a écrit :
+> Hello,
+> 
+> As was decided in tonight IRC meeting, the priority tasks for sysadmin in
+> the next days will be :
+>  * the configuration of pam_ldap, nss_ldap, and everything needed to
+>    allow commits from LDAP accounts on SVN
+
+>  * the configuration of forums with LDAP accounts (to be finished)
+
+A first step would be to make sure that people in charge of forum read
+this list and are subscribed to it. And another step would be to know
+what they do, since I am spammed every day by the cron job who update of
+urpmi who is bounced to root at zarb alias, as the server is
+misconfigurated ( ie, it send mail to a alias that do not exist ).
+
+>  * the configuration of sympa mailing lists server using LDAP for users
+>    authentication
+
+We didn't really discussed how and what we will use ldap and sympa for,
+and that we setup without thinking first about the full picture.
+
+Ie, if sympa use ldap for authentication, does that mean that people
+will be forced to use identity to subscribe ? 
+How would it goes for moderation ?
+How would they do for subscription ?
+
+There is lots of topic that we didn't really discussed about ML setup
+like :
+ - list moderation policy 
+ - archiving
+ - migration from the old server ( especially for archives migrations )
+ - setting a proper spam filter, with greylisting and sympa integration
+ - web interface setup and requirement 
+ - etc, etc
+
+So we should not start by installing software on production server,
+testing it and saying "it is almost ready", but first by thinking about
+what we need and what will happen, test it elsewhere, and then deploy
+it. 
+
+
+> Regarding the soft/ repository :
+>  * misc will send an email to discuss a new soft/ repository
+>    organisation
+done
+
+>  * we will import a copy of the Mandriva soft/ repository as
+>    svn.mageia.org/soft-cleaning, and will use this repository to clean
+>    all projects. Each project when ready will be imported in the new
+>    soft/ repository (when the new organisation has been decided). The
+>    soft-cleaning repository will only be used to do the cleaning work
+>    and will be erased when finished.
+
+Without history ?
+
+Because there is software that do not requires cleaning ( like mdvsys or
+some software that were fully created by the community ).
+
+-- 
+Michael Scherer
+
+
+ + + + + + + + + +
+

+ +
+More information about the Mageia-sysadm +mailing list
+ -- cgit v1.2.1