--===============0104821711==
Content-Type: multipart/signed;
  boundary="nextPart1318787.JCotkXdmHm";
  protocol="application/pgp-signature";
  micalg=pgp-sha1
Content-Transfer-Encoding: 7bit

--nextPart1318787.JCotkXdmHm
Content-Type: text/plain;
  charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

On Sunday 30 March 2008, Andreas Pakulat wrote:
> But even though both bindings are in quite good shape - AFAIK and both
> languages should be pre-approved.

+1 for python and ruby.

the fact that they've been around for some years now and apps built with th=
em=20
work well gives me enough confidence to have included-with-KDE-releases app=
s=20
rely on them.

i agree with Andreas that there is room for improvement on both sets of=20
bindings. i think these improvement will happen quicker if they actually ge=
t=20
used more, just like how our libs improve much more rapidly and in useful=20
directions when they get real world use.

=2D-=20
Aaron J. Seigo
humru othro a kohnu se
GPG Fingerprint: 8B8B 2209 0C6F 7C47 B1EA  EE75 D6B7 2EB1 A7F1 DB43

KDE core developer sponsored by Trolltech

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

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.4-svn0 (GNU/Linux)

iD8DBQBH7+X71rcusafx20MRAj0BAKCKQMVIrpUT3a1wAmoMgWjK6+hELgCfZr2d
/+FntXKgXaU6PsidiuA5RLg=
=Bknr
-----END PGP SIGNATURE-----

--nextPart1318787.JCotkXdmHm--

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

_______________________________________________
release-team mailing list
release-team@kde.org
https://mail.kde.org/mailman/listinfo/release-team

--===============0104821711==--