--nextPart4632502.mLNHfiJ5mN
Content-Transfer-Encoding: 7Bit
Content-Type: text/plain; charset="ISO-8859-1"

On Saturday, December 3, 2011 17:48:17 Lamarque V. Souza wrote:
> https://projects.kde.org/projects/playground/base/libmm-qt
> https://projects.kde.org/projects/playground/base/libnm-qt

i know its relatively late to bring this up, but better before a first initial 
release to do so: is there any chance that these libraries could get more 
descriptive names?

there is already a "libmm" which is actually a shared memory helper, unrelated 
to libmm-qt (though the name suggests otherwise). "mm" and "nm" really don't 
say much about what these libraries do. the names are ambiguous and stand a 
high chance of collision with other libraries.

i know that the networkmanager project decided to call their library libnm, 
but we don't need to repeat such errors ourselves, right? :)

-- 
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 Qt Development Frameworks

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

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

iEYEABECAAYFAk7bNyUACgkQ1rcusafx20N7vQCfShCWu9YK3fw7oeUmuxz8P1s1
8zwAn1IELXYTQqvKy/4lVJT+uwIBMhcb
=17MC
-----END PGP SIGNATURE-----

--nextPart4632502.mLNHfiJ5mN--