From ys148558@sac.sfbay.sun.com Mon Jul 27 22:46:13 2009 Received: from newsunmail1brm.central.sun.com (newsunmail1brm.Central.Sun.COM [129.147.62.245]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id n6S5kDuX004177 for ; Mon, 27 Jul 2009 22:46:13 -0700 (PDT) Received: from nwk-avmta-2.sfbay.sun.com (nwk-avmta-2.SFBay.Sun.COM [129.145.155.6]) by newsunmail1brm.central.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id n6S5kA6e001907; Mon, 27 Jul 2009 23:46:12 -0600 (MDT) Received: from pmxchannel-daemon.nwk-avmta-2.sfbay.sun.com by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0KNH00H3L9CY0D00@nwk-avmta-2.sfbay.sun.com>; Mon, 27 Jul 2009 22:46:10 -0700 (PDT) Received: from dm-sfbay-02.sfbay.sun.com ([129.146.11.31]) by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KNH00B4E9CY0D80@nwk-avmta-2.sfbay.sun.com>; Mon, 27 Jul 2009 22:46:10 -0700 (PDT) Received: from sac.sfbay.sun.com (sac.SFBay.Sun.COM [129.146.226.132]) by dm-sfbay-02.sfbay.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id n6S5kAVw036199; Mon, 27 Jul 2009 22:46:10 -0700 (PDT) Received: from sac.sfbay.sun.com (localhost [127.0.0.1]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id n6S5k93G004172; Mon, 27 Jul 2009 22:46:09 -0700 (PDT) Received: (from ys148558@localhost) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8/Submit) id n6S5k9AY004168; Mon, 27 Jul 2009 22:46:09 -0700 (PDT) Date: Mon, 27 Jul 2009 22:46:09 -0700 (PDT) From: Yong Young Sun Subject: Update libchewing from 0.3.0 to 0.3.2 [PSARC/2009/416 Self Review] To: PSARC-ext@sun.com Cc: gto-ext@sun.com Message-id: <200907280546.n6S5k9AY004168@sac.sfbay.sun.com> Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 Status: RO Content-Length: 1252 Template Version: @(#)sac_nextcase 1.68 02/23/09 SMI This information is Copyright 2009 Sun Microsystems 1. Introduction 1.1. Project/Component Working Name: Update libchewing from 0.3.0 to 0.3.2 1.2. Name of Document Author/Supplier: Author: Yong Sun 1.3 Date of This Document: 27 July, 2009 4. Technical Description libchewing is a popular library for Traditional Chinese input method engine licensed in LGPLv2.1. And there are some input methods, like iiimf-twle-chewing, scim-chewing depends on this library to provide input services to users. The version currently shipped in nevada/opensolaris is 0.3.0, while the community recently released a newer version, 0.3.2. In this new release, the API/ABI compatiblities were broken, and some new features are added. iiimf-twle-chewing and scim-chewing had been updated to work with 0.3.2, we therefore need to deliver the updated version to nevada/opensolaris. The interfaces (header files and shared library) remain the same as before. 6. Resources and Schedule 6.4. Steering Committee requested information 6.4.1. Consolidation C-team Name: Globalization 6.5. ARC review type: Automatic 6.6. ARC Exposure: open From gdamore@sun.com Mon Jul 27 23:04:39 2009 Received: from sunmail5.uk.sun.com (sunmail5.UK.Sun.COM [129.156.85.165]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id n6S64cjd004670 for ; Mon, 27 Jul 2009 23:04:38 -0700 (PDT) Received: from brm-avmta-1.central.sun.com (brm-avmta-1.Central.Sun.COM [129.147.4.11]) by sunmail5.uk.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id n6S64ZNc010007; Tue, 28 Jul 2009 07:04:37 +0100 (BST) Received: from pmxchannel-daemon.brm-avmta-1.central.sun.com by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0KNH0080RA7N3S00@brm-avmta-1.central.sun.com>; Tue, 28 Jul 2009 00:04:35 -0600 (MDT) Received: from sca-es-mail-1.sun.com ([192.18.43.132]) by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KNH00M6PA7MHP90@brm-avmta-1.central.sun.com>; Tue, 28 Jul 2009 00:04:34 -0600 (MDT) Received: from fe-sfbay-09.sun.com ([192.18.43.129]) by sca-es-mail-1.sun.com (8.13.7+Sun/8.12.9) with ESMTP id n6S64Y2C029279; Mon, 27 Jul 2009 23:04:34 -0700 (PDT) Received: from conversion-daemon.fe-sfbay-09.sun.com by fe-sfbay-09.sun.com (Sun Java(tm) System Messaging Server 7u2-7.02 64bit (built Apr 16 2009)) id <0KNH00600A4A4K00@fe-sfbay-09.sun.com>; Mon, 27 Jul 2009 23:04:34 -0700 (PDT) Received: from [192.168.251.11] ([unknown] [76.93.15.33]) by fe-sfbay-09.sun.com (Sun Java(tm) System Messaging Server 7u2-7.02 64bit (built Apr 16 2009)) with ESMTPSA id <0KNH00JEPA7K2L70@fe-sfbay-09.sun.com>; Mon, 27 Jul 2009 23:04:32 -0700 (PDT) Date: Mon, 27 Jul 2009 23:04:31 -0700 From: "Garrett D'Amore" Subject: Re: Update libchewing from 0.3.0 to 0.3.2 [PSARC/2009/416 Self Review] In-reply-to: <200907280546.n6S5k9AY004168@sac.sfbay.sun.com> Sender: Garrett.Damore@sun.com To: Yong Young Sun Cc: PSARC-ext@sun.com, gto-ext@sun.com Message-id: <4A6E94EF.3000807@sun.com> MIME-version: 1.0 Content-type: text/plain; CHARSET=US-ASCII; format=flowed Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 References: <200907280546.n6S5k9AY004168@sac.sfbay.sun.com> User-Agent: Thunderbird 2.0.0.18 (X11/20081201) Status: RO Content-Length: 1625 Yong Young Sun wrote: > Template Version: @(#)sac_nextcase 1.68 02/23/09 SMI > This information is Copyright 2009 Sun Microsystems > 1. Introduction > 1.1. Project/Component Working Name: > Update libchewing from 0.3.0 to 0.3.2 > 1.2. Name of Document Author/Supplier: > Author: Yong Sun > 1.3 Date of This Document: > 27 July, 2009 > > 4. Technical Description > > libchewing is a popular library for Traditional Chinese input method engine > licensed in LGPLv2.1. And there are some input methods, like > iiimf-twle-chewing, scim-chewing depends on this library to provide input > services to users. > > The version currently shipped in nevada/opensolaris is 0.3.0, while the > community recently released a newer version, 0.3.2. In this new release, > the API/ABI compatiblities were broken, and some new features are added. > Do you have more information about what interfaces were broken, how they were broken, and what the likely impact upon users and developers is? What was the commitment level to the previous interfaces? > iiimf-twle-chewing and scim-chewing had been updated to work with 0.3.2, > we therefore need to deliver the updated version to nevada/opensolaris. > > The interfaces (header files and shared library) remain the same as > before. > Is there a previous ARC case number that we can look at? - Garrett > 6. Resources and Schedule > 6.4. Steering Committee requested information > 6.4.1. Consolidation C-team Name: > Globalization > 6.5. ARC review type: Automatic > 6.6. ARC Exposure: open > > From Alan.Hargreaves@sun.com Mon Jul 27 23:07:48 2009 Received: from newsunmail1brm.central.sun.com (newsunmail1brm.Central.Sun.COM [129.147.62.245]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id n6S67mND004781 for ; Mon, 27 Jul 2009 23:07:48 -0700 (PDT) Received: from nwk-avmta-1.SFBay.Sun.COM (nwk-avmta-1.SFBay.Sun.COM [129.146.11.74]) by newsunmail1brm.central.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id n6S67Nrc010295; Tue, 28 Jul 2009 00:07:47 -0600 (MDT) Received: from pmxchannel-daemon.nwk-avmta-1.sfbay.Sun.COM by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0KNH0090BACX5F00@nwk-avmta-1.sfbay.Sun.COM>; Mon, 27 Jul 2009 23:07:45 -0700 (PDT) Received: from sineb-mail-1.sun.com ([192.18.19.6]) by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KNH00F1SACWDDF0@nwk-avmta-1.sfbay.Sun.COM>; Mon, 27 Jul 2009 23:07:45 -0700 (PDT) Received: from fe-apac-05.sun.com (fe-apac-05.sun.com [192.18.19.176] (may be forged)) by sineb-mail-1.sun.com (8.13.6+Sun/8.12.9) with ESMTP id n6S67htY012992; Tue, 28 Jul 2009 06:07:43 +0000 (GMT) Received: from conversion-daemon.mail-apac.sun.com by mail-apac.sun.com (Sun Java(tm) System Messaging Server 7u2-7.02 64bit (built Apr 16 2009)) id <0KNH00D00A1G8F00@mail-apac.sun.com>; Tue, 28 Jul 2009 14:07:43 +0800 (SGT) Received: from [129.158.12.60] ([unknown] [129.158.12.60]) by mail-apac.sun.com (Sun Java(tm) System Messaging Server 7u2-7.02 64bit (built Apr 16 2009)) with ESMTPSA id <0KNH0072GACTO1D0@mail-apac.sun.com>; Tue, 28 Jul 2009 14:07:43 +0800 (SGT) Date: Tue, 28 Jul 2009 16:06:38 +1000 From: Alan Hargreaves Subject: Re: Update libchewing from 0.3.0 to 0.3.2 [PSARC/2009/416 Self Review] In-reply-to: <200907280546.n6S5k9AY004168@sac.sfbay.sun.com> Sender: Alan.Hargreaves@sun.com To: Yong Young Sun Cc: PSARC-ext@sun.com, gto-ext@sun.com Message-id: <4A6E956E.5000301@Sun.COM> MIME-version: 1.0 Content-type: text/plain; CHARSET=US-ASCII; format=flowed Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 References: <200907280546.n6S5k9AY004168@sac.sfbay.sun.com> User-Agent: Thunderbird 2.0.0.22 (X11/20090706) Status: RO Content-Length: 1914 I am concerned that this update breaks compatibility, yet is being done as a self review. Are there any other consumers of this library that could potentially be broken by this update? If so, how will this be dealt with? What binding are you looking for? As I only see nevada/opensolaris mentioned, I am assuming minor. Can you mention the case number which contains the prior interfaces/bindings? Regards, Alan Hargreaves Yong Young Sun wrote: > Template Version: @(#)sac_nextcase 1.68 02/23/09 SMI > This information is Copyright 2009 Sun Microsystems > 1. Introduction > 1.1. Project/Component Working Name: > Update libchewing from 0.3.0 to 0.3.2 > 1.2. Name of Document Author/Supplier: > Author: Yong Sun > 1.3 Date of This Document: > 27 July, 2009 > > 4. Technical Description > > libchewing is a popular library for Traditional Chinese input method engine > licensed in LGPLv2.1. And there are some input methods, like > iiimf-twle-chewing, scim-chewing depends on this library to provide input > services to users. > > The version currently shipped in nevada/opensolaris is 0.3.0, while the > community recently released a newer version, 0.3.2. In this new release, > the API/ABI compatiblities were broken, and some new features are added. > > iiimf-twle-chewing and scim-chewing had been updated to work with 0.3.2, > we therefore need to deliver the updated version to nevada/opensolaris. > > The interfaces (header files and shared library) remain the same as > before. > > 6. Resources and Schedule > 6.4. Steering Committee requested information > 6.4.1. Consolidation C-team Name: > Globalization > 6.5. ARC review type: Automatic > 6.6. ARC Exposure: open > > -- Alan Hargreaves - http://blogs.sun.com/tpenta Staff Engineer (Kernel/VOSJEC/Performance) Asia Pacific/Emerging Markets Sun Microsystems From Yong.Sun@sun.com Mon Jul 27 23:53:08 2009 Received: from sunmail3mpk.sfbay.sun.com (sunmail3mpk.SFBay.Sun.COM [129.146.11.52]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id n6S6r8Fq005218 for ; Mon, 27 Jul 2009 23:53:08 -0700 (PDT) Received: from brm-avmta-1.central.sun.com (brm-avmta-1.Central.Sun.COM [129.147.4.11]) by sunmail3mpk.sfbay.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id n6S6r1wj009196; Mon, 27 Jul 2009 23:53:07 -0700 (PDT) Received: from pmxchannel-daemon.brm-avmta-1.central.sun.com by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0KNH00D15CGHGL00@brm-avmta-1.central.sun.com>; Tue, 28 Jul 2009 00:53:05 -0600 (MDT) Received: from sineb-mail-1.sun.com ([192.18.19.6]) by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KNH00DAMCGG0W00@brm-avmta-1.central.sun.com>; Tue, 28 Jul 2009 00:53:05 -0600 (MDT) Received: from fe-apac-05.sun.com (fe-apac-05.sun.com [192.18.19.176] (may be forged)) by sineb-mail-1.sun.com (8.13.6+Sun/8.12.9) with ESMTP id n6S6r4dv016506; Tue, 28 Jul 2009 06:53:04 +0000 (GMT) Received: from conversion-daemon.mail-apac.sun.com by mail-apac.sun.com (Sun Java(tm) System Messaging Server 7u2-7.02 64bit (built Apr 16 2009)) id <0KNH00400CG7D400@mail-apac.sun.com>; Tue, 28 Jul 2009 14:53:04 +0800 (SGT) Received: from [129.158.150.46] ([unknown] [129.158.150.46]) by mail-apac.sun.com (Sun Java(tm) System Messaging Server 7u2-7.02 64bit (built Apr 16 2009)) with ESMTPSA id <0KNH0037OCGEY8I0@mail-apac.sun.com>; Tue, 28 Jul 2009 14:53:03 +0800 (SGT) Date: Tue, 28 Jul 2009 14:53:26 +0800 From: Yong Sun Subject: Re: Update libchewing from 0.3.0 to 0.3.2 [PSARC/2009/416 Self Review] In-reply-to: <4A6E956E.5000301@Sun.COM> Sender: Yong.Sun@sun.com To: Alan Hargreaves , gdamore@sun.com Cc: Yong Young Sun , PSARC-ext@sun.com, gto-ext@sun.com Message-id: <4A6EA066.206@Sun.COM> MIME-version: 1.0 Content-type: text/plain; CHARSET=US-ASCII; format=flowed Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 References: <200907280546.n6S5k9AY004168@sac.sfbay.sun.com> <4A6E956E.5000301@Sun.COM> User-Agent: Thunderbird 2.0.0.21 (X11/20090623) Status: RO Content-Length: 2673 Hi, Alan, Garrett, Thanks for reviewing. The initial integration of libchewing is covered in PSARC/2005/525, as a project private interface, located in /usr/lib/iiim. And when scim is integrated (covered in PSARC/2008/418), libchewing is required both by scim-chewing and iiimf-twle-chewing, so it's moved to /usr/lib. Currently, there is no other client applications depends on libchewing, besides scim-chewing and iiimf-twle-chewing. Here is the release announcement for version 0.3.2, which lists the what's new, http://groups.google.com/group/chewing/browse_thread/thread/0067e04c8ea29ff3, please read the bottom half for the English version. And yes, I only require a minor binding. I will update the case material to include this info. Regards, Alan Hargreaves wrote: > I am concerned that this update breaks compatibility, yet is being > done as a self review. Are there any other consumers of this library > that could potentially be broken by this update? If so, how will this > be dealt with? > > What binding are you looking for? As I only see nevada/opensolaris > mentioned, I am assuming minor. > > Can you mention the case number which contains the prior > interfaces/bindings? > > Regards, > Alan Hargreaves > > > Yong Young Sun wrote: >> Template Version: @(#)sac_nextcase 1.68 02/23/09 SMI >> This information is Copyright 2009 Sun Microsystems >> 1. Introduction >> 1.1. Project/Component Working Name: >> Update libchewing from 0.3.0 to 0.3.2 >> 1.2. Name of Document Author/Supplier: >> Author: Yong Sun >> 1.3 Date of This Document: >> 27 July, 2009 >> >> 4. Technical Description >> >> libchewing is a popular library for Traditional Chinese input >> method engine >> licensed in LGPLv2.1. And there are some input methods, like >> iiimf-twle-chewing, scim-chewing depends on this library to >> provide input >> services to users. >> >> The version currently shipped in nevada/opensolaris is 0.3.0, >> while the >> community recently released a newer version, 0.3.2. In this new >> release, >> the API/ABI compatiblities were broken, and some new features are >> added. >> >> iiimf-twle-chewing and scim-chewing had been updated to work with >> 0.3.2, >> we therefore need to deliver the updated version to >> nevada/opensolaris. >> >> The interfaces (header files and shared library) remain the same as >> before. >> >> 6. Resources and Schedule >> 6.4. Steering Committee requested information >> 6.4.1. Consolidation C-team Name: >> Globalization >> 6.5. ARC review type: Automatic >> 6.6. ARC Exposure: open >> >> > From Alan.Hargreaves@sun.com Tue Jul 28 00:08:15 2009 Received: from newsunmail1brm.central.sun.com (newsunmail1brm.Central.Sun.COM [129.147.62.245]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id n6S78EMQ009731 for ; Tue, 28 Jul 2009 00:08:14 -0700 (PDT) Received: from nwk-avmta-1.SFBay.Sun.COM (nwk-avmta-1.SFBay.Sun.COM [129.146.11.74]) by newsunmail1brm.central.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id n6S78B6k036917; Tue, 28 Jul 2009 01:08:14 -0600 (MDT) Received: from pmxchannel-daemon.nwk-avmta-1.sfbay.Sun.COM by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0KNH00L09D5P8N00@nwk-avmta-1.sfbay.Sun.COM>; Tue, 28 Jul 2009 00:08:13 -0700 (PDT) Received: from sineb-mail-1.sun.com ([192.18.19.6]) by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KNH009IZD5OC8D0@nwk-avmta-1.sfbay.Sun.COM>; Tue, 28 Jul 2009 00:08:13 -0700 (PDT) Received: from fe-apac-05.sun.com (fe-apac-05.sun.com [192.18.19.176] (may be forged)) by sineb-mail-1.sun.com (8.13.6+Sun/8.12.9) with ESMTP id n6S78BfP017656; Tue, 28 Jul 2009 07:08:12 +0000 (GMT) Received: from conversion-daemon.mail-apac.sun.com by mail-apac.sun.com (Sun Java(tm) System Messaging Server 7u2-7.02 64bit (built Apr 16 2009)) id <0KNH00B00CY9TI00@mail-apac.sun.com>; Tue, 28 Jul 2009 15:08:12 +0800 (SGT) Received: from [129.158.12.60] ([unknown] [129.158.12.60]) by mail-apac.sun.com (Sun Java(tm) System Messaging Server 7u2-7.02 64bit (built Apr 16 2009)) with ESMTPSA id <0KNH007FED5LO1F0@mail-apac.sun.com>; Tue, 28 Jul 2009 15:08:11 +0800 (SGT) Date: Tue, 28 Jul 2009 17:07:06 +1000 From: Alan Hargreaves Subject: Re: Update libchewing from 0.3.0 to 0.3.2 [PSARC/2009/416 Self Review] In-reply-to: <4A6EA066.206@Sun.COM> Sender: Alan.Hargreaves@sun.com To: Yong Sun Cc: gdamore@sun.com, Yong Young Sun , PSARC-ext@sun.com, gto-ext@sun.com Message-id: <4A6EA39A.4060806@Sun.COM> MIME-version: 1.0 Content-type: text/plain; CHARSET=US-ASCII; format=flowed Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 References: <200907280546.n6S5k9AY004168@sac.sfbay.sun.com> <4A6E956E.5000301@Sun.COM> <4A6EA066.206@Sun.COM> User-Agent: Thunderbird 2.0.0.22 (X11/20090706) Status: RO Content-Length: 3496 So, if I read the prior cases correctly, you are promoting libchewing form Project/Private to something else (Committed?) and we do have some incompatible changes to interfaces. Can you perhaps outline what the incompatible changes are? Might it be a better idea to leave the stability of libchewing as it currently is (Project/Private under the old stability system) and have contract scim-chewing take out a contract? My feeling is that if you want to raise the stability, this case should probably be promoted to a fast track. Regards, Alan Hargreaves Yong Sun wrote: > Hi, Alan, Garrett, > > Thanks for reviewing. > > The initial integration of libchewing is covered in PSARC/2005/525, as > a project private interface, located in /usr/lib/iiim. And when scim > is integrated (covered in PSARC/2008/418), libchewing is required both > by scim-chewing and iiimf-twle-chewing, so it's moved to /usr/lib. > > Currently, there is no other client applications depends on > libchewing, besides scim-chewing and iiimf-twle-chewing. > > Here is the release announcement for version 0.3.2, which lists the > what's new, > http://groups.google.com/group/chewing/browse_thread/thread/0067e04c8ea29ff3, > please read the bottom half for the English version. > > And yes, I only require a minor binding. I will update the case > material to include this info. > > Regards, > > Alan Hargreaves wrote: >> I am concerned that this update breaks compatibility, yet is being >> done as a self review. Are there any other consumers of this library >> that could potentially be broken by this update? If so, how will this >> be dealt with? >> >> What binding are you looking for? As I only see nevada/opensolaris >> mentioned, I am assuming minor. >> >> Can you mention the case number which contains the prior >> interfaces/bindings? >> >> Regards, >> Alan Hargreaves >> >> >> Yong Young Sun wrote: >>> Template Version: @(#)sac_nextcase 1.68 02/23/09 SMI >>> This information is Copyright 2009 Sun Microsystems >>> 1. Introduction >>> 1.1. Project/Component Working Name: >>> Update libchewing from 0.3.0 to 0.3.2 >>> 1.2. Name of Document Author/Supplier: >>> Author: Yong Sun >>> 1.3 Date of This Document: >>> 27 July, 2009 >>> >>> 4. Technical Description >>> >>> libchewing is a popular library for Traditional Chinese input >>> method engine >>> licensed in LGPLv2.1. And there are some input methods, like >>> iiimf-twle-chewing, scim-chewing depends on this library to >>> provide input >>> services to users. >>> >>> The version currently shipped in nevada/opensolaris is 0.3.0, >>> while the >>> community recently released a newer version, 0.3.2. In this new >>> release, >>> the API/ABI compatiblities were broken, and some new features >>> are added. >>> >>> iiimf-twle-chewing and scim-chewing had been updated to work >>> with 0.3.2, >>> we therefore need to deliver the updated version to >>> nevada/opensolaris. >>> >>> The interfaces (header files and shared library) remain the same as >>> before. >>> >>> 6. Resources and Schedule >>> 6.4. Steering Committee requested information >>> 6.4.1. Consolidation C-team Name: >>> Globalization >>> 6.5. ARC review type: Automatic >>> 6.6. ARC Exposure: open >>> >>> >> > -- Alan Hargreaves - http://blogs.sun.com/tpenta Staff Engineer (Kernel/VOSJEC/Performance) Asia Pacific/Emerging Markets Sun Microsystems From Alan.Hargreaves@Sun.COM Tue Jul 28 00:34:56 2009 Received: from sunmail2sca.sfbay.sun.com (sunmail2sca.SFBay.Sun.COM [129.145.155.234]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id n6S7YuS4010612 for ; Tue, 28 Jul 2009 00:34:56 -0700 (PDT) Received: from brm-avmta-1.central.sun.com (brm-avmta-1.Central.Sun.COM [129.147.4.11]) by sunmail2sca.sfbay.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id n6S7YuMF016661; Tue, 28 Jul 2009 00:34:56 -0700 (PDT) Received: from pmxchannel-daemon.brm-avmta-1.central.sun.com by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0KNH00H01EE8V100@brm-avmta-1.central.sun.com>; Tue, 28 Jul 2009 01:34:56 -0600 (MDT) Received: from sineb-mail-2.sun.com ([192.18.19.7]) by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KNH00DX8EE60Q30@brm-avmta-1.central.sun.com>; Tue, 28 Jul 2009 01:34:55 -0600 (MDT) Received: from fe-apac-06.sun.com (fe-apac-06.sun.com [192.18.19.177] (may be forged)) by sineb-mail-2.sun.com (8.13.6+Sun/8.12.9) with ESMTP id n6S7Yr5u017575; Tue, 28 Jul 2009 07:34:53 +0000 (GMT) Received: from conversion-daemon.mail-apac.sun.com by mail-apac.sun.com (Sun Java(tm) System Messaging Server 7u2-7.02 64bit (built Apr 16 2009)) id <0KNH00500E1IW800@mail-apac.sun.com>; Tue, 28 Jul 2009 15:34:53 +0800 (SGT) Received: from [129.158.12.60] ([unknown] [129.158.12.60]) by mail-apac.sun.com (Sun Java(tm) System Messaging Server 7u2-7.02 64bit (built Apr 16 2009)) with ESMTPSA id <0KNH001E9EE39PM0@mail-apac.sun.com>; Tue, 28 Jul 2009 15:34:53 +0800 (SGT) Date: Tue, 28 Jul 2009 17:33:48 +1000 From: Alan Hargreaves Subject: Re: Update libchewing from 0.3.0 to 0.3.2 [PSARC/2009/416 Self Review] In-reply-to: <4A6EA39A.4060806@Sun.COM> Sender: Alan.Hargreaves@Sun.COM To: Yong Sun Cc: gdamore@Sun.COM, Yong Young Sun , PSARC-ext@Sun.COM, gto-ext@Sun.COM Message-id: <4A6EA9DC.5050104@Sun.COM> MIME-version: 1.0 Content-type: text/html; CHARSET=US-ASCII Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 References: <200907280546.n6S5k9AY004168@sac.sfbay.sun.com> <4A6E956E.5000301@Sun.COM> <4A6EA066.206@Sun.COM> <4A6EA39A.4060806@Sun.COM> User-Agent: Thunderbird 2.0.0.22 (X11/20090706) Status: RO Content-Length: 5326

You can find a contract template at http://sac.sfbay/arc/ARC-Templates/contract

Regards,
Alan Hargreaves


Alan Hargreaves wrote:
So, if I read the prior cases correctly, you are promoting libchewing form Project/Private to something else (Committed?) and we do have some incompatible changes to interfaces.

Can you perhaps outline what the incompatible changes are?

Might it be a better idea to leave the stability of libchewing as it currently is (Project/Private under the old stability system) and have contract scim-chewing take out a contract?

My feeling is that if you want to raise the stability, this case should probably be promoted to a fast track.

Regards,
Alan Hargreaves


Yong Sun wrote:
Hi, Alan, Garrett,

Thanks for reviewing.

The initial integration of libchewing is covered in PSARC/2005/525, as a project private interface, located in /usr/lib/iiim. And when scim is integrated (covered in PSARC/2008/418), libchewing is required both by scim-chewing and iiimf-twle-chewing, so it's moved to /usr/lib.

Currently, there is no other client applications depends on libchewing, besides scim-chewing and iiimf-twle-chewing.

Here is the release announcement for version 0.3.2, which lists the what's new,  http://groups.google.com/group/chewing/browse_thread/thread/0067e04c8ea29ff3, please read the bottom half for the English version.

And yes, I only require a minor binding. I will update the case material to include this info.

Regards,

Alan Hargreaves wrote:
I am concerned that this update breaks compatibility, yet is being done as a self review. Are there any other consumers of this library that could potentially be broken by this update? If so, how will this be dealt with?

What binding are you looking for? As I only see nevada/opensolaris mentioned, I am assuming minor.

Can you mention the case number which contains the prior interfaces/bindings?

Regards,
Alan Hargreaves


Yong Young Sun wrote:
Template Version: @(#)sac_nextcase 1.68 02/23/09 SMI
This information is Copyright 2009 Sun Microsystems
1. Introduction
    1.1. Project/Component Working Name:
     Update libchewing from 0.3.0 to 0.3.2
    1.2. Name of Document Author/Supplier:
     Author:  Yong Sun
    1.3  Date of This Document:
    27 July, 2009

4. Technical Description

    libchewing is a popular library for Traditional Chinese input method engine
    licensed in LGPLv2.1. And there are some input methods, like
    iiimf-twle-chewing, scim-chewing depends on this library to provide input
    services to users.

    The version currently shipped in nevada/opensolaris is 0.3.0, while the
    community recently released a newer version, 0.3.2. In this new release,
    the API/ABI compatiblities were broken, and some new features are added.

    iiimf-twle-chewing and scim-chewing had been updated to work with 0.3.2,
    we therefore need to deliver the updated version to nevada/opensolaris.

    The interfaces (header files and shared library) remain the same as
    before.

6. Resources and Schedule
    6.4. Steering Committee requested information
       6.4.1. Consolidation C-team Name:
        Globalization
    6.5. ARC review type: Automatic
    6.6. ARC Exposure: open

  




-- 
Alan Hargreaves - http://blogs.sun.com/tpenta
Staff Engineer (Kernel/VOSJEC/Performance)
Asia Pacific/Emerging Markets
Sun Microsystems
From Yong.Sun@sun.com Tue Jul 28 01:15:58 2009 Received: from sunmail4.singapore.sun.com (sunmail4.Singapore.Sun.COM [129.158.71.19]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id n6S8FvT7011805 for ; Tue, 28 Jul 2009 01:15:58 -0700 (PDT) Received: from nwk-avmta-1.SFBay.Sun.COM (nwk-avmta-1.SFBay.Sun.COM [129.146.11.74]) by sunmail4.singapore.sun.com (8.13.4+Sun/8.13.3/ENSMAIL,v2.2) with ESMTP id n6S8FUaS007392; Tue, 28 Jul 2009 16:15:56 +0800 (SGT) Received: from pmxchannel-daemon.nwk-avmta-1.sfbay.Sun.COM by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0KNH00B0JGADEY00@nwk-avmta-1.sfbay.Sun.COM>; Tue, 28 Jul 2009 01:15:49 -0700 (PDT) Received: from sineb-mail-1.sun.com ([192.18.19.6]) by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KNH000AQGABV4C0@nwk-avmta-1.sfbay.Sun.COM>; Tue, 28 Jul 2009 01:15:48 -0700 (PDT) Received: from fe-apac-05.sun.com (fe-apac-05.sun.com [192.18.19.176] (may be forged)) by sineb-mail-1.sun.com (8.13.6+Sun/8.12.9) with ESMTP id n6S8Fl6n022620; Tue, 28 Jul 2009 08:15:47 +0000 (GMT) Received: from conversion-daemon.mail-apac.sun.com by mail-apac.sun.com (Sun Java(tm) System Messaging Server 7u2-7.02 64bit (built Apr 16 2009)) id <0KNH00E00G19TV00@mail-apac.sun.com>; Tue, 28 Jul 2009 16:15:47 +0800 (SGT) Received: from [129.158.150.46] ([unknown] [129.158.150.46]) by mail-apac.sun.com (Sun Java(tm) System Messaging Server 7u2-7.02 64bit (built Apr 16 2009)) with ESMTPSA id <0KNH0039LGAAY8M0@mail-apac.sun.com>; Tue, 28 Jul 2009 16:15:47 +0800 (SGT) Date: Tue, 28 Jul 2009 16:16:09 +0800 From: Yong Sun Subject: Re: Update libchewing from 0.3.0 to 0.3.2 [PSARC/2009/416 Self Review] In-reply-to: <4A6EA39A.4060806@Sun.COM> Sender: Yong.Sun@sun.com To: Alan Hargreaves Cc: gdamore@sun.com, Yong Young Sun , PSARC-ext@sun.com, gto-ext@sun.com Message-id: <4A6EB3C9.8000402@Sun.COM> MIME-version: 1.0 Content-type: multipart/mixed; boundary="Boundary_(ID_gq5HQl+DEe/XVR+4/rR81w)" X-PMX-Version: 5.4.1.325704 References: <200907280546.n6S5k9AY004168@sac.sfbay.sun.com> <4A6E956E.5000301@Sun.COM> <4A6EA066.206@Sun.COM> <4A6EA39A.4060806@Sun.COM> User-Agent: Thunderbird 2.0.0.21 (X11/20090623) Status: RO Content-Length: 12111 This is a multi-part message in MIME format. --Boundary_(ID_gq5HQl+DEe/XVR+4/rR81w) Content-type: text/plain; CHARSET=US-ASCII; format=flowed Content-transfer-encoding: 7BIT No, I don't intend to promote it to committed, probably uncommitted is fine. I attached all API changes (in diff format), most of them are about initialization, configuration, and candidate iterating. And some interfaces are removed (or moved to internal private), like char/utf8_char utilities, user_phrase manipulating, zuin/pinyin utilities. And libchewing, scim-chewing, iiimf-twle-chewing are all community opensource softwares. I don't know if we need/could have a contract for them. Regards, Alan Hargreaves wrote: > So, if I read the prior cases correctly, you are promoting libchewing > form Project/Private to something else (Committed?) and we do have > some incompatible changes to interfaces. > > Can you perhaps outline what the incompatible changes are? > > Might it be a better idea to leave the stability of libchewing as it > currently is (Project/Private under the old stability system) and have > contract scim-chewing take out a contract? > > My feeling is that if you want to raise the stability, this case > should probably be promoted to a fast track. > > Regards, > Alan Hargreaves > > > Yong Sun wrote: >> Hi, Alan, Garrett, >> >> Thanks for reviewing. >> >> The initial integration of libchewing is covered in PSARC/2005/525, >> as a project private interface, located in /usr/lib/iiim. And when >> scim is integrated (covered in PSARC/2008/418), libchewing is >> required both by scim-chewing and iiimf-twle-chewing, so it's moved >> to /usr/lib. >> >> Currently, there is no other client applications depends on >> libchewing, besides scim-chewing and iiimf-twle-chewing. >> >> Here is the release announcement for version 0.3.2, which lists the >> what's new, >> http://groups.google.com/group/chewing/browse_thread/thread/0067e04c8ea29ff3, >> please read the bottom half for the English version. >> >> And yes, I only require a minor binding. I will update the case >> material to include this info. >> >> Regards, >> >> Alan Hargreaves wrote: >>> I am concerned that this update breaks compatibility, yet is being >>> done as a self review. Are there any other consumers of this library >>> that could potentially be broken by this update? If so, how will >>> this be dealt with? >>> >>> What binding are you looking for? As I only see nevada/opensolaris >>> mentioned, I am assuming minor. >>> >>> Can you mention the case number which contains the prior >>> interfaces/bindings? >>> >>> Regards, >>> Alan Hargreaves >>> >>> >>> Yong Young Sun wrote: >>>> Template Version: @(#)sac_nextcase 1.68 02/23/09 SMI >>>> This information is Copyright 2009 Sun Microsystems >>>> 1. Introduction >>>> 1.1. Project/Component Working Name: >>>> Update libchewing from 0.3.0 to 0.3.2 >>>> 1.2. Name of Document Author/Supplier: >>>> Author: Yong Sun >>>> 1.3 Date of This Document: >>>> 27 July, 2009 >>>> >>>> 4. Technical Description >>>> >>>> libchewing is a popular library for Traditional Chinese input >>>> method engine >>>> licensed in LGPLv2.1. And there are some input methods, like >>>> iiimf-twle-chewing, scim-chewing depends on this library to >>>> provide input >>>> services to users. >>>> >>>> The version currently shipped in nevada/opensolaris is 0.3.0, >>>> while the >>>> community recently released a newer version, 0.3.2. In this new >>>> release, >>>> the API/ABI compatiblities were broken, and some new features >>>> are added. >>>> >>>> iiimf-twle-chewing and scim-chewing had been updated to work >>>> with 0.3.2, >>>> we therefore need to deliver the updated version to >>>> nevada/opensolaris. >>>> >>>> The interfaces (header files and shared library) remain the >>>> same as >>>> before. >>>> >>>> 6. Resources and Schedule >>>> 6.4. Steering Committee requested information >>>> 6.4.1. Consolidation C-team Name: >>>> Globalization >>>> 6.5. ARC review type: Automatic >>>> 6.6. ARC Exposure: open >>>> >>>> >>> >> > --Boundary_(ID_gq5HQl+DEe/XVR+4/rR81w) Content-type: text/plain; name=chewing_api_changes.diff Content-transfer-encoding: 7BIT Content-disposition: inline; filename=chewing_api_changes.diff --- chewing-0.3.0/1 2009-07-28 15:42:15.671765769 +0800 +++ chewing-0.3.2/1 2009-07-28 15:41:49.757000958 +0800 @@ -1,18 +1,22 @@ -char.h:int GetCharFirst( Word *, uint16 ); -char.h:int GetCharNext ( Word * ); -char.h:int InitChar( const char * ); -chewing-utf8-util.h:char *ueStrSeek( char *src, size_t n ); -chewing-utf8-util.h:int ueBytesFromChar( unsigned char b ); -chewing-utf8-util.h:int ueStrLen( char *str ); -chewing-utf8-util.h:int ueStrNCpy( char dest[], const char *src, size_t n, int end ); +chewingio.h:char* chewing_get_KBString( ChewingContext * ); chewingio.h:ChewingContext *chewing_new(); chewingio.h:int chewing_Configure( ChewingContext *, ChewingConfigData *pcd ); +chewingio.h:int chewing_get_addPhraseDirection( ChewingContext * ); +chewingio.h:int chewing_get_autoShiftCur( ChewingContext * ); +chewingio.h:int chewing_get_candPerPage( ChewingContext * ); chewingio.h:int chewing_get_ChiEngMode( ChewingContext * ); +chewingio.h:int chewing_get_easySymbolInput( ChewingContext * ); +chewingio.h:int chewing_get_escCleanAllBuf( ChewingContext * ); +chewingio.h:int chewing_get_hsuSelKeyType( ChewingContext * ); +chewingio.h:int chewing_get_KBType( ChewingContext * ); +chewingio.h:int chewing_get_maxChiSymbolLen( ChewingContext * ); +chewingio.h:int chewing_get_phoneSeqLen( ChewingContext * ); +chewingio.h:int chewing_get_phraseChoiceRearward( ChewingContext * ); chewingio.h:int chewing_get_ShapeMode( ChewingContext * ); +chewingio.h:int chewing_get_spaceAsSelection( ChewingContext * ); chewingio.h:int chewing_handle_Backspace( ChewingContext * ); chewingio.h:int chewing_handle_Capslock( ChewingContext * ); chewingio.h:int chewing_handle_CtrlNum( ChewingContext *, int key ); -chewingio.h:int chewing_handle_CtrlOption( ChewingContext *, int key ); chewingio.h:int chewing_handle_DblTab( ChewingContext * ); chewingio.h:int chewing_handle_Default( ChewingContext *, int key ); chewingio.h:int chewing_handle_Del( ChewingContext * ); @@ -23,6 +27,8 @@ chewingio.h:int chewing_handle_Home( ChewingContext * ); chewingio.h:int chewing_handle_Left( ChewingContext * ); chewingio.h:int chewing_handle_Numlock( ChewingContext *, int key); +chewingio.h:int chewing_handle_PageDown( ChewingContext * ); +chewingio.h:int chewing_handle_PageUp( ChewingContext * ); chewingio.h:int chewing_handle_Right( ChewingContext * ); chewingio.h:int chewing_handle_ShiftLeft( ChewingContext * ); chewingio.h:int chewing_handle_ShiftRight( ChewingContext * ); @@ -30,46 +36,37 @@ chewingio.h:int chewing_handle_Space( ChewingContext * ); chewingio.h:int chewing_handle_Tab( ChewingContext * ); chewingio.h:int chewing_handle_Up( ChewingContext * ); +chewingio.h:int chewing_Init( const char *dataPath, const char *hashPath ); chewingio.h:int chewing_KBStr2Num( char str[] ); chewingio.h:int chewing_Reset( ChewingContext * ); chewingio.h:int chewing_set_KBType( ChewingContext *, int kbtype ); -chewingio.h:void chewing_free( ChewingContext * ); +chewingio.h:int* chewing_get_selKey( ChewingContext * ); +chewingio.h:uint16 *chewing_get_phoneSeq( ChewingContext * ); +chewingio.h:void chewing_delete( ChewingContext * ); +chewingio.h:void chewing_free( void * ); +chewingio.h:void chewing_set_addPhraseDirection( ChewingContext *, int direction ); +chewingio.h:void chewing_set_autoShiftCur( ChewingContext *, int mode ); +chewingio.h:void chewing_set_candPerPage( ChewingContext *, int n ); chewingio.h:void chewing_set_ChiEngMode( ChewingContext *, int mode ); +chewingio.h:void chewing_set_easySymbolInput( ChewingContext *, int mode ); +chewingio.h:void chewing_set_escCleanAllBuf( ChewingContext *, int mode ); +chewingio.h:void chewing_set_hsuSelKeyType( ChewingContext *, int mode ); +chewingio.h:void chewing_set_maxChiSymbolLen( ChewingContext *, int n ); +chewingio.h:void chewing_set_phraseChoiceRearward( ChewingContext *, int mode ); +chewingio.h:void chewing_set_selKey( ChewingContext *, int *selkeys, int len ); chewingio.h:void chewing_set_ShapeMode( ChewingContext *, int mode ); +chewingio.h:void chewing_set_spaceAsSelection( ChewingContext *, int mode ); chewingio.h:void chewing_Terminate(); -dict.h:int GetPhraseFirst( Phrase *phr_ptr, int phone_phr_id ); -dict.h:int GetPhraseNext ( Phrase *phr_ptr ); -dict.h:int InitDict( const char * ); -global.h:int ChoiceEndChoice( ChewingData * ); -global.h:int ChoiceFirstAvail( ChewingData * ); -global.h:int ChoiceNextAvail( ChewingData * ); -global.h:int ChoicePrevAvail( ChewingData * ); -global.h:int ChoiceSelect( ChewingData *, int selectNo ); -global.h:int IsIntersect( IntervalType in1, IntervalType in2 ); -global.h:int PhoneFromKey( char *pho, const char *inputkey, int kbtype, int searchTimes ); -global.h:int PhoneInxFromKey( int key, int type, int kbtype, int searchTimes ); -global.h:int TreeFindPhrase( int begin, int end, const uint16 *phoneSeq ); -global.h:uint16 UintFromPhone( const char *phone ); -global.h:uint16 UintFromPhoneInx( const int ph_inx[] ); -global.h:void ReadTree( const char * ); -hanyupinyin.h:int HanyuPinYinToZuin( char *pinyinKeySeq, char *zuinKeySeq ); -hash.h:HASH_ITEM *HashFindEntry( const uint16 phoneSeq[], const char wordSeq[] ); -hash.h:HASH_ITEM *HashFindPhone( const uint16 phoneSeq[] ); -hash.h:HASH_ITEM *HashFindPhonePhrase( const uint16 phoneSeq[], HASH_ITEM *pHashLast ); -hash.h:HASH_ITEM *HashInsert( UserPhraseData *pData ); -hash.h:int AlcUserPhraseSeq( UserPhraseData *pData, int phonelen, int wordlen ); -hash.h:int ReadHash( const char *path ); -hash.h:void FreeHashTable( void ); -hash.h:void HashModify( HASH_ITEM *pItem ); mod_aux.h:char *chewing_aux_String( ChewingContext * ); mod_aux.h:char *chewing_buffer_String( ChewingContext * ); mod_aux.h:char *chewing_cand_String( ChewingContext * ); mod_aux.h:char *chewing_commit_String( ChewingContext * ); -mod_aux.h:char *chewing_cursor_Current( ChewingContext * ); +mod_aux.h:char *chewing_kbtype_String( ChewingContext * ); mod_aux.h:char *chewing_zuin_String( ChewingContext *, int *zuin_count ); mod_aux.h:int chewing_aux_Check( ChewingContext * ); mod_aux.h:int chewing_aux_Length( ChewingContext * ); mod_aux.h:int chewing_buffer_Check( ChewingContext * ); +mod_aux.h:int chewing_buffer_Len( ChewingContext * ); mod_aux.h:int chewing_cand_CheckDone( ChewingContext * ); mod_aux.h:int chewing_cand_ChoicePerPage( ChewingContext * ); mod_aux.h:int chewing_cand_CurrentPage( ChewingContext * ); @@ -77,14 +74,14 @@ mod_aux.h:int chewing_cand_TotalChoice( ChewingContext * ); mod_aux.h:int chewing_cand_TotalPage( ChewingContext * ); mod_aux.h:int chewing_commit_Check( ChewingContext * ); +mod_aux.h:int chewing_cursor_Current( ChewingContext * ); +mod_aux.h:int chewing_interval_hasNext( ChewingContext * ); +mod_aux.h:int chewing_kbtype_hasNext( ChewingContext * ); +mod_aux.h:int chewing_kbtype_Total( ChewingContext * ); mod_aux.h:int chewing_keystroke_CheckIgnore( ChewingContext * ); mod_aux.h:int chewing_zuin_Check( ChewingContext * ); mod_aux.h:void chewing_cand_Enumerate( ChewingContext * ); -userphrase.h:int UserUpdatePhrase( const uint16 phoneSeq[], const char wordSeq[] ); -userphrase.h:UserPhraseData *UserGetPhraseFirst( const uint16 phoneSeq[] ); -userphrase.h:UserPhraseData *UserGetPhraseNext( const uint16 phoneSeq[] ); -zuin.h:int ZuinIsEntering( ZuinData * ); -zuin.h:int ZuinPhoInput( ZuinData *,int key ); /* assume `key' is "ascii" code. */ -zuin.h:int ZuinRemoveAll( ZuinData * ); -zuin.h:int ZuinRemoveLast( ZuinData * ); +mod_aux.h:void chewing_interval_Enumerate( ChewingContext * ); +mod_aux.h:void chewing_interval_Get( ChewingContext *, IntervalType *it ); +mod_aux.h:void chewing_kbtype_Enumerate( ChewingContext * ); --Boundary_(ID_gq5HQl+DEe/XVR+4/rR81w)-- From Alan.Hargreaves@Sun.COM Tue Jul 28 01:20:16 2009 Received: from sunmail5.uk.sun.com (sunmail5.UK.Sun.COM [129.156.85.165]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id n6S8KG7K011843 for ; Tue, 28 Jul 2009 01:20:16 -0700 (PDT) Received: from nwk-avmta-2.sfbay.sun.com (nwk-avmta-2.SFBay.Sun.COM [129.145.155.6]) by sunmail5.uk.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id n6S8AE1v022860; Tue, 28 Jul 2009 09:20:13 +0100 (BST) Received: from pmxchannel-daemon.nwk-avmta-2.sfbay.sun.com by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0KNH00403GHJP200@nwk-avmta-2.sfbay.sun.com>; Tue, 28 Jul 2009 01:20:07 -0700 (PDT) Received: from sineb-mail-1.sun.com ([192.18.19.6]) by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KNH00MXSGHHOA40@nwk-avmta-2.sfbay.sun.com>; Tue, 28 Jul 2009 01:20:06 -0700 (PDT) Received: from fe-apac-05.sun.com (fe-apac-05.sun.com [192.18.19.176] (may be forged)) by sineb-mail-1.sun.com (8.13.6+Sun/8.12.9) with ESMTP id n6S8K5Pe022924; Tue, 28 Jul 2009 08:20:05 +0000 (GMT) Received: from conversion-daemon.mail-apac.sun.com by mail-apac.sun.com (Sun Java(tm) System Messaging Server 7u2-7.02 64bit (built Apr 16 2009)) id <0KNH00J00GFSHE00@mail-apac.sun.com>; Tue, 28 Jul 2009 16:20:05 +0800 (SGT) Received: from [129.158.12.60] ([unknown] [129.158.12.60]) by mail-apac.sun.com (Sun Java(tm) System Messaging Server 7u2-7.02 64bit (built Apr 16 2009)) with ESMTPSA id <0KNH007SUGHFO1H0@mail-apac.sun.com>; Tue, 28 Jul 2009 16:20:05 +0800 (SGT) Date: Tue, 28 Jul 2009 18:19:00 +1000 From: Alan Hargreaves Subject: Re: Update libchewing from 0.3.0 to 0.3.2 [PSARC/2009/416 Self Review] In-reply-to: <4A6EB3C9.8000402@Sun.COM> Sender: Alan.Hargreaves@Sun.COM To: Yong Sun Cc: gdamore@Sun.COM, Yong Young Sun , PSARC-ext@Sun.COM, gto-ext@Sun.COM Message-id: <4A6EB474.4060704@Sun.COM> MIME-version: 1.0 Content-type: text/plain; CHARSET=US-ASCII; format=flowed Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 References: <200907280546.n6S5k9AY004168@sac.sfbay.sun.com> <4A6E956E.5000301@Sun.COM> <4A6EA066.206@Sun.COM> <4A6EA39A.4060806@Sun.COM> <4A6EB3C9.8000402@Sun.COM> User-Agent: Thunderbird 2.0.0.22 (X11/20090706) Status: RO Content-Length: 4597 All that having a contract means is that within the developer groups working on these two projects for Solaris/OpenSolaris there is an agreement that if a change is to be made to the library that the scim people will be notified. This looks a lot closer to what you actually want. alan. Yong Sun wrote: > No, I don't intend to promote it to committed, probably uncommitted is > fine. > > I attached all API changes (in diff format), most of them are about > initialization, configuration, and candidate iterating. And some > interfaces are removed (or moved to internal private), like > char/utf8_char utilities, user_phrase manipulating, zuin/pinyin > utilities. > > And libchewing, scim-chewing, iiimf-twle-chewing are all community > opensource softwares. I don't know if we need/could have a contract > for them. > > Regards, > > Alan Hargreaves wrote: >> So, if I read the prior cases correctly, you are promoting libchewing >> form Project/Private to something else (Committed?) and we do have >> some incompatible changes to interfaces. >> >> Can you perhaps outline what the incompatible changes are? >> >> Might it be a better idea to leave the stability of libchewing as it >> currently is (Project/Private under the old stability system) and >> have contract scim-chewing take out a contract? >> >> My feeling is that if you want to raise the stability, this case >> should probably be promoted to a fast track. >> >> Regards, >> Alan Hargreaves >> >> >> Yong Sun wrote: >>> Hi, Alan, Garrett, >>> >>> Thanks for reviewing. >>> >>> The initial integration of libchewing is covered in PSARC/2005/525, >>> as a project private interface, located in /usr/lib/iiim. And when >>> scim is integrated (covered in PSARC/2008/418), libchewing is >>> required both by scim-chewing and iiimf-twle-chewing, so it's moved >>> to /usr/lib. >>> >>> Currently, there is no other client applications depends on >>> libchewing, besides scim-chewing and iiimf-twle-chewing. >>> >>> Here is the release announcement for version 0.3.2, which lists the >>> what's new, >>> http://groups.google.com/group/chewing/browse_thread/thread/0067e04c8ea29ff3, >>> please read the bottom half for the English version. >>> >>> And yes, I only require a minor binding. I will update the case >>> material to include this info. >>> >>> Regards, >>> >>> Alan Hargreaves wrote: >>>> I am concerned that this update breaks compatibility, yet is being >>>> done as a self review. Are there any other consumers of this >>>> library that could potentially be broken by this update? If so, how >>>> will this be dealt with? >>>> >>>> What binding are you looking for? As I only see nevada/opensolaris >>>> mentioned, I am assuming minor. >>>> >>>> Can you mention the case number which contains the prior >>>> interfaces/bindings? >>>> >>>> Regards, >>>> Alan Hargreaves >>>> >>>> >>>> Yong Young Sun wrote: >>>>> Template Version: @(#)sac_nextcase 1.68 02/23/09 SMI >>>>> This information is Copyright 2009 Sun Microsystems >>>>> 1. Introduction >>>>> 1.1. Project/Component Working Name: >>>>> Update libchewing from 0.3.0 to 0.3.2 >>>>> 1.2. Name of Document Author/Supplier: >>>>> Author: Yong Sun >>>>> 1.3 Date of This Document: >>>>> 27 July, 2009 >>>>> >>>>> 4. Technical Description >>>>> >>>>> libchewing is a popular library for Traditional Chinese input >>>>> method engine >>>>> licensed in LGPLv2.1. And there are some input methods, like >>>>> iiimf-twle-chewing, scim-chewing depends on this library to >>>>> provide input >>>>> services to users. >>>>> >>>>> The version currently shipped in nevada/opensolaris is 0.3.0, >>>>> while the >>>>> community recently released a newer version, 0.3.2. In this >>>>> new release, >>>>> the API/ABI compatiblities were broken, and some new features >>>>> are added. >>>>> >>>>> iiimf-twle-chewing and scim-chewing had been updated to work >>>>> with 0.3.2, >>>>> we therefore need to deliver the updated version to >>>>> nevada/opensolaris. >>>>> >>>>> The interfaces (header files and shared library) remain the >>>>> same as >>>>> before. >>>>> >>>>> 6. Resources and Schedule >>>>> 6.4. Steering Committee requested information >>>>> 6.4.1. Consolidation C-team Name: >>>>> Globalization >>>>> 6.5. ARC review type: Automatic >>>>> 6.6. ARC Exposure: open >>>>> >>>>> >>>> >>> >> > -- Alan Hargreaves - http://blogs.sun.com/tpenta Staff Engineer (Kernel/VOSJEC/Performance) Asia Pacific/Emerging Markets Sun Microsystems From Yong.Sun@sun.com Tue Jul 28 01:26:15 2009 Received: from sunmail2sca.sfbay.sun.com (sunmail2sca.SFBay.Sun.COM [129.145.155.234]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id n6S8QFeR011904 for ; Tue, 28 Jul 2009 01:26:15 -0700 (PDT) Received: from brm-avmta-1.central.sun.com (brm-avmta-1.Central.Sun.COM [129.147.4.11]) by sunmail2sca.sfbay.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id n6S8Q2pa004400; Tue, 28 Jul 2009 01:26:15 -0700 (PDT) Received: from pmxchannel-daemon.brm-avmta-1.central.sun.com by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0KNH0003BGRO3K00@brm-avmta-1.central.sun.com>; Tue, 28 Jul 2009 02:26:12 -0600 (MDT) Received: from sineb-mail-2.sun.com ([192.18.19.7]) by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KNH00D2CGRL0Q80@brm-avmta-1.central.sun.com>; Tue, 28 Jul 2009 02:26:10 -0600 (MDT) Received: from fe-apac-05.sun.com (fe-apac-05.sun.com [192.18.19.176] (may be forged)) by sineb-mail-2.sun.com (8.13.6+Sun/8.12.9) with ESMTP id n6S8Q8t0021011; Tue, 28 Jul 2009 08:26:08 +0000 (GMT) Received: from conversion-daemon.mail-apac.sun.com by mail-apac.sun.com (Sun Java(tm) System Messaging Server 7u2-7.02 64bit (built Apr 16 2009)) id <0KNH00J00GFSHD00@mail-apac.sun.com>; Tue, 28 Jul 2009 16:26:08 +0800 (SGT) Received: from [129.158.150.46] ([unknown] [129.158.150.46]) by mail-apac.sun.com (Sun Java(tm) System Messaging Server 7u2-7.02 64bit (built Apr 16 2009)) with ESMTPSA id <0KNH00JABGRJX000@mail-apac.sun.com>; Tue, 28 Jul 2009 16:26:08 +0800 (SGT) Date: Tue, 28 Jul 2009 16:26:31 +0800 From: Yong Sun Subject: Re: Update libchewing from 0.3.0 to 0.3.2 [PSARC/2009/416 Self Review] In-reply-to: <4A6EB474.4060704@Sun.COM> Sender: Yong.Sun@sun.com To: Alan Hargreaves Cc: gdamore@sun.com, Yong Young Sun , PSARC-ext@sun.com, gto-ext@sun.com Message-id: <4A6EB637.5020806@Sun.COM> MIME-version: 1.0 Content-type: text/plain; CHARSET=US-ASCII; format=flowed Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 References: <200907280546.n6S5k9AY004168@sac.sfbay.sun.com> <4A6E956E.5000301@Sun.COM> <4A6EA066.206@Sun.COM> <4A6EA39A.4060806@Sun.COM> <4A6EB3C9.8000402@Sun.COM> <4A6EB474.4060704@Sun.COM> User-Agent: Thunderbird 2.0.0.21 (X11/20090623) Status: RO Content-Length: 4825 Hi, Alan, We (G11N input-method engineer team) are actually the people who maintaining the solaris porting of libchewing, scim-chewing, and iiimf-twle-chewing (we also developed this one). :) Regards, Alan Hargreaves wrote: > All that having a contract means is that within the developer groups > working on these two projects for Solaris/OpenSolaris there is an > agreement that if a change is to be made to the library that the scim > people will be notified. > > This looks a lot closer to what you actually want. > > alan. > > Yong Sun wrote: >> No, I don't intend to promote it to committed, probably uncommitted >> is fine. >> >> I attached all API changes (in diff format), most of them are about >> initialization, configuration, and candidate iterating. And some >> interfaces are removed (or moved to internal private), like >> char/utf8_char utilities, user_phrase manipulating, zuin/pinyin >> utilities. >> >> And libchewing, scim-chewing, iiimf-twle-chewing are all community >> opensource softwares. I don't know if we need/could have a contract >> for them. >> >> Regards, >> >> Alan Hargreaves wrote: >>> So, if I read the prior cases correctly, you are promoting >>> libchewing form Project/Private to something else (Committed?) and >>> we do have some incompatible changes to interfaces. >>> >>> Can you perhaps outline what the incompatible changes are? >>> >>> Might it be a better idea to leave the stability of libchewing as it >>> currently is (Project/Private under the old stability system) and >>> have contract scim-chewing take out a contract? >>> >>> My feeling is that if you want to raise the stability, this case >>> should probably be promoted to a fast track. >>> >>> Regards, >>> Alan Hargreaves >>> >>> >>> Yong Sun wrote: >>>> Hi, Alan, Garrett, >>>> >>>> Thanks for reviewing. >>>> >>>> The initial integration of libchewing is covered in PSARC/2005/525, >>>> as a project private interface, located in /usr/lib/iiim. And when >>>> scim is integrated (covered in PSARC/2008/418), libchewing is >>>> required both by scim-chewing and iiimf-twle-chewing, so it's moved >>>> to /usr/lib. >>>> >>>> Currently, there is no other client applications depends on >>>> libchewing, besides scim-chewing and iiimf-twle-chewing. >>>> >>>> Here is the release announcement for version 0.3.2, which lists the >>>> what's new, >>>> http://groups.google.com/group/chewing/browse_thread/thread/0067e04c8ea29ff3, >>>> please read the bottom half for the English version. >>>> >>>> And yes, I only require a minor binding. I will update the case >>>> material to include this info. >>>> >>>> Regards, >>>> >>>> Alan Hargreaves wrote: >>>>> I am concerned that this update breaks compatibility, yet is being >>>>> done as a self review. Are there any other consumers of this >>>>> library that could potentially be broken by this update? If so, >>>>> how will this be dealt with? >>>>> >>>>> What binding are you looking for? As I only see nevada/opensolaris >>>>> mentioned, I am assuming minor. >>>>> >>>>> Can you mention the case number which contains the prior >>>>> interfaces/bindings? >>>>> >>>>> Regards, >>>>> Alan Hargreaves >>>>> >>>>> >>>>> Yong Young Sun wrote: >>>>>> Template Version: @(#)sac_nextcase 1.68 02/23/09 SMI >>>>>> This information is Copyright 2009 Sun Microsystems >>>>>> 1. Introduction >>>>>> 1.1. Project/Component Working Name: >>>>>> Update libchewing from 0.3.0 to 0.3.2 >>>>>> 1.2. Name of Document Author/Supplier: >>>>>> Author: Yong Sun >>>>>> 1.3 Date of This Document: >>>>>> 27 July, 2009 >>>>>> >>>>>> 4. Technical Description >>>>>> >>>>>> libchewing is a popular library for Traditional Chinese input >>>>>> method engine >>>>>> licensed in LGPLv2.1. And there are some input methods, like >>>>>> iiimf-twle-chewing, scim-chewing depends on this library to >>>>>> provide input >>>>>> services to users. >>>>>> >>>>>> The version currently shipped in nevada/opensolaris is 0.3.0, >>>>>> while the >>>>>> community recently released a newer version, 0.3.2. In this >>>>>> new release, >>>>>> the API/ABI compatiblities were broken, and some new features >>>>>> are added. >>>>>> >>>>>> iiimf-twle-chewing and scim-chewing had been updated to work >>>>>> with 0.3.2, >>>>>> we therefore need to deliver the updated version to >>>>>> nevada/opensolaris. >>>>>> >>>>>> The interfaces (header files and shared library) remain the >>>>>> same as >>>>>> before. >>>>>> >>>>>> 6. Resources and Schedule >>>>>> 6.4. Steering Committee requested information >>>>>> 6.4.1. Consolidation C-team Name: >>>>>> Globalization >>>>>> 6.5. ARC review type: Automatic >>>>>> 6.6. ARC Exposure: open >>>>>> >>>>>> >>>>> >>>> >>> >> > From Alan.Hargreaves@sun.com Tue Jul 28 01:36:13 2009 Received: from sunmail4.singapore.sun.com (sunmail4.Singapore.Sun.COM [129.158.71.19]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id n6S8aCg3012006 for ; Tue, 28 Jul 2009 01:36:13 -0700 (PDT) Received: from brm-avmta-1.central.sun.com (brm-avmta-1.Central.Sun.COM [129.147.4.11]) by sunmail4.singapore.sun.com (8.13.4+Sun/8.13.3/ENSMAIL,v2.2) with ESMTP id n6S8ZuTE018118; Tue, 28 Jul 2009 16:36:11 +0800 (SGT) Received: from pmxchannel-daemon.brm-avmta-1.central.sun.com by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0KNH0010PH8A5700@brm-avmta-1.central.sun.com>; Tue, 28 Jul 2009 02:36:10 -0600 (MDT) Received: from sineb-mail-1.sun.com ([192.18.19.6]) by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KNH00DPJH880S70@brm-avmta-1.central.sun.com>; Tue, 28 Jul 2009 02:36:09 -0600 (MDT) Received: from fe-apac-06.sun.com (fe-apac-06.sun.com [192.18.19.177] (may be forged)) by sineb-mail-1.sun.com (8.13.6+Sun/8.12.9) with ESMTP id n6S8a8XY023986; Tue, 28 Jul 2009 08:36:08 +0000 (GMT) Received: from conversion-daemon.mail-apac.sun.com by mail-apac.sun.com (Sun Java(tm) System Messaging Server 7u2-7.02 64bit (built Apr 16 2009)) id <0KNH00400H5UVZ00@mail-apac.sun.com>; Tue, 28 Jul 2009 16:36:08 +0800 (SGT) Received: from [129.158.12.60] ([unknown] [129.158.12.60]) by mail-apac.sun.com (Sun Java(tm) System Messaging Server 7u2-7.02 64bit (built Apr 16 2009)) with ESMTPSA id <0KNH00GMEH86MM10@mail-apac.sun.com>; Tue, 28 Jul 2009 16:36:08 +0800 (SGT) Date: Tue, 28 Jul 2009 18:35:03 +1000 From: Alan Hargreaves Subject: Re: Update libchewing from 0.3.0 to 0.3.2 [PSARC/2009/416 Self Review] In-reply-to: <4A6EB637.5020806@Sun.COM> Sender: Alan.Hargreaves@sun.com To: Yong Sun Cc: gdamore@sun.com, Yong Young Sun , PSARC-ext@sun.com, gto-ext@sun.com Message-id: <4A6EB837.5080507@Sun.COM> MIME-version: 1.0 Content-type: text/plain; CHARSET=US-ASCII; format=flowed Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 References: <200907280546.n6S5k9AY004168@sac.sfbay.sun.com> <4A6E956E.5000301@Sun.COM> <4A6EA066.206@Sun.COM> <4A6EA39A.4060806@Sun.COM> <4A6EB3C9.8000402@Sun.COM> <4A6EB474.4060704@Sun.COM> <4A6EB637.5020806@Sun.COM> User-Agent: Thunderbird 2.0.0.22 (X11/20090706) Status: RO Content-Length: 5424 Excellent. That makes the contract easy and the case much simpler. I would suggest leave the stability of libchewing as it is. Fill out the contract form and place a copy in the directory of this case (as well as the email I think). Other PSARC folks, have I missed anything here? alan. Yong Sun wrote: > Hi, Alan, > > We (G11N input-method engineer team) are actually the people who > maintaining the solaris porting of libchewing, scim-chewing, and > iiimf-twle-chewing (we also developed this one). :) > > Regards, > > Alan Hargreaves wrote: >> All that having a contract means is that within the developer groups >> working on these two projects for Solaris/OpenSolaris there is an >> agreement that if a change is to be made to the library that the scim >> people will be notified. >> >> This looks a lot closer to what you actually want. >> >> alan. >> >> Yong Sun wrote: >>> No, I don't intend to promote it to committed, probably uncommitted >>> is fine. >>> >>> I attached all API changes (in diff format), most of them are about >>> initialization, configuration, and candidate iterating. And some >>> interfaces are removed (or moved to internal private), like >>> char/utf8_char utilities, user_phrase manipulating, zuin/pinyin >>> utilities. >>> >>> And libchewing, scim-chewing, iiimf-twle-chewing are all community >>> opensource softwares. I don't know if we need/could have a contract >>> for them. >>> >>> Regards, >>> >>> Alan Hargreaves wrote: >>>> So, if I read the prior cases correctly, you are promoting >>>> libchewing form Project/Private to something else (Committed?) and >>>> we do have some incompatible changes to interfaces. >>>> >>>> Can you perhaps outline what the incompatible changes are? >>>> >>>> Might it be a better idea to leave the stability of libchewing as >>>> it currently is (Project/Private under the old stability system) >>>> and have contract scim-chewing take out a contract? >>>> >>>> My feeling is that if you want to raise the stability, this case >>>> should probably be promoted to a fast track. >>>> >>>> Regards, >>>> Alan Hargreaves >>>> >>>> >>>> Yong Sun wrote: >>>>> Hi, Alan, Garrett, >>>>> >>>>> Thanks for reviewing. >>>>> >>>>> The initial integration of libchewing is covered in >>>>> PSARC/2005/525, as a project private interface, located in >>>>> /usr/lib/iiim. And when scim is integrated (covered in >>>>> PSARC/2008/418), libchewing is required both by scim-chewing and >>>>> iiimf-twle-chewing, so it's moved to /usr/lib. >>>>> >>>>> Currently, there is no other client applications depends on >>>>> libchewing, besides scim-chewing and iiimf-twle-chewing. >>>>> >>>>> Here is the release announcement for version 0.3.2, which lists >>>>> the what's new, >>>>> http://groups.google.com/group/chewing/browse_thread/thread/0067e04c8ea29ff3, >>>>> please read the bottom half for the English version. >>>>> >>>>> And yes, I only require a minor binding. I will update the case >>>>> material to include this info. >>>>> >>>>> Regards, >>>>> >>>>> Alan Hargreaves wrote: >>>>>> I am concerned that this update breaks compatibility, yet is >>>>>> being done as a self review. Are there any other consumers of >>>>>> this library that could potentially be broken by this update? If >>>>>> so, how will this be dealt with? >>>>>> >>>>>> What binding are you looking for? As I only see >>>>>> nevada/opensolaris mentioned, I am assuming minor. >>>>>> >>>>>> Can you mention the case number which contains the prior >>>>>> interfaces/bindings? >>>>>> >>>>>> Regards, >>>>>> Alan Hargreaves >>>>>> >>>>>> >>>>>> Yong Young Sun wrote: >>>>>>> Template Version: @(#)sac_nextcase 1.68 02/23/09 SMI >>>>>>> This information is Copyright 2009 Sun Microsystems >>>>>>> 1. Introduction >>>>>>> 1.1. Project/Component Working Name: >>>>>>> Update libchewing from 0.3.0 to 0.3.2 >>>>>>> 1.2. Name of Document Author/Supplier: >>>>>>> Author: Yong Sun >>>>>>> 1.3 Date of This Document: >>>>>>> 27 July, 2009 >>>>>>> >>>>>>> 4. Technical Description >>>>>>> >>>>>>> libchewing is a popular library for Traditional Chinese >>>>>>> input method engine >>>>>>> licensed in LGPLv2.1. And there are some input methods, like >>>>>>> iiimf-twle-chewing, scim-chewing depends on this library to >>>>>>> provide input >>>>>>> services to users. >>>>>>> >>>>>>> The version currently shipped in nevada/opensolaris is >>>>>>> 0.3.0, while the >>>>>>> community recently released a newer version, 0.3.2. In this >>>>>>> new release, >>>>>>> the API/ABI compatiblities were broken, and some new >>>>>>> features are added. >>>>>>> >>>>>>> iiimf-twle-chewing and scim-chewing had been updated to work >>>>>>> with 0.3.2, >>>>>>> we therefore need to deliver the updated version to >>>>>>> nevada/opensolaris. >>>>>>> >>>>>>> The interfaces (header files and shared library) remain the >>>>>>> same as >>>>>>> before. >>>>>>> >>>>>>> 6. Resources and Schedule >>>>>>> 6.4. Steering Committee requested information >>>>>>> 6.4.1. Consolidation C-team Name: >>>>>>> Globalization >>>>>>> 6.5. ARC review type: Automatic >>>>>>> 6.6. ARC Exposure: open >>>>>>> >>>>>>> >>>>>> >>>>> >>>> >>> >> > -- Alan Hargreaves - http://blogs.sun.com/tpenta Staff Engineer (Kernel/VOSJEC/Performance) Asia Pacific/Emerging Markets Sun Microsystems From Alan.Hargreaves@sun.com Tue Jul 28 01:53:12 2009 Received: from sunmail4.singapore.sun.com (sunmail4.Singapore.Sun.COM [129.158.71.19]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id n6S8rB01012206 for ; Tue, 28 Jul 2009 01:53:12 -0700 (PDT) Received: from nwk-avmta-1.SFBay.Sun.COM (nwk-avmta-1.SFBay.Sun.COM [129.146.11.74]) by sunmail4.singapore.sun.com (8.13.4+Sun/8.13.3/ENSMAIL,v2.2) with ESMTP id n6S8r7HA026029; Tue, 28 Jul 2009 16:53:10 +0800 (SGT) Received: from pmxchannel-daemon.nwk-avmta-1.sfbay.Sun.COM by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0KNH00I0JI0MJM00@nwk-avmta-1.sfbay.Sun.COM>; Tue, 28 Jul 2009 01:53:10 -0700 (PDT) Received: from sineb-mail-2.sun.com ([192.18.19.7]) by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KNH00DJWI0JH920@nwk-avmta-1.sfbay.Sun.COM>; Tue, 28 Jul 2009 01:53:08 -0700 (PDT) Received: from fe-apac-06.sun.com (fe-apac-06.sun.com [192.18.19.177] (may be forged)) by sineb-mail-2.sun.com (8.13.6+Sun/8.12.9) with ESMTP id n6S8r7cu022696; Tue, 28 Jul 2009 08:53:07 +0000 (GMT) Received: from conversion-daemon.mail-apac.sun.com by mail-apac.sun.com (Sun Java(tm) System Messaging Server 7u2-7.02 64bit (built Apr 16 2009)) id <0KNH00A00HNXR000@mail-apac.sun.com>; Tue, 28 Jul 2009 16:53:07 +0800 (SGT) Received: from [129.158.12.60] ([unknown] [129.158.12.60]) by mail-apac.sun.com (Sun Java(tm) System Messaging Server 7u2-7.02 64bit (built Apr 16 2009)) with ESMTPSA id <0KNH00G4UI0GMM20@mail-apac.sun.com>; Tue, 28 Jul 2009 16:53:06 +0800 (SGT) Date: Tue, 28 Jul 2009 18:52:02 +1000 From: Alan Hargreaves Subject: Re: Update libchewing from 0.3.0 to 0.3.2 [PSARC/2009/416 Self Review] In-reply-to: <4A6EB837.5080507@Sun.COM> Sender: Alan.Hargreaves@sun.com To: Yong Sun Cc: gdamore@sun.com, Yong Young Sun , PSARC-ext@sun.com, gto-ext@sun.com Message-id: <4A6EBC32.3030101@Sun.COM> MIME-version: 1.0 Content-type: text/plain; CHARSET=US-ASCII; format=flowed Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 References: <200907280546.n6S5k9AY004168@sac.sfbay.sun.com> <4A6E956E.5000301@Sun.COM> <4A6EA066.206@Sun.COM> <4A6EA39A.4060806@Sun.COM> <4A6EB3C9.8000402@Sun.COM> <4A6EB474.4060704@Sun.COM> <4A6EB637.5020806@Sun.COM> <4A6EB837.5080507@Sun.COM> User-Agent: Thunderbird 2.0.0.22 (X11/20090706) Status: RO Content-Length: 5935 Another option that you have, if we are talking about delivering into the same consolidation may also be instead of contracting the interfaces, use this case to extend the original to include the new code that needs the library. This would make some sense given that the one group is looking after everything here. alan. Alan Hargreaves wrote: > Excellent. That makes the contract easy and the case much simpler. I > would suggest leave the stability of libchewing as it is. Fill out the > contract form and place a copy in the directory of this case (as well > as the email I think). > > Other PSARC folks, have I missed anything here? > > alan. > > Yong Sun wrote: >> Hi, Alan, >> >> We (G11N input-method engineer team) are actually the people who >> maintaining the solaris porting of libchewing, scim-chewing, and >> iiimf-twle-chewing (we also developed this one). :) >> >> Regards, >> >> Alan Hargreaves wrote: >>> All that having a contract means is that within the developer groups >>> working on these two projects for Solaris/OpenSolaris there is an >>> agreement that if a change is to be made to the library that the >>> scim people will be notified. >>> >>> This looks a lot closer to what you actually want. >>> >>> alan. >>> >>> Yong Sun wrote: >>>> No, I don't intend to promote it to committed, probably uncommitted >>>> is fine. >>>> >>>> I attached all API changes (in diff format), most of them are about >>>> initialization, configuration, and candidate iterating. And some >>>> interfaces are removed (or moved to internal private), like >>>> char/utf8_char utilities, user_phrase manipulating, zuin/pinyin >>>> utilities. >>>> >>>> And libchewing, scim-chewing, iiimf-twle-chewing are all community >>>> opensource softwares. I don't know if we need/could have a contract >>>> for them. >>>> >>>> Regards, >>>> >>>> Alan Hargreaves wrote: >>>>> So, if I read the prior cases correctly, you are promoting >>>>> libchewing form Project/Private to something else (Committed?) and >>>>> we do have some incompatible changes to interfaces. >>>>> >>>>> Can you perhaps outline what the incompatible changes are? >>>>> >>>>> Might it be a better idea to leave the stability of libchewing as >>>>> it currently is (Project/Private under the old stability system) >>>>> and have contract scim-chewing take out a contract? >>>>> >>>>> My feeling is that if you want to raise the stability, this case >>>>> should probably be promoted to a fast track. >>>>> >>>>> Regards, >>>>> Alan Hargreaves >>>>> >>>>> >>>>> Yong Sun wrote: >>>>>> Hi, Alan, Garrett, >>>>>> >>>>>> Thanks for reviewing. >>>>>> >>>>>> The initial integration of libchewing is covered in >>>>>> PSARC/2005/525, as a project private interface, located in >>>>>> /usr/lib/iiim. And when scim is integrated (covered in >>>>>> PSARC/2008/418), libchewing is required both by scim-chewing and >>>>>> iiimf-twle-chewing, so it's moved to /usr/lib. >>>>>> >>>>>> Currently, there is no other client applications depends on >>>>>> libchewing, besides scim-chewing and iiimf-twle-chewing. >>>>>> >>>>>> Here is the release announcement for version 0.3.2, which lists >>>>>> the what's new, >>>>>> http://groups.google.com/group/chewing/browse_thread/thread/0067e04c8ea29ff3, >>>>>> please read the bottom half for the English version. >>>>>> >>>>>> And yes, I only require a minor binding. I will update the case >>>>>> material to include this info. >>>>>> >>>>>> Regards, >>>>>> >>>>>> Alan Hargreaves wrote: >>>>>>> I am concerned that this update breaks compatibility, yet is >>>>>>> being done as a self review. Are there any other consumers of >>>>>>> this library that could potentially be broken by this update? If >>>>>>> so, how will this be dealt with? >>>>>>> >>>>>>> What binding are you looking for? As I only see >>>>>>> nevada/opensolaris mentioned, I am assuming minor. >>>>>>> >>>>>>> Can you mention the case number which contains the prior >>>>>>> interfaces/bindings? >>>>>>> >>>>>>> Regards, >>>>>>> Alan Hargreaves >>>>>>> >>>>>>> >>>>>>> Yong Young Sun wrote: >>>>>>>> Template Version: @(#)sac_nextcase 1.68 02/23/09 SMI >>>>>>>> This information is Copyright 2009 Sun Microsystems >>>>>>>> 1. Introduction >>>>>>>> 1.1. Project/Component Working Name: >>>>>>>> Update libchewing from 0.3.0 to 0.3.2 >>>>>>>> 1.2. Name of Document Author/Supplier: >>>>>>>> Author: Yong Sun >>>>>>>> 1.3 Date of This Document: >>>>>>>> 27 July, 2009 >>>>>>>> >>>>>>>> 4. Technical Description >>>>>>>> >>>>>>>> libchewing is a popular library for Traditional Chinese >>>>>>>> input method engine >>>>>>>> licensed in LGPLv2.1. And there are some input methods, like >>>>>>>> iiimf-twle-chewing, scim-chewing depends on this library to >>>>>>>> provide input >>>>>>>> services to users. >>>>>>>> >>>>>>>> The version currently shipped in nevada/opensolaris is >>>>>>>> 0.3.0, while the >>>>>>>> community recently released a newer version, 0.3.2. In this >>>>>>>> new release, >>>>>>>> the API/ABI compatiblities were broken, and some new >>>>>>>> features are added. >>>>>>>> >>>>>>>> iiimf-twle-chewing and scim-chewing had been updated to >>>>>>>> work with 0.3.2, >>>>>>>> we therefore need to deliver the updated version to >>>>>>>> nevada/opensolaris. >>>>>>>> >>>>>>>> The interfaces (header files and shared library) remain the >>>>>>>> same as >>>>>>>> before. >>>>>>>> >>>>>>>> 6. Resources and Schedule >>>>>>>> 6.4. Steering Committee requested information >>>>>>>> 6.4.1. Consolidation C-team Name: >>>>>>>> Globalization >>>>>>>> 6.5. ARC review type: Automatic >>>>>>>> 6.6. ARC Exposure: open >>>>>>>> >>>>>>>> >>>>>>> >>>>>> >>>>> >>>> >>> >> > -- Alan Hargreaves - http://blogs.sun.com/tpenta Staff Engineer (Kernel/VOSJEC/Performance) Asia Pacific/Emerging Markets Sun Microsystems From gdamore@sun.com Tue Jul 28 02:00:59 2009 Received: from sunmail2sca.sfbay.sun.com (sunmail2sca.SFBay.Sun.COM [129.145.155.234]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id n6S90xkZ012694 for ; Tue, 28 Jul 2009 02:00:59 -0700 (PDT) Received: from nwk-avmta-2.sfbay.sun.com (nwk-avmta-2.SFBay.Sun.COM [129.145.155.6]) by sunmail2sca.sfbay.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id n6S90wCE017265; Tue, 28 Jul 2009 02:00:58 -0700 (PDT) Received: from pmxchannel-daemon.nwk-avmta-2.sfbay.sun.com by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0KNH00703IDMGI00@nwk-avmta-2.sfbay.sun.com>; Tue, 28 Jul 2009 02:00:58 -0700 (PDT) Received: from sca-es-mail-2.sun.com ([192.18.43.133]) by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KNH00MVGIDKO560@nwk-avmta-2.sfbay.sun.com>; Tue, 28 Jul 2009 02:00:57 -0700 (PDT) Received: from fe-sfbay-10.sun.com ([192.18.43.129]) by sca-es-mail-2.sun.com (8.13.7+Sun/8.12.9) with ESMTP id n6S90u1U003873; Tue, 28 Jul 2009 02:00:56 -0700 (PDT) Received: from conversion-daemon.fe-sfbay-10.sun.com by fe-sfbay-10.sun.com (Sun Java(tm) System Messaging Server 7u2-7.02 64bit (built Apr 16 2009)) id <0KNH00L00IC8Z400@fe-sfbay-10.sun.com>; Tue, 28 Jul 2009 02:00:56 -0700 (PDT) Received: from [192.168.251.11] ([unknown] [76.93.15.33]) by fe-sfbay-10.sun.com (Sun Java(tm) System Messaging Server 7u2-7.02 64bit (built Apr 16 2009)) with ESMTPSA id <0KNH00686IDJGCF0@fe-sfbay-10.sun.com>; Tue, 28 Jul 2009 02:00:56 -0700 (PDT) Date: Tue, 28 Jul 2009 02:00:55 -0700 From: "Garrett D'Amore" Subject: Re: Update libchewing from 0.3.0 to 0.3.2 [PSARC/2009/416 Self Review] In-reply-to: <4A6EBC32.3030101@Sun.COM> Sender: Garrett.Damore@sun.com To: Alan Hargreaves Cc: Yong Sun , Yong Young Sun , PSARC-ext@sun.com, gto-ext@sun.com Message-id: <4A6EBE47.9030800@sun.com> MIME-version: 1.0 Content-type: text/plain; CHARSET=US-ASCII; format=flowed Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 References: <200907280546.n6S5k9AY004168@sac.sfbay.sun.com> <4A6E956E.5000301@Sun.COM> <4A6EA066.206@Sun.COM> <4A6EA39A.4060806@Sun.COM> <4A6EB3C9.8000402@Sun.COM> <4A6EB474.4060704@Sun.COM> <4A6EB637.5020806@Sun.COM> <4A6EB837.5080507@Sun.COM> <4A6EBC32.3030101@Sun.COM> User-Agent: Thunderbird 2.0.0.18 (X11/20081201) Status: RO Content-Length: 6792 It looks like this stuff is coming together, but I'd like to propose for now promoting this to a regular fast track. I don't see anything intrinsically wrong here, and the case will almost certainly be approved on Wednesday. Having it be a fast track gives me a warm fuzzy knowing that the details are properly handled here at ARC before the underlying code is delivered into any consolidation. Either one of you can change the case to a fast track. Please set the time out for Thursday if you like; its shorter than the norm for a fast track, but if things look like they haven't gelled properly on Wednesday we can ask for more time at that point. (And as I said, I'd be rather surprised at this point if we don't get the administrivia here dealt with properly by then.) -- Garrett Alan Hargreaves wrote: > Another option that you have, if we are talking about delivering into > the same consolidation may also be instead of contracting the > interfaces, use this case to extend the original to include the new > code that needs the library. This would make some sense given that the > one group is looking after everything here. > > alan. > > Alan Hargreaves wrote: >> Excellent. That makes the contract easy and the case much simpler. I >> would suggest leave the stability of libchewing as it is. Fill out >> the contract form and place a copy in the directory of this case (as >> well as the email I think). >> >> Other PSARC folks, have I missed anything here? >> >> alan. >> >> Yong Sun wrote: >>> Hi, Alan, >>> >>> We (G11N input-method engineer team) are actually the people who >>> maintaining the solaris porting of libchewing, scim-chewing, and >>> iiimf-twle-chewing (we also developed this one). :) >>> >>> Regards, >>> >>> Alan Hargreaves wrote: >>>> All that having a contract means is that within the developer >>>> groups working on these two projects for Solaris/OpenSolaris there >>>> is an agreement that if a change is to be made to the library that >>>> the scim people will be notified. >>>> >>>> This looks a lot closer to what you actually want. >>>> >>>> alan. >>>> >>>> Yong Sun wrote: >>>>> No, I don't intend to promote it to committed, probably >>>>> uncommitted is fine. >>>>> >>>>> I attached all API changes (in diff format), most of them are >>>>> about initialization, configuration, and candidate iterating. And >>>>> some interfaces are removed (or moved to internal private), like >>>>> char/utf8_char utilities, user_phrase manipulating, zuin/pinyin >>>>> utilities. >>>>> >>>>> And libchewing, scim-chewing, iiimf-twle-chewing are all community >>>>> opensource softwares. I don't know if we need/could have a >>>>> contract for them. >>>>> >>>>> Regards, >>>>> >>>>> Alan Hargreaves wrote: >>>>>> So, if I read the prior cases correctly, you are promoting >>>>>> libchewing form Project/Private to something else (Committed?) >>>>>> and we do have some incompatible changes to interfaces. >>>>>> >>>>>> Can you perhaps outline what the incompatible changes are? >>>>>> >>>>>> Might it be a better idea to leave the stability of libchewing as >>>>>> it currently is (Project/Private under the old stability system) >>>>>> and have contract scim-chewing take out a contract? >>>>>> >>>>>> My feeling is that if you want to raise the stability, this case >>>>>> should probably be promoted to a fast track. >>>>>> >>>>>> Regards, >>>>>> Alan Hargreaves >>>>>> >>>>>> >>>>>> Yong Sun wrote: >>>>>>> Hi, Alan, Garrett, >>>>>>> >>>>>>> Thanks for reviewing. >>>>>>> >>>>>>> The initial integration of libchewing is covered in >>>>>>> PSARC/2005/525, as a project private interface, located in >>>>>>> /usr/lib/iiim. And when scim is integrated (covered in >>>>>>> PSARC/2008/418), libchewing is required both by scim-chewing and >>>>>>> iiimf-twle-chewing, so it's moved to /usr/lib. >>>>>>> >>>>>>> Currently, there is no other client applications depends on >>>>>>> libchewing, besides scim-chewing and iiimf-twle-chewing. >>>>>>> >>>>>>> Here is the release announcement for version 0.3.2, which lists >>>>>>> the what's new, >>>>>>> http://groups.google.com/group/chewing/browse_thread/thread/0067e04c8ea29ff3, >>>>>>> please read the bottom half for the English version. >>>>>>> >>>>>>> And yes, I only require a minor binding. I will update the case >>>>>>> material to include this info. >>>>>>> >>>>>>> Regards, >>>>>>> >>>>>>> Alan Hargreaves wrote: >>>>>>>> I am concerned that this update breaks compatibility, yet is >>>>>>>> being done as a self review. Are there any other consumers of >>>>>>>> this library that could potentially be broken by this update? >>>>>>>> If so, how will this be dealt with? >>>>>>>> >>>>>>>> What binding are you looking for? As I only see >>>>>>>> nevada/opensolaris mentioned, I am assuming minor. >>>>>>>> >>>>>>>> Can you mention the case number which contains the prior >>>>>>>> interfaces/bindings? >>>>>>>> >>>>>>>> Regards, >>>>>>>> Alan Hargreaves >>>>>>>> >>>>>>>> >>>>>>>> Yong Young Sun wrote: >>>>>>>>> Template Version: @(#)sac_nextcase 1.68 02/23/09 SMI >>>>>>>>> This information is Copyright 2009 Sun Microsystems >>>>>>>>> 1. Introduction >>>>>>>>> 1.1. Project/Component Working Name: >>>>>>>>> Update libchewing from 0.3.0 to 0.3.2 >>>>>>>>> 1.2. Name of Document Author/Supplier: >>>>>>>>> Author: Yong Sun >>>>>>>>> 1.3 Date of This Document: >>>>>>>>> 27 July, 2009 >>>>>>>>> >>>>>>>>> 4. Technical Description >>>>>>>>> >>>>>>>>> libchewing is a popular library for Traditional Chinese >>>>>>>>> input method engine >>>>>>>>> licensed in LGPLv2.1. And there are some input methods, like >>>>>>>>> iiimf-twle-chewing, scim-chewing depends on this library >>>>>>>>> to provide input >>>>>>>>> services to users. >>>>>>>>> >>>>>>>>> The version currently shipped in nevada/opensolaris is >>>>>>>>> 0.3.0, while the >>>>>>>>> community recently released a newer version, 0.3.2. In >>>>>>>>> this new release, >>>>>>>>> the API/ABI compatiblities were broken, and some new >>>>>>>>> features are added. >>>>>>>>> >>>>>>>>> iiimf-twle-chewing and scim-chewing had been updated to >>>>>>>>> work with 0.3.2, >>>>>>>>> we therefore need to deliver the updated version to >>>>>>>>> nevada/opensolaris. >>>>>>>>> >>>>>>>>> The interfaces (header files and shared library) remain >>>>>>>>> the same as >>>>>>>>> before. >>>>>>>>> >>>>>>>>> 6. Resources and Schedule >>>>>>>>> 6.4. Steering Committee requested information >>>>>>>>> 6.4.1. Consolidation C-team Name: >>>>>>>>> Globalization >>>>>>>>> 6.5. ARC review type: Automatic >>>>>>>>> 6.6. ARC Exposure: open >>>>>>>>> >>>>>>>>> >>>>>>>> >>>>>>> >>>>>> >>>>> >>>> >>> >> > From Alan.Hargreaves@sun.com Tue Jul 28 02:08:48 2009 Received: from sunmail4.singapore.sun.com (sunmail4.Singapore.Sun.COM [129.158.71.19]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id n6S98l2Q012893 for ; Tue, 28 Jul 2009 02:08:48 -0700 (PDT) Received: from nwk-avmta-2.sfbay.sun.com (nwk-avmta-2.SFBay.Sun.COM [129.145.155.6]) by sunmail4.singapore.sun.com (8.13.4+Sun/8.13.3/ENSMAIL,v2.2) with ESMTP id n6S98kx6002913; Tue, 28 Jul 2009 17:08:46 +0800 (SGT) Received: from pmxchannel-daemon.nwk-avmta-2.sfbay.sun.com by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0KNH0070ZIQLY600@nwk-avmta-2.sfbay.sun.com>; Tue, 28 Jul 2009 02:08:45 -0700 (PDT) Received: from sineb-mail-1.sun.com ([192.18.19.6]) by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KNH00MN2IQKO570@nwk-avmta-2.sfbay.sun.com>; Tue, 28 Jul 2009 02:08:45 -0700 (PDT) Received: from fe-apac-05.sun.com (fe-apac-05.sun.com [192.18.19.176] (may be forged)) by sineb-mail-1.sun.com (8.13.6+Sun/8.12.9) with ESMTP id n6S98hEc026168; Tue, 28 Jul 2009 09:08:43 +0000 (GMT) Received: from conversion-daemon.mail-apac.sun.com by mail-apac.sun.com (Sun Java(tm) System Messaging Server 7u2-7.02 64bit (built Apr 16 2009)) id <0KNH00M00I95MZ00@mail-apac.sun.com>; Tue, 28 Jul 2009 17:08:43 +0800 (SGT) Received: from [129.158.12.60] ([unknown] [129.158.12.60]) by mail-apac.sun.com (Sun Java(tm) System Messaging Server 7u2-7.02 64bit (built Apr 16 2009)) with ESMTPSA id <0KNH007ESIQGO1J0@mail-apac.sun.com>; Tue, 28 Jul 2009 17:08:43 +0800 (SGT) Date: Tue, 28 Jul 2009 19:07:37 +1000 From: Alan Hargreaves Subject: Re: Update libchewing from 0.3.0 to 0.3.2 [PSARC/2009/416 Self Review] In-reply-to: <4A6EBE47.9030800@sun.com> Sender: Alan.Hargreaves@sun.com To: "Garrett D'Amore" Cc: Yong Sun , PSARC-ext@sun.com, gto-ext@sun.com Message-id: <4A6EBFD9.4060100@Sun.COM> MIME-version: 1.0 Content-type: text/plain; CHARSET=US-ASCII; format=flowed Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 References: <200907280546.n6S5k9AY004168@sac.sfbay.sun.com> <4A6E956E.5000301@Sun.COM> <4A6EA066.206@Sun.COM> <4A6EA39A.4060806@Sun.COM> <4A6EB3C9.8000402@Sun.COM> <4A6EB474.4060704@Sun.COM> <4A6EB637.5020806@Sun.COM> <4A6EB837.5080507@Sun.COM> <4A6EBC32.3030101@Sun.COM> <4A6EBE47.9030800@sun.com> User-Agent: Thunderbird 2.0.0.22 (X11/20090706) Status: RO Content-Length: 7166 done. alan. Garrett D'Amore wrote: > It looks like this stuff is coming together, but I'd like to propose > for now promoting this to a regular fast track. I don't see anything > intrinsically wrong here, and the case will almost certainly be > approved on Wednesday. Having it be a fast track gives me a warm > fuzzy knowing that the details are properly handled here at ARC before > the underlying code is delivered into any consolidation. > > Either one of you can change the case to a fast track. Please set the > time out for Thursday if you like; its shorter than the norm for a > fast track, but if things look like they haven't gelled properly on > Wednesday we can ask for more time at that point. > > (And as I said, I'd be rather surprised at this point if we don't get > the administrivia here dealt with properly by then.) > > -- Garrett > > Alan Hargreaves wrote: >> Another option that you have, if we are talking about delivering into >> the same consolidation may also be instead of contracting the >> interfaces, use this case to extend the original to include the new >> code that needs the library. This would make some sense given that >> the one group is looking after everything here. >> >> alan. >> >> Alan Hargreaves wrote: >>> Excellent. That makes the contract easy and the case much simpler. I >>> would suggest leave the stability of libchewing as it is. Fill out >>> the contract form and place a copy in the directory of this case (as >>> well as the email I think). >>> >>> Other PSARC folks, have I missed anything here? >>> >>> alan. >>> >>> Yong Sun wrote: >>>> Hi, Alan, >>>> >>>> We (G11N input-method engineer team) are actually the people who >>>> maintaining the solaris porting of libchewing, scim-chewing, and >>>> iiimf-twle-chewing (we also developed this one). :) >>>> >>>> Regards, >>>> >>>> Alan Hargreaves wrote: >>>>> All that having a contract means is that within the developer >>>>> groups working on these two projects for Solaris/OpenSolaris there >>>>> is an agreement that if a change is to be made to the library that >>>>> the scim people will be notified. >>>>> >>>>> This looks a lot closer to what you actually want. >>>>> >>>>> alan. >>>>> >>>>> Yong Sun wrote: >>>>>> No, I don't intend to promote it to committed, probably >>>>>> uncommitted is fine. >>>>>> >>>>>> I attached all API changes (in diff format), most of them are >>>>>> about initialization, configuration, and candidate iterating. And >>>>>> some interfaces are removed (or moved to internal private), like >>>>>> char/utf8_char utilities, user_phrase manipulating, zuin/pinyin >>>>>> utilities. >>>>>> >>>>>> And libchewing, scim-chewing, iiimf-twle-chewing are all >>>>>> community opensource softwares. I don't know if we need/could >>>>>> have a contract for them. >>>>>> >>>>>> Regards, >>>>>> >>>>>> Alan Hargreaves wrote: >>>>>>> So, if I read the prior cases correctly, you are promoting >>>>>>> libchewing form Project/Private to something else (Committed?) >>>>>>> and we do have some incompatible changes to interfaces. >>>>>>> >>>>>>> Can you perhaps outline what the incompatible changes are? >>>>>>> >>>>>>> Might it be a better idea to leave the stability of libchewing >>>>>>> as it currently is (Project/Private under the old stability >>>>>>> system) and have contract scim-chewing take out a contract? >>>>>>> >>>>>>> My feeling is that if you want to raise the stability, this case >>>>>>> should probably be promoted to a fast track. >>>>>>> >>>>>>> Regards, >>>>>>> Alan Hargreaves >>>>>>> >>>>>>> >>>>>>> Yong Sun wrote: >>>>>>>> Hi, Alan, Garrett, >>>>>>>> >>>>>>>> Thanks for reviewing. >>>>>>>> >>>>>>>> The initial integration of libchewing is covered in >>>>>>>> PSARC/2005/525, as a project private interface, located in >>>>>>>> /usr/lib/iiim. And when scim is integrated (covered in >>>>>>>> PSARC/2008/418), libchewing is required both by scim-chewing >>>>>>>> and iiimf-twle-chewing, so it's moved to /usr/lib. >>>>>>>> >>>>>>>> Currently, there is no other client applications depends on >>>>>>>> libchewing, besides scim-chewing and iiimf-twle-chewing. >>>>>>>> >>>>>>>> Here is the release announcement for version 0.3.2, which lists >>>>>>>> the what's new, >>>>>>>> http://groups.google.com/group/chewing/browse_thread/thread/0067e04c8ea29ff3, >>>>>>>> please read the bottom half for the English version. >>>>>>>> >>>>>>>> And yes, I only require a minor binding. I will update the case >>>>>>>> material to include this info. >>>>>>>> >>>>>>>> Regards, >>>>>>>> >>>>>>>> Alan Hargreaves wrote: >>>>>>>>> I am concerned that this update breaks compatibility, yet is >>>>>>>>> being done as a self review. Are there any other consumers of >>>>>>>>> this library that could potentially be broken by this update? >>>>>>>>> If so, how will this be dealt with? >>>>>>>>> >>>>>>>>> What binding are you looking for? As I only see >>>>>>>>> nevada/opensolaris mentioned, I am assuming minor. >>>>>>>>> >>>>>>>>> Can you mention the case number which contains the prior >>>>>>>>> interfaces/bindings? >>>>>>>>> >>>>>>>>> Regards, >>>>>>>>> Alan Hargreaves >>>>>>>>> >>>>>>>>> >>>>>>>>> Yong Young Sun wrote: >>>>>>>>>> Template Version: @(#)sac_nextcase 1.68 02/23/09 SMI >>>>>>>>>> This information is Copyright 2009 Sun Microsystems >>>>>>>>>> 1. Introduction >>>>>>>>>> 1.1. Project/Component Working Name: >>>>>>>>>> Update libchewing from 0.3.0 to 0.3.2 >>>>>>>>>> 1.2. Name of Document Author/Supplier: >>>>>>>>>> Author: Yong Sun >>>>>>>>>> 1.3 Date of This Document: >>>>>>>>>> 27 July, 2009 >>>>>>>>>> >>>>>>>>>> 4. Technical Description >>>>>>>>>> >>>>>>>>>> libchewing is a popular library for Traditional Chinese >>>>>>>>>> input method engine >>>>>>>>>> licensed in LGPLv2.1. And there are some input methods, like >>>>>>>>>> iiimf-twle-chewing, scim-chewing depends on this library >>>>>>>>>> to provide input >>>>>>>>>> services to users. >>>>>>>>>> >>>>>>>>>> The version currently shipped in nevada/opensolaris is >>>>>>>>>> 0.3.0, while the >>>>>>>>>> community recently released a newer version, 0.3.2. In >>>>>>>>>> this new release, >>>>>>>>>> the API/ABI compatiblities were broken, and some new >>>>>>>>>> features are added. >>>>>>>>>> >>>>>>>>>> iiimf-twle-chewing and scim-chewing had been updated to >>>>>>>>>> work with 0.3.2, >>>>>>>>>> we therefore need to deliver the updated version to >>>>>>>>>> nevada/opensolaris. >>>>>>>>>> >>>>>>>>>> The interfaces (header files and shared library) remain >>>>>>>>>> the same as >>>>>>>>>> before. >>>>>>>>>> >>>>>>>>>> 6. Resources and Schedule >>>>>>>>>> 6.4. Steering Committee requested information >>>>>>>>>> 6.4.1. Consolidation C-team Name: >>>>>>>>>> Globalization >>>>>>>>>> 6.5. ARC review type: Automatic >>>>>>>>>> 6.6. ARC Exposure: open >>>>>>>>>> >>>>>>>>>> >>>>>>>>> >>>>>>>> >>>>>>> >>>>>> >>>>> >>>> >>> >> > -- Alan Hargreaves - http://blogs.sun.com/tpenta Staff Engineer (Kernel/VOSJEC/Performance) Asia Pacific/Emerging Markets Sun Microsystems From alan.hargreaves@sun.com Tue Jul 28 20:52:37 2009 Received: from sunmail5.uk.sun.com (sunmail5.UK.Sun.COM [129.156.85.165]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id n6T3qbL2001459 for ; Tue, 28 Jul 2009 20:52:37 -0700 (PDT) Received: from nwk-avmta-1.SFBay.Sun.COM (nwk-avmta-1.SFBay.Sun.COM [129.146.11.74]) by sunmail5.uk.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id n6T3qZCW026583; Wed, 29 Jul 2009 04:52:36 +0100 (BST) Received: from pmxchannel-daemon.nwk-avmta-1.sfbay.Sun.COM by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0KNI00A05YRNJI00@nwk-avmta-1.sfbay.Sun.COM>; Tue, 28 Jul 2009 20:52:35 -0700 (PDT) Received: from sineb-mail-2.sun.com ([192.18.19.7]) by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KNI0037OYRMXE50@nwk-avmta-1.sfbay.Sun.COM>; Tue, 28 Jul 2009 20:52:35 -0700 (PDT) Received: from fe-apac-05.sun.com (fe-apac-05.sun.com [192.18.19.176] (may be forged)) by sineb-mail-2.sun.com (8.13.6+Sun/8.12.9) with ESMTP id n6T3qXT9024093; Wed, 29 Jul 2009 03:52:33 +0000 (GMT) Received: from conversion-daemon.mail-apac.sun.com by mail-apac.sun.com (Sun Java(tm) System Messaging Server 7u2-7.02 64bit (built Apr 16 2009)) id <0KNI00H00YO0F900@mail-apac.sun.com>; Wed, 29 Jul 2009 11:52:33 +0800 (SGT) Received: from [129.158.12.60] ([unknown] [129.158.12.60]) by mail-apac.sun.com (Sun Java(tm) System Messaging Server 7u2-7.02 64bit (built Apr 16 2009)) with ESMTPSA id <0KNI008HWYRJDBA0@mail-apac.sun.com>; Wed, 29 Jul 2009 11:52:33 +0800 (SGT) Date: Wed, 29 Jul 2009 13:51:26 +1000 From: Alan Hargreaves Subject: Re: Update libchewing from 0.3.0 to 0.3.2 [PSARC/2009/416 Self Review] In-reply-to: <4A6EBFD9.4060100@Sun.COM> Sender: alan.hargreaves@sun.com To: "Garrett D'Amore" Cc: Yong Sun , PSARC-ext@sun.com, gto-ext@sun.com Message-id: <4A6FC73E.9000305@Sun.COM> MIME-version: 1.0 Content-type: text/html; CHARSET=US-ASCII Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 References: <200907280546.n6S5k9AY004168@sac.sfbay.sun.com> <4A6E956E.5000301@Sun.COM> <4A6EA066.206@Sun.COM> <4A6EA39A.4060806@Sun.COM> <4A6EB3C9.8000402@Sun.COM> <4A6EB474.4060704@Sun.COM> <4A6EB637.5020806@Sun.COM> <4A6EB837.5080507@Sun.COM> <4A6EBC32.3030101@Sun.COM> <4A6EBE47.9030800@sun.com> <4A6EBFD9.4060100@Sun.COM> User-Agent: Thunderbird 2.0.0.22 (X11/20090706) Status: RO Content-Length: 10332

Yong Sun, I'd be a lot more comfortable with this if you took one of the two suggested courses. That is

  1. Contract the required interfaces
  2. Extend the original project to include the new deliverable
This week's meeting will be held at 10am Pacific time tomorrow (about 13 hours from now).

Regards,
Alan Hargreaves

Alan Hargreaves wrote:
done.

alan.

Garrett D'Amore wrote:
It looks like this stuff is coming together, but I'd like to propose for now promoting this to a regular fast track.  I don't see anything intrinsically wrong here, and the case will almost certainly be approved on Wednesday.  Having it be a fast track gives me a warm fuzzy knowing that the details are properly handled here at ARC before the underlying code is delivered into any consolidation.

Either one of you can change the case to a fast track.  Please set the time out for Thursday if you like; its shorter than the norm for a fast track, but if things look like they haven't gelled properly on Wednesday we can ask for more time at that point.

(And as I said, I'd be rather surprised at this point if we don't get the administrivia here dealt with properly by then.)

   -- Garrett

Alan Hargreaves wrote:
Another option that you have, if we are talking about delivering into the same consolidation may also be instead of contracting the interfaces, use this case to extend the original to include the new code that needs the library. This would make some sense given that the one group is looking after everything here.

alan.

Alan Hargreaves wrote:
Excellent. That makes the contract easy and the case much simpler. I would suggest leave the stability of libchewing as it is. Fill out the contract form and place a copy in the directory of this case (as well as the email I think).

Other PSARC folks, have I missed anything here?

alan.

Yong Sun wrote:
Hi, Alan,

We (G11N input-method engineer team) are actually the people who maintaining the solaris porting of libchewing, scim-chewing, and iiimf-twle-chewing (we also developed this one). :)

Regards,

Alan Hargreaves wrote:
All that having a contract means is that within the developer groups working on these two projects for Solaris/OpenSolaris there is an agreement that if a change is to be made to the library that the scim people will be notified.

This looks a lot closer to what you actually want.

alan.

Yong Sun wrote:
No, I don't intend to promote it to committed, probably uncommitted is fine.

I attached all API changes (in diff format), most of them are about initialization, configuration, and candidate iterating. And some interfaces are removed (or moved to internal private), like char/utf8_char utilities, user_phrase manipulating, zuin/pinyin utilities.

And libchewing, scim-chewing, iiimf-twle-chewing are all community opensource softwares. I don't know if we need/could have a contract for them.

Regards,

Alan Hargreaves wrote:
So, if I read the prior cases correctly, you are promoting libchewing form Project/Private to something else (Committed?) and we do have some incompatible changes to interfaces.

Can you perhaps outline what the incompatible changes are?

Might it be a better idea to leave the stability of libchewing as it currently is (Project/Private under the old stability system) and have contract scim-chewing take out a contract?

My feeling is that if you want to raise the stability, this case should probably be promoted to a fast track.

Regards,
Alan Hargreaves


Yong Sun wrote:
Hi, Alan, Garrett,

Thanks for reviewing.

The initial integration of libchewing is covered in PSARC/2005/525, as a project private interface, located in /usr/lib/iiim. And when scim is integrated (covered in PSARC/2008/418), libchewing is required both by scim-chewing and iiimf-twle-chewing, so it's moved to /usr/lib.

Currently, there is no other client applications depends on libchewing, besides scim-chewing and iiimf-twle-chewing.

Here is the release announcement for version 0.3.2, which lists the what's new,  http://groups.google.com/group/chewing/browse_thread/thread/0067e04c8ea29ff3, please read the bottom half for the English version.

And yes, I only require a minor binding. I will update the case material to include this info.

Regards,

Alan Hargreaves wrote:
I am concerned that this update breaks compatibility, yet is being done as a self review. Are there any other consumers of this library that could potentially be broken by this update? If so, how will this be dealt with?

What binding are you looking for? As I only see nevada/opensolaris mentioned, I am assuming minor.

Can you mention the case number which contains the prior interfaces/bindings?

Regards,
Alan Hargreaves


Yong Young Sun wrote:
Template Version: @(#)sac_nextcase 1.68 02/23/09 SMI
This information is Copyright 2009 Sun Microsystems
1. Introduction
    1.1. Project/Component Working Name:
     Update libchewing from 0.3.0 to 0.3.2
    1.2. Name of Document Author/Supplier:
     Author:  Yong Sun
    1.3  Date of This Document:
    27 July, 2009

4. Technical Description

    libchewing is a popular library for Traditional Chinese input method engine
    licensed in LGPLv2.1. And there are some input methods, like
    iiimf-twle-chewing, scim-chewing depends on this library to provide input
    services to users.

    The version currently shipped in nevada/opensolaris is 0.3.0, while the
    community recently released a newer version, 0.3.2. In this new release,
    the API/ABI compatiblities were broken, and some new features are added.

    iiimf-twle-chewing and scim-chewing had been updated to work with 0.3.2,
    we therefore need to deliver the updated version to nevada/opensolaris.

    The interfaces (header files and shared library) remain the same as
    before.

6. Resources and Schedule
    6.4. Steering Committee requested information
       6.4.1. Consolidation C-team Name:
        Globalization
    6.5. ARC review type: Automatic
    6.6. ARC Exposure: open

  











-- 
Alan Hargreaves - http://blogs.sun.com/tpenta
Principal Field Technologist (Kernel/VOSJEC/Performance)
Asia Pacific/Emerging Markets
Sun Microsystems
From Alan.Hargreaves@sun.com Wed Jul 29 10:06:49 2009 Received: from sunmail4.singapore.sun.com (sunmail4.Singapore.Sun.COM [129.158.71.19]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id n6TH6mpM001816 for ; Wed, 29 Jul 2009 10:06:49 -0700 (PDT) Received: from brm-avmta-1.central.sun.com (brm-avmta-1.Central.Sun.COM [129.147.4.11]) by sunmail4.singapore.sun.com (8.13.4+Sun/8.13.3/ENSMAIL,v2.2) with ESMTP id n6TH6UKv014058; Thu, 30 Jul 2009 01:06:47 +0800 (SGT) Received: from pmxchannel-daemon.brm-avmta-1.central.sun.com by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0KNJ00K0JZJANE00@brm-avmta-1.central.sun.com>; Wed, 29 Jul 2009 11:06:46 -0600 (MDT) Received: from sineb-mail-1.sun.com ([192.18.19.6]) by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KNJ005E7ZJ8VX90@brm-avmta-1.central.sun.com>; Wed, 29 Jul 2009 11:06:45 -0600 (MDT) Received: from fe-apac-06.sun.com (fe-apac-06.sun.com [192.18.19.177] (may be forged)) by sineb-mail-1.sun.com (8.13.6+Sun/8.12.9) with ESMTP id n6TH6i58005209; Wed, 29 Jul 2009 17:06:44 +0000 (GMT) Received: from conversion-daemon.mail-apac.sun.com by mail-apac.sun.com (Sun Java(tm) System Messaging Server 7u2-7.02 64bit (built Apr 16 2009)) id <0KNJ00500ZHH4C00@mail-apac.sun.com>; Thu, 30 Jul 2009 01:06:44 +0800 (SGT) Received: from [129.158.12.60] ([unknown] [129.158.12.60]) by mail-apac.sun.com (Sun Java(tm) System Messaging Server 7u2-7.02 64bit (built Apr 16 2009)) with ESMTPSA id <0KNJ005NSZJ4P590@mail-apac.sun.com>; Thu, 30 Jul 2009 01:06:44 +0800 (SGT) Date: Thu, 30 Jul 2009 03:05:36 +1000 From: Alan Hargreaves Subject: Re: Update libchewing from 0.3.0 to 0.3.2 [PSARC/2009/416 Self Review] In-reply-to: <4A6FC73E.9000305@Sun.COM> Sender: Alan.Hargreaves@sun.com To: "Garrett D'Amore" Cc: Yong Sun , PSARC-ext@sun.com, gto-ext@sun.com Message-id: <4A708160.7090705@Sun.COM> MIME-version: 1.0 Content-type: text/html; CHARSET=US-ASCII Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 References: <200907280546.n6S5k9AY004168@sac.sfbay.sun.com> <4A6E956E.5000301@Sun.COM> <4A6EA066.206@Sun.COM> <4A6EA39A.4060806@Sun.COM> <4A6EB3C9.8000402@Sun.COM> <4A6EB474.4060704@Sun.COM> <4A6EB637.5020806@Sun.COM> <4A6EB837.5080507@Sun.COM> <4A6EBC32.3030101@Sun.COM> <4A6EBE47.9030800@sun.com> <4A6EBFD9.4060100@Sun.COM> <4A6FC73E.9000305@Sun.COM> User-Agent: Thunderbird 2.0.0.22 (X11/20090706) Status: RO Content-Length: 11562

After some discussion between Yong Sun, Garrett and myself Yong Sun decided to go with option #2 and modified the case as follows:

Template Version: @(#)sac_nextcase 1.68 02/23/09 SMI
This information is Copyright 2009 Sun Microsystems
1. Introduction
    1.1. Project/Component Working Name:
	 Update libchewing from 0.3.0 to 0.3.2
    1.2. Name of Document Author/Supplier:
	 Author:  Yong Sun
    1.3  Date of This Document:
	27 July, 2009

4. Technical Description

    libchewing is a popular library for Traditional Chinese input method engine
    licensed in LGPLv2.1. And there are some input methods, like
    iiimf-twle-chewing, scim-chewing depends on this library to provide input
    services to users.

    The version currently shipped in nevada/opensolaris is 0.3.0, while the
    community recently released a newer version, 0.3.2. In this new release,
    the API/ABI compatiblities were broken, and some new features are added.

    iiimf-twle-chewing and scim-chewing had been updated to work with 0.3.2,
    we therefore need to deliver the updated version to nevada/opensolaris.

    The interfaces (header files and shared library) remain the same as
    before, i.e., Project Private.

    This project extends PSARC/2005/525 by merging PSARC/2008/418 into
    it so that scim-chewing can use the project private interfaces of
    libchewing. Both projects are maintained by the same team (G11N input
    method engineer team) and deliver into the same consolidation. 

6. Resources and Schedule
    6.4. Steering Committee requested information
   	6.4.1. Consolidation C-team Name:
		Globalization
    6.5. ARC review type: Automatic
    6.6. ARC Exposure: open

Alan Hargreaves wrote:

Yong Sun, I'd be a lot more comfortable with this if you took one of the two suggested courses. That is

  1. Contract the required interfaces
  2. Extend the original project to include the new deliverable
This week's meeting will be held at 10am Pacific time tomorrow (about 13 hours from now).

Regards,
Alan Hargreaves

Alan Hargreaves wrote:
done.

alan.

Garrett D'Amore wrote:
It looks like this stuff is coming together, but I'd like to propose for now promoting this to a regular fast track.  I don't see anything intrinsically wrong here, and the case will almost certainly be approved on Wednesday.  Having it be a fast track gives me a warm fuzzy knowing that the details are properly handled here at ARC before the underlying code is delivered into any consolidation.

Either one of you can change the case to a fast track.  Please set the time out for Thursday if you like; its shorter than the norm for a fast track, but if things look like they haven't gelled properly on Wednesday we can ask for more time at that point.

(And as I said, I'd be rather surprised at this point if we don't get the administrivia here dealt with properly by then.)

   -- Garrett

Alan Hargreaves wrote:
Another option that you have, if we are talking about delivering into the same consolidation may also be instead of contracting the interfaces, use this case to extend the original to include the new code that needs the library. This would make some sense given that the one group is looking after everything here.

alan.

Alan Hargreaves wrote:
Excellent. That makes the contract easy and the case much simpler. I would suggest leave the stability of libchewing as it is. Fill out the contract form and place a copy in the directory of this case (as well as the email I think).

Other PSARC folks, have I missed anything here?

alan.

Yong Sun wrote:
Hi, Alan,

We (G11N input-method engineer team) are actually the people who maintaining the solaris porting of libchewing, scim-chewing, and iiimf-twle-chewing (we also developed this one). :)

Regards,

Alan Hargreaves wrote:
All that having a contract means is that within the developer groups working on these two projects for Solaris/OpenSolaris there is an agreement that if a change is to be made to the library that the scim people will be notified.

This looks a lot closer to what you actually want.

alan.

Yong Sun wrote:
No, I don't intend to promote it to committed, probably uncommitted is fine.

I attached all API changes (in diff format), most of them are about initialization, configuration, and candidate iterating. And some interfaces are removed (or moved to internal private), like char/utf8_char utilities, user_phrase manipulating, zuin/pinyin utilities.

And libchewing, scim-chewing, iiimf-twle-chewing are all community opensource softwares. I don't know if we need/could have a contract for them.

Regards,

Alan Hargreaves wrote:
So, if I read the prior cases correctly, you are promoting libchewing form Project/Private to something else (Committed?) and we do have some incompatible changes to interfaces.

Can you perhaps outline what the incompatible changes are?

Might it be a better idea to leave the stability of libchewing as it currently is (Project/Private under the old stability system) and have contract scim-chewing take out a contract?

My feeling is that if you want to raise the stability, this case should probably be promoted to a fast track.

Regards,
Alan Hargreaves


Yong Sun wrote:
Hi, Alan, Garrett,

Thanks for reviewing.

The initial integration of libchewing is covered in PSARC/2005/525, as a project private interface, located in /usr/lib/iiim. And when scim is integrated (covered in PSARC/2008/418), libchewing is required both by scim-chewing and iiimf-twle-chewing, so it's moved to /usr/lib.

Currently, there is no other client applications depends on libchewing, besides scim-chewing and iiimf-twle-chewing.

Here is the release announcement for version 0.3.2, which lists the what's new,  http://groups.google.com/group/chewing/browse_thread/thread/0067e04c8ea29ff3, please read the bottom half for the English version.

And yes, I only require a minor binding. I will update the case material to include this info.

Regards,

Alan Hargreaves wrote:
I am concerned that this update breaks compatibility, yet is being done as a self review. Are there any other consumers of this library that could potentially be broken by this update? If so, how will this be dealt with?

What binding are you looking for? As I only see nevada/opensolaris mentioned, I am assuming minor.

Can you mention the case number which contains the prior interfaces/bindings?

Regards,
Alan Hargreaves


Yong Young Sun wrote:
Template Version: @(#)sac_nextcase 1.68 02/23/09 SMI
This information is Copyright 2009 Sun Microsystems
1. Introduction
    1.1. Project/Component Working Name:
     Update libchewing from 0.3.0 to 0.3.2
    1.2. Name of Document Author/Supplier:
     Author:  Yong Sun
    1.3  Date of This Document:
    27 July, 2009

4. Technical Description

    libchewing is a popular library for Traditional Chinese input method engine
    licensed in LGPLv2.1. And there are some input methods, like
    iiimf-twle-chewing, scim-chewing depends on this library to provide input
    services to users.

    The version currently shipped in nevada/opensolaris is 0.3.0, while the
    community recently released a newer version, 0.3.2. In this new release,
    the API/ABI compatiblities were broken, and some new features are added.

    iiimf-twle-chewing and scim-chewing had been updated to work with 0.3.2,
    we therefore need to deliver the updated version to nevada/opensolaris.

    The interfaces (header files and shared library) remain the same as
    before.

6. Resources and Schedule
    6.4. Steering Committee requested information
       6.4.1. Consolidation C-team Name:
        Globalization
    6.5. ARC review type: Automatic
    6.6. ARC Exposure: open

  











-- 
Alan Hargreaves - http://blogs.sun.com/tpenta
Principal Field Technologist (Kernel/VOSJEC/Performance)
Asia Pacific/Emerging Markets
Sun Microsystems
  

-- 
Alan Hargreaves - http://blogs.sun.com/tpenta
Principal Field Technologist (Kernel/VOSJEC/Performance)
Asia Pacific/Emerging Markets
Sun Microsystems
From gdamore@sun.com Wed Jul 29 10:59:29 2009 Received: from sunmail4.singapore.sun.com (sunmail4.Singapore.Sun.COM [129.158.71.19]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id n6THxSJv003902 for ; Wed, 29 Jul 2009 10:59:28 -0700 (PDT) Received: from nwk-avmta-1.SFBay.Sun.COM (nwk-avmta-1.SFBay.Sun.COM [129.146.11.74]) by sunmail4.singapore.sun.com (8.13.4+Sun/8.13.3/ENSMAIL,v2.2) with ESMTP id n6THxKee009996; Thu, 30 Jul 2009 01:59:26 +0800 (SGT) Received: from pmxchannel-daemon.nwk-avmta-1.sfbay.Sun.COM by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0KNK00D031Z2BZ00@nwk-avmta-1.sfbay.Sun.COM>; Wed, 29 Jul 2009 10:59:26 -0700 (PDT) Received: from sca-es-mail-1.sun.com ([192.18.43.132]) by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KNK005E11Z2BOC0@nwk-avmta-1.sfbay.Sun.COM>; Wed, 29 Jul 2009 10:59:26 -0700 (PDT) Received: from fe-sfbay-10.sun.com ([192.18.43.129]) by sca-es-mail-1.sun.com (8.13.7+Sun/8.12.9) with ESMTP id n6THxPYV024110; Wed, 29 Jul 2009 10:59:25 -0700 (PDT) Received: from conversion-daemon.fe-sfbay-10.sun.com by fe-sfbay-10.sun.com (Sun Java(tm) System Messaging Server 7u2-7.02 64bit (built Apr 16 2009)) id <0KNK006001F1PH00@fe-sfbay-10.sun.com>; Wed, 29 Jul 2009 10:59:25 -0700 (PDT) Received: from [192.168.251.11] ([unknown] [76.93.15.33]) by fe-sfbay-10.sun.com (Sun Java(tm) System Messaging Server 7u2-7.02 64bit (built Apr 16 2009)) with ESMTPSA id <0KNK00FJP1YP76F0@fe-sfbay-10.sun.com>; Wed, 29 Jul 2009 10:59:14 -0700 (PDT) Date: Wed, 29 Jul 2009 10:59:13 -0700 From: "Garrett D'Amore" Subject: Re: Update libchewing from 0.3.0 to 0.3.2 [PSARC/2009/416 Self Review] In-reply-to: <4A708160.7090705@Sun.COM> Sender: Garrett.Damore@sun.com To: Alan Hargreaves Cc: Yong Sun , PSARC-ext@sun.com, gto-ext@sun.com Message-id: <4A708DF1.7000204@sun.com> MIME-version: 1.0 Content-type: text/plain; CHARSET=US-ASCII; format=flowed Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 References: <200907280546.n6S5k9AY004168@sac.sfbay.sun.com> <4A6E956E.5000301@Sun.COM> <4A6EA066.206@Sun.COM> <4A6EA39A.4060806@Sun.COM> <4A6EB3C9.8000402@Sun.COM> <4A6EB474.4060704@Sun.COM> <4A6EB637.5020806@Sun.COM> <4A6EB837.5080507@Sun.COM> <4A6EBC32.3030101@Sun.COM> <4A6EBE47.9030800@sun.com> <4A6EBFD9.4060100@Sun.COM> <4A6FC73E.9000305@Sun.COM> <4A708160.7090705@Sun.COM> User-Agent: Thunderbird 2.0.0.18 (X11/20081201) Status: RO Content-Length: 10275 With that, I'm happy, and the case can be closed approved. - Garrett Alan Hargreaves wrote: > > After some discussion between Yong Sun, Garrett and myself Yong Sun > decided to go with option #2 and modified the case as follows: > > Template Version: @(#)sac_nextcase 1.68 02/23/09 SMI > This information is Copyright 2009 Sun Microsystems > 1. Introduction > 1.1. Project/Component Working Name: > Update libchewing from 0.3.0 to 0.3.2 > 1.2. Name of Document Author/Supplier: > Author: Yong Sun > 1.3 Date of This Document: > 27 July, 2009 > > 4. Technical Description > > libchewing is a popular library for Traditional Chinese input method engine > licensed in LGPLv2.1. And there are some input methods, like > iiimf-twle-chewing, scim-chewing depends on this library to provide input > services to users. > > The version currently shipped in nevada/opensolaris is 0.3.0, while the > community recently released a newer version, 0.3.2. In this new release, > the API/ABI compatiblities were broken, and some new features are added. > > iiimf-twle-chewing and scim-chewing had been updated to work with 0.3.2, > we therefore need to deliver the updated version to nevada/opensolaris. > > The interfaces (header files and shared library) remain the same as > before, i.e., Project Private. > > This project extends PSARC/2005/525 by merging PSARC/2008/418 into > it so that scim-chewing can use the project private interfaces of > libchewing. Both projects are maintained by the same team (G11N input > method engineer team) and deliver into the same consolidation. > > 6. Resources and Schedule > 6.4. Steering Committee requested information > 6.4.1. Consolidation C-team Name: > Globalization > 6.5. ARC review type: Automatic > 6.6. ARC Exposure: open > > > > Alan Hargreaves wrote: >> >> Yong Sun, I'd be a lot more comfortable with this if you took one of >> the two suggested courses. That is >> >> 1. Contract the required interfaces >> 2. Extend the original project to include the new deliverable >> >> This week's meeting will be held at 10am Pacific time tomorrow (about >> 13 hours from now). >> >> Regards, >> Alan Hargreaves >> >> Alan Hargreaves wrote: >>> done. >>> >>> alan. >>> >>> Garrett D'Amore wrote: >>>> It looks like this stuff is coming together, but I'd like to >>>> propose for now promoting this to a regular fast track. I don't >>>> see anything intrinsically wrong here, and the case will almost >>>> certainly be approved on Wednesday. Having it be a fast track >>>> gives me a warm fuzzy knowing that the details are properly handled >>>> here at ARC before the underlying code is delivered into any >>>> consolidation. >>>> >>>> Either one of you can change the case to a fast track. Please set >>>> the time out for Thursday if you like; its shorter than the norm >>>> for a fast track, but if things look like they haven't gelled >>>> properly on Wednesday we can ask for more time at that point. >>>> >>>> (And as I said, I'd be rather surprised at this point if we don't >>>> get the administrivia here dealt with properly by then.) >>>> >>>> -- Garrett >>>> >>>> Alan Hargreaves wrote: >>>>> Another option that you have, if we are talking about delivering >>>>> into the same consolidation may also be instead of contracting the >>>>> interfaces, use this case to extend the original to include the >>>>> new code that needs the library. This would make some sense given >>>>> that the one group is looking after everything here. >>>>> >>>>> alan. >>>>> >>>>> Alan Hargreaves wrote: >>>>>> Excellent. That makes the contract easy and the case much >>>>>> simpler. I would suggest leave the stability of libchewing as it >>>>>> is. Fill out the contract form and place a copy in the directory >>>>>> of this case (as well as the email I think). >>>>>> >>>>>> Other PSARC folks, have I missed anything here? >>>>>> >>>>>> alan. >>>>>> >>>>>> Yong Sun wrote: >>>>>>> Hi, Alan, >>>>>>> >>>>>>> We (G11N input-method engineer team) are actually the people who >>>>>>> maintaining the solaris porting of libchewing, scim-chewing, and >>>>>>> iiimf-twle-chewing (we also developed this one). :) >>>>>>> >>>>>>> Regards, >>>>>>> >>>>>>> Alan Hargreaves wrote: >>>>>>>> All that having a contract means is that within the developer >>>>>>>> groups working on these two projects for Solaris/OpenSolaris >>>>>>>> there is an agreement that if a change is to be made to the >>>>>>>> library that the scim people will be notified. >>>>>>>> >>>>>>>> This looks a lot closer to what you actually want. >>>>>>>> >>>>>>>> alan. >>>>>>>> >>>>>>>> Yong Sun wrote: >>>>>>>>> No, I don't intend to promote it to committed, probably >>>>>>>>> uncommitted is fine. >>>>>>>>> >>>>>>>>> I attached all API changes (in diff format), most of them are >>>>>>>>> about initialization, configuration, and candidate iterating. >>>>>>>>> And some interfaces are removed (or moved to internal >>>>>>>>> private), like char/utf8_char utilities, user_phrase >>>>>>>>> manipulating, zuin/pinyin utilities. >>>>>>>>> >>>>>>>>> And libchewing, scim-chewing, iiimf-twle-chewing are all >>>>>>>>> community opensource softwares. I don't know if we need/could >>>>>>>>> have a contract for them. >>>>>>>>> >>>>>>>>> Regards, >>>>>>>>> >>>>>>>>> Alan Hargreaves wrote: >>>>>>>>>> So, if I read the prior cases correctly, you are promoting >>>>>>>>>> libchewing form Project/Private to something else >>>>>>>>>> (Committed?) and we do have some incompatible changes to >>>>>>>>>> interfaces. >>>>>>>>>> >>>>>>>>>> Can you perhaps outline what the incompatible changes are? >>>>>>>>>> >>>>>>>>>> Might it be a better idea to leave the stability of >>>>>>>>>> libchewing as it currently is (Project/Private under the old >>>>>>>>>> stability system) and have contract scim-chewing take out a >>>>>>>>>> contract? >>>>>>>>>> >>>>>>>>>> My feeling is that if you want to raise the stability, this >>>>>>>>>> case should probably be promoted to a fast track. >>>>>>>>>> >>>>>>>>>> Regards, >>>>>>>>>> Alan Hargreaves >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> Yong Sun wrote: >>>>>>>>>>> Hi, Alan, Garrett, >>>>>>>>>>> >>>>>>>>>>> Thanks for reviewing. >>>>>>>>>>> >>>>>>>>>>> The initial integration of libchewing is covered in >>>>>>>>>>> PSARC/2005/525, as a project private interface, located in >>>>>>>>>>> /usr/lib/iiim. And when scim is integrated (covered in >>>>>>>>>>> PSARC/2008/418), libchewing is required both by scim-chewing >>>>>>>>>>> and iiimf-twle-chewing, so it's moved to /usr/lib. >>>>>>>>>>> >>>>>>>>>>> Currently, there is no other client applications depends on >>>>>>>>>>> libchewing, besides scim-chewing and iiimf-twle-chewing. >>>>>>>>>>> >>>>>>>>>>> Here is the release announcement for version 0.3.2, which >>>>>>>>>>> lists the what's new, >>>>>>>>>>> http://groups.google.com/group/chewing/browse_thread/thread/0067e04c8ea29ff3, >>>>>>>>>>> please read the bottom half for the English version. >>>>>>>>>>> >>>>>>>>>>> And yes, I only require a minor binding. I will update the >>>>>>>>>>> case material to include this info. >>>>>>>>>>> >>>>>>>>>>> Regards, >>>>>>>>>>> >>>>>>>>>>> Alan Hargreaves wrote: >>>>>>>>>>>> I am concerned that this update breaks compatibility, yet >>>>>>>>>>>> is being done as a self review. Are there any other >>>>>>>>>>>> consumers of this library that could potentially be broken >>>>>>>>>>>> by this update? If so, how will this be dealt with? >>>>>>>>>>>> >>>>>>>>>>>> What binding are you looking for? As I only see >>>>>>>>>>>> nevada/opensolaris mentioned, I am assuming minor. >>>>>>>>>>>> >>>>>>>>>>>> Can you mention the case number which contains the prior >>>>>>>>>>>> interfaces/bindings? >>>>>>>>>>>> >>>>>>>>>>>> Regards, >>>>>>>>>>>> Alan Hargreaves >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> Yong Young Sun wrote: >>>>>>>>>>>>> Template Version: @(#)sac_nextcase 1.68 02/23/09 SMI >>>>>>>>>>>>> This information is Copyright 2009 Sun Microsystems >>>>>>>>>>>>> 1. Introduction >>>>>>>>>>>>> 1.1. Project/Component Working Name: >>>>>>>>>>>>> Update libchewing from 0.3.0 to 0.3.2 >>>>>>>>>>>>> 1.2. Name of Document Author/Supplier: >>>>>>>>>>>>> Author: Yong Sun >>>>>>>>>>>>> 1.3 Date of This Document: >>>>>>>>>>>>> 27 July, 2009 >>>>>>>>>>>>> >>>>>>>>>>>>> 4. Technical Description >>>>>>>>>>>>> >>>>>>>>>>>>> libchewing is a popular library for Traditional >>>>>>>>>>>>> Chinese input method engine >>>>>>>>>>>>> licensed in LGPLv2.1. And there are some input >>>>>>>>>>>>> methods, like >>>>>>>>>>>>> iiimf-twle-chewing, scim-chewing depends on this >>>>>>>>>>>>> library to provide input >>>>>>>>>>>>> services to users. >>>>>>>>>>>>> >>>>>>>>>>>>> The version currently shipped in nevada/opensolaris is >>>>>>>>>>>>> 0.3.0, while the >>>>>>>>>>>>> community recently released a newer version, 0.3.2. In >>>>>>>>>>>>> this new release, >>>>>>>>>>>>> the API/ABI compatiblities were broken, and some new >>>>>>>>>>>>> features are added. >>>>>>>>>>>>> >>>>>>>>>>>>> iiimf-twle-chewing and scim-chewing had been updated >>>>>>>>>>>>> to work with 0.3.2, >>>>>>>>>>>>> we therefore need to deliver the updated version to >>>>>>>>>>>>> nevada/opensolaris. >>>>>>>>>>>>> >>>>>>>>>>>>> The interfaces (header files and shared library) >>>>>>>>>>>>> remain the same as >>>>>>>>>>>>> before. >>>>>>>>>>>>> >>>>>>>>>>>>> 6. Resources and Schedule >>>>>>>>>>>>> 6.4. Steering Committee requested information >>>>>>>>>>>>> 6.4.1. Consolidation C-team Name: >>>>>>>>>>>>> Globalization >>>>>>>>>>>>> 6.5. ARC review type: Automatic >>>>>>>>>>>>> 6.6. ARC Exposure: open >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>> >>>>>>>>> >>>>>>>> >>>>>>> >>>>>> >>>>> >>>> >>> >> >> -- >> Alan Hargreaves - http://blogs.sun.com/tpenta >> Principal Field Technologist (Kernel/VOSJEC/Performance) >> Asia Pacific/Emerging Markets >> Sun Microsystems >> > > -- > Alan Hargreaves - http://blogs.sun.com/tpenta > Principal Field Technologist (Kernel/VOSJEC/Performance) > Asia Pacific/Emerging Markets > Sun Microsystems > From Alan.Hargreaves@sun.com Wed Jul 29 15:46:18 2009 Received: from sunmail5.uk.sun.com (sunmail5.UK.Sun.COM [129.156.85.165]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id n6TMkHqJ014290 for ; Wed, 29 Jul 2009 15:46:17 -0700 (PDT) Received: from nwk-avmta-1.SFBay.Sun.COM (nwk-avmta-1.SFBay.Sun.COM [129.146.11.74]) by sunmail5.uk.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id n6TMkE8q005006; Wed, 29 Jul 2009 23:46:16 +0100 (BST) Received: from pmxchannel-daemon.nwk-avmta-1.sfbay.Sun.COM by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0KNK00N03F934O00@nwk-avmta-1.sfbay.Sun.COM>; Wed, 29 Jul 2009 15:46:15 -0700 (PDT) Received: from sineb-mail-2.sun.com ([192.18.19.7]) by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KNK00HP7F92BN30@nwk-avmta-1.sfbay.Sun.COM>; Wed, 29 Jul 2009 15:46:15 -0700 (PDT) Received: from fe-apac-05.sun.com (fe-apac-05.sun.com [192.18.19.176] (may be forged)) by sineb-mail-2.sun.com (8.13.6+Sun/8.12.9) with ESMTP id n6TMkDS7029911; Wed, 29 Jul 2009 22:46:13 +0000 (GMT) Received: from conversion-daemon.mail-apac.sun.com by mail-apac.sun.com (Sun Java(tm) System Messaging Server 7u2-7.02 64bit (built Apr 16 2009)) id <0KNK00J00F2ZG800@mail-apac.sun.com>; Thu, 30 Jul 2009 06:46:13 +0800 (SGT) Received: from [129.158.12.60] ([unknown] [129.158.12.60]) by mail-apac.sun.com (Sun Java(tm) System Messaging Server 7u2-7.02 64bit (built Apr 16 2009)) with ESMTPSA id <0KNK00JLAF8ZE640@mail-apac.sun.com>; Thu, 30 Jul 2009 06:46:13 +0800 (SGT) Date: Thu, 30 Jul 2009 08:45:06 +1000 From: Alan Hargreaves Subject: Re: Update libchewing from 0.3.0 to 0.3.2 [PSARC/2009/416 Self Review] In-reply-to: <4A708DF1.7000204@sun.com> Sender: Alan.Hargreaves@sun.com To: "Garrett D'Amore" Cc: Yong Sun , PSARC-ext@sun.com, gto-ext@sun.com Message-id: <4A70D0F2.9000101@Sun.COM> MIME-version: 1.0 Content-type: text/plain; CHARSET=US-ASCII; format=flowed Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 References: <200907280546.n6S5k9AY004168@sac.sfbay.sun.com> <4A6E956E.5000301@Sun.COM> <4A6EA066.206@Sun.COM> <4A6EA39A.4060806@Sun.COM> <4A6EB3C9.8000402@Sun.COM> <4A6EB474.4060704@Sun.COM> <4A6EB637.5020806@Sun.COM> <4A6EB837.5080507@Sun.COM> <4A6EBC32.3030101@Sun.COM> <4A6EBE47.9030800@sun.com> <4A6EBFD9.4060100@Sun.COM> <4A6FC73E.9000305@Sun.COM> <4A708160.7090705@Sun.COM> <4A708DF1.7000204@sun.com> User-Agent: Thunderbird 2.0.0.22 (X11/20090706) Status: RO Content-Length: 10856 I've so marked it approved and added some comments.. alan. Garrett D'Amore wrote: > With that, I'm happy, and the case can be closed approved. > > - Garrett > > Alan Hargreaves wrote: >> >> After some discussion between Yong Sun, Garrett and myself Yong Sun >> decided to go with option #2 and modified the case as follows: >> >> Template Version: @(#)sac_nextcase 1.68 02/23/09 SMI >> This information is Copyright 2009 Sun Microsystems >> 1. Introduction >> 1.1. Project/Component Working Name: >> Update libchewing from 0.3.0 to 0.3.2 >> 1.2. Name of Document Author/Supplier: >> Author: Yong Sun >> 1.3 Date of This Document: >> 27 July, 2009 >> >> 4. Technical Description >> >> libchewing is a popular library for Traditional Chinese input >> method engine >> licensed in LGPLv2.1. And there are some input methods, like >> iiimf-twle-chewing, scim-chewing depends on this library to >> provide input >> services to users. >> >> The version currently shipped in nevada/opensolaris is 0.3.0, >> while the >> community recently released a newer version, 0.3.2. In this new >> release, >> the API/ABI compatiblities were broken, and some new features are >> added. >> >> iiimf-twle-chewing and scim-chewing had been updated to work with >> 0.3.2, >> we therefore need to deliver the updated version to >> nevada/opensolaris. >> >> The interfaces (header files and shared library) remain the same as >> before, i.e., Project Private. >> >> This project extends PSARC/2005/525 by merging PSARC/2008/418 into >> it so that scim-chewing can use the project private interfaces of >> libchewing. Both projects are maintained by the same team (G11N >> input >> method engineer team) and deliver into the same consolidation. >> 6. Resources and Schedule >> 6.4. Steering Committee requested information >> 6.4.1. Consolidation C-team Name: >> Globalization >> 6.5. ARC review type: Automatic >> 6.6. ARC Exposure: open >> >> >> Alan Hargreaves wrote: >>> >>> Yong Sun, I'd be a lot more comfortable with this if you took one of >>> the two suggested courses. That is >>> >>> 1. Contract the required interfaces >>> 2. Extend the original project to include the new deliverable >>> >>> This week's meeting will be held at 10am Pacific time tomorrow >>> (about 13 hours from now). >>> >>> Regards, >>> Alan Hargreaves >>> >>> Alan Hargreaves wrote: >>>> done. >>>> >>>> alan. >>>> >>>> Garrett D'Amore wrote: >>>>> It looks like this stuff is coming together, but I'd like to >>>>> propose for now promoting this to a regular fast track. I don't >>>>> see anything intrinsically wrong here, and the case will almost >>>>> certainly be approved on Wednesday. Having it be a fast track >>>>> gives me a warm fuzzy knowing that the details are properly >>>>> handled here at ARC before the underlying code is delivered into >>>>> any consolidation. >>>>> >>>>> Either one of you can change the case to a fast track. Please set >>>>> the time out for Thursday if you like; its shorter than the norm >>>>> for a fast track, but if things look like they haven't gelled >>>>> properly on Wednesday we can ask for more time at that point. >>>>> >>>>> (And as I said, I'd be rather surprised at this point if we don't >>>>> get the administrivia here dealt with properly by then.) >>>>> >>>>> -- Garrett >>>>> >>>>> Alan Hargreaves wrote: >>>>>> Another option that you have, if we are talking about delivering >>>>>> into the same consolidation may also be instead of contracting >>>>>> the interfaces, use this case to extend the original to include >>>>>> the new code that needs the library. This would make some sense >>>>>> given that the one group is looking after everything here. >>>>>> >>>>>> alan. >>>>>> >>>>>> Alan Hargreaves wrote: >>>>>>> Excellent. That makes the contract easy and the case much >>>>>>> simpler. I would suggest leave the stability of libchewing as it >>>>>>> is. Fill out the contract form and place a copy in the directory >>>>>>> of this case (as well as the email I think). >>>>>>> >>>>>>> Other PSARC folks, have I missed anything here? >>>>>>> >>>>>>> alan. >>>>>>> >>>>>>> Yong Sun wrote: >>>>>>>> Hi, Alan, >>>>>>>> >>>>>>>> We (G11N input-method engineer team) are actually the people >>>>>>>> who maintaining the solaris porting of libchewing, >>>>>>>> scim-chewing, and iiimf-twle-chewing (we also developed this >>>>>>>> one). :) >>>>>>>> >>>>>>>> Regards, >>>>>>>> >>>>>>>> Alan Hargreaves wrote: >>>>>>>>> All that having a contract means is that within the developer >>>>>>>>> groups working on these two projects for Solaris/OpenSolaris >>>>>>>>> there is an agreement that if a change is to be made to the >>>>>>>>> library that the scim people will be notified. >>>>>>>>> >>>>>>>>> This looks a lot closer to what you actually want. >>>>>>>>> >>>>>>>>> alan. >>>>>>>>> >>>>>>>>> Yong Sun wrote: >>>>>>>>>> No, I don't intend to promote it to committed, probably >>>>>>>>>> uncommitted is fine. >>>>>>>>>> >>>>>>>>>> I attached all API changes (in diff format), most of them are >>>>>>>>>> about initialization, configuration, and candidate iterating. >>>>>>>>>> And some interfaces are removed (or moved to internal >>>>>>>>>> private), like char/utf8_char utilities, user_phrase >>>>>>>>>> manipulating, zuin/pinyin utilities. >>>>>>>>>> >>>>>>>>>> And libchewing, scim-chewing, iiimf-twle-chewing are all >>>>>>>>>> community opensource softwares. I don't know if we need/could >>>>>>>>>> have a contract for them. >>>>>>>>>> >>>>>>>>>> Regards, >>>>>>>>>> >>>>>>>>>> Alan Hargreaves wrote: >>>>>>>>>>> So, if I read the prior cases correctly, you are promoting >>>>>>>>>>> libchewing form Project/Private to something else >>>>>>>>>>> (Committed?) and we do have some incompatible changes to >>>>>>>>>>> interfaces. >>>>>>>>>>> >>>>>>>>>>> Can you perhaps outline what the incompatible changes are? >>>>>>>>>>> >>>>>>>>>>> Might it be a better idea to leave the stability of >>>>>>>>>>> libchewing as it currently is (Project/Private under the old >>>>>>>>>>> stability system) and have contract scim-chewing take out a >>>>>>>>>>> contract? >>>>>>>>>>> >>>>>>>>>>> My feeling is that if you want to raise the stability, this >>>>>>>>>>> case should probably be promoted to a fast track. >>>>>>>>>>> >>>>>>>>>>> Regards, >>>>>>>>>>> Alan Hargreaves >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> Yong Sun wrote: >>>>>>>>>>>> Hi, Alan, Garrett, >>>>>>>>>>>> >>>>>>>>>>>> Thanks for reviewing. >>>>>>>>>>>> >>>>>>>>>>>> The initial integration of libchewing is covered in >>>>>>>>>>>> PSARC/2005/525, as a project private interface, located in >>>>>>>>>>>> /usr/lib/iiim. And when scim is integrated (covered in >>>>>>>>>>>> PSARC/2008/418), libchewing is required both by >>>>>>>>>>>> scim-chewing and iiimf-twle-chewing, so it's moved to >>>>>>>>>>>> /usr/lib. >>>>>>>>>>>> >>>>>>>>>>>> Currently, there is no other client applications depends on >>>>>>>>>>>> libchewing, besides scim-chewing and iiimf-twle-chewing. >>>>>>>>>>>> >>>>>>>>>>>> Here is the release announcement for version 0.3.2, which >>>>>>>>>>>> lists the what's new, >>>>>>>>>>>> http://groups.google.com/group/chewing/browse_thread/thread/0067e04c8ea29ff3, >>>>>>>>>>>> please read the bottom half for the English version. >>>>>>>>>>>> >>>>>>>>>>>> And yes, I only require a minor binding. I will update the >>>>>>>>>>>> case material to include this info. >>>>>>>>>>>> >>>>>>>>>>>> Regards, >>>>>>>>>>>> >>>>>>>>>>>> Alan Hargreaves wrote: >>>>>>>>>>>>> I am concerned that this update breaks compatibility, yet >>>>>>>>>>>>> is being done as a self review. Are there any other >>>>>>>>>>>>> consumers of this library that could potentially be broken >>>>>>>>>>>>> by this update? If so, how will this be dealt with? >>>>>>>>>>>>> >>>>>>>>>>>>> What binding are you looking for? As I only see >>>>>>>>>>>>> nevada/opensolaris mentioned, I am assuming minor. >>>>>>>>>>>>> >>>>>>>>>>>>> Can you mention the case number which contains the prior >>>>>>>>>>>>> interfaces/bindings? >>>>>>>>>>>>> >>>>>>>>>>>>> Regards, >>>>>>>>>>>>> Alan Hargreaves >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> Yong Young Sun wrote: >>>>>>>>>>>>>> Template Version: @(#)sac_nextcase 1.68 02/23/09 SMI >>>>>>>>>>>>>> This information is Copyright 2009 Sun Microsystems >>>>>>>>>>>>>> 1. Introduction >>>>>>>>>>>>>> 1.1. Project/Component Working Name: >>>>>>>>>>>>>> Update libchewing from 0.3.0 to 0.3.2 >>>>>>>>>>>>>> 1.2. Name of Document Author/Supplier: >>>>>>>>>>>>>> Author: Yong Sun >>>>>>>>>>>>>> 1.3 Date of This Document: >>>>>>>>>>>>>> 27 July, 2009 >>>>>>>>>>>>>> >>>>>>>>>>>>>> 4. Technical Description >>>>>>>>>>>>>> >>>>>>>>>>>>>> libchewing is a popular library for Traditional >>>>>>>>>>>>>> Chinese input method engine >>>>>>>>>>>>>> licensed in LGPLv2.1. And there are some input >>>>>>>>>>>>>> methods, like >>>>>>>>>>>>>> iiimf-twle-chewing, scim-chewing depends on this >>>>>>>>>>>>>> library to provide input >>>>>>>>>>>>>> services to users. >>>>>>>>>>>>>> >>>>>>>>>>>>>> The version currently shipped in nevada/opensolaris >>>>>>>>>>>>>> is 0.3.0, while the >>>>>>>>>>>>>> community recently released a newer version, 0.3.2. >>>>>>>>>>>>>> In this new release, >>>>>>>>>>>>>> the API/ABI compatiblities were broken, and some new >>>>>>>>>>>>>> features are added. >>>>>>>>>>>>>> >>>>>>>>>>>>>> iiimf-twle-chewing and scim-chewing had been updated >>>>>>>>>>>>>> to work with 0.3.2, >>>>>>>>>>>>>> we therefore need to deliver the updated version to >>>>>>>>>>>>>> nevada/opensolaris. >>>>>>>>>>>>>> >>>>>>>>>>>>>> The interfaces (header files and shared library) >>>>>>>>>>>>>> remain the same as >>>>>>>>>>>>>> before. >>>>>>>>>>>>>> >>>>>>>>>>>>>> 6. Resources and Schedule >>>>>>>>>>>>>> 6.4. Steering Committee requested information >>>>>>>>>>>>>> 6.4.1. Consolidation C-team Name: >>>>>>>>>>>>>> Globalization >>>>>>>>>>>>>> 6.5. ARC review type: Automatic >>>>>>>>>>>>>> 6.6. ARC Exposure: open >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>> >>>>>>>>> >>>>>>>> >>>>>>> >>>>>> >>>>> >>>> >>> >>> -- >>> Alan Hargreaves - http://blogs.sun.com/tpenta >>> Principal Field Technologist (Kernel/VOSJEC/Performance) >>> Asia Pacific/Emerging Markets >>> Sun Microsystems >>> >> >> -- >> Alan Hargreaves - http://blogs.sun.com/tpenta >> Principal Field Technologist (Kernel/VOSJEC/Performance) >> Asia Pacific/Emerging Markets >> Sun Microsystems >> > -- Alan Hargreaves - http://blogs.sun.com/tpenta Principal Field Technologist (Kernel/VOSJEC/Performance) Asia Pacific/Emerging Markets Sun Microsystems From Alan.Hargreaves@Sun.COM Wed Jul 29 15:57:40 2009 Received: from sunmail5.uk.sun.com (sunmail5.UK.Sun.COM [129.156.85.165]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id n6TMvdgo014762 for ; Wed, 29 Jul 2009 15:57:40 -0700 (PDT) Received: from nwk-avmta-1.SFBay.Sun.COM (nwk-avmta-1.SFBay.Sun.COM [129.146.11.74]) by sunmail5.uk.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id n6TMvcTC012440; Wed, 29 Jul 2009 23:57:38 +0100 (BST) Received: from pmxchannel-daemon.nwk-avmta-1.sfbay.Sun.COM by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0KNK00201FS2BD00@nwk-avmta-1.sfbay.Sun.COM>; Wed, 29 Jul 2009 15:57:38 -0700 (PDT) Received: from sineb-mail-1.sun.com ([192.18.19.6]) by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KNK00HRRFS0BP30@nwk-avmta-1.sfbay.Sun.COM>; Wed, 29 Jul 2009 15:57:37 -0700 (PDT) Received: from fe-apac-05.sun.com (fe-apac-05.sun.com [192.18.19.176] (may be forged)) by sineb-mail-1.sun.com (8.13.6+Sun/8.12.9) with ESMTP id n6TMvaJ8009750; Wed, 29 Jul 2009 22:57:36 +0000 (GMT) Received: from conversion-daemon.mail-apac.sun.com by mail-apac.sun.com (Sun Java(tm) System Messaging Server 7u2-7.02 64bit (built Apr 16 2009)) id <0KNK00K00FEDVC00@mail-apac.sun.com>; Thu, 30 Jul 2009 06:57:36 +0800 (SGT) Received: from [129.158.12.60] ([unknown] [129.158.12.60]) by mail-apac.sun.com (Sun Java(tm) System Messaging Server 7u2-7.02 64bit (built Apr 16 2009)) with ESMTPSA id <0KNK00JNJFRXE640@mail-apac.sun.com>; Thu, 30 Jul 2009 06:57:36 +0800 (SGT) Date: Thu, 30 Jul 2009 08:56:28 +1000 From: Alan Hargreaves Subject: [Resend due to tool breakage] Re: Update libchewing from 0.3.0 to 0.3.2 [PSARC/2009/416 Self Review] In-reply-to: <4A708DF1.7000204@sun.com> Sender: Alan.Hargreaves@Sun.COM To: "Garrett D'Amore" Cc: Yong Sun , PSARC-ext@Sun.COM, gto-ext@Sun.COM Message-id: <4A70D39C.90403@Sun.COM> MIME-version: 1.0 Content-type: text/plain; CHARSET=US-ASCII; format=flowed Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 References: <200907280546.n6S5k9AY004168@sac.sfbay.sun.com> <4A6E956E.5000301@Sun.COM> <4A6EA066.206@Sun.COM> <4A6EA39A.4060806@Sun.COM> <4A6EB3C9.8000402@Sun.COM> <4A6EB474.4060704@Sun.COM> <4A6EB637.5020806@Sun.COM> <4A6EB837.5080507@Sun.COM> <4A6EBC32.3030101@Sun.COM> <4A6EBE47.9030800@sun.com> <4A6EBFD9.4060100@Sun.COM> <4A6FC73E.9000305@Sun.COM> <4A708160.7090705@Sun.COM> <4A708DF1.7000204@sun.com> User-Agent: Thunderbird 2.0.0.22 (X11/20090706) Status: RO Content-Length: 10855 I've so marked it approved and added some comments. alan. Garrett D'Amore wrote: > With that, I'm happy, and the case can be closed approved. > > - Garrett > > Alan Hargreaves wrote: >> >> After some discussion between Yong Sun, Garrett and myself Yong Sun >> decided to go with option #2 and modified the case as follows: >> >> Template Version: @(#)sac_nextcase 1.68 02/23/09 SMI >> This information is Copyright 2009 Sun Microsystems >> 1. Introduction >> 1.1. Project/Component Working Name: >> Update libchewing from 0.3.0 to 0.3.2 >> 1.2. Name of Document Author/Supplier: >> Author: Yong Sun >> 1.3 Date of This Document: >> 27 July, 2009 >> >> 4. Technical Description >> >> libchewing is a popular library for Traditional Chinese input >> method engine >> licensed in LGPLv2.1. And there are some input methods, like >> iiimf-twle-chewing, scim-chewing depends on this library to >> provide input >> services to users. >> >> The version currently shipped in nevada/opensolaris is 0.3.0, >> while the >> community recently released a newer version, 0.3.2. In this new >> release, >> the API/ABI compatiblities were broken, and some new features are >> added. >> >> iiimf-twle-chewing and scim-chewing had been updated to work with >> 0.3.2, >> we therefore need to deliver the updated version to >> nevada/opensolaris. >> >> The interfaces (header files and shared library) remain the same as >> before, i.e., Project Private. >> >> This project extends PSARC/2005/525 by merging PSARC/2008/418 into >> it so that scim-chewing can use the project private interfaces of >> libchewing. Both projects are maintained by the same team (G11N >> input >> method engineer team) and deliver into the same consolidation. >> 6. Resources and Schedule >> 6.4. Steering Committee requested information >> 6.4.1. Consolidation C-team Name: >> Globalization >> 6.5. ARC review type: Automatic >> 6.6. ARC Exposure: open >> >> >> Alan Hargreaves wrote: >>> >>> Yong Sun, I'd be a lot more comfortable with this if you took one of >>> the two suggested courses. That is >>> >>> 1. Contract the required interfaces >>> 2. Extend the original project to include the new deliverable >>> >>> This week's meeting will be held at 10am Pacific time tomorrow >>> (about 13 hours from now). >>> >>> Regards, >>> Alan Hargreaves >>> >>> Alan Hargreaves wrote: >>>> done. >>>> >>>> alan. >>>> >>>> Garrett D'Amore wrote: >>>>> It looks like this stuff is coming together, but I'd like to >>>>> propose for now promoting this to a regular fast track. I don't >>>>> see anything intrinsically wrong here, and the case will almost >>>>> certainly be approved on Wednesday. Having it be a fast track >>>>> gives me a warm fuzzy knowing that the details are properly >>>>> handled here at ARC before the underlying code is delivered into >>>>> any consolidation. >>>>> >>>>> Either one of you can change the case to a fast track. Please set >>>>> the time out for Thursday if you like; its shorter than the norm >>>>> for a fast track, but if things look like they haven't gelled >>>>> properly on Wednesday we can ask for more time at that point. >>>>> >>>>> (And as I said, I'd be rather surprised at this point if we don't >>>>> get the administrivia here dealt with properly by then.) >>>>> >>>>> -- Garrett >>>>> >>>>> Alan Hargreaves wrote: >>>>>> Another option that you have, if we are talking about delivering >>>>>> into the same consolidation may also be instead of contracting >>>>>> the interfaces, use this case to extend the original to include >>>>>> the new code that needs the library. This would make some sense >>>>>> given that the one group is looking after everything here. >>>>>> >>>>>> alan. >>>>>> >>>>>> Alan Hargreaves wrote: >>>>>>> Excellent. That makes the contract easy and the case much >>>>>>> simpler. I would suggest leave the stability of libchewing as it >>>>>>> is. Fill out the contract form and place a copy in the directory >>>>>>> of this case (as well as the email I think). >>>>>>> >>>>>>> Other PSARC folks, have I missed anything here? >>>>>>> >>>>>>> alan. >>>>>>> >>>>>>> Yong Sun wrote: >>>>>>>> Hi, Alan, >>>>>>>> >>>>>>>> We (G11N input-method engineer team) are actually the people >>>>>>>> who maintaining the solaris porting of libchewing, >>>>>>>> scim-chewing, and iiimf-twle-chewing (we also developed this >>>>>>>> one). :) >>>>>>>> >>>>>>>> Regards, >>>>>>>> >>>>>>>> Alan Hargreaves wrote: >>>>>>>>> All that having a contract means is that within the developer >>>>>>>>> groups working on these two projects for Solaris/OpenSolaris >>>>>>>>> there is an agreement that if a change is to be made to the >>>>>>>>> library that the scim people will be notified. >>>>>>>>> >>>>>>>>> This looks a lot closer to what you actually want. >>>>>>>>> >>>>>>>>> alan. >>>>>>>>> >>>>>>>>> Yong Sun wrote: >>>>>>>>>> No, I don't intend to promote it to committed, probably >>>>>>>>>> uncommitted is fine. >>>>>>>>>> >>>>>>>>>> I attached all API changes (in diff format), most of them are >>>>>>>>>> about initialization, configuration, and candidate iterating. >>>>>>>>>> And some interfaces are removed (or moved to internal >>>>>>>>>> private), like char/utf8_char utilities, user_phrase >>>>>>>>>> manipulating, zuin/pinyin utilities. >>>>>>>>>> >>>>>>>>>> And libchewing, scim-chewing, iiimf-twle-chewing are all >>>>>>>>>> community opensource softwares. I don't know if we need/could >>>>>>>>>> have a contract for them. >>>>>>>>>> >>>>>>>>>> Regards, >>>>>>>>>> >>>>>>>>>> Alan Hargreaves wrote: >>>>>>>>>>> So, if I read the prior cases correctly, you are promoting >>>>>>>>>>> libchewing form Project/Private to something else >>>>>>>>>>> (Committed?) and we do have some incompatible changes to >>>>>>>>>>> interfaces. >>>>>>>>>>> >>>>>>>>>>> Can you perhaps outline what the incompatible changes are? >>>>>>>>>>> >>>>>>>>>>> Might it be a better idea to leave the stability of >>>>>>>>>>> libchewing as it currently is (Project/Private under the old >>>>>>>>>>> stability system) and have contract scim-chewing take out a >>>>>>>>>>> contract? >>>>>>>>>>> >>>>>>>>>>> My feeling is that if you want to raise the stability, this >>>>>>>>>>> case should probably be promoted to a fast track. >>>>>>>>>>> >>>>>>>>>>> Regards, >>>>>>>>>>> Alan Hargreaves >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> Yong Sun wrote: >>>>>>>>>>>> Hi, Alan, Garrett, >>>>>>>>>>>> >>>>>>>>>>>> Thanks for reviewing. >>>>>>>>>>>> >>>>>>>>>>>> The initial integration of libchewing is covered in >>>>>>>>>>>> PSARC/2005/525, as a project private interface, located in >>>>>>>>>>>> /usr/lib/iiim. And when scim is integrated (covered in >>>>>>>>>>>> PSARC/2008/418), libchewing is required both by >>>>>>>>>>>> scim-chewing and iiimf-twle-chewing, so it's moved to >>>>>>>>>>>> /usr/lib. >>>>>>>>>>>> >>>>>>>>>>>> Currently, there is no other client applications depends on >>>>>>>>>>>> libchewing, besides scim-chewing and iiimf-twle-chewing. >>>>>>>>>>>> >>>>>>>>>>>> Here is the release announcement for version 0.3.2, which >>>>>>>>>>>> lists the what's new, >>>>>>>>>>>> http://groups.google.com/group/chewing/browse_thread/thread/0067e04c8ea29ff3, >>>>>>>>>>>> please read the bottom half for the English version. >>>>>>>>>>>> >>>>>>>>>>>> And yes, I only require a minor binding. I will update the >>>>>>>>>>>> case material to include this info. >>>>>>>>>>>> >>>>>>>>>>>> Regards, >>>>>>>>>>>> >>>>>>>>>>>> Alan Hargreaves wrote: >>>>>>>>>>>>> I am concerned that this update breaks compatibility, yet >>>>>>>>>>>>> is being done as a self review. Are there any other >>>>>>>>>>>>> consumers of this library that could potentially be broken >>>>>>>>>>>>> by this update? If so, how will this be dealt with? >>>>>>>>>>>>> >>>>>>>>>>>>> What binding are you looking for? As I only see >>>>>>>>>>>>> nevada/opensolaris mentioned, I am assuming minor. >>>>>>>>>>>>> >>>>>>>>>>>>> Can you mention the case number which contains the prior >>>>>>>>>>>>> interfaces/bindings? >>>>>>>>>>>>> >>>>>>>>>>>>> Regards, >>>>>>>>>>>>> Alan Hargreaves >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> Yong Young Sun wrote: >>>>>>>>>>>>>> Template Version: @(#)sac_nextcase 1.68 02/23/09 SMI >>>>>>>>>>>>>> This information is Copyright 2009 Sun Microsystems >>>>>>>>>>>>>> 1. Introduction >>>>>>>>>>>>>> 1.1. Project/Component Working Name: >>>>>>>>>>>>>> Update libchewing from 0.3.0 to 0.3.2 >>>>>>>>>>>>>> 1.2. Name of Document Author/Supplier: >>>>>>>>>>>>>> Author: Yong Sun >>>>>>>>>>>>>> 1.3 Date of This Document: >>>>>>>>>>>>>> 27 July, 2009 >>>>>>>>>>>>>> >>>>>>>>>>>>>> 4. Technical Description >>>>>>>>>>>>>> >>>>>>>>>>>>>> libchewing is a popular library for Traditional >>>>>>>>>>>>>> Chinese input method engine >>>>>>>>>>>>>> licensed in LGPLv2.1. And there are some input >>>>>>>>>>>>>> methods, like >>>>>>>>>>>>>> iiimf-twle-chewing, scim-chewing depends on this >>>>>>>>>>>>>> library to provide input >>>>>>>>>>>>>> services to users. >>>>>>>>>>>>>> >>>>>>>>>>>>>> The version currently shipped in nevada/opensolaris >>>>>>>>>>>>>> is 0.3.0, while the >>>>>>>>>>>>>> community recently released a newer version, 0.3.2. >>>>>>>>>>>>>> In this new release, >>>>>>>>>>>>>> the API/ABI compatiblities were broken, and some new >>>>>>>>>>>>>> features are added. >>>>>>>>>>>>>> >>>>>>>>>>>>>> iiimf-twle-chewing and scim-chewing had been updated >>>>>>>>>>>>>> to work with 0.3.2, >>>>>>>>>>>>>> we therefore need to deliver the updated version to >>>>>>>>>>>>>> nevada/opensolaris. >>>>>>>>>>>>>> >>>>>>>>>>>>>> The interfaces (header files and shared library) >>>>>>>>>>>>>> remain the same as >>>>>>>>>>>>>> before. >>>>>>>>>>>>>> >>>>>>>>>>>>>> 6. Resources and Schedule >>>>>>>>>>>>>> 6.4. Steering Committee requested information >>>>>>>>>>>>>> 6.4.1. Consolidation C-team Name: >>>>>>>>>>>>>> Globalization >>>>>>>>>>>>>> 6.5. ARC review type: Automatic >>>>>>>>>>>>>> 6.6. ARC Exposure: open >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>> >>>>>>>>> >>>>>>>> >>>>>>> >>>>>> >>>>> >>>> >>> >>> -- >>> Alan Hargreaves - http://blogs.sun.com/tpenta >>> Principal Field Technologist (Kernel/VOSJEC/Performance) >>> Asia Pacific/Emerging Markets >>> Sun Microsystems >>> >> >> -- >> Alan Hargreaves - http://blogs.sun.com/tpenta >> Principal Field Technologist (Kernel/VOSJEC/Performance) >> Asia Pacific/Emerging Markets >> Sun Microsystems >> > -- Alan Hargreaves - http://blogs.sun.com/tpenta Principal Field Technologist (Kernel/VOSJEC/Performance) Asia Pacific/Emerging Markets Sun Microsystems