What I meant was to - retain the MIT license and not change the license - maintain in our repo. - optionally recognize the provenance (either in NOTICE or in the directory)
On 2/5/13 1:44 PM, "Chip Childers" <chip.child...@sungard.com> wrote: >On Tue, Feb 5, 2013 at 2:34 PM, Chiradeep Vittal ><chiradeep.vit...@citrix.com> wrote: >> Rohit, >> I see that you have followed the code from >> >>https://github.com/jedi4ever/veewee/tree/master/templates/Debian-7.0-b4-i >>38 >> 6-netboot >> >> >> Since that code is under MIT license: >> https://github.com/jedi4ever/veewee/blob/master/License >> >> >> I think we should not check it in or reproduce the MIT license. > >Just to be clear, by "reproduce", are you suggesting that we include >the legal docs for this? (assuming that we want to keep it in the >repo, which I'm personally a +1 on) > >> On 2/5/13 4:24 AM, "Rohit Yadav" <bhais...@apache.org> wrote: >> >>>Just wanted to share some wip, based on the way we can build devcloud >>>and basebox appliance, I've added a template systemvm appliance which >>>can be built using veewee and currently has VMDK disk image format. >>>It's based on Debian b4-i386, has 256MB ram and 2GB HDD. The built >>>vbox disk can be exported as ova, raw disk image, qcow2 etc. >>>I've put it under tools/appliance. Maybe we should move our appliance >>>building code which is in tools/devcloud/src to tools/appliance? Pl. >>>feel free to hack on it, update the README and scripts. >>> >>>We now just need to port the patches/systemvm/debian/buildsystemvm.sh >>>to tools/appliance/definitions/systemvmtemplate/base.sh and add >>>cleanup code. >>> >>> - Install [RVM](https://rvm.io/rvm/install) >>> - Setup paths: export PATH=~/.rvm/bin:$PATH >>> - Install Ruby 1.9.3, if it installed some other version: rvm install >>>1.9.3 >>> >>>cd tools/appliance >>>veewee vbox list >>>(Modify scripts in definitions/systemvmtemplate/ as per needs) >>>veewee vbox build 'systemvmtemplate' >>>veewee vbox up 'systemvmtemplate' # start the box >>> >>>Regards. >> >>
