Mailing-List: contact cloudstack-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: cloudstack-dev@incubator.apache.org
Date: Sat, 22 Sep 2012 05:59:08 +1100 (NCT)
From: "Chiradeep Vittal (JIRA)" <jira@apache.org>
To: cloudstack-dev@incubator.apache.org
Message-ID: <498863722.108900.1348253948247.JavaMail.jiratomcat@arcas>
In-Reply-To: <1755196908.102833.1348149488660.JavaMail.jiratomcat@arcas>
Subject: [jira] [Closed] (CLOUDSTACK-172) Establish legal use of
 patches/systemvm/debian/vpn/etc/ppp/options.xl2tpd
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/CLOUDSTACK-172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Chiradeep Vittal closed CLOUDSTACK-172.
---------------------------------------

    Resolution: Fixed
      Assignee: Chiradeep Vittal

Written specifically for CloudStack by Chiradeep Vittal (chiradeep@apache.org) after consulting the manual for xl2tpd and the examples provided by the software
                
> Establish legal use of patches/systemvm/debian/vpn/etc/ppp/options.xl2tpd
> -------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-172
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-172
>             Project: CloudStack
>          Issue Type: Bug
>    Affects Versions: pre-4.0.0
>            Reporter: Chip Childers
>            Assignee: Chiradeep Vittal
>            Priority: Blocker
>              Labels: licensing
>             Fix For: 4.0.0
>
>
> We need to establish if the following file is one of the following:
> 1) Written specifically for CloudStack
> 2) Taken (and perhaps modified) from a source that has an ASLv2 compatible license
> 3) Taken (and perhaps modified) from a source that does not have a compatible license, and then figure out what to do about it.
> patches/systemvm/debian/vpn/etc/ppp/options.xl2tpd

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira