Re: [VOTE] Apache VCL Ready to Graduate
+1 Whoot! Regards, Alan On May 10, 2012, at 8:01 AM, Andy Kurth wrote: This vote is to determine if the Apache VCL community believes the project is ready to graduate from the incubator to a top level project. Everyone in the community is encouraged to vote. Please reply expressing one of the following: +1 : yes, Apache VCL is ready to graduate to a top level project 0 : ambivalent -1 : no, Apache VCL is not ready to graduate to a top level project This vote will be closed on Tuesday, May 15, 2012 at 5:00 pm EST. If this vote passes, the community will draft a board resolution and present it to the IPMC. Thank You, Andy Kurth
Re: [DISCUSS] Graduation
On May 1, 2012, at 9:44 AM, Andy Kurth wrote: This thread is to discuss whether the Apache VCL community feels that this incubating project is ready to proceed with the process to graduate to a top level ASF project. There are several requirements which must be met and steps completed in order to graduate. This discussion thread is the first step towards graduation. Please review the following pages. http://incubator.apache.org/guides/graduation.html http://incubator.apache.org/incubation/Incubation_Policy.html#Graduating+from+the+Incubator There are many items described in the ASF graduation documentation which we have obviously satisfied (create a release, etc). The following are issues that I feel either need to be addressed, would be concerned about regarding board/mentor approval, or have been brought up before. Please share your thoughts. Also, please review the ASF graduation documentation and bring up anything else which might be a concern. Status File: (https://svn.apache.org/repos/asf/incubator/public/trunk/content/projects/vcl.xml) This is not up to date and is missing information. Previous board reports need to be added. News items need to be added containing the string new committer. Doing this will cause the numberCommittersNew column on the Status of the Clutch page to turn green (http://incubator.apache.org/clutch.html). Also, the list of commiters in the status file and project page hasn't changed since Apache VCL started. The new committers obviously need to be added. I'm not sure how the original list was decided upon, but I feel several names should be removed since they have not contributed any code and some have not been involved in the community at all. I think the list should be Aaron Coburn, David Hutchins, Andy Kurth, James O'Dell, Aaron Peeler, Josh Thompson. Also, Brian Bouterse contributed some code a while ago. I'm not sure if he is still interested in being a committer. I can update this tomorrow. Diversity: ASF requirement: The project is not highly dependent on any single contributor (there are at least 3 legally independent committers and there is no single company or entity that is vital to the success of the project). This issue has been raised before. I feel we meet this requirement and that the community is generally diverse, can govern itself, and be self-sufficient. I agree. Website: This is not necessarily a requirement for graduation but I feel that it should be addressed prior to graduation. Our website/documentation is pretty rough and really should be redesigned. I'm guessing the board members will look at it prior to voting. In addition, there will likely be a press release if/when we graduate and website views will spike. This shouldn't hold up the graduation process, but I would like agreement that this should be completed by graduation. Up to you guys. I support this project's graduation. Regards, Alan
Re: VCL board report due on Nov 9th
We may still be able to squeak in. Any takers? Regards, Alan On Nov 3, 2011, at 5:43 AM, Josh Thompson wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 The November board report is due this coming Wednesday. It is really pretty easy to do and a simple way to get a little more involved with the VCL community. The following page explains what needs to be done to create it, including explaining how to just copy the last one so that you can just make a few changes to it instead of having to write it from scratch. https://cwiki.apache.org/confluence/display/VCL/Board+Reports Josh - -- - --- Josh Thompson VCL Developer North Carolina State University my GPG/PGP key can be found at pgp.mit.edu -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.17 (GNU/Linux) iEYEARECAAYFAk6yjGkACgkQV/LQcNdtPQPiUACfbPP92dHrvBiYH32EyzbIprTW U5sAnieYhlSUySnfhmVMxT0G3GbfbG7y =4H51 -END PGP SIGNATURE-
Re: Licensing aspects of a VCL project
On Jun 2, 2010, at 12:09 PM, Woods, David M. Dr. wrote: Hi, I've asked about this before, and didn't get a lot of response, but licensing issues are turning out to be a major issue in our VCL pilot project, so I would be interested in talking to anyone who can share licensing details of software that is being provided to students in a VCL environment. We are finding that software vendors understand the VCL concept. In general, licenses allow the software to run on university owned machines, so it's legal to run in a VM. Where some vendors have problems is providing access to this software from student (or any machines not owned by the university) machines. Some vendors don't have a problem with this, but some tell us that this is not allowed. It doesn't make a lot of sense to me - it's not a problem for a student to access the VCL from a university owned PC in a lab, but is a problem for the student to access the VCL from a machine owned by a student? The vendors would be happy to sell us additional licenses to allow us to allow students to access the VCL from the student’s personal machine, but this would add a lot to the cost of a full scale VCL implementation, so we would like to learn more about licensing at other places that have implemented a VCL to check with what vendors are telling us. If you have a licensing manager who would be willing to talk to our licensing manager, please send me contact info. Do I understand correctly when I say that you do not have a licensing problem installing the core VCL, VCL-2.1 as distributed from the Apache Software Foundation, but have discovered licensing issues w/ subsequent vendor specific add-ons? Regards, Alan
