--===============1066986816==
Content-Type: multipart/signed;
  boundary="nextPart2476555.uN9JmyETeT";
  protocol="application/pgp-signature";
  micalg=pgp-sha1
Content-Transfer-Encoding: 7bit

--nextPart2476555.uN9JmyETeT
Content-Type: Text/Plain;
  charset="iso-8859-15"
Content-Transfer-Encoding: quoted-printable

On Wednesday 05 August 2009 09:38:45 Aaron J. Seigo wrote:
> > Somewhere along the line, too, we have to consider how we sell to those
> > users that an alternative way of doing that particular thing has been (=
or
> > is being) done in a plasmoid.  That's often the case.  As far as I can
> > see, if the desired end can be achieved the developer has done his job.
> >  It's then up to the user to learn a new way of working.
>
> agreed; there are three things i can think of that could be done as part =
of
> a multi-facet solution (though i'm not sure what mix would be best right
> now):
>
> * post a clear list of things that will not be re-implemented and why; th=
is
> is FAQ material really and shouldn't be host for discussion.
>
> * write tutorials on the "KDE4 way" to get those things done
>
> * encourage people to look at the features that are new in KDE4, get them
> looking forwards rather than backwards; right now i do fear that we spend=
 a
> lot of time as a community looking over our shoulder. we need to do some =
of
> that, for sure, but probably not as much as we're doing now. unfortunatel=
y,
> our documentation on "stuff you can do with KDE4" is fairly slim due to i=
ts
> youthfulness.
>
> i assume the above is probably what you had in mind as well, or at least
> similar?

Pretty-well, yes. =20

1) WONTFIX list - why not a protected page on UserBase?  It's quite possibl=
e=20
to create a hidden page with the url posted to this list and left open for =
a=20
week or some other agreed period, after which it is linked prominently from=
=20
the Welcome Page or maybe the Intro to KDE page, at the same time as being=
=20
marked Protected.  From that date only sysops will be able to add material,=
=20
but I could handle that.

2) We already have http://userbase.kde.org/Tutorials/KDE3toKDE4.  This need=
s=20
reviewing and updating, with additional information.  I it gets too long I =
can=20
split it into sections with linked pages.  I really think this is the best=
=20
place for it.

3) No real answer, other than to say that if we put 1) and 2) into place we=
=20
can get them productive as quickly as possible, then hopefully have a bette=
r=20
community feeling to enable us to get them looking forward.

Like you, I've seen some converts - quite a few, actually - so I do believe=
 it=20
can be done.  But not without planning and effort.  I'm happy to work on=20
UserBase, but we need lots more people to contribute.  At the moment a very=
=20
few people are carrying the load - and this goes for Translators as well as=
=20
contributors).

And while we're at it, I *have* noticed the huge effort in translations by=
=20
Qiii2006 and Claus_chr.  They are doing a wonderful job.

Anne
=2D-=20
New to KDE4? - get help from http://userbase.kde.org
Just found a cool new feature?  Add it to UserBase

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

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

iEYEABECAAYFAkp5S3EACgkQbMErw/n0TZq1SACcCgchVzDBleJZ6EK4/ebCmBO/
I7gAn2uvdAoOleuvtYGFcQiyDKnNRa9U
=5aKv
-----END PGP SIGNATURE-----

--nextPart2476555.uN9JmyETeT--

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

 
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<

--===============1066986816==--