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
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<TITLE> [Mageia-dev] About Mandriva tools future : Host Mandriva tools on github
</TITLE>
<LINK REL="Index" HREF="index.html" >
<LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20About%20Mandriva%20tools%20future%20%3A%20Host%20Mandriva%20tools%0A%09on%20github&In-Reply-To=%3Ci84eqs%24naa%241%40dough.gmane.org%3E">
<META NAME="robots" CONTENT="index,nofollow">
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
<LINK REL="Previous" HREF="000603.html">
<LINK REL="Next" HREF="000580.html">
</HEAD>
<BODY BGCOLOR="#ffffff">
<H1>[Mageia-dev] About Mandriva tools future : Host Mandriva tools on github</H1>
<B>Marc Paré</B>
<A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20About%20Mandriva%20tools%20future%20%3A%20Host%20Mandriva%20tools%0A%09on%20github&In-Reply-To=%3Ci84eqs%24naa%241%40dough.gmane.org%3E"
TITLE="[Mageia-dev] About Mandriva tools future : Host Mandriva tools on github">marc at marcpare.com
</A><BR>
<I>Fri Oct 1 12:57:32 CEST 2010</I>
<P><UL>
<LI>Previous message: <A HREF="000603.html">[Mageia-dev] About Mandriva tools future : Host Mandriva tools on github
</A></li>
<LI>Next message: <A HREF="000580.html">[Mageia-dev] About Mandriva tools future : Host Mandriva tools on github
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#579">[ date ]</a>
<a href="thread.html#579">[ thread ]</a>
<a href="subject.html#579">[ subject ]</a>
<a href="author.html#579">[ author ]</a>
</LI>
</UL>
<HR>
<!--beginarticle-->
<PRE>Le 2010-10-01 06:38, Fabrice Facorat a écrit :
><i> I've been following closely all the Mandriva vs Mageia story. I found
</I>><i> it unfortunate that we have to come to this way, but I guess there's a
</I>><i> serious fracture between Mandriva and part of its community. We have
</I>><i> no choice except to cope with this and try to do our best to allow
</I>><i> this unfortunate situation to found a sensible solution in the future.
</I>><i>
</I>><i> As we know, one of the Mandriva strenght are the Mandriva tools,
</I>><i> however Mandriva tools have some issues :
</I>><i> - they are written in perl. Sorry for perl dev, but I do still think
</I>><i> that perl is harder to understand than C-like based syntax langages.
</I>><i> However we must admit that we are not going to rewrite all the
</I>><i> Mandriva tools ;-) However better documentation ( PerlDoc tags ) could
</I>><i> help a little.
</I>><i>
</I>><i> - Mandriva tools are not used by others distributions ( except
</I>><i> PCLinuxOS, United Linux, and ... Mageia ) and so have few external
</I>><i> contributions : They notably lack visibility.
</I>><i>
</I>><i> I do think also that Mandriva will have to use its ressources in an
</I>><i> efficient way.
</I>><i>
</I>><i> Here aree my proposals, feel free to discuss :
</I>><i>
</I>><i> 1. host Mandriva tools on github or code.google.com. This will ease
</I>><i> fork maintenance and tracking, to contribute back ( without having to
</I>><i> have a Mandriva account )
</I>><i>
</I>><i> 2. Make some decisions about the tools we should keep, and the ones we
</I>><i> should ... trash. For example we did replace printerdrake with
</I>><i> system-config-printer ( python ), and msec have been rewritten (
</I>><i> python ). Whereas I do think that system-config-printer is way buggier
</I>><i> than printerdrake, I guess that at some points, we will have to do
</I>><i> this more and more : replace some Mandriva tools with for example some
</I>><i> Fedora ones. Please note however that this bring its own issues :
</I>><i> python vs perl, and the integration with the rest of Mandriva
</I>><i> infrastructure
</I>><i>
</I>><i> 3. A decision will have to be made concerning net_applet and NetworkManager
</I>><i>
</I>><i> 4. Whereas I do love rpmdrake, I do think also that something will
</I>><i> have to be done about it as its UI is clearly outdated and not on par
</I>><i> with the competition :
</I>><i> - Ubuntu software center :
</I>><i> <A HREF="http://seilo.geekyogre.com/2010/09/software-center-with-a-dose-of-zeitgeist-and-maybe-teamgeist/">http://seilo.geekyogre.com/2010/09/software-center-with-a-dose-of-zeitgeist-and-maybe-teamgeist/</A>
</I>><i> , <A HREF="http://en.wikipedia.org/wiki/Ubuntu_Software_Center">http://en.wikipedia.org/wiki/Ubuntu_Software_Center</A> ,
</I>><i> <A HREF="https://wiki.ubuntu.com/SoftwareCenter">https://wiki.ubuntu.com/SoftwareCenter</A>
</I>><i> - iTunes App Store :
</I>><i> <A HREF="http://www.askdavetaylor.com/how_to_download_iphone_apps_from_apple_itunes_store.html">http://www.askdavetaylor.com/how_to_download_iphone_apps_from_apple_itunes_store.html</A>
</I>><i> , <A HREF="http://cybernetnews.com/download-iphone-firmware-20-itunes-77-app-store-and-more/">http://cybernetnews.com/download-iphone-firmware-20-itunes-77-app-store-and-more/</A>
</I>><i> - Interesting discussion about PackageKit direction :
</I>><i> <A HREF="http://mairin.wordpress.com/2010/09/01/a-story-about-updates-and-people/">http://mairin.wordpress.com/2010/09/01/a-story-about-updates-and-people/</A>
</I>><i>
</I>><i> So we may have to completely rewrite rpmdrake UI or switch to
</I>><i> packagekit with and urpmi backend.
</I>><i>
</I>><i> 5. Junior tasks contributions. I noticed while visiting the
</I>><i> LibreOffice website. They have junior task for people willing to
</I>><i> contribute to the codebase, and most of theses junior tasks consist to
</I>><i> improve code clarity, fix comments. I guess that the same thing could
</I>><i> be done with Mandriva tools, notably adding perldoc tags/comments.
</I>><i>
</I>><i> Last but not least, I know that on Mageia ML, there was a discussion
</I>><i> about the people we should target. Here are some interesting
</I>><i> reflexions :
</I>><i> Sweet Caroline : <A HREF="http://mairin.wordpress.com/2010/09/02/sweet-caroline/">http://mairin.wordpress.com/2010/09/02/sweet-caroline/</A>
</I>><i> fedoraproject.org redesign update :
</I>><i> <A HREF="http://mairin.wordpress.com/2010/09/03/fedoraproject-org-redesign-update/">http://mairin.wordpress.com/2010/09/03/fedoraproject-org-redesign-update/</A>
</I>><i> You must be this tall to ride: __ :
</I>><i> <A HREF="http://mairin.wordpress.com/2010/10/01/you-must-be-this-tall-to-ride-__/">http://mairin.wordpress.com/2010/10/01/you-must-be-this-tall-to-ride-__/</A>
</I>><i>
</I>><i>
</I>
Thanks for your observations Fabrice.
Just speaking from the "user" point of view. Let us not lose sight that
one of the strong points of Mandriva/Mageia is the use of the MCC.
Having all the controls under one title and well integrated is what
really distinguishes Mandriva from the other distros. Practically in all
of the news items that I have read of Mandriva, they mention the
powerful tools at the users' disposal to help in configure/maintain the
Mandriva distro, and this type of comment has been going on for years.
I hope that Mageia would not stray from this tool. Whichever way the
devs decide to programme the tools from the back-en does not matter to
the user. How easily it is to configure/maintain the distro is what
counts to the user and it is quite a strong selling point.
When I help out people with their Mandriva setup and I tell them to go
to their MCC (if they are not familiar with it, I usually say "You know,
the blue sceen and red wrench thingy at the bottom of your monitor.",
they are confortable in using it.
The only thing that I find lacking for the MCC is the lack of immediate
help. If a user has never used a section of MCC, they will normally
abandon the use of that section. But if there were a help button that
would explain, in a graphic way (either video or by slide show) the use
of that section, then that would go a long way in helping out.
I sincerely hope that the MCC (Mageia Contol Centre) will not be abandoned.
Marc
</PRE>
<!--endarticle-->
<HR>
<P><UL>
<!--threads-->
<LI>Previous message: <A HREF="000603.html">[Mageia-dev] About Mandriva tools future : Host Mandriva tools on github
</A></li>
<LI>Next message: <A HREF="000580.html">[Mageia-dev] About Mandriva tools future : Host Mandriva tools on github
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#579">[ date ]</a>
<a href="thread.html#579">[ thread ]</a>
<a href="subject.html#579">[ subject ]</a>
<a href="author.html#579">[ 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>
|
