I'm ready to contribute some documentation, but I don't know who/how
to create the vcl apache.org wiki. Who can provide this?
Secure Open Systems Initiative
On Nov 14, 2008, at 11:21 AM, Matt Hogstrom wrote:
Alan, et al.
Since you've been through this part a few times what are the next
steps for getting code into the VCL project?
My initial guess is to have one of the NC State folks check it in to
SVN and then we begin changing copyrights, etc.
As a heads up, before checking in code I understand that the VCL
code base uses several different projects we should not be checking
in items that are non-Apache licensed. For the dependencies we
should highlight what they are and where to get them. It would be
really useful if we started documenting some of this on the Wiki so
folks who sniff the project can see what's what, where they can get
involved, etc. Anyone out there interested in helping out with
pulling some of that together?