1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
|
<!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=%3CAANLkTimkeepUuOHw-2BD%2Bw9TS-12Q5ySA2ToSCwAwsmi%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="000545.html">
<LINK REL="Next" HREF="000551.html">
</HEAD>
<BODY BGCOLOR="#ffffff">
<H1>[Mageia-sysadm] Main tasks for the next days</H1>
<B>Romain d'Alverny</B>
<A HREF="mailto:mageia-sysadm%40mageia.org?Subject=Re%3A%20%5BMageia-sysadm%5D%20Main%20tasks%20for%20the%20next%20days&In-Reply-To=%3CAANLkTimkeepUuOHw-2BD%2Bw9TS-12Q5ySA2ToSCwAwsmi%40mail.gmail.com%3E"
TITLE="[Mageia-sysadm] Main tasks for the next days">rdalverny at gmail.com
</A><BR>
<I>Tue Nov 16 09:01:55 CET 2010</I>
<P><UL>
<LI>Previous message: <A HREF="000545.html">[Mageia-sysadm] Main tasks for the next days
</A></li>
<LI>Next message: <A HREF="000551.html">[Mageia-sysadm] Main tasks for the next days
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#548">[ date ]</a>
<a href="thread.html#548">[ thread ]</a>
<a href="subject.html#548">[ subject ]</a>
<a href="author.html#548">[ author ]</a>
</LI>
</UL>
<HR>
<!--beginarticle-->
<PRE>On Tue, Nov 16, 2010 at 00:55, Michael Scherer <<A HREF="https://www.mageia.org/mailman/listinfo/mageia-sysadm">misc at zarb.org</A>> wrote:
><i> Le mardi 16 novembre 2010 à 00:12 +0100, nicolas vigier a écrit :
</I>>><i> [...]
</I>>><i>  * the configuration of sympa mailing lists server using LDAP for users
</I>>><i>    authentication
</I>><i>
</I>><i> We didn't really discussed how and what we will use ldap and sympa for,
</I>><i> and that we setup without thinking first about the full picture.
</I>><i>
</I>><i> Ie, if sympa use ldap for authentication, does that mean that people
</I>><i> will be forced to use identity to subscribe ?
</I>><i> How would it goes for moderation ?
</I>><i> How would they do for subscription ?
</I>
I think that we must have two separate ways to:
- identify someone is a member of a team
- identify someone is subscribed to a team mailing-list
because someone may want to follow team activity, without being
formally involved in it.
So whether we manage both in LDAP or only team-membership (and leave
mailing-list subscription management to sympa alone), I don't know.
><i> There is lots of topic that we didn't really discussed about ML setup
</I>><i> like :
</I>><i>  - list moderation policy
</I>
Do you have an example of such a policy?
><i>  - archiving
</I>
Not sure it makes for all, but, subscriptions to public ml should
state that all communications on these lists are archived.
><i>  - migration from the old server ( especially for archives migrations )
</I>
I don't know if we can import Mailman archives into Sympa ones. If
not, maybe we should just copy plain archives into a specific place
and put redirection rules for existing ones.
><i>  - setting a proper spam filter, with greylisting and sympa integration
</I>
How is it managed at this time with Mailman? Can't this be done after
Sympa production setup?
><i>  - web interface setup and requirement
</I>
Isn't a sympa vanilla install correct for that?
>><i>  * we will import a copy of the Mandriva soft/ repository as
</I>>><i>    svn.mageia.org/soft-cleaning, and will use this repository to clean
</I>>><i>    all projects. Each project when ready will be imported in the new
</I>>><i>    soft/ repository (when the new organisation has been decided). The
</I>>><i>    soft-cleaning repository will only be used to do the cleaning work
</I>>><i>    and will be erased when finished.
</I>><i>
</I>><i> Without history ?
</I>
Without svn history, this what I thought we agreed on yesterday
(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>
it is).
><i> Because there is software that do not requires cleaning ( like mdvsys or
</I>><i> some software that were fully created by the community ).
</I>
Not related, but isn't this a supplementary reason to have a separate
SVN repository for each project, and not a single one for soft/ (as it
is today)?
Cheers,
Romain
</PRE>
<!--endarticle-->
<HR>
<P><UL>
<!--threads-->
<LI>Previous message: <A HREF="000545.html">[Mageia-sysadm] Main tasks for the next days
</A></li>
<LI>Next message: <A HREF="000551.html">[Mageia-sysadm] Main tasks for the next days
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#548">[ date ]</a>
<a href="thread.html#548">[ thread ]</a>
<a href="subject.html#548">[ subject ]</a>
<a href="author.html#548">[ 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>
|
