pig-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Olga Natkovich (JIRA)" <j...@apache.org>
Subject [jira] Commented: (PIG-34) Making Pig release ready
Date Mon, 30 Jun 2008 18:27:45 GMT

    [ https://issues.apache.org/jira/browse/PIG-34?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12609322#action_12609322
] 

Olga Natkovich commented on PIG-34:
-----------------------------------

Licenses:

| # | Software | Distribution      | License            | Authorized | Comments
-------------------------------------------------------------------------------------------------------------------------------------
| 1 | javacc     | binary                 | BSD                  | yes              |
| 2 | junit         | not distributed  | CPL                  | reciprocal  | should be ok
since we don't ditribute it
| 3 | hadoop  | binary + source | Apache            | yes              |
| 4 | bzip2      | source                 | Apache            | yes              | we modify
the source code
| 5 | jsch        | binary                  | Modified BSD  | ?                  |
| 6 | shock     | source                | ??                      | ?                  | 


I have a couple of questions regarding the license:

(1) Ben - what is the situation with shock code as far as the license?
(2) To our mentors - what is the policy regarding modified BSF license as the case with jsch?
(3) To our mentors - I assume that it is ok to modify code with apache license, is this correct?



> Making Pig release ready
> ------------------------
>
>                 Key: PIG-34
>                 URL: https://issues.apache.org/jira/browse/PIG-34
>             Project: Pig
>          Issue Type: New Feature
>            Reporter: Olga Natkovich
>            Assignee: Olga Natkovich
>         Attachments: PIG-34-v02.patch, PIG-34_v_1.patch
>
>
> This is from email on pig-dev from Bertrand Delacretaz:
> I wrote a blog post [3] while mentoring Wicket, it might help as an overview.
> > ...I found some online documents
> > (http://incubator.apache.org/guides/releasemanagement.htm) about it 
> > but I don't have a very good feel for what is the minimal set of 
> > things we need to do to get ready....
> I'd say the minimal set is
> 1) Check that the required external libraries (if any) can be distributed, see [2]
> 2) Create the required NOTICE and LICENSE files, see [1] and [2]
> 3) Generate distribution artifacts which include this info
> 4) Call for review of these artifacts, followed by a vote here and then a vote by the
Incubator PMC.
> -Bertrand
> [1] http://incubator.apache.org/guides/releasemanagement.html
> [2] http://people.apache.org/~cliffs/3party.html
> [3] http://www.codeconsult.ch/bertrand/archives/000759.html

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message