We definitely needed something like that, great! Do you think it would make sense to split the instructions into two parts? Something like:
1. Prepare your environment to make it work with our dev infra - "the stuff you won't need to do in the future" 2. Build a module - "The actual workflow" I guess might make it easier for people to understand it/see it less complicated more quickly. And then we could even provide a Vagrantfile with everything from the first part prepared. Does it make sense? On Tuesday, 30 August 2016, Ralph Bean <[email protected]> wrote: > Hi all! > > First, check out the logs/minutes from today's Modularity WG meeting: > > https://meetbot.fedoraproject.org/teams/modularity_wg/ > modularity_wg.2016-08-30-15.00.html > > We identified that we needed a doc on how to fool around with our > prototype build infrastructure (partly staging, partly a dev > environment). We wrote this up which should help if people want to > try it out: > > https://fedoraproject.org/wiki/Modularity/HowToBuildAModuleInStaging > > Let us know in #fedora-modularity if/when something about it doesn't > work and we'll take a look together. :) > > Cheers- > -Ralph > -- Adam Šamalík --------------------------- Associate Software Engineer Red Hat
-- devel mailing list [email protected] https://lists.fedoraproject.org/admin/lists/[email protected]
