incubator-cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chip Childers (JIRA)" <j...@apache.org>
Subject [jira] [Reopened] (CLOUDSTACK-145) Establish legal use of patches/systemvm/debian/config/etc/ssh/sshd_config
Date Tue, 25 Sep 2012 17:10:07 GMT

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

Chip Childers reopened CLOUDSTACK-145:
--------------------------------------

      Assignee: Joe Brockmeier  (was: Chiradeep Vittal)

Joe,

I'm reopening this issue, because we need to determine exactly what license terms should be
included in our LICENSE file for this config.  Since you did a bunch of the research initially
(and Chiradeep confirmed his perspective), can you sort that out and let us know if this is
the standard BSD 3-Clause, BSD 2-Clause, or highlight the specific custom text that we should
include as the appropriate license?

Thanks a ton!

-chip
                
> Establish legal use of patches/systemvm/debian/config/etc/ssh/sshd_config
> -------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-145
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-145
>             Project: CloudStack
>          Issue Type: Bug
>    Affects Versions: pre-4.0.0
>            Reporter: Chip Childers
>            Assignee: Joe Brockmeier
>            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/config/etc/ssh/sshd_config

--
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

Mime
View raw message