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
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<TITLE> [Mageia-sysadm] list of things to do in sysadmin
</TITLE>
<LINK REL="Index" HREF="index.html" >
<LINK REL="made" HREF="mailto:mageia-sysadm%40mageia.org?Subject=Re%3A%20%5BMageia-sysadm%5D%20list%20of%20things%20to%20do%20in%20sysadmin&In-Reply-To=%3CBANLkTikkGM%3DV7NAExOsGZYSTkg9iN_0-Ww%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="003307.html">
<LINK REL="Next" HREF="003309.html">
</HEAD>
<BODY BGCOLOR="#ffffff">
<H1>[Mageia-sysadm] list of things to do in sysadmin</H1>
<B>Romain d'Alverny</B>
<A HREF="mailto:mageia-sysadm%40mageia.org?Subject=Re%3A%20%5BMageia-sysadm%5D%20list%20of%20things%20to%20do%20in%20sysadmin&In-Reply-To=%3CBANLkTikkGM%3DV7NAExOsGZYSTkg9iN_0-Ww%40mail.gmail.com%3E"
TITLE="[Mageia-sysadm] list of things to do in sysadmin">rdalverny at gmail.com
</A><BR>
<I>Fri Apr 8 12:06:36 CEST 2011</I>
<P><UL>
<LI>Previous message: <A HREF="003307.html">[Mageia-sysadm] list of things to do in sysadmin
</A></li>
<LI>Next message: <A HREF="003309.html">[Mageia-sysadm] list of things to do in sysadmin
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#3308">[ date ]</a>
<a href="thread.html#3308">[ thread ]</a>
<a href="subject.html#3308">[ subject ]</a>
<a href="author.html#3308">[ author ]</a>
</LI>
</UL>
<HR>
<!--beginarticle-->
<PRE>On Fri, Apr 8, 2011 at 11:03, nicolas vigier <<A HREF="https://www.mageia.org/mailman/listinfo/mageia-sysadm">boklm at mars-attacks.org</A>> wrote:
><i> First we need to check if it's doing what we want. And check that we
</I>><i> all agree on what it should do. I didn't look in details, but :
</I>><i>  - I think gitorious allows anybody to create his own repositories. But
</I>><i>   I think what we want is shared repositories, and I don't know if we
</I>><i>   want to host personal ones too.
</I>
The whole interest of gitorious is precisely that (easily forking a
repository for pushing patches afterwise). If we cut this off, we
better not use this solution at all.
><i>  - We need to see how we manage commit permissions. We probably want to
</I>><i>   use ldap groups for this, I don't know if it's possible with
</I>><i>   gitorious/redmine
</I>
About gitorious, I don't know if we can interface with its own ACLs,
but there's a web-based UI for managing that there, per repository.
Better use it.
><i>  - gitorious or redmine include wikis, forums, bug tracker. Maybe we
</I>><i>   don't want that, so we should be able to disable them.
</I>
Yep. Or consider that is a separate forge.
><i>  - if we only use this tool to create new repositories and have a web
</I>><i>   interface to show commits but use none of the advanced features of
</I>><i>   gitorious/redmine, maybe a few scripts in puppet and gitweb is more
</I>><i>   simple than customising gitorious/redmine to do exactly what we want.
</I>
The point is: do we use a tool that already builds a multi-projects
forge, or do we build our own?
For the distribution and Mageia project itself, everything revolves
around a few monolithic bits at this time: Bugzilla, SVN, buildsystem.
If we want to give separate "upstream" identities to software in /soft
(or to some tools still buried down here and there), each one should
have its own:
- fully customizable web page (with an obvious path to it) - with a
default template provided for those who don't need/want to customize
- documentation/wiki
- bug/feature tracker
- code repository + web output of it
- perhaps a mini blog, but a forum seems less likely to happen there
If we want to give some flexibility into the project to incumbate
small projects to embbed into or derive from Mageia, creating such a
new "upstream" project should be, at least for some people, as easy as
using a single web form - so yes, it would be somehow like what
tuxfamily, savannah, indefero, google code, github, etc. - shall we
use these instead then? I believe we are not all in sync about this.
So the question is: do we build this with something existing that
duplicates somehow what we have already, and integrate it as we can?
or do we build this on top of what we already have?
><i> So someone needs to see exactly what is needed, with people that will use
</I>><i> the repositories, and look at all available tools to be able to decide
</I>><i> what we should use.
</I>
We've got to decide at some points too. Or we will still be at this
point in 6 months.
Romain
</PRE>
<!--endarticle-->
<HR>
<P><UL>
<!--threads-->
<LI>Previous message: <A HREF="003307.html">[Mageia-sysadm] list of things to do in sysadmin
</A></li>
<LI>Next message: <A HREF="003309.html">[Mageia-sysadm] list of things to do in sysadmin
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#3308">[ date ]</a>
<a href="thread.html#3308">[ thread ]</a>
<a href="subject.html#3308">[ subject ]</a>
<a href="author.html#3308">[ 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>
|
