Back! My family has just recovered from a hellish bout of the flue/ cold.

IIUC, all as have to make sure is that all the code in trunk is

1) All code ASL'ed
2)The code base must contain only ASL or ASL-compatible dependencies
3) License grant complete

1) I do see some code having the AS 2.0 header. I see that others do not, e.g. the VBS scripts. 2) I'm not familiar with the provenance of this code. Can someone provide a little history? What are its dependencies?
3) Depends on 2.

Regards,
Alan

On Dec 12, 2008, at 11:54 AM, Matt Hogstrom wrote:

Great news that the code is flowing.

Note that the tags dir by convention is not changeable. I'm short of time so I'd like to as Alan to comment on the procedures for clearing the code and getting it cleaned up in trunk.

Looking forward to looking at the code.

Thanks


On Dec 12, 2008, at 1:31 PM, Josh Thompson wrote:

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

All,

We've just imported VCL v2.0 code into the ASF subversion repository. We
imported it under

https://svn.apache.org/repos/asf/incubator/vcl/tags/import

and copied from there to tags/VCL-2.0.0 and to trunk.

There are several dependencies that still need to be documented on how to setup a fully operational system (things like setting up an image library, configuration setups to manage various provisioning engines - xcat, vmware,
standalone unix machines - 3rd party utilities and drivers, etc).

We'll be working on that documentation a little next week, but focusing on it
more after the Christmas break.

Josh, Aaron, and Andy
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFJQq4gV/LQcNdtPQMRAkZOAJ9TI2cYI8WArJo/jaD6fdpDYpk09ACeI2CW
lVmivYWWPd3HiRjd9ZGhZ40=
=5tnj
-----END PGP SIGNATURE-----




Reply via email to