From dev-return-35142-apmail-harmony-dev-archive=harmony.apache.org@harmony.apache.org Wed Oct 22 08:19:48 2008
Return-Path:
Delivered-To: apmail-harmony-dev-archive@www.apache.org
Received: (qmail 28861 invoked from network); 22 Oct 2008 08:19:48 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2)
by minotaur.apache.org with SMTP; 22 Oct 2008 08:19:48 -0000
Received: (qmail 85171 invoked by uid 500); 22 Oct 2008 08:19:49 -0000
Delivered-To: apmail-harmony-dev-archive@harmony.apache.org
Received: (qmail 85135 invoked by uid 500); 22 Oct 2008 08:19:49 -0000
Mailing-List: contact dev-help@harmony.apache.org; run by ezmlm
Precedence: bulk
List-Help:
List-Unsubscribe:
List-Post:
List-Id:
Reply-To: dev@harmony.apache.org
Delivered-To: mailing list dev@harmony.apache.org
Received: (qmail 85124 invoked by uid 99); 22 Oct 2008 08:19:49 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 22 Oct 2008 01:19:49 -0700
X-ASF-Spam-Status: No, hits=-0.0 required=10.0
tests=SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (athena.apache.org: domain of t.p.ellison@gmail.com designates 64.233.182.189 as permitted sender)
Received: from [64.233.182.189] (HELO nf-out-0910.google.com) (64.233.182.189)
by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 22 Oct 2008 08:18:37 +0000
Received: by nf-out-0910.google.com with SMTP id c7so1515221nfi.40
for ; Wed, 22 Oct 2008 01:19:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=gmail.com; s=gamma;
h=domainkey-signature:received:received:message-id:date:from
:user-agent:mime-version:to:subject:references:in-reply-to
:x-enigmail-version:content-type:content-transfer-encoding;
bh=o3zUX300y4WEz9K6s+kGo8GNgTKfkav+4rVWo5cQaeY=;
b=Cm5l8meqN5A83tyf0ZwuJEF/YlX7a9wMtBvT0HEvaqH17FUKW/Z8ZHZ0T5kN1YwrNp
5S51PcvyWcZTawlBGPm1ifRxF6VRo3aqS4OSmYpnNxrcXu4K3y0tBHfpwrUwF4HfT2/5
FOHSVTio39R6s6DhMf1vlhEDOrW/w7dNlBPZs=
DomainKey-Signature: a=rsa-sha1; c=nofws;
d=gmail.com; s=gamma;
h=message-id:date:from:user-agent:mime-version:to:subject:references
:in-reply-to:x-enigmail-version:content-type
:content-transfer-encoding;
b=Hi/C1uxL73sZ0+A8oPFJc9S23tOvNlt0XqlcVFg14SyD90n/jN7zNnMIoguWqx4Jtc
OVU47TaZCaGku1TgDGmAcHJGVtf8KNjVFYA+//AS9W3PDi3EnAV1hgXnHO/4ojpGhFRl
d0La8r91PkXMADAcJFOLwfKXx9h4JT58BCWWw=
Received: by 10.210.120.7 with SMTP id s7mr11569576ebc.30.1224663553775;
Wed, 22 Oct 2008 01:19:13 -0700 (PDT)
Received: from ?9.20.183.164? (blueice3n1.uk.ibm.com [195.212.29.83])
by mx.google.com with ESMTPS id 23sm13670189eya.7.2008.10.22.01.19.12
(version=SSLv3 cipher=RC4-MD5);
Wed, 22 Oct 2008 01:19:12 -0700 (PDT)
Message-ID: <48FEE1E2.8000902@gmail.com>
Date: Wed, 22 Oct 2008 09:18:42 +0100
From: Tim Ellison
User-Agent: Thunderbird 2.0.0.17 (Windows/20080914)
MIME-Version: 1.0
To: dev@harmony.apache.org
Subject: Re: Android source: open for business
References: <8084e12c0810211425t4a02494fyacb78fa66eb65182@mail.gmail.com>
In-Reply-To: <8084e12c0810211425t4a02494fyacb78fa66eb65182@mail.gmail.com>
X-Enigmail-Version: 0.95.7
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 8bit
X-Virus-Checked: Checked by ClamAV on apache.org
Hi Dan.
Congratulations on getting the Android code out the door! A significant
milestone on the great journey.
I think there are various levels that we can imagine cooperating, and we
should discuss which will be most effective for both the Android and
Harmony projects.
At the simplest level we can maintain parallel code streams and exchange
patches for bugs found in each. Its an easy place to start, but
ultimately this would be less than ideal since it would require both
projects to evaluate the appropriateness of each patch we make, and I
believe we would eventually drift apart.
At the other end of the scale, Harmony (or Android) could produce the
'right shape' delivery for incorporating, unmodified, into Android (or
Harmony). This would mean bugs get fixed at one location, mindful of
the uses in various projects.
The challenge is to understand which axes of flexibility should be
defined for the Harmony class libraries in order to deliver on our users
needs. Today, we simply split things into functional areas, but I can
see that we might also want to configure to target environment as you
and Chris Gray have described.
The open Android site looks good, and I recognize a great deal of it
from the Apache perspective -- which will make working together much
easier. However, I didn't see anything about contributors' prior
access, like the Harmony ACQ [1]. Is that information considered for
Android contributors?
[1] http://harmony.apache.org/auth_cont_quest.html
Regards,
Tim
Dan Bornstein wrote:
> Greetings, Harmony People.
>
> Earlier today, the Android project pushed its first open source
> release out the door. You can find all the details here:
>
>
> If you dig into the source, you'll find some no doubt very
> familiar-looking files under . Once again, I thank
> you all for your important contributions!
>
> We have been spending all our time recently trying to get two products
> out the door — one being a software build for the "G1" device, and the
> other being the source code itself along with the related tools — but
> now that the dust is settling, we are beginning to contemplate how
> best to get our library code back in sync with the Harmony mainline.
> We have changes we've made that we are reasonably sure would be useful
> to Harmony, and we've made others we are pretty sure don't make sense
> for Harmony's primary target of desktop/server class machines.
>
> In the coming months, expect to see us working on merging changes in
> both directions. In the mean time, please do poke around in our code,
> and, should you be inspired to do so, we'd be tickled pink if you
> wanted either to pull changes from us or submit patches back. We're
> just getting ramped up on operating in the open, so I apologize in
> advance for the inevitable hiccups.
>
> Warm regards,
>
> -dan
>