You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@vcl.apache.org by Josh Thompson <jo...@ncsu.edu> on 2009/10/21 19:27:34 UTC
[VOTE] release VCL 2.1
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
I created a release artifact based off of trunk. I copied trunk to a tag
under the tags area of the repo that is named release-2.1-RC1:
http://svn.apache.org/repos/asf/incubator/vcl/tags/release-2.1-RC1/
The artifact is an export from that tag. The artifact, MD5 and SHA1 sums, and
my GPG signature of it are available from my space on people.a.o:
http://people.apache.org/~jfthomps/apache-VCL-2.1-RC1-incubating/
The list of resolved JIRA issues associated with this release can be found on
the VCL 2.1 release page:
http://cwiki.apache.org/VCL/vcl-21-unreleased.html#VCL2.1%2528unreleased%2529-ChangeLog
Installation instructions are on the Confluence site and in the INSTALLATION
file included in the artifact.
Aaron, Andy, and I have completed a test install of all parts and were able to
successfully create and capture a base image.
Please vote to publish this release.
(Question to mentors: Do I need to vote in a successive email in this thread,
or is this post an implicit vote?)
- --
- -------------------------------
Josh Thompson
Systems Programmer
Advanced Computing | VCL Developer
North Carolina State University
Josh_Thompson@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)
iD8DBQFK30SGV/LQcNdtPQMRAhk8AJsGL4m0J1v0DC7U9Yyc31TIRjKXFACdE0bM
827++1u0XH9c2GqKP/pAE80=
=QrMV
-----END PGP SIGNATURE-----
Re: [VOTE] release VCL 2.1
Posted by "Alan D. Cabrera" <li...@toolazydogs.com>.
As a general statement, I'm pretty sure that if a section of our code
required an artifact that was incompatible with AL 2.0 then we would
have a problem. We can double check that on the legal-discuss@ list.
For packages that optionally require an artifact that was incompatible
with AL 2.0 I must confess that I'm not sure.
I think we should double check both on the legal-discuss@ list. It
would be helpful to have a list of packages, their license, and if
they are required or not.
Regards,
Alan
On Oct 27, 2009, at 9:30 AM, Aaron Peeler wrote:
> I would like to highlight that we're not packaging/redistributing
> these artifacts and in some cases they are optional depending on how
> the Apache VCL code is being used. The perl, perl modules, mysql and
> php requirements to get VCL operational are listed in both the
> INSTALLATION and README files.
>
> For example the windows drivers are only necessary if using xCAT to
> provision bare-metal Windows installations, and even then it is
> dependent on the type of hardware one is trying to install. So these
> windows OS drivers can vary greatly.
>
> Aaron
>
>
> --On October 27, 2009 8:59:05 AM -0700 "Alan D. Cabrera" <list@toolazydogs.com
> > wrote:
>
>>> * 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-discuss@. I agree w/
>> Kevan
>> we should be upfront and in your face about these requirements.
>> IIUC,
>> maybe it belongs in the NOTICE file?
>>
>>> * 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...
>
>
>
> Aaron Peeler
> OIT Advanced Computing
> College of Engineering-NCSU
> 919.513.4571
> http://vcl.ncsu.edu
Re: [VOTE] release VCL 2.1
Posted by Aaron Peeler <aa...@ncsu.edu>.
I would like to highlight that we're not packaging/redistributing these
artifacts and in some cases they are optional depending on how the Apache
VCL code is being used. The perl, perl modules, mysql and php requirements
to get VCL operational are listed in both the INSTALLATION and README
files.
For example the windows drivers are only necessary if using xCAT to
provision bare-metal Windows installations, and even then it is dependent
on the type of hardware one is trying to install. So these windows OS
drivers can vary greatly.
Aaron
--On October 27, 2009 8:59:05 AM -0700 "Alan D. Cabrera"
<li...@toolazydogs.com> wrote:
>> * 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-discuss@. I agree w/ Kevan
> we should be upfront and in your face about these requirements. IIUC,
> maybe it belongs in the NOTICE file?
>
>> * 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...
Aaron Peeler
OIT Advanced Computing
College of Engineering-NCSU
919.513.4571
http://vcl.ncsu.edu
Re: [VOTE] release VCL 2.1
Posted by Sean Dilda <se...@duke.edu>.
Alan D. Cabrera wrote:
>
> I did a search through files for ncsu and found:
>
Should direct references to NCSU and NCSU-specific code be considered
something to remove (for the longterm, not necessarily for this
release)? If so, there are some I've run across that I'd be happy to
bring up to the list. However, I'd like to make sure there's community
interest in changing those before bringing them up to the list.
Thanks,
Sean
Re: [VOTE] release VCL 2.1
Posted by Josh Thompson <jo...@ncsu.edu>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Wednesday October 28, 2009, Alan D. Cabrera wrote:
> >> ./managementnode/lib/VCL/Module/Provisioning/esxthin.pm: Brian
> >> Bouterse <bm...@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:
> >> myuserid@NCSU<br>
> >> ./web/.ht-inc/xmlrpcWrappers.php: * example: myuserid\@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-discuss@. 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_Thompson@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-----
Re: [VOTE] release VCL 2.1
Posted by "Alan D. Cabrera" <li...@toolazydogs.com>.
On Oct 27, 2009, at 10:34 AM, Josh Thompson wrote:
>> The directory of the untared release is release-2.1-RC1. I would
>> prefer apache-VCL-2.1-RC1-incubating.
>
> We'll do this again with an RC2. I'll name the directory
> apache-VCL-2.1-RC2-incubating for that one. However, I'll wait on
> closing
> this thread with a [RESULT] email until we've finished vetting what
> needs to
> change to get a passing vote.
>
>> I did a search through files for ncsu and found:
>>
>> acabrera-mn:release-2.1-RC1 acabrera$ find . -type f -exec grep -iH
>> NCSU {} \;
>> ./managementnode/lib/VCL/Module/Provisioning/esxthin.pm: Brian
>> Bouterse <bm...@ncsu.edu>
>> ./web/.ht-inc/conf.php:$ENABLE_ITECSAUTH = 0; // use ITECS
>> accounts (also called "Non-NCSU" accounts)
>> ./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 ",
>> ./web/.ht-inc/xmlrpc_example.php: $file =
>> file_get_contents("https://vcl.ncsu.edu/scheduling/index.php?mode=xmlrpccal
>> 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=xmlrp
>> ccall "</span>, <span class="keyword">false</span>, $context);
>> ./web/.ht-inc/xmlrpcdocs/xmlrpcWrappers_8php.html: example:
>> myuserid@NCSU<br>
>> ./web/.ht-inc/xmlrpcWrappers.php: * example: myuserid\@NCSU\n
>>
>> 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?
Also, what does the group feel about having author tags?
>
>> 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-discuss@. 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.
Regards,
Alan
Re: [VOTE] release VCL 2.1
Posted by Josh Thompson <jo...@ncsu.edu>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
> On Oct 21, 2009, at 10:27 AM, Josh Thompson wrote:
> > (Question to mentors: Do I need to vote in a successive email in
> > this thread,
> > or is this post an implicit vote?)
>
> A different email is the custom.
I added a note to the release procedures page that the release manager should
vote in a different email than the one calling for the vote.
> The directory of the untared release is release-2.1-RC1. I would
> prefer apache-VCL-2.1-RC1-incubating.
We'll do this again with an RC2. I'll name the directory
apache-VCL-2.1-RC2-incubating for that one. However, I'll wait on closing
this thread with a [RESULT] email until we've finished vetting what needs to
change to get a passing vote.
> I did a search through files for ncsu and found:
>
> acabrera-mn:release-2.1-RC1 acabrera$ find . -type f -exec grep -iH
> NCSU {} \;
> ./managementnode/lib/VCL/Module/Provisioning/esxthin.pm: Brian
> Bouterse <bm...@ncsu.edu>
> ./web/.ht-inc/conf.php:$ENABLE_ITECSAUTH = 0; // use ITECS
> accounts (also called "Non-NCSU" accounts)
> ./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 ",
> ./web/.ht-inc/xmlrpc_example.php: $file =
> file_get_contents("https://vcl.ncsu.edu/scheduling/index.php?mode=xmlrpccal
>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=xmlrp
>ccall "</span>, <span class="keyword">false</span>, $context);
> ./web/.ht-inc/xmlrpcdocs/xmlrpcWrappers_8php.html: example:
> myuserid@NCSU<br>
> ./web/.ht-inc/xmlrpcWrappers.php: * example: myuserid\@NCSU\n
>
> 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.
> 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-discuss@. I agree w/
> Kevan we should be upfront and in your face about these requirements.
> IIUC, maybe it belongs in the NOTICE file?
>
> > * 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.
>
>
> Regards,
> Alan
- --
- -------------------------------
Josh Thompson
Systems Programmer
Advanced Computing | VCL Developer
North Carolina State University
Josh_Thompson@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)
iD8DBQFK5y8TV/LQcNdtPQMRAiTOAJ4h1d1HdeXnO5RwXyn8WuXPCH9ajACfTlti
dntYJoIoBw+ahC3jHCijdkg=
=kMlu
-----END PGP SIGNATURE-----
Re: [VOTE] release VCL 2.1
Posted by Aaron Peeler <aa...@ncsu.edu>.
Yes - I think any NCSU references will need to be removed.
In addition to posting here. If you would also create a jira issue.
Aaron
--On November 2, 2009 9:26:55 PM -0500 Sean Dilda <se...@duke.edu> wrote:
> Alan D. Cabrera wrote:
>>
>> I did a search through files for ncsu and found:
>>
>
> Should direct references to NCSU and NCSU-specific code be considered
> something to remove (for the longterm, not necessarily for this release)?
> If so, there are some I've run across that I'd be happy to bring up to
> the list. However, I'd like to make sure there's community interest in
> changing those before bringing them up to the list.
>
>
> Thanks,
>
>
> Sean
Aaron Peeler
OIT Advanced Computing
College of Engineering-NCSU
919.513.4571
http://vcl.ncsu.edu
Re: [VOTE] release VCL 2.1
Posted by "Alan D. Cabrera" <li...@toolazydogs.com>.
I initially sent this to Josh.
Regards,
Alan
On Oct 21, 2009, at 10:27 AM, Josh Thompson wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> I created a release artifact based off of trunk. I copied trunk to
> a tag
> under the tags area of the repo that is named release-2.1-RC1:
>
> http://svn.apache.org/repos/asf/incubator/vcl/tags/release-2.1-RC1/
>
> The artifact is an export from that tag. The artifact, MD5 and SHA1
> sums, and
> my GPG signature of it are available from my space on people.a.o:
>
> http://people.apache.org/~jfthomps/apache-VCL-2.1-RC1-incubating/
>
> The list of resolved JIRA issues associated with this release can be
> found on
> the VCL 2.1 release page:
>
> http://cwiki.apache.org/VCL/vcl-21-unreleased.html#VCL2.1%2528unreleased%2529-ChangeLog
>
> Installation instructions are on the Confluence site and in the
> INSTALLATION
> file included in the artifact.
>
> Aaron, Andy, and I have completed a test install of all parts and
> were able to
> successfully create and capture a base image.
>
> Please vote to publish this release.
>
> (Question to mentors: Do I need to vote in a successive email in
> this thread,
> or is this post an implicit vote?)
A different email is the custom.
The directory of the untared release is release-2.1-RC1. I would
prefer apache-VCL-2.1-RC1-incubating.
I did a search through files for ncsu and found:
acabrera-mn:release-2.1-RC1 acabrera$ find . -type f -exec grep -iH
NCSU {} \;
./managementnode/lib/VCL/Module/Provisioning/esxthin.pm: Brian
Bouterse <bm...@ncsu.edu>
./web/.ht-inc/conf.php:$ENABLE_ITECSAUTH = 0; // use ITECS
accounts (also called "Non-NCSU" accounts)
./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
",
./web/.ht-inc/xmlrpc_example.php: $file = file_get_contents("https://vcl.ncsu.edu/scheduling/index.php?mode=xmlrpccall
", 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=xmlrpccall
"</span>, <span class="keyword">false</span>, $context);
./web/.ht-inc/xmlrpcdocs/xmlrpcWrappers_8php.html: example:
myuserid@NCSU<br>
./web/.ht-inc/xmlrpcWrappers.php: * example: myuserid\@NCSU\n
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?
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-discuss@. I agree w/
Kevan we should be upfront and in your face about these requirements.
IIUC, maybe it belongs in the NOTICE file?
> * 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.
Regards,
Alan
Re: [VOTE] release VCL 2.1
Posted by Josh Thompson <jo...@ncsu.edu>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
That's fine. Several of us were at a conference all day today and will be
tomorrow as well anyway.
Josh
On Thu October 22 2009 12:57:29 pm Alan D. Cabrera wrote:
> I don't have time to double check this release until this weekend.
> Normally votes are 72 hours. I request that we don't count the votes
> until Monday, if that's ok.
>
>
> Regards,
> Alan
>
> On Oct 21, 2009, at 10:27 AM, Josh Thompson wrote:
> > -----BEGIN PGP SIGNED MESSAGE-----
> > Hash: SHA1
> >
> > I created a release artifact based off of trunk. I copied trunk to
> > a tag
> > under the tags area of the repo that is named release-2.1-RC1:
> >
> > http://svn.apache.org/repos/asf/incubator/vcl/tags/release-2.1-RC1/
> >
> > The artifact is an export from that tag. The artifact, MD5 and SHA1
> > sums, and
> > my GPG signature of it are available from my space on people.a.o:
> >
> > http://people.apache.org/~jfthomps/apache-VCL-2.1-RC1-incubating/
> >
> > The list of resolved JIRA issues associated with this release can be
> > found on
> > the VCL 2.1 release page:
> >
> > http://cwiki.apache.org/VCL/vcl-21-unreleased.html#VCL2.1%2528unreleased%
> >2529-ChangeLog
> >
> > Installation instructions are on the Confluence site and in the
> > INSTALLATION
> > file included in the artifact.
> >
> > Aaron, Andy, and I have completed a test install of all parts and
> > were able to
> > successfully create and capture a base image.
> >
> > Please vote to publish this release.
> >
> > (Question to mentors: Do I need to vote in a successive email in
> > this thread,
> > or is this post an implicit vote?)
> > - --
> > - -------------------------------
> > Josh Thompson
> > Systems Programmer
> > Advanced Computing | VCL Developer
> > North Carolina State University
> >
> > Josh_Thompson@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)
> >
> > iD8DBQFK30SGV/LQcNdtPQMRAhk8AJsGL4m0J1v0DC7U9Yyc31TIRjKXFACdE0bM
> > 827++1u0XH9c2GqKP/pAE80=
> > =QrMV
> > -----END PGP SIGNATURE-----
- --
- -------------------------------
Josh Thompson
Systems Programmer
Virtual Computing Lab (VCL)
North Carolina State University
Josh_Thompson@ncsu.edu
919-515-5323
my GPG/PGP key can be found at www.keyserver.net
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.11 (GNU/Linux)
iD8DBQFK4QMTV/LQcNdtPQMRAuNiAJwJ0WsP7IDgB8X5YneNoGcqmIz5ygCfVUe4
y6/cQYVx4fRbCJeaC6BoYBg=
=eFx1
-----END PGP SIGNATURE-----
Re: [VOTE] release VCL 2.1
Posted by "Alan D. Cabrera" <li...@toolazydogs.com>.
I don't have time to double check this release until this weekend.
Normally votes are 72 hours. I request that we don't count the votes
until Monday, if that's ok.
Regards,
Alan
On Oct 21, 2009, at 10:27 AM, Josh Thompson wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> I created a release artifact based off of trunk. I copied trunk to
> a tag
> under the tags area of the repo that is named release-2.1-RC1:
>
> http://svn.apache.org/repos/asf/incubator/vcl/tags/release-2.1-RC1/
>
> The artifact is an export from that tag. The artifact, MD5 and SHA1
> sums, and
> my GPG signature of it are available from my space on people.a.o:
>
> http://people.apache.org/~jfthomps/apache-VCL-2.1-RC1-incubating/
>
> The list of resolved JIRA issues associated with this release can be
> found on
> the VCL 2.1 release page:
>
> http://cwiki.apache.org/VCL/vcl-21-unreleased.html#VCL2.1%2528unreleased%2529-ChangeLog
>
> Installation instructions are on the Confluence site and in the
> INSTALLATION
> file included in the artifact.
>
> Aaron, Andy, and I have completed a test install of all parts and
> were able to
> successfully create and capture a base image.
>
> Please vote to publish this release.
>
> (Question to mentors: Do I need to vote in a successive email in
> this thread,
> or is this post an implicit vote?)
> - --
> - -------------------------------
> Josh Thompson
> Systems Programmer
> Advanced Computing | VCL Developer
> North Carolina State University
>
> Josh_Thompson@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)
>
> iD8DBQFK30SGV/LQcNdtPQMRAhk8AJsGL4m0J1v0DC7U9Yyc31TIRjKXFACdE0bM
> 827++1u0XH9c2GqKP/pAE80=
> =QrMV
> -----END PGP SIGNATURE-----
Re: [VOTE] release VCL 2.1
Posted by Andy Kurth <an...@ncsu.edu>.
I will look up the licenses of the modules the install_perl_libs.pl script
downloads/installs and include a disclaimer when the script is executed. I will
add the license information to the list of prerequisites in README. Will this
be sufficient?
-Andy
Kevan Miller wrote:
>
> On Oct 23, 2009, at 10:36 PM, Josh Thompson wrote:
>
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>
>> On Fri October 23 2009 4:45:26 pm Kevan Miller wrote:
>>> On Oct 21, 2009, at 1:27 PM, Josh Thompson wrote:
>>>> (Question to mentors: Do I need to vote in a successive email in
>>>> this thread,
>>>> or is this post an implicit vote?)
>>>
>>> You should either include an explicit +1 in the initial vote email, or
>>> "reply" in another email. Either is acceptable. I kind of prefer a
>>> separate email, but that's just me...
>>
>> Okay - since I didn't include and explicit +1 in the initial message,
>> I'll do
>> it here.
>>
>> +1
>>
>>> Most votes will include a formal statement on what the vote is about.
>>> E.g.:
>>>
>>> [ ] +1 yes, release VCL 2.1
>>> [ ] 0 dunno
>>> [ ] -1 no, don't release VCL 2.1 (provide reasons).
>>
>> Now that you mention it, I remember seeing that in some places.
>> Somehow, I
>> came up with an example email calling for a vote that I linked to off
>> of this
>> page:
>>
>> http://cwiki.apache.org/confluence/display/VCL/VCL+Release+Procedures
>>
>> direct link to email:
>>
>> http://mail-archives.apache.org/mod_mbox/stdcxx-dev/200601.mbox/%3C43C1C0A0.7040401@roguewave.com%3E
>>
>>
>> That email doesn't include what you mentioned. I'll revise the
>> release docs
>> to explain that part should be in there and maybe find a better example
>> email.
>>
>>> This is the strangest Apache "release" that I've ever seen... Taking
>>> some getting used to... I have some questions/comments. Haven't
>>> decided on my vote, yet.
>>
>> Since this is the only Apache "release" those of us from NCSU have
>> ever seen,
>> can you explain further why you say it is so strange? I thought the
>> release
>> procedures page followed the suggested guidelines pretty well. I'm
>> assuming
>> the items listed below aren't explaining that but are points you think
>> need
>> addressing before finalizing a release.
>
> It's "strange" to me, because I typically assume there is a binary
> build, in addition to the source. Installation seems pretty involved.
> I'm just going to be *reading* the installation steps, not actually
> following them...
>
>>
>>> * web/.ht-inc/conf.php contains references to Shibboleth and UNC. I
>>> assume that's holdover from VCL's origins.
>>
>> 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.
>
> It's fine, I think...
>
>>
>>> * 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.
>>
>> The web frontend only requires dojo to be installed. It is Apache
>> Licensed.
>> The licensing for JPGraph is explained in the INSTALLATION file as
>> well as
>> the fact that it is not needed. There are several options on how you use
>> VCL, and therefore what external software is needed for use by the
>> backend.
>> I'll defer to Aaron and Andy to answer this point further since the
>> backend
>> is not my area of focus.
>>
>>> * 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...
>
> So, my concern is that we're clear about the licensing implications of
> VCL. If VCL automatically downloads some set of libraries, then users
> need to be made aware of the licensing implications...
>
> --kevan
>
>
--
Andy Kurth
Virtual Computing Lab
Office of Information Technology
North Carolina State University
andy_kurth@ncsu.edu
919.513.4090
Re: [VOTE] release VCL 2.1
Posted by Andy Kurth <an...@ncsu.edu>.
I gathered the license information for the Perl modules downloaded and installed
by install_perl_libs.pl and added this information to README. Two of the
modules use LGPL. The others use the Artistic License or GPL. It would be
great if someone could go through them and double check.
There was one module (Digest-HMAC) which I couldn't find the license for. The
Digest-HMAC module was a dependency for the Authen-SASL 2.12 module. The
Digest-HMAC module no longer appears to be a dependency for Authen-SASL 2.13. I
updated the Authen-SASL URL to fetch version 2.13 and removed Digest-HMAC from
install_perl_libs.pl and README.
I added code to install_perl_libs.pl which requires the user to enter 'YES' the
script will install and download the modules. The following is displayed:
=====================================================================
*** NOTICE ***
This script will download and install Perl modules distributed under
the following licenses:
- The "Artistic License"
- GNU General Public License (GPL)
- GNU Library or "Lesser" General Public License (LGPL)
See the README file for more information.
=====================================================================
Type YES to proceed, type NO to abort:
Regarding the Microsoft artifacts, the instructions direct the person installing
the management node to the URL of the page where the supplemental utilities can
be obtained. These are not direct download links. Can the responsibility to
read the license terms provided by the 3rd party be left to the person
downloading the files?
Thanks,
Andy
Andy Kurth wrote:
> I will look up the licenses of the modules the install_perl_libs.pl
> script downloads/installs and include a disclaimer when the script is
> executed. I will add the license information to the list of
> prerequisites in README. Will this be sufficient?
>
> -Andy
>
> Kevan Miller wrote:
>>
>> On Oct 23, 2009, at 10:36 PM, Josh Thompson wrote:
>>
>>> -----BEGIN PGP SIGNED MESSAGE-----
>>> Hash: SHA1
>>>
>>> On Fri October 23 2009 4:45:26 pm Kevan Miller wrote:
>>>> On Oct 21, 2009, at 1:27 PM, Josh Thompson wrote:
>>>>> (Question to mentors: Do I need to vote in a successive email in
>>>>> this thread,
>>>>> or is this post an implicit vote?)
>>>>
>>>> You should either include an explicit +1 in the initial vote email, or
>>>> "reply" in another email. Either is acceptable. I kind of prefer a
>>>> separate email, but that's just me...
>>>
>>> Okay - since I didn't include and explicit +1 in the initial message,
>>> I'll do
>>> it here.
>>>
>>> +1
>>>
>>>> Most votes will include a formal statement on what the vote is about.
>>>> E.g.:
>>>>
>>>> [ ] +1 yes, release VCL 2.1
>>>> [ ] 0 dunno
>>>> [ ] -1 no, don't release VCL 2.1 (provide reasons).
>>>
>>> Now that you mention it, I remember seeing that in some places.
>>> Somehow, I
>>> came up with an example email calling for a vote that I linked to off
>>> of this
>>> page:
>>>
>>> http://cwiki.apache.org/confluence/display/VCL/VCL+Release+Procedures
>>>
>>> direct link to email:
>>>
>>> http://mail-archives.apache.org/mod_mbox/stdcxx-dev/200601.mbox/%3C43C1C0A0.7040401@roguewave.com%3E
>>>
>>>
>>> That email doesn't include what you mentioned. I'll revise the
>>> release docs
>>> to explain that part should be in there and maybe find a better example
>>> email.
>>>
>>>> This is the strangest Apache "release" that I've ever seen... Taking
>>>> some getting used to... I have some questions/comments. Haven't
>>>> decided on my vote, yet.
>>>
>>> Since this is the only Apache "release" those of us from NCSU have
>>> ever seen,
>>> can you explain further why you say it is so strange? I thought the
>>> release
>>> procedures page followed the suggested guidelines pretty well. I'm
>>> assuming
>>> the items listed below aren't explaining that but are points you
>>> think need
>>> addressing before finalizing a release.
>>
>> It's "strange" to me, because I typically assume there is a binary
>> build, in addition to the source. Installation seems pretty involved.
>> I'm just going to be *reading* the installation steps, not actually
>> following them...
>>
>>>
>>>> * web/.ht-inc/conf.php contains references to Shibboleth and UNC. I
>>>> assume that's holdover from VCL's origins.
>>>
>>> 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.
>>
>> It's fine, I think...
>>
>>>
>>>> * 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.
>>>
>>> The web frontend only requires dojo to be installed. It is Apache
>>> Licensed.
>>> The licensing for JPGraph is explained in the INSTALLATION file as
>>> well as
>>> the fact that it is not needed. There are several options on how you
>>> use
>>> VCL, and therefore what external software is needed for use by the
>>> backend.
>>> I'll defer to Aaron and Andy to answer this point further since the
>>> backend
>>> is not my area of focus.
>>>
>>>> * 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...
>>
>> So, my concern is that we're clear about the licensing implications of
>> VCL. If VCL automatically downloads some set of libraries, then users
>> need to be made aware of the licensing implications...
>>
>> --kevan
>>
>>
>
--
Andy Kurth
Virtual Computing Lab
Office of Information Technology
North Carolina State University
andy_kurth@ncsu.edu
919.513.4090
Re: [VOTE] release VCL 2.1
Posted by Kevan Miller <ke...@gmail.com>.
On Oct 23, 2009, at 10:36 PM, Josh Thompson wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On Fri October 23 2009 4:45:26 pm Kevan Miller wrote:
>> On Oct 21, 2009, at 1:27 PM, Josh Thompson wrote:
>>> (Question to mentors: Do I need to vote in a successive email in
>>> this thread,
>>> or is this post an implicit vote?)
>>
>> You should either include an explicit +1 in the initial vote email,
>> or
>> "reply" in another email. Either is acceptable. I kind of prefer a
>> separate email, but that's just me...
>
> Okay - since I didn't include and explicit +1 in the initial
> message, I'll do
> it here.
>
> +1
>
>> Most votes will include a formal statement on what the vote is about.
>> E.g.:
>>
>> [ ] +1 yes, release VCL 2.1
>> [ ] 0 dunno
>> [ ] -1 no, don't release VCL 2.1 (provide reasons).
>
> Now that you mention it, I remember seeing that in some places.
> Somehow, I
> came up with an example email calling for a vote that I linked to
> off of this
> page:
>
> http://cwiki.apache.org/confluence/display/VCL/VCL+Release+Procedures
>
> direct link to email:
>
> http://mail-archives.apache.org/mod_mbox/stdcxx-dev/200601.mbox/%3C43C1C0A0.7040401@roguewave.com%3E
>
> That email doesn't include what you mentioned. I'll revise the
> release docs
> to explain that part should be in there and maybe find a better
> example
> email.
>
>> This is the strangest Apache "release" that I've ever seen... Taking
>> some getting used to... I have some questions/comments. Haven't
>> decided on my vote, yet.
>
> Since this is the only Apache "release" those of us from NCSU have
> ever seen,
> can you explain further why you say it is so strange? I thought the
> release
> procedures page followed the suggested guidelines pretty well. I'm
> assuming
> the items listed below aren't explaining that but are points you
> think need
> addressing before finalizing a release.
It's "strange" to me, because I typically assume there is a binary
build, in addition to the source. Installation seems pretty involved.
I'm just going to be *reading* the installation steps, not actually
following them...
>
>> * web/.ht-inc/conf.php contains references to Shibboleth and UNC. I
>> assume that's holdover from VCL's origins.
>
> 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.
It's fine, I think...
>
>> * 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.
>
> The web frontend only requires dojo to be installed. It is Apache
> Licensed.
> The licensing for JPGraph is explained in the INSTALLATION file as
> well as
> the fact that it is not needed. There are several options on how
> you use
> VCL, and therefore what external software is needed for use by the
> backend.
> I'll defer to Aaron and Andy to answer this point further since the
> backend
> is not my area of focus.
>
>> * 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...
So, my concern is that we're clear about the licensing implications of
VCL. If VCL automatically downloads some set of libraries, then users
need to be made aware of the licensing implications...
--kevan
Re: [VOTE] release VCL 2.1
Posted by Josh Thompson <jo...@ncsu.edu>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Fri October 23 2009 4:45:26 pm Kevan Miller wrote:
> On Oct 21, 2009, at 1:27 PM, Josh Thompson wrote:
> > (Question to mentors: Do I need to vote in a successive email in
> > this thread,
> > or is this post an implicit vote?)
>
> You should either include an explicit +1 in the initial vote email, or
> "reply" in another email. Either is acceptable. I kind of prefer a
> separate email, but that's just me...
Okay - since I didn't include and explicit +1 in the initial message, I'll do
it here.
+1
> Most votes will include a formal statement on what the vote is about.
> E.g.:
>
> [ ] +1 yes, release VCL 2.1
> [ ] 0 dunno
> [ ] -1 no, don't release VCL 2.1 (provide reasons).
Now that you mention it, I remember seeing that in some places. Somehow, I
came up with an example email calling for a vote that I linked to off of this
page:
http://cwiki.apache.org/confluence/display/VCL/VCL+Release+Procedures
direct link to email:
http://mail-archives.apache.org/mod_mbox/stdcxx-dev/200601.mbox/%3C43C1C0A0.7040401@roguewave.com%3E
That email doesn't include what you mentioned. I'll revise the release docs
to explain that part should be in there and maybe find a better example
email.
> This is the strangest Apache "release" that I've ever seen... Taking
> some getting used to... I have some questions/comments. Haven't
> decided on my vote, yet.
Since this is the only Apache "release" those of us from NCSU have ever seen,
can you explain further why you say it is so strange? I thought the release
procedures page followed the suggested guidelines pretty well. I'm assuming
the items listed below aren't explaining that but are points you think need
addressing before finalizing a release.
> * web/.ht-inc/conf.php contains references to Shibboleth and UNC. I
> assume that's holdover from VCL's origins.
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.
> * 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.
The web frontend only requires dojo to be installed. It is Apache Licensed.
The licensing for JPGraph is explained in the INSTALLATION file as well as
the fact that it is not needed. There are several options on how you use
VCL, and therefore what external software is needed for use by the backend.
I'll defer to Aaron and Andy to answer this point further since the backend
is not my area of focus.
> * 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...
>
> --kevan
Thanks for your comments. We want this to be as successful and "correctly
released" as possible.
Josh
- --
- -------------------------------
Josh Thompson
Systems Programmer
Virtual Computing Lab (VCL)
North Carolina State University
Josh_Thompson@ncsu.edu
919-515-5323
my GPG/PGP key can be found at www.keyserver.net
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.11 (GNU/Linux)
iD8DBQFK4mhDV/LQcNdtPQMRAhOKAJ9YIi3FqH5djL0/xbLbqGqhax1v6ACeNcMO
ff9+YnGGvn98/wITV49jS7M=
=T1db
-----END PGP SIGNATURE-----
Re: [VOTE] release VCL 2.1
Posted by Kevan Miller <ke...@gmail.com>.
On Oct 21, 2009, at 1:27 PM, Josh Thompson wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> I created a release artifact based off of trunk. I copied trunk to
> a tag
> under the tags area of the repo that is named release-2.1-RC1:
>
> http://svn.apache.org/repos/asf/incubator/vcl/tags/release-2.1-RC1/
>
> The artifact is an export from that tag. The artifact, MD5 and SHA1
> sums, and
> my GPG signature of it are available from my space on people.a.o:
>
> http://people.apache.org/~jfthomps/apache-VCL-2.1-RC1-incubating/
>
> The list of resolved JIRA issues associated with this release can be
> found on
> the VCL 2.1 release page:
>
> http://cwiki.apache.org/VCL/vcl-21-unreleased.html#VCL2.1%2528unreleased%2529-ChangeLog
>
> Installation instructions are on the Confluence site and in the
> INSTALLATION
> file included in the artifact.
>
> Aaron, Andy, and I have completed a test install of all parts and
> were able to
> successfully create and capture a base image.
>
> Please vote to publish this release.
>
> (Question to mentors: Do I need to vote in a successive email in
> this thread,
> or is this post an implicit vote?)
You should either include an explicit +1 in the initial vote email, or
"reply" in another email. Either is acceptable. I kind of prefer a
separate email, but that's just me...
Most votes will include a formal statement on what the vote is about.
E.g.:
[ ] +1 yes, release VCL 2.1
[ ] 0 dunno
[ ] -1 no, don't release VCL 2.1 (provide reasons).
This is the strangest Apache "release" that I've ever seen... Taking
some getting used to... I have some questions/comments. Haven't
decided on my vote, yet.
* web/.ht-inc/conf.php contains references to Shibboleth and UNC. I
assume that's holdover from VCL's origins.
* 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.
* 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...
--kevan