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

On Tuesday 22 May 2007 19:08, Justin Karneges wrote:
> On Tuesday 22 May 2007 4:19 pm, George Staikos wrote:
> > Look, if this whole thing is not about smartcards but instead a
> > backhanded way to get us to give a blind blessing to throwing away
> > the code that's there and using QCA, you're just wasting all our
> > time.
>
> Hmm, the thread seems to be getting a little sour.
>
> I would certainly like to see all of KDE use QCA.  If smartcards are the
> way in, then I'd be pretty happy about that.  Personally, I'm mostly
> interested in providing a migration path for KDE away from openssl, as we=
ll
> as simply being responsible for a major component of my favorite desktop.
>
> However, Alon is here only for smartcards.  You can google his name, he
> makes a fuss at every project about including smartcard support, and he
> doesn't just talk, he writes code.  He has created patches, large code
> contributions, and sometimes entire replacement projects to accomplish his
> goal.
>
> Alon came to QCA, because he thought that it was the place to implement
> smartcard support for KDE.  Who could blame him?  QCA was part of
> kdesupport, it had rudimentary smartcard capability already (by me), and
> QSsl didn't exist yet.  The man is on a mission, and his smartcard plugin
> for QCA is several thousand lines and fully completed.
>
> I just wanted to admit my own bias here, but assure you that Alon is not
> politically motivated.  He's just very insistent, and rolls into every
> project like a boulder. :)
>
> -Justin

While I personally understand his want, I also see the other side of this t=
o,=20
and agree with Aaron that we should meet in the middle ground instead of=20
bullying Thiago and George that "my way is better", since that comes off=20
fairly heavy handed, and people WON'T want to work with you if you call the=
=20
quality work they do crap. To be sure, the best thing to do now is follow=20
Aaron's blueprint of coming up with the front-end API, then the middle-ware=
=20
that will allow for a replacable backend, etc. This way we're getting=20
solutions instead of irritation on all sides.

=2D-=20
Gary L. Greene, Jr.
Sent from: uriel
 19:15:44 up 40 days, 23:31, 11 users,  load average: 0.35, 0.30, 0.31
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
Developer and Project Lead for the AltimatOS open source project
Volunteer Developer for the KDE open source project
 See www.tolharadys.net and www.kde.org for more information
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

Please avoid sending me Word or PowerPoint attachments.

--nextPart3194807.Gf1dLOJAoT
Content-Type: application/pgp-signature

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

iD8DBQBGU6T++psNrGG9CbMRApiyAKCeB0QI1RLvj8wOX3uV06wp1F/GlwCggsU8
ilarBOHOZq5oUfumiCd2/E4=
=PWVR
-----END PGP SIGNATURE-----

--nextPart3194807.Gf1dLOJAoT--