Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
RE: [babel-dev] Re: babel-dev Digest, Vol 6, Issue 7

Actually, the approval process needs to flow from the project leadership to the PMC. E.g. the project leaders have to indicate that this is a tool they want to use with the project.

 

 

From: babel-dev-bounces@xxxxxxxxxxx [mailto:babel-dev-bounces@xxxxxxxxxxx] On Behalf Of Daniel McGowan
Sent: Tuesday, February 05, 2008 6:33 AM
To: babel-dev@xxxxxxxxxxx
Subject: [babel-dev] Re: babel-dev Digest, Vol 6, Issue 7

 

The tool is proprietary but free (as in beer). So I believe it is acceptable according to the policy.

Also, as Kit mentioned we are in the process of open sourcing the tool.

Should I submit a request to EMO?

babel-dev-request@xxxxxxxxxxx wrote:

And here is the policy describing when and how Eclipse projects can use proprietary software products in development J

 

From what I can see in  that document, NLW is a proprietary tool, no?

 

Mike Milinkovich

Office: +1.613.224.9461 x228

Mobile: +1.613.220.3223

mike.milinkovich@xxxxxxxxxxx

 

Back to the top