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
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<TITLE> [Mageia-dev] Some changes on svn
</TITLE>
<LINK REL="Index" HREF="index.html" >
<LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Some%20changes%20on%20svn&In-Reply-To=%3C1303422621.2307.184.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="004133.html">
</HEAD>
<BODY BGCOLOR="#ffffff">
<H1>[Mageia-dev] Some changes on svn</H1>
<B>Michael Scherer</B>
<A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Some%20changes%20on%20svn&In-Reply-To=%3C1303422621.2307.184.camel%40akroma.ephaone.org%3E"
TITLE="[Mageia-dev] Some changes on svn">misc at zarb.org
</A><BR>
<I>Thu Apr 21 23:50:21 CEST 2011</I>
<P><UL>
<LI>Previous message: <A HREF="004133.html">[Mageia-dev] Some changes on svn
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#4134">[ date ]</a>
<a href="thread.html#4134">[ thread ]</a>
<a href="subject.html#4134">[ subject ]</a>
<a href="author.html#4134">[ author ]</a>
</LI>
</UL>
<HR>
<!--beginarticle-->
<PRE>Le jeudi 21 avril 2011 à 22:49 +0200, Michael Scherer a écrit :
><i> Hi,
</I>><i>
</I>><i> I have done some change regarding svn access, and while I am carefully
</I>><i> testing to not break it, if someone has a problem, please report it
</I>><i> ( with your login, telling if you can connect or not ).
</I>><i>
</I>><i> The goal is to simplify the way we manage everything, so translators can
</I>><i> later be able to commit their work.
</I>
So it seems to work fine.
But now, this lead me to another question :
- how do we manage commit access to the repository soft/
For now, only packagers can access it, mainly because that's the only
group we had at that time. But in fact, I see no reason to use this
group more than another.
We have a few choice :
- let anybody commit , all people in shell_access group could do it.
Right now, that mean sysadmins, web developer, forum developers,
translators, packagers and apprentices.
- create a group for developers, and let them have access on the svn,
and add i18n committers on a subset.
I was about to do the 2nd stuff, but looking for documentation, the svn
book convinced me to do the first one (
<A HREF="http://svnbook.red-bean.com/nightly/en/svn.serverconfig.pathbasedauthz.html">http://svnbook.red-bean.com/nightly/en/svn.serverconfig.pathbasedauthz.html</A> ).
But this solution kinda negate the goal and the existence of "developer
team". On the other hand, the team do not exist right now.
What do people think of it ?
--
Michael Scherer
</PRE>
<!--endarticle-->
<HR>
<P><UL>
<!--threads-->
<LI>Previous message: <A HREF="004133.html">[Mageia-dev] Some changes on svn
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#4134">[ date ]</a>
<a href="thread.html#4134">[ thread ]</a>
<a href="subject.html#4134">[ subject ]</a>
<a href="author.html#4134">[ author ]</a>
</LI>
</UL>
<hr>
<a href="https://www.mageia.org/mailman/listinfo/mageia-dev">More information about the Mageia-dev
mailing list</a><br>
</body></html>
|
