This is a multi-part message in MIME format.
--------------FC9EEB4E981CF5B4D5689631
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Hi folks,

I am a bit curious about how things will work once you folks hit feature
freeze or code freeze stage in KDE 2.0. Does KDE branch off to an
unstable branch like other open source projects? I think it is a bit too
late for the rest of our developers to join your feature freeze cycle as
it will take us some time to ramp up but we are starting. Nevertheless,
there are still several areas and new control panel modules that we
would like to start from scratch. These for sure will not make it in KDE
2.0 in time. Where should we put these projects in KDE's CVS tree and
not affected by your code freeze?

On several side notes, I have also secured half a dozen of our full time
QA people to help you folks with the KDE 1.9 cycle. That is the least we
can do for now to contribute to KDE 2.0 until our developers catch up
with your stream of code. So do expect a lot of bug reports from us
whenever your beta cycle is ready. We have also offered our help to
several developers with bug fixing and the tasks on the open tasks page.
Unfortunately, that page is hopelessly outdated as most of the tasks
that we volunteered are already taken or done. Oh well!

Is there anyone doing nightly builds and packaging for Debian? If not, I
can find someone to do this too. If yes, we can possibly work together
too.

We have also finally hired a full time UI designer for KDE to help you
folks with any UI design issue. His name is Tom Heferek and he is a very
senior UI designer with lots of experience. However, he is new to Linux
and KDE so give him some time to ramp up and he will join the kde
look&feel group as soon as he settles in. (He only started with us two
days ago.) It took us almost 6 months to find a good and experienced UI
designer for KDE.

We are also looking into integrating our Windows and NFS connectivity
code with KDE 2.0 as well but I don't expect we will have a good
solution on this soon enough for KDE 2.0. We are also in the process of
migrating some of our existing control panels in Corel LINUX to KDE 2.0
as well. I am opened to suggestions so please let me know on how we can
help further. Otherwise, we will just wait patiently for KDE 1.9 and let
our QA team do the work. Thanks.

Hans Petter Bieker wrote:

> On Tue, 28 Mar 2000, Andre Charbonneau wrote:
>
> > I have a copy of the standard's draft.  It can be found here:
> > http://wwwold.dkuug.dk/jtc1/sc22/wg20/docs/n634.txt
> > Basically, the standard is about adding new stuff to the POSIX
> system
> > level locale material, and renaming it to "FDCC set".
>
> Looks nice. I have been thinking about adding support for localization
>
> support for papers in KDE, but I think it's too late (feature freez in
>
> kdelibs and stuff).
>
> -bieker-
>
> Norwegian University of Science and Technology, Engineering
> Cybernetics
>                  bieker@stud.ntnu.no / bieker@kde.org

--------------FC9EEB4E981CF5B4D5689631
Content-Type: text/x-vcard; charset=us-ascii;
 name="mingp.vcf"
Content-Transfer-Encoding: 7bit
Content-Description: Card for Ming W. Poon
Content-Disposition: attachment;
 filename="mingp.vcf"

begin:vcard 
n:Poon;Ming
x-mozilla-html:FALSE
url:www.corel.com
org:Corel Corporation;Corel LINUX
adr:;;1600 Carling Avenue;Ottawa;Ontario;K1Z-8R7;Canada
version:2.1
email;internet:mingp@corel.com
title:Development Manager
x-mozilla-cpt:;25344
fn:Ming Poon
end:vcard

--------------FC9EEB4E981CF5B4D5689631--