diff options
Diffstat (limited to 'zarb-ml/mageia-dev/20100930/000476.html')
| -rw-r--r-- | zarb-ml/mageia-dev/20100930/000476.html | 115 |
1 files changed, 115 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/20100930/000476.html b/zarb-ml/mageia-dev/20100930/000476.html new file mode 100644 index 000000000..dd58bddaa --- /dev/null +++ b/zarb-ml/mageia-dev/20100930/000476.html @@ -0,0 +1,115 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Mageia-dev] Identifying Target Markets + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Identifying%20Target%20Markets&In-Reply-To=%3C4CA49A15.9030000%40roadrunner.com%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="000467.html"> + <LINK REL="Next" HREF="000478.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] Identifying Target Markets</H1> + <B>Frank Griffin</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Identifying%20Target%20Markets&In-Reply-To=%3C4CA49A15.9030000%40roadrunner.com%3E" + TITLE="[Mageia-dev] Identifying Target Markets">ftg at roadrunner.com + </A><BR> + <I>Thu Sep 30 16:09:25 CEST 2010</I> + <P><UL> + <LI>Previous message: <A HREF="000467.html">[Mageia-dev] Identifying Target Markets +</A></li> + <LI>Next message: <A HREF="000478.html">[Mageia-dev] Identifying Target Markets +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#476">[ date ]</a> + <a href="thread.html#476">[ thread ]</a> + <a href="subject.html#476">[ subject ]</a> + <a href="author.html#476">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>Marc Paré wrote: +><i> Le 2010-09-30 07:21, Graham Lauder a écrit : +</I>>><i> +</I>>><i> The "feel" to me that came from the brainstorming was that Mageia +</I>>><i> could be +</I>>><i> marketed as the "Family Distro". +</I>><i> I think that if you target the software packages that are compatible +</I>><i> with Educational software advocated by educational organizations, we +</I>><i> could make quite large inroads in the adaptability of Mageia. +</I> +I think that these are endeavors for an entity which is exactly what +we've just got done saying Mageia *isn't*, namely a commercial venture. + +Currently, the package inventory of Mandriva is fairly all-inclusive, +and I don't think we should abandon any specific interest group. +Mandriva may have to do this to remain commercially viable - we do not. + +However, let me try to translate your desires into a more technical +objective that would meet the need.. + +Traditionally, the MDV ISO-building process has been complex, not +well-documented, and difficult for anyone outside of MDV to use. I +think Mageia should have a simplified process for package selection that +would enable community users to assemble install ISOs geared to specific +needs, such as those you mention. This should be as easy as +constructing an ISO using k3b or brasero, but would need to be driven by +the RPM information (e.g. requires). Actually, a lot of the RPMDrake +design could be used (if not much of the actual code) to allow a user to +drag and drop Application Categories or specific packages. As with any +CD/DVD burner, the GUI would keep track of whether you were over the +limit for the volume size, so that you could then pare the package list. + +This would allow us to have as many ISOs (or ISO sets) as there are +people interested in maintaining the individual content lists. You +could have a server version, an office desktop version, a games version, +an education version, a power-user version, etc. It would also end the +endless bickering among those who want every media combination from a +stub-based full network install to a fully self-contained multi-DVD or +even Blu-Ray install. You want it, you design it, you press the button +and build it. + +It should not be too difficult to write a utility that goes through a +content list and automatically updates the package names to newer +versions, so maintenance could be minimal. Of course, you'd need to +fire up the build utility to see if there are new package requirements +or if you've exceeded your space constraint. + +These need not all be available on the same release date. Whatever we +decide constitutes a "core" set could form the actual release, with the +others appearing as the interested groups have time to produce them. + +Another idea that fits with this is the concept of a two-tiered install: +create a single general-purpose bare-bones ISO that installs a common +baseline of packages, and create a variety of secondary install ISOs +geared to specific audiences. People would download the common one plus +whichever other(s) they wanted. +</PRE> + + + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="000467.html">[Mageia-dev] Identifying Target Markets +</A></li> + <LI>Next message: <A HREF="000478.html">[Mageia-dev] Identifying Target Markets +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#476">[ date ]</a> + <a href="thread.html#476">[ thread ]</a> + <a href="subject.html#476">[ subject ]</a> + <a href="author.html#476">[ 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> |