Return-Path: X-Original-To: apmail-incubator-cloudstack-dev-archive@minotaur.apache.org Delivered-To: apmail-incubator-cloudstack-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 1EE23D35E for ; Tue, 31 Jul 2012 20:53:00 +0000 (UTC) Received: (qmail 31489 invoked by uid 500); 31 Jul 2012 20:52:59 -0000 Delivered-To: apmail-incubator-cloudstack-dev-archive@incubator.apache.org Received: (qmail 31464 invoked by uid 500); 31 Jul 2012 20:52:59 -0000 Mailing-List: contact cloudstack-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: cloudstack-dev@incubator.apache.org Delivered-To: mailing list cloudstack-dev@incubator.apache.org Received: (qmail 31454 invoked by uid 99); 31 Jul 2012 20:52:59 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 31 Jul 2012 20:52:59 +0000 X-ASF-Spam-Status: No, hits=-1.6 required=5.0 tests=RCVD_IN_DNSWL_MED,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (athena.apache.org: local policy) Received: from [74.125.149.240] (HELO na3sys009aog116.obsmtp.com) (74.125.149.240) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 31 Jul 2012 20:52:53 +0000 Received: from mail-vc0-f170.google.com ([209.85.220.170]) (using TLSv1) by na3sys009aob116.postini.com ([74.125.148.12]) with SMTP ID DSNKUBhFjcN4+6n0JCJX8pQGa3aY64qJw/uM@postini.com; Tue, 31 Jul 2012 13:52:33 PDT Received: by vcbgb30 with SMTP id gb30so7081138vcb.29 for ; Tue, 31 Jul 2012 13:52:29 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type :x-gm-message-state; bh=7+uZ4vk1VA1yR6KTuh2wV6yc4dTv0hfe1sXiYxcBeWQ=; b=A6ezmM2L43GuhyX4OBE8Z4mu2ocrdgpIMkgZDG7tkHFZK1tFZutxOk7Vt1AeouzoJG YjGPeLyGNqiLatosiW2vbhl5XaYe1Twns68hm5atcPauidtVLIglarpNTKCelByaVTL/ fnWrD6mEjgHQWxIjgf/7E1X8LdcrSQ1s1FMDBFWZZLMx5VlSdFyGhzMv7h7piytxCcYF 0lANsMSEl3yU4NQjPcbCAV8BWDhLcA05PJYrotpMtclUOZjpejmi3cAwfv7BzGvlsLiV TEAYcti/45A45EAlK4bcHJ+m5xAigdLwx1bGupQhWOoV8hlYIGFGBdHAtxLhBRcZ2Hg7 5qAA== MIME-Version: 1.0 Received: by 10.52.19.133 with SMTP id f5mr13340586vde.41.1343767949256; Tue, 31 Jul 2012 13:52:29 -0700 (PDT) Received: by 10.220.62.78 with HTTP; Tue, 31 Jul 2012 13:52:29 -0700 (PDT) Date: Tue, 31 Jul 2012 16:52:29 -0400 Message-ID: Subject: Official ASF process for re-writing code? From: Chip Childers To: cloudstack-dev@incubator.apache.org Content-Type: text/plain; charset=ISO-8859-1 X-Gm-Message-State: ALoCoQni++zBR5doOISbeatcjNQfwFIxQ+KIgDCO575p/d4LhwJk8vpUTSwHqXnELtAA0C040kFO X-Virus-Checked: Checked by ClamAV on apache.org Does anyone know the official ASF stance on what it means to "re-write" a section of code? Specifically, I was looking at the F5 code [1] that was found during license header changes (and is considered a release blocker bug [2]). The code is actually quite trivial in nature, and I'm wondering what it would take to correctly write a replacement class file. My assumption is that simply re-naming variables wouldn't work (and even if that was enough, there are only a handful of them in the file). Guidance from Citrix folks that might have had discussions with ASF legal on this already, or from the project mentors. Thanks! -chip [1] - https://git-wip-us.apache.org/repos/asf?p=incubator-cloudstack.git;a=blob;f=core/src/com/cloud/network/resource/XTrustProvider.java [2] - http://bugs.cloudstack.org/browse/CS-15732