summaryrefslogtreecommitdiffstats
path: root/zarb-ml/mageia-dev/2012-September/019060.html
diff options
context:
space:
mode:
Diffstat (limited to 'zarb-ml/mageia-dev/2012-September/019060.html')
-rw-r--r--zarb-ml/mageia-dev/2012-September/019060.html117
1 files changed, 117 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/2012-September/019060.html b/zarb-ml/mageia-dev/2012-September/019060.html
new file mode 100644
index 000000000..3e05fa163
--- /dev/null
+++ b/zarb-ml/mageia-dev/2012-September/019060.html
@@ -0,0 +1,117 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
+<HTML>
+ <HEAD>
+ <TITLE> [Mageia-dev] The shiny new Control Center
+ </TITLE>
+ <LINK REL="Index" HREF="index.html" >
+ <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20The%20shiny%20new%20Control%20Center&In-Reply-To=%3C20120930182152.GY21938%40mars-attacks.org%3E">
+ <META NAME="robots" CONTENT="index,nofollow">
+ <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
+ <LINK REL="Previous" HREF="019048.html">
+ <LINK REL="Next" HREF="019032.html">
+ </HEAD>
+ <BODY BGCOLOR="#ffffff">
+ <H1>[Mageia-dev] The shiny new Control Center</H1>
+ <B>nicolas vigier</B>
+ <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20The%20shiny%20new%20Control%20Center&In-Reply-To=%3C20120930182152.GY21938%40mars-attacks.org%3E"
+ TITLE="[Mageia-dev] The shiny new Control Center">boklm at mars-attacks.org
+ </A><BR>
+ <I>Sun Sep 30 20:21:52 CEST 2012</I>
+ <P><UL>
+ <LI>Previous message: <A HREF="019048.html">[Mageia-dev] The shiny new Control Center
+</A></li>
+ <LI>Next message: <A HREF="019032.html">[Mageia-dev] build problem
+</A></li>
+ <LI> <B>Messages sorted by:</B>
+ <a href="date.html#19060">[ date ]</a>
+ <a href="thread.html#19060">[ thread ]</a>
+ <a href="subject.html#19060">[ subject ]</a>
+ <a href="author.html#19060">[ author ]</a>
+ </LI>
+ </UL>
+ <HR>
+<!--beginarticle-->
+<PRE>On Sat, 29 Sep 2012, Steven Tucker wrote:
+
+&gt;<i> Hi everyone,
+</I>&gt;<i>
+</I>&gt;<i> I have been doing a little work on the proposed control center - mcc2
+</I>&gt;<i>
+</I>&gt;<i> <A HREF="https://wiki.mageia.org/en/Feature:UiAbstraction4mcc">https://wiki.mageia.org/en/Feature:UiAbstraction4mcc</A>
+</I>&gt;<i>
+</I>&gt;<i> and would like to put a couple of questions forward to find some direction.
+</I>&gt;<i>
+</I>&gt;<i>
+</I>&gt;<i> 1/ What should we call it ??
+</I>&gt;<i>
+</I>&gt;<i> I have been using mcc2 as a working name, however I'm not convinced
+</I>&gt;<i> this is the right approach. I will soon be uploading the code (been using
+</I>&gt;<i> my own svn repo up till now), and it would be good to start with the name
+</I>&gt;<i> it will stick with. Should the name relate to Mageia?, or should it be more
+</I>&gt;<i> generic?
+</I>
+If it's intended to become a replacement for MCC in the future, maybe
+this could be named something like &quot;mcc-new&quot; or &quot;mcc-libyui&quot; as a
+temporary name in the svn, and renamed to mcc or an other name when
+it's ready to replace the old mcc.
+
+&gt;<i>
+</I>&gt;<i> 2/ What languages should be available for writing modules? (Perl, C++,
+</I>&gt;<i> python and Ruby are possibilities)
+</I>&gt;<i>
+</I>&gt;<i> So far mcc2 has been written in Perl (even though I had never
+</I>&gt;<i> written a line of Perl prior to starting this) so as to make porting
+</I>&gt;<i> existing modules a matter of just replacing the Ui calls, but I do like the
+</I>&gt;<i> idea of allowing the modules to be written in more than 1 language to
+</I>&gt;<i> encourage more contributors who may be turned off by having to learn
+</I>&gt;<i> another language.
+</I>&gt;<i> Sticking with Perl will make mcc2 core easier, so I may do that initially
+</I>&gt;<i> regardless. What do you all think?? Is sticking with 1 language preferred
+</I>&gt;<i> even if it means less contributors, or is the goal to attract as many
+</I>&gt;<i> module developers as possible?
+</I>
+Do you plan to keep compatibility with current mcc modules ?
+The modules are also used in the installer. To avoid maintaining two
+versions of the modules, the same modules should work in the installer
+and mcc.
+
+&gt;<i>
+</I>&gt;<i> 3/ What should the license be?
+</I>&gt;<i> I would be happy to make it GPL V3, but is there any argument for
+</I>&gt;<i> something different ?
+</I>&gt;<i>
+</I>&gt;<i> 4/ As an official Mageia project, do I need to sign the copyright over to
+</I>&gt;<i> Mageia ??
+</I>&gt;<i> I am more than happy to do so, I would only ask that I get noted
+</I>&gt;<i> somewhere as the developer, hopefully others will join the developer list
+</I>&gt;<i> as well.
+</I>
+I think you can keep the copyright. Releasing the software under an open
+source license should be enough. Mageia does not own copyright of the
+other softwares.
+
+</PRE>
+
+
+
+
+<!--endarticle-->
+ <HR>
+ <P><UL>
+ <!--threads-->
+ <LI>Previous message: <A HREF="019048.html">[Mageia-dev] The shiny new Control Center
+</A></li>
+ <LI>Next message: <A HREF="019032.html">[Mageia-dev] build problem
+</A></li>
+ <LI> <B>Messages sorted by:</B>
+ <a href="date.html#19060">[ date ]</a>
+ <a href="thread.html#19060">[ thread ]</a>
+ <a href="subject.html#19060">[ subject ]</a>
+ <a href="author.html#19060">[ 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>