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
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<TITLE> [Mageia-dev] How will be the realese cycle?
</TITLE>
<LINK REL="Index" HREF="index.html" >
<LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20How%20will%20be%20the%20realese%20cycle%3F&In-Reply-To=%3C201010071136.41991.stormi%40laposte.net%3E">
<META NAME="robots" CONTENT="index,nofollow">
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
<LINK REL="Previous" HREF="000969.html">
<LINK REL="Next" HREF="000972.html">
</HEAD>
<BODY BGCOLOR="#ffffff">
<H1>[Mageia-dev] How will be the realese cycle?</H1>
<B>Samuel Verschelde</B>
<A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20How%20will%20be%20the%20realese%20cycle%3F&In-Reply-To=%3C201010071136.41991.stormi%40laposte.net%3E"
TITLE="[Mageia-dev] How will be the realese cycle?">stormi at laposte.net
</A><BR>
<I>Thu Oct 7 11:36:41 CEST 2010</I>
<P><UL>
<LI>Previous message: <A HREF="000969.html">[Mageia-dev] How will be the realese cycle?
</A></li>
<LI>Next message: <A HREF="000972.html">[Mageia-dev] How will be the realese cycle?
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#971">[ date ]</a>
<a href="thread.html#971">[ thread ]</a>
<a href="subject.html#971">[ subject ]</a>
<a href="author.html#971">[ author ]</a>
</LI>
</UL>
<HR>
<!--beginarticle-->
<PRE>
Le jeudi 7 octobre 2010 11:20:04, Buchan Milne a écrit :
><i> The fact that almost no-one on this list seems to have known about backports
</I>><i> at all doesn't mean that the backports feature is not useful, it may be that
</I>><i> it wasn't accessible enough to end users.
</I>
+1
><i> Now, maybe the user interface needs to be improved. For example, maybe there
</I>><i> should be no dropdown box, but instead when searching for a package by name,
</I>><i> it should show you all the versions:
</I>><i>
</I>><i> ============================================================================
</I>><i> Find: | digikam | In: ->Graphical applications |By: ->Package Name
</I>><i> ----------------------------------------------------------------------------
</I>><i> Package| |Status | Action
</I>><i> +digikam |Security update recommended |Update |
</I>><i> - 1.3.0-1mdv |Installed |Uninstall |
</I>><i> - 1.3.0-1.1mdv |Security Update |Update |
</I>><i> - 1.4.0-4mdv |Unsupported upgrade (backport) |Upgrade |
</I>><i>
</I>><i> -----------------------------------------------------------------------------
</I>><i> digikam - A KDE ........
</I>><i>
</I>><i> =============================================================================
</I>
+1
><i>
</I>><i>
</I>><i> Alternatively, maybe a "What's new" view?
</I>
Oh yes, let's do it !
><i>
</I>><i> Maybe a rating/voting/popularity system should be available, however in the
</I>><i> past people had complained about privacy issues, which I think may have
</I>><i> resulted in little effort being put into completion of drakstats.
</I>><i>
</I>><i> So, maybe a web site should also be developed, which allows users to also
</I>><i> access package rating information, and which provides some kind of
</I>><i> installation feature.
</I>
Yes this web site could :
- allow package rating
- show download stats (if possible)
- show recent versions updates (with the highest rating packages more visible than an obscure lib :))
- allow backport / new package requests (I know, bugzilla used to be the place where you did that previously, but can't we find a way to link both). This way packagers would have more visibility on the user's needs.
><i> I think one problem Mandriva had was that users refused to believe that:
</I>><i> -Mandriva was open
</I>><i> -Contributors could easily improve the distribution
</I>><i> -Mandriva probably already had most of what they wanted, and if it didn't,
</I>><i> they should do what they can do to help
</I>><i>
</I>><i> For example, many people complained about bugs that get no attention, but *1*
</I>><i> contributor managed to change that perception to some extent. However, if more
</I>><i> people contributed, more bugs would actually be fixed.
</I>><i>
</I>><i> Mandriva the company may have been a barrier to contribution to some, and I
</I>><i> think one of the most important aspects of Mageia is ensuring that
</I>><i> contributors know exactly what happens to their contribution, and knowing that
</I>><i> the financial state of a company does not impact the future availability of
</I>><i> the project to which they contributed.
</I>><i>
</I>
OK, buchan, how do we start ? Shall we put improvements proposals (UI, website, ...) on the wiki, on
<A HREF="http://mageia.org/wiki/doku.php?id=rollingdebate">http://mageia.org/wiki/doku.php?id=rollingdebate</A> ?
><i>
</I>><i> The problem is to make it *easier* for users to get new versions of software,
</I>><i> not to force everyone to upgrade constantly.
</I>
+1
Samuel
</PRE>
<!--endarticle-->
<HR>
<P><UL>
<!--threads-->
<LI>Previous message: <A HREF="000969.html">[Mageia-dev] How will be the realese cycle?
</A></li>
<LI>Next message: <A HREF="000972.html">[Mageia-dev] How will be the realese cycle?
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#971">[ date ]</a>
<a href="thread.html#971">[ thread ]</a>
<a href="subject.html#971">[ subject ]</a>
<a href="author.html#971">[ 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>
|
