Return-Path: Delivered-To: apmail-lenya-dev-archive@www.apache.org Received: (qmail 71988 invoked from network); 15 Jun 2009 20:22:59 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 15 Jun 2009 20:22:59 -0000 Received: (qmail 70517 invoked by uid 500); 15 Jun 2009 20:23:10 -0000 Delivered-To: apmail-lenya-dev-archive@lenya.apache.org Received: (qmail 70429 invoked by uid 500); 15 Jun 2009 20:23:10 -0000 Mailing-List: contact dev-help@lenya.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@lenya.apache.org Delivered-To: mailing list dev@lenya.apache.org Received: (qmail 70419 invoked by uid 99); 15 Jun 2009 20:23:10 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 15 Jun 2009 20:23:10 +0000 X-ASF-Spam-Status: No, hits=2.2 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of salexse@gmail.com designates 209.85.220.207 as permitted sender) Received: from [209.85.220.207] (HELO mail-fx0-f207.google.com) (209.85.220.207) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 15 Jun 2009 20:22:59 +0000 Received: by fxm3 with SMTP id 3so3936416fxm.5 for ; Mon, 15 Jun 2009 13:22:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type; bh=/HgC7Y+epUaTbCDO4UBpP09uXxW1x3mA0EmkVIthDrI=; b=PtOdhehIgfOAjqztEd5UUZcEgS38x48hVs3I4FNXmPbf72SxIbJPZiqQcjSBFnZl+s PwgnGMFMjGmrJlbbIAeFhDKQQEwy5wnBOeQc0tYDp64gYc4YmrD+lLfScGhKJ0134PQP xV2rqycWR2q1ihcZaJTC5AKCWgXkuhOM2gGWY= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=W05E9M4+dILX54Puysypa3JAAxX6NH3CT9cFpY8tyHLfxXOgSbs6cenGIIXy9MeHJI Vzz3LlrMd5omFcU1iCs06VwAHiYxbEqoxsXIEi6Z+ePVpkK6CH4iHIvTxbY1vAMiIMnU IaeDbpsLRcX0f5GXvzgoVRSgHcTaGOZvIF2RU= MIME-Version: 1.0 Received: by 10.223.114.68 with SMTP id d4mr4646538faq.86.1245097358444; Mon, 15 Jun 2009 13:22:38 -0700 (PDT) In-Reply-To: <4A2FCE64.2040109@apache.org> References: <734eb5540906081307t57d7e78dm6d606baf0f004f98@mail.gmail.com> <4A2FCE64.2040109@apache.org> Date: Tue, 16 Jun 2009 00:22:38 +0400 Message-ID: <734eb5540906151322i5d6726e7pa5b15bbfb73986b5@mail.gmail.com> Subject: Re: xmldiff module From: "Alexander S. Sizemin" To: dev@lenya.apache.org Content-Type: multipart/alternative; boundary=001636c5b184c2cb17046c68d137 X-Virus-Checked: Checked by ClamAV on apache.org --001636c5b184c2cb17046c68d137 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Hi devs, I'm not much experienced in the field of licencing, so I have a question regarding a third-party code usage. What I want to figure out is if there any way to use opensource non-ASF code witin the Lenya module devlopment? Particularly, one of such non-ASF licences is QPL v1.0 ( http://en.wikipedia.org/wiki/QPL). I can't say there is a great need of using the particular solution, which is under QPL, but it's usage will give a much better outcome and will help to solve problems more effectively, that's why it is so desirable for me. Thank you, Alexander 2009/6/10 Richard Frovarp > Alexander S. Sizemin wrote: > >> Hello devs, >> I'm working on xmldiff module and I need some guidance: >> >> 1) I want to change usecase policies for default publication to grant >> rights for new usecases. >> Shall I create an additonal patch against svn code or there is a way to >> integrate this changes to my module? >> >> Create an additional patch against the svn code. I believe in the past > we've also just included directions on how to make the change yourself for > extra modules. > > > 2) I want to use some existing code from diff module, which is neither in >> Lenya core nor Lenya standard modules. >> I'm going to use only it's java codebase, so the question is >> do I need to import existing diff module though standard module config or >> I can simply employ it's codebase in a form of packed jar file? >> > > I would say import the existing diff, although that will potentially create > some odd dependencies. It's going to depend on how much of the code base you > end up reusing. It's possible that the two modules would actually be merged > into one when it is brought into the code base. It's going to depend on the > functionality of each. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscribe@lenya.apache.org > For additional commands, e-mail: dev-help@lenya.apache.org > > --001636c5b184c2cb17046c68d137 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hi devs,
I'm not much experienced in the field of licencing,
so I= have a question regarding a third-party code usage.

What I want to = figure out is if there any way to use opensource non-ASF code witin the Len= ya module devlopment?
Particularly, one of such non-ASF licences is QPL v1.0 (http://en.wikipedia.org/wiki/QPL).
I can&#= 39;t say there is a great need of using the particular solution, which is u= nder QPL,
but it's usage will give a much better outcome and will help to solve p= roblems more effectively,
that's why it is so desirable for me.
<= br>Thank you,
Alexander

2009/6/10 Rich= ard Frovarp <rf= rovarp@apache.org>
Alexander S. Sizemin wrote:
Hello devs,
I'm working on xmldiff module and I need some guidance:

1) I want to change usecase policies for default publication to grant right= s for new usecases.
Shall I create an additonal patch against svn code or there is a way to int= egrate this changes to my module?

Create an additional patch against the svn code. I believe in the past we&#= 39;ve also just included directions on how to make the change yourself for = extra modules.



2) I want to use some existing code from diff module, which is neither in L= enya core nor Lenya standard modules.
I'm going to use only it's java codebase, so the question is
do I need to import existing diff module though standard module config or I can simply employ it's codebase in a form of packed jar file?

I would say import the existing diff, although that will potentially create= some odd dependencies. It's going to depend on how much of the code ba= se you end up reusing. It's possible that the two modules would actuall= y be merged into one when it is brought into the code base. It's going = to depend on the functionality of each.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lenya.apache.org
For additional commands, e-mail: dev-help@lenya.apache.org


--001636c5b184c2cb17046c68d137--