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: > <http://source.android.com/> > > If you dig into the source, you'll find some no doubt very > familiar-looking files under <dalvik/libcore/*>. 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 >
