<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div bgcolor="#FFFFFF" text="#000000">Does it mean that it will be organized as it is in gitorious?
Meaning:<br>
rock.core (now it's rock.base + rock.toolchain + rock.gui + some
drivers like transformer, frame-helper and few more)<br>
rock.slam<br>
rock.drivers<br>
rock.control<br>
rock.planning<br>
rock.tutorials<br>
...</div></blockquote><div>Yes.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div bgcolor="#FFFFFF" text="#000000"><div class="">Question: Would the new rock package set have an impact in the
folder structure? Meaning frame-helper will be located into
./core/frame-helper instead of the current
./image-processing/frame-helper or perhaps
./core/image-processing/frame-helper<br></div></div></blockquote><div>No. The folder structure stays the same. </div><div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000">
Since there is already a kind of renaming during the migration
(e.g.: rock.core). Question: Do we what to rename some rock package
set (i.e: it would make more sense to have one called
rock.perception which could be the current rock.image-processing +
image stitching + pcl related stuffs, + future things ...) for me it
is +1<br></div></blockquote><div>I think this is a separate matter. Would you see the folders being merged as well ?</div><div><br></div><div>Sylvain</div></div></div></div>