[Mageia-dev] The shiny new Control Center

Sun Sep 30 20:21:52 CEST 2012

On Sat, 29 Sep 2012, Steven Tucker wrote:
+
+> Hi everyone,
+>
+> I have been doing a little work on the proposed control center - mcc2
+>
+> https://wiki.mageia.org/en/Feature:UiAbstraction4mcc
+>
+> and would like to put a couple of questions forward to find some direction.
+>
+>
+> 1/ What should we call it ??
+>
+>         I have been using mcc2 as a working name, however I'm not convinced 
+> this is the right approach. I will soon be uploading the code (been using 
+> my own svn repo up till now), and it would be good to start with the name 
+> it will stick with. Should the name relate to Mageia?, or should it be more 
+> generic?
+
+If it's intended to become a replacement for MCC in the future, maybe
+this could be named something like "mcc-new" or "mcc-libyui" as a
+temporary name in the svn, and renamed to mcc or an other name when
+it's ready to replace the old mcc.
+
+>
+> 2/ What languages should be available for writing modules? (Perl, C++, 
+> python and Ruby are possibilities)
+>
+>         So far mcc2 has been written in Perl (even though I had never 
+> written a line of Perl prior to starting this) so as to make porting 
+> existing modules a matter of just replacing the Ui calls, but I do like the 
+> idea of allowing the modules to be written in more than 1 language to 
+> encourage more contributors who may be turned off by having to learn 
+> another language.
+> Sticking with Perl will make mcc2 core easier, so I may do that initially 
+> regardless. What do you all think?? Is sticking with 1 language preferred 
+> even if it means less contributors, or is the goal to attract as many 
+> module developers as possible?
+
+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.
+
+>
+> 3/ What should the license be?
+>         I would be happy to make it GPL V3, but is there any argument for 
+> something different ?
+>
+> 4/ As an official Mageia project, do I need to sign the copyright over to 
+> Mageia ??
+>         I am more than happy to do so, I would only ask that I get noted 
+> somewhere as the developer, hopefully others will join the developer list 
+> as well.
+
+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.
+
+