<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<br>
<br>
<div class="moz-cite-prefix">On 08/11/2015 02:17 PM, Aline Manera
wrote:<br>
</div>
<blockquote cite="mid:55CA2E39.9050207@linux.vnet.ibm.com"
type="cite">
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
<br>
<br>
<div class="moz-cite-prefix">On 11/08/2015 13:27, Kevin Zander
wrote:<br>
</div>
<blockquote cite="mid:1439310445.3434.5.camel@linux.vnet.ibm.com"
type="cite">
<meta http-equiv="content-type" content="text/html;
charset=windows-1252">
<div>On Tue, 2015-08-11 at 11:47 -0300, Aline Manera wrote:</div>
<blockquote type="cite"> Hi all,<br>
<br>
As we have agreed on moving the Kimchi Host tab to Ginger
community and creating a new plugin (ginger-basic), I want to
list step-by-step what we need to do *on Kimchi side*.<br>
<br>
1) Will we call this new plugin as ginger-basic? Any other
suggestion?<br>
</blockquote>
<div><br>
</div>
<div>I think keeping it as ginger is better. ginger-basic sounds
like there's ginger-advanced (or similar), when there really
isn't anything like that. What we have is just additional
functionality based on your OS flavor. So keeping ginger as
the plugin name, to me, is the easiest. Then all it takes is
looking up your flavor: ginger-[ppc|z|pickled]</div>
</blockquote>
<br>
The final goal of ginger-basic is to handle only host basic
information, host statistics and debug reports.<br>
Those features were identified as common between Kimchi and Ginger
so the need of a new plugin (ginger-basic).<br>
You can check the other thread where we decided to do that in: <a
moz-do-not-send="true" class="moz-txt-link-freetext"
href="http://lists.ovirt.org/pipermail/kimchi-devel/2015-August/011173.html">http://lists.ovirt.org/pipermail/kimchi-devel/2015-August/011173.html</a><br>
<br>
The idea of this email in only clarify what we need to do as we've
already had an agreement in the concept.<br>
<br>
About the plugin name, you can suggest other one which may be
better understood than ginger-basic - as you said it sounds to
there is a ginger-advanced.<br>
</blockquote>
<br>
'ginger-basic' is just a name. We can rename it to ginger-hostinfo,
ginger-basicinfo and the plug-in that will add the current Ginger
features can be named 'ginger-adm', 'ginger-advanced' ....<br>
<br>
We can discuss how each plug-in will be named (a discussion which
belongs to <a class="moz-txt-link-abbreviated" href="mailto:ginger-dev-list@nongnu.org">ginger-dev-list@nongnu.org</a> ) but, in my opinion, agreeing
with the design is more important ATM.<br>
<br>
<blockquote cite="mid:55CA2E39.9050207@linux.vnet.ibm.com"
type="cite"> <br>
<blockquote cite="mid:1439310445.3434.5.camel@linux.vnet.ibm.com"
type="cite">
<div><br>
</div>
<blockquote type="cite"> <br>
2) Create the new plugin structure into wok branch, ie, create
a directory named ginger-basic (?) and all it is needed to
launch it as a wok plugin, including building and packaging
details.<br>
In this first moment, the entire Host tab will be part of
the ginger-basic - just to move the discussion as soon as
possible to Ginger community.<br>
<br>
3) Add ginger-basic plugin as a Kimchi dependency.<br>
<br>
Once we have those items done, I will create a new repository
for ginger-basic under kimchi-project organization in Github.<br>
After that, the discussion *will be moved to Ginger
community*, ie, all patches and discussion must be sent to the
Ginger mailing list (<a moz-do-not-send="true"
href="https://lists.nongnu.org/mailman/listinfo/ginger-dev-list"
style="box-sizing: border-box; color: rgb(64, 120, 192);
text-decoration: none; font-family: 'Helvetica Neue',
Helvetica, 'Segoe UI', Arial, freesans, sans-serif;
font-size: 16px; font-style: normal; font-variant: normal;
font-weight: normal; letter-spacing: normal; line-height:
20.4799995422363px; orphans: auto; text-align: left;
text-indent: 0px; text-transform: none; white-space: normal;
widows: 1; word-spacing: 0px; -webkit-text-stroke-width:
0px; background-color: rgb(255, 255, 255);">https://lists.nongnu.org/mailman/listinfo/ginger-dev-list</a><span
style="color: rgb(51, 51, 51); font-family: 'Helvetica
Neue', Helvetica, 'Segoe UI', Arial, freesans, sans-serif;
font-size: 16px; font-style: normal; font-variant: normal;
font-weight: normal; letter-spacing: normal; line-height:
20.4799995422363px; orphans: auto; text-align: left;
text-indent: 0px; text-transform: none; white-space: normal;
widows: 1; word-spacing: 0px; -webkit-text-stroke-width:
0px; display: inline !important; float: none;
background-color: rgb(255, 255, 255);"><span
class="Apple-converted-space"></span></span>)<br>
<br>
I have sent to Ginger community the next steps to be done
there. Please, check: "[Ginger-dev-list] [RFC] Inheriting
Kimchi's Host tab"<br>
<br>
Let me know what you think about that.<br>
<br>
Regards,<br>
Aline Manera<br>
<br>
<br>
<pre>_______________________________________________
Kimchi-devel mailing list
<a moz-do-not-send="true" href="mailto:Kimchi-devel@ovirt.org">Kimchi-devel@ovirt.org</a>
<a moz-do-not-send="true" href="http://lists.ovirt.org/mailman/listinfo/kimchi-devel">http://lists.ovirt.org/mailman/listinfo/kimchi-devel</a>
</pre>
</blockquote>
</blockquote>
<br>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Kimchi-devel mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Kimchi-devel@ovirt.org">Kimchi-devel@ovirt.org</a>
<a class="moz-txt-link-freetext" href="http://lists.ovirt.org/mailman/listinfo/kimchi-devel">http://lists.ovirt.org/mailman/listinfo/kimchi-devel</a>
</pre>
</blockquote>
<br>
</body>
</html>