--===============1222783247==
Content-Type: multipart/signed;
	boundary="nextPart12407238.eesTEJcuhc";
	 protocol="application/pgp-signature";
	 micalg=pgp-sha1


--nextPart12407238.eesTEJcuhc
Content-Type: text/plain;
  charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

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.

Re-reading my mail I'm shamed to say I forgot to point out that while the=20
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)
* Getting a phone-conference system up (landline or skype or so) for core=20
developers to coordinate (to avoid duplicating work and releasing stress=20
that comes from electronic communication)
* your input here ;)

Btw, I just finished recompiling and did some reading/hacking etc, its nice=
=20
to see a rather large jump in functionality since the last time I looked.=20
Great progress guys! And cool stuff too!
=2D-=20
Thomas Zander

--nextPart12407238.eesTEJcuhc
Content-Type: application/pgp-signature; name=signature.asc 
Content-Description: This is a digitally signed message part.

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

iD8DBQBHud7RCojCW6H2z/QRAi/cAKCFely2skH6aPpb647QrIe2RhPMxgCgqQBU
5SX3/WHtFsJ3XL2+v4KdFgE=
=+4P3
-----END PGP SIGNATURE-----

--nextPart12407238.eesTEJcuhc--

--===============1222783247==
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

--===============1222783247==--