summaryrefslogtreecommitdiffstats
path: root/zarb-ml/mageia-discuss/20101029/002720.html
diff options
context:
space:
mode:
Diffstat (limited to 'zarb-ml/mageia-discuss/20101029/002720.html')
-rw-r--r--zarb-ml/mageia-discuss/20101029/002720.html101
1 files changed, 101 insertions, 0 deletions
diff --git a/zarb-ml/mageia-discuss/20101029/002720.html b/zarb-ml/mageia-discuss/20101029/002720.html
new file mode 100644
index 000000000..ee56f6d78
--- /dev/null
+++ b/zarb-ml/mageia-discuss/20101029/002720.html
@@ -0,0 +1,101 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
+<HTML>
+ <HEAD>
+ <TITLE> [Mageia-discuss] Mageia-discuss Digest, Vol 2, Issue 119 Package descriptions
+ </TITLE>
+ <LINK REL="Index" HREF="index.html" >
+ <LINK REL="made" HREF="mailto:mageia-discuss%40mageia.org?Subject=Re%3A%20%5BMageia-discuss%5D%20Mageia-discuss%20Digest%2C%20Vol%202%2C%0A%20Issue%20119%20%20Package%20descriptions&In-Reply-To=%3C4CCA36B9.4060607%40laposte.net%3E">
+ <META NAME="robots" CONTENT="index,nofollow">
+ <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
+ <LINK REL="Previous" HREF="002735.html">
+ <LINK REL="Next" HREF="002721.html">
+ </HEAD>
+ <BODY BGCOLOR="#ffffff">
+ <H1>[Mageia-discuss] Mageia-discuss Digest, Vol 2, Issue 119 Package descriptions</H1>
+ <B>andre999</B>
+ <A HREF="mailto:mageia-discuss%40mageia.org?Subject=Re%3A%20%5BMageia-discuss%5D%20Mageia-discuss%20Digest%2C%20Vol%202%2C%0A%20Issue%20119%20%20Package%20descriptions&In-Reply-To=%3C4CCA36B9.4060607%40laposte.net%3E"
+ TITLE="[Mageia-discuss] Mageia-discuss Digest, Vol 2, Issue 119 Package descriptions">andr55 at laposte.net
+ </A><BR>
+ <I>Fri Oct 29 04:51:37 CEST 2010</I>
+ <P><UL>
+ <LI>Previous message: <A HREF="002735.html">[Mageia-discuss] what aabout an automated way of doing it?
+</A></li>
+ <LI>Next message: <A HREF="002721.html">[Mageia-discuss] Suggestions
+</A></li>
+ <LI> <B>Messages sorted by:</B>
+ <a href="date.html#2720">[ date ]</a>
+ <a href="thread.html#2720">[ thread ]</a>
+ <a href="subject.html#2720">[ subject ]</a>
+ <a href="author.html#2720">[ author ]</a>
+ </LI>
+ </UL>
+ <HR>
+<!--beginarticle-->
+<PRE>Ben a &#233;crit :
+&gt;<i> Perhaps the packagers and the backporters (assuming we have any)
+</I>&gt;<i> should have their own digest mailing list. The packagers are very
+</I>&gt;<i> busy but the backporters (community members with the basic knowledge
+</I>&gt;<i> to make an RPM from Cauldron) would be proud and happy to make sense
+</I>&gt;<i> of users package description suggestions and pass on a heads up to the
+</I>&gt;<i> packager if a good suggestion comes along. It would cut down on the
+</I>&gt;<i> noise that a true packager would have to wade through and, once a
+</I>&gt;<i> relationship is developed between a packager and a backporter,
+</I>&gt;<i> 'could' make the packagers job somewhat easier while at the same time
+</I>&gt;<i> (assuming that the backporters are good community members i.e. IRC,
+</I>&gt;<i> newbie and expert mailing list etc.) give users an easily accessible
+</I>&gt;<i> point of contact for regular users. I think users would appreciate
+</I>&gt;<i> this. Backporters would be glad to be a part of both the user and dev
+</I>&gt;<i> community and packagers would be able to participate in the community
+</I>&gt;<i> at the level they feel they are able to without feeling that they are
+</I>&gt;<i> stretched thin.
+</I>&gt;<i> While I'm on this subject. I think it might be a good idea to have
+</I>&gt;<i> assigned backporters for packages or groups of packages. Just a thought.
+</I>&gt;<i> benja22
+</I>
+A backporter is a packager who makes a backport. Making a backport
+could be more complex than making an ordinary package, since the
+packager would have to adjust the dependancies of a more recent package
+to match those available in a previous release. Otherwise installing
+the package could involve considerable other downloads.
+
+Of course it wouldn't be a bad idea, as you suggest, for less
+experienced packagers to focus on improving package descriptions.
+There has already been suggestions of having &quot;master&quot; (experienced) and
+&quot;apprentice&quot; (not-so-experienced) contributors for various functions,
+including packaging.
+This idea would fit well with that.
+
+As far as digests go, if you want to reply to something from a digest,
+it would be better to remove all parts not pertaining to your response,
+including the digest overhead.
+This makes it easier for others to follow your logic.
+(And if you plan to respond to a lot of posts, it might be better to
+subscribe to the usual individual post list.)
+
+- Andr&#233;
+</PRE>
+
+
+
+
+
+<!--endarticle-->
+ <HR>
+ <P><UL>
+ <!--threads-->
+ <LI>Previous message: <A HREF="002735.html">[Mageia-discuss] what aabout an automated way of doing it?
+</A></li>
+ <LI>Next message: <A HREF="002721.html">[Mageia-discuss] Suggestions
+</A></li>
+ <LI> <B>Messages sorted by:</B>
+ <a href="date.html#2720">[ date ]</a>
+ <a href="thread.html#2720">[ thread ]</a>
+ <a href="subject.html#2720">[ subject ]</a>
+ <a href="author.html#2720">[ author ]</a>
+ </LI>
+ </UL>
+
+<hr>
+<a href="https://www.mageia.org/mailman/listinfo/mageia-discuss">More information about the Mageia-discuss
+mailing list</a><br>
+</body></html>