From koffice-devel  Tue Feb 19 08:16:11 2008
From: Thomas Zander <zander () kde ! org>
Date: Tue, 19 Feb 2008 08:16:11 +0000
To: koffice-devel
Subject: Re: KWord for 2.0
Message-Id: <200802190916.17430.zander () kde ! org>
X-MARC-Message: https://marc.info/?l=koffice-devel&m=120340904203746
MIME-Version: 1
Content-Type: multipart/mixed; boundary="--===============0978591001=="


--===============0978591001==
Content-Type: multipart/signed;
	boundary="nextPart1271664.XQEapsd0LC";
	 protocol="application/pgp-signature";
	 micalg=pgp-sha1


--nextPart1271664.XQEapsd0LC
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

Hi Cyrille, thanks for your answer :)

On Monday 18 February 2008 20:59:29 Cyrille Berger wrote:
> On Monday 18 February 2008, Thomas Zander wrote:
> > On Monday 18 February 2008 16:49:01 Thomas Zander wrote:
> > > one [org] basically asked me what we need to do to make sure KWord
> > > can be released in 2.0, so we can get someone to do it.
>
> The thing is the we don't have a more extensive list, and honestly, we
> have limited time to work on it, especially has you have seen, koffice
> core developers have decided to concentrate on getting kpresenter out
> (the reasons are detailed here [1]). That said, it doesn't prevent
> anyone to work on KWord, the decision on where to put the effort is up
> to the developer. But indeed, as you mentioned it, coordination is
> crucial.

Indeed, I could probably come up with a list myself. But my main goal here=
=20
is to do this the correct way; which means including anyone that wants to=20
have a say into this todo-list.  Please tell me bugs, missing features=20
etc that are keeping KWord from being releasable.

> > Re-reading my mail I'm shamed to say I forgot to point out that while
> > the goal is clear; to make sure KWord gets a leg up and gets released
> > with 2.0, the best way to do that is still under investigation.
> >
> > Some things we talked about include;
> > * Hiring someone for 3 or 4 months to do the work. (this is our ideal
> > now)
>
> I am sure it can't hurt, and it can certainly brings a lot, so if it
> can be done, it would be great.

The money is mostly a done deal, now we need to find a qualified person=20
that can drop everything he is doing for the next 3-4 months. Thats the=20
hard part :)

Hmm, hard part...
some months ago Boud asked me to leave, and he was right, actually, I was=20
far to close on the subject matter, especially without any time to code=20
things.  My role in this kword-for-2.0 project is uncertain, maybe=20
mentor, maybe sidelines. Not sure yet. One thing is certain in my mind;=20
whatever my role I won't get into any discussions except maybe for the=20
occasional "I meant xyz with that tech". I want to avoid anyone from=20
feeling upset.

Ok, enough sentimentals :)
Be blunt with me, please;  if you think this is a bad idea just say so=20
(preferably also why), or just anything else thats on your mind.

Thanks!
=2D-=20
Thomas Zander

--nextPart1271664.XQEapsd0LC
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQBHupBRCojCW6H2z/QRAnU1AKCIYPFMGcNjzaWYhRjHgGG49LMMbwCfdoVR
7xrRUjGxBlmztJgCLv+7N0I=
=dOoW
-----END PGP SIGNATURE-----

--nextPart1271664.XQEapsd0LC--

--===============0978591001==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
koffice-devel mailing list
koffice-devel@kde.org
https://mail.kde.org/mailman/listinfo/koffice-devel

--===============0978591001==--