[Rock-dev] Draft of Github-based development process [IMPORTANT]

[Sylvain Joyeux]

One other idea:

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.

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.

Thoughts ?


On Thu, May 15, 2014 at 10:41 AM, Sylvain Joyeux <bir.sylvain at gmail.com>wrote:

> Since we were talking about setting up actual push permissions when moving
> to github, I've drafted a "process with github" document.
>
> PLEASE REVIEW
>
> 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 ...
>
>    http://rock.opendfki.de/wiki/WikiStart/Standards/RG9
>
> Sylvain
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.dfki.de/pipermail/rock-dev/attachments/20140522/449824a3/attachment.htm