-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Wednesday October 28, 2009, Alan D. Cabrera wrote:
> >> ./managementnode/lib/VCL/Module/Provisioning/esxthin.pm: Brian > >> Bouterse <bmbou...@ncsu.edu> I don't have a preference about allowing author tags. I'd prefer not to /require/ them. I don't use them personally because I don't like having to keep up with who modified the code and when. > >> ./web/.ht-inc/conf.php:$ENABLE_ITECSAUTH = 0; // use ITECS > >> accounts (also called "Non-NCSU" accounts) I already explained this one. > >> ./web/.ht-inc/conf.php: "URL" => > >> "https://federation.northcarolina.edu/wayf/wayf_framed.php?fed=FED_SHIB_ > >>UNC _DEV&version=dropdown&entityID=https%3A%2F%2Fvcl.ncsu.edu%2Fsp > >> %2Fshibboleth& > >> return=http%3A%2F%2Fvcl.ncsu.edu%2FShibboleth.sso%2FDS%3FSAMLDS > >> %3D1%26target > >> %3Dhttp%3A%2F%2Fvcl.ncsu.edu%2Fscheduling%2Fshibauth%2F ", I left it in there as an example of how Shibboleth authentication would be added in. It is commented out, but I can completely remove it if you think it is confusing. In a previous email, Kevan said he was okay with leaving it in there. > >> ./web/.ht-inc/xmlrpc_example.php: $file = > >> file_get_contents("https://vcl.ncsu.edu/scheduling/index.php?mode=xmlrpc > >>cal l ", false, $context); > >> ./web/.ht-inc/xmlrpcdocs/xmlrpc__example_8php-example.html: > >> $file = file_get_contents(<span > >> class="stringliteral">"https://vcl.ncsu.edu/scheduling/index.php?mode=xm > >>lrp ccall "</span>, <span class="keyword">false</span>, $context); > >> ./web/.ht-inc/xmlrpcdocs/xmlrpcWrappers_8php.html: example: > >> myuse...@ncsu<br> > >> ./web/.ht-inc/xmlrpcWrappers.php: * example: myuser...@ncsu\n xmlrpc_example.php only exists for doxygen to generate xmlrpc__example8php-example.html, which is documentation on how to use the XMLRPC API, as is xmlrpcWrappers_8php.html. The reference in xmlrpcWrappers.php is from inline documentation used to generate xmlrpcWrappers_8php.html. > >> I'm not sure if we, ASF VCL, has a policy about authors being in > >> files. Some keep them in, others feel that it detracts from the > >> community aspect of the project and after a while the distinction > >> gets > >> blurred after many people have hand their hands in the code. Up to > >> you guys. In any case I think these references to ncsu might need to > >> be scrubbed. > >> > >> What is ITECS? > > > > ITECS is a department at NCSU. I wrote a web based accounts system > > for them > > some time ago that could be used with any php web app. In the > > future, I'll > > be rolling that system in to Apache VCL. It is disabled in the code > > right > > now. I'd prefer not to remove all references to it, delaying this > > release, > > and then turn around and add it back (with appropriately renamed > > variables) > > in an upcoming release. > > I think that might fly. > > What about the ncsu references? Explained inline above. > Also, what does the group feel about having author tags? My thoughts are expressed inline above. > >> Kevan makes a few points: > >>> * Instructions on installation, prereqs, etc should be clear that a > >>> user must determine the licensing of the technologies that you are > >>> requiring/referring to/downloading. It's not clear to me if that > >>> information is being conveyed. Clearly, you require GPL, LGPL, and > >>> microsoft proprietary artifacts. Wondering how much of this needs to > >>> flow through legal-discuss... Prolly Alan and Matt have thought > >>> about this already. > >> > >> I was not aware of this. We need to get a full laundry list of > >> what's > >> require and why and probably vet it w. legal-disc...@. I agree w/ > >> Kevan we should be upfront and in your face about these requirements. > >> IIUC, maybe it belongs in the NOTICE file? > > The list will have an opinion on this if it's not already written > somewhere. > > >>> * managementnode/bin/install_perl_libs.pl will download install > >>> libraries, IIUC. What are the licenses of these artifacts? Users > >>> need to be made aware of what you are doing for them... > >> > >> Agreed. > > My understanding that this is being taken care of and will most likely > be merged w/ the effort above. I'm composing a message right now to explain the situation and ask advice from the legal-discuss list. Josh - -- - ------------------------------- Josh Thompson Systems Programmer Advanced Computing | VCL Developer North Carolina State University josh_thomp...@ncsu.edu 919-515-5323 my GPG/PGP key can be found at pgp.mit.edu -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFK6a0vV/LQcNdtPQMRArlMAJ9/80YatIJmd2suWG6/rnZ8mDf3TwCeNmPx RIwZNbZCNtF2YkiHP65HQx0= =oIth -----END PGP SIGNATURE-----