<div dir="ltr">One other idea:<div><br><div>Instead of keeping rock-base and rock-toolchain separated, I would like to keep the "core" packages into a single rock-core organization. I think it would really make a lot more sense from an organization point of view. The core packages that are currently not in rock-toolchain (aggregator, transformer, vizkit*) could be moved there as well.</div>
</div><div><br></div><div>In addition, I would like to merge the two package sets. We would then have a rock.core package set that defines a rock.base and rock.toolchain metapackages so that people can build without the toolchain.</div>
<div><br></div><div>Thoughts ?</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Thu, May 15, 2014 at 10:41 AM, Sylvain Joyeux <span dir="ltr"><<a href="mailto:bir.sylvain@gmail.com" target="_blank">bir.sylvain@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div>Since we were talking about setting up actual push permissions when moving to github, I've drafted a "process with github" document.</div>
<div><br></div><div>PLEASE REVIEW</div><div><br></div>
<div>It will of course need to be updated as we go with it, but it is important to have a consensus on at least the first version ...</div><div><br></div> <a href="http://rock.opendfki.de/wiki/WikiStart/Standards/RG9" target="_blank">http://rock.opendfki.de/wiki/WikiStart/Standards/RG9</a><span class="HOEnZb"><font color="#888888"><br>
<div><br></div><div>Sylvain</div></font></span></div>
</blockquote></div><br></div>