<div dir="ltr"><div><div><div>I've updated the <a href="https://docs.google.com/drawings/d/1zovHiCJu0TnlKDuSq4xvRcuhThiR7G3ZdOWobooerdc/edit">document</a> to reflect our discussions.<br><br></div>I will need 2 new droolsjbpm repositories: drools-iwb and kie-iwb-shared; Geoffrey, Mark can you please create these (if you are in agreement)?<br>
<br></div>I have notionally included jBPM on the diagram to illustrate how consistency across KIE could be achieved. I am not restructuring their modules.<br><br></div><div>With kind regards,<br><br></div><div>Mike<br></div>
</div><div class="gmail_extra"><br><br><div class="gmail_quote">On 10 April 2013 20:22, Michael Anstis <span dir="ltr"><<a href="mailto:michael.anstis@gmail.com" target="_blank">michael.anstis@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><p dir="ltr">I was going to use the following Group/Artifact IDs:</p>
<p dir="ltr">org.drools:drools-iwb for Drools editors</p>
<p dir="ltr">org.kie:guvnor for generic Guvnor. </p>
<p dir="ltr">org.kie:kie-iwb-shared for the module for things that both Drools and jBPM editors need.</p>
<p dir="ltr">I'd plan on kie-ide becoming kie-iwb.</p><div class="HOEnZb"><div class="h5">
<div class="gmail_quote">On 10 Apr 2013 19:19, "Mark Proctor" <<a href="mailto:mproctor@codehaus.org" target="_blank">mproctor@codehaus.org</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div style="word-wrap:break-word">Did we decided on an extension, instead of IDE?<div><br></div><div>Mark<br><div><div>On 10 Apr 2013, at 17:11, Michael Anstis <<a href="mailto:michael.anstis@gmail.com" target="_blank">michael.anstis@gmail.com</a>> wrote:</div>
<br><blockquote type="cite"><div dir="ltr">I will be starting the split tomorrow.<br><br></div><div class="gmail_extra"><br><br><div class="gmail_quote">On 2 April 2013 11:23, Mark Proctor <span dir="ltr"><<a href="mailto:mproctor@codehaus.org" target="_blank">mproctor@codehaus.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">studio might be a problem, like suite and platform, it might overlap with something they prefer in the RHT product names.<br>
<br>
We could have "workbench" instead of "work". That would still be under IWE. Integrated Workbench Environment. Or we could drop the Enviornement and have IWB - Integrated WorkBench.<br>
<br>
Mostly I want to make sure we don't chose something that skewer people's thinking that it's only suitable for a specific use case, hence my search for a more generic term. Also that we find a suitably short acronym. This framework can form the basis of a variety of use cases.<br>
<br>
IDE - Integrated Development Environment<br>
IWE - Integrated WorkBench Environment.<br>
IWB - Integrated WorkBench<br>
AWD - Advanced WorkBench<br>
<span><font color="#888888"><br>
Mark<br>
</font></span><div><div><br>
On 2 Apr 2013, at 10:05, Wolfgang Laun <<a href="mailto:wolfgang.laun@gmail.com" target="_blank">wolfgang.laun@gmail.com</a>> wrote:<br>
<br>
> On 02/04/2013, Michael Anstis <<a href="mailto:michael.anstis@gmail.com" target="_blank">michael.anstis@gmail.com</a>> wrote:<br>
>> I'm easy with "W" instead of "D". How about "Integrated Work Studio"<br>
>> instead of "Environment"?<br>
>><br>
><br>
> Seems to me that people have forgotten about the good old work bench.<br>
> Too nutsy-and-boltsy for the brighter future?<br>
><br>
> -W<br>
> _______________________________________________<br>
> rules-dev mailing list<br>
> <a href="mailto:rules-dev@lists.jboss.org" target="_blank">rules-dev@lists.jboss.org</a><br>
> <a href="https://lists.jboss.org/mailman/listinfo/rules-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/rules-dev</a><br>
<br>
<br>
_______________________________________________<br>
rules-dev mailing list<br>
<a href="mailto:rules-dev@lists.jboss.org" target="_blank">rules-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/rules-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/rules-dev</a><br>
</div></div></blockquote></div><br></div>
_______________________________________________<br>rules-dev mailing list<br><a href="mailto:rules-dev@lists.jboss.org" target="_blank">rules-dev@lists.jboss.org</a><br><a href="https://lists.jboss.org/mailman/listinfo/rules-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/rules-dev</a></blockquote>
</div><br></div></div><br>_______________________________________________<br>
rules-dev mailing list<br>
<a href="mailto:rules-dev@lists.jboss.org" target="_blank">rules-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/rules-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/rules-dev</a><br></blockquote></div>
</div></div></blockquote></div><br></div>