No subject
Thu Aug 25 14:47:23 CEST 2005
"The site is currently pretty sparse, but that's where the users come
in :-) I started a little bit of my personal developer page showing
off some of my work on Extenders, and Aaron has been filling out the
news section as time permits, but it's really up to the community to
use this or not at this point. I, for one, hope we do!"
So people:
1) This wiki should only have content for contributors that have experience=
=20
on this new project that doesn't yet exist and are familiar with an=20
undocumented project.
2) Please write public documentation in accordance with private undocumente=
d=20
conversations.
"the point of the wiki is not to inform new people, but to help developers=
=20
who are already familiar with the project work together." Ahhh KDE, where=
=20
99% of the projects beg for new blood, and the other 1% actively turn peopl=
e=20
away.
As wiki administrator, I'd recommend that you place guidance on your=20
expectations for content and growth on the site itself. Posting stances on=
=20
this mailing fall into the very trap of: "tracking the progress of the=20
plethora of ideas revolving around Plasma has been somewhat troublesome, as=
=20
they are scattered throughout the usual channels (IRC,mailing list,=20
kde-artists forum)".
Regards,
Wade
On 8/25/05, Matt Broadstone <mbroadst at gmail.com> wrote:
>=20
> On 8/25/05, Wade Olson <wade at corefunction.com> wrote:
> > I agree.
> >
> > You must have been spying on me through my webcam=20
> (need...more...tinfoil)
> > as I updated about 10 wiki pages last night.
> >
> > Alas, it's 5:15 am now and I have to drive straight to a consulting
> > engagement in another state. But I will try to put in some of this
> > information later tonight.
> >
> > Thanks,
> > Wade
> >
> >
> >
> > Vinay Khaitan wrote:
> > Don't you think, All of this should have gone to plasma Wiki ?
> > Well, I already though about contacting Aaron. I really feel,
> > manything is missing in plasma wiki for new developers. The wiki
> > should detail the process.
> >
> No it should not.. Aaron and I talked about this when I was first
> setting up the wiki. The wiki is not meant to be a place where you can
> find out how to get involved and get started, but instead a place
> where you can find lots of specific reference information on the
> internals of Plasma. For instance, this is the reason we have not
> posted instructions on setting up the kde4 environment on the wiki,
> information like this belongs on the main web page. A lot of wade's
> information is OK, but the point of the wiki is not to inform new
> people, but to help developers who are already familiar with the
> project work together.
>=20
> >
> > On 8/24/05, Wade Olson <wadejolson at gmail.com> wrote:
> >
> >
> > Hi Markus,
> >
> > Thanks for the email and welcome!
> >
> > I know that interest is booming for Plasma, which is turning into both =
a
> > blessing and a curse for Aaron. Hopefully with aKademy coming up=20
> shortly,
> > more information and immediate tasks will be forthcoming.
> >
> > In the interim, for people who are just joining this young project, can=
=20
> I
> > recommend:
> > * Give everyone a brief synopsis of your background=20
> (student/professional,
> > home country, software experience, KDE experience)
> > * List where you think you might fit in initially (and remember that no=
t
> > everyone can just step in and do the fun work of drawing on a whiteboar=
d=20
> and
> > having legions do their C++ bidding)
> > * Do your project homework. Learn as much about Plasma as you can from:
> > http://plasma.kde.org/cms/1086
> > http://plasma.kde.org/wiki/
> >
> >=20
> http://kde-artists.org/main/component/option,com_smf/Itemid,48/expv,0/boa=
rd,5.0
> > http://appeal.kde.org/wiki/Appeal
> > http://netdragon.sourceforge.net/ssuperkaramba.html
> > (for historical reference)
> > Competitive analysis: Apple, MS, Gnome, 3rd party widgets
> > * Do your functional homework. For example, if you plan on helping with
> > usability, make sure you are familiar with sites like:
> > http://www.openusability.org/
> > http://www.kde.org/areas/guidelines/html/
> > (and many other interface guidelines...like apple.com <http://apple.com=
>'s=20
> work)
> > Or, if you plan on coding, of course you want to be familiar with:
> > http://developer.kde.org/
> > http://www.trolltech.com/developer/
> > http://qtdeveloper.net/
> > Any site that help with OOA/OOD/Design Patterns
> >
> > These simple steps can help others learn more about you, help Aaron
> > organize skill sets and person-power, and minimize initial delays due t=
o
> > lack of preparation.
> >
> > No matter how people feel about software development bureaucracy, there=
=20
> are
> > very basic project planning and resourcing tasks that have to be=20
> coordinated
> > with such a large disparate group forming so quickly.
> >
> > Not only is Plasma going to be unbelievable, but it's really going to=
=20
> get
> > people to learn about more sophisticated programming techniques,=20
> usability
> > and various testing methodologies. I'd say this group is a microcosm of
> > what going to go on with KDE in general as it expreiences growing pains=
.
> >
> > So welcome, and hold tight while things get organized, but hopefully
> > there's plenty everyone can do in the meantime to sharpen their skills=
=20
> and
> > familiarity.
> >
> > Wade
> >
> > *Note: This email does not necessarily reflect the views of those that=
=20
> know
> > their head from their arse.
> >
> >
> >
> > On 8/24/05, Markus Hofmann <markus.hofmann at gmail.com> wrote:
> >
> >
> > Hi everybody,
> >
> > I want to join the plasma team too.
> >
> > For four weeks I read an interesting article about the plasma project
> > and I subscribed theailing list. With the help of Hans I got kde4
> > compiled on my computer.
> >
> > I don't have experience in QT programming but I'm interested to learn.
> >
> > I'm really motivated to help you.
> >
> > Greeting
> >
> > Markus
> > _______________________________________________
> > Panel-devel mailing list
> > Panel-devel at kde.org
> > https://mail.kde.org/mailman/listinfo/panel-devel
> >
> >
> >
> > _______________________________________________
> > Panel-devel mailing list
> > Panel-devel at kde.org
> > https://mail.kde.org/mailman/listinfo/panel-devel
> >
> >
> >
> >
> >
> >
> >
> > _______________________________________________
> > Panel-devel mailing list
> > Panel-devel at kde.org
> > https://mail.kde.org/mailman/listinfo/panel-devel
> >
> >
> >
> _______________________________________________
> Panel-devel mailing list
> Panel-devel at kde.org
> https://mail.kde.org/mailman/listinfo/panel-devel
>
------=_Part_4873_4924055.1125006172945
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
And the circular logic finally reaches its origin/destination....<br><br>
First sentence on the website: "This is a wiki put up for the develope=
rs of Plasma, the next generation
desktop for KDE 4.0. We are using DokuWiki, which is a standards
compliant, simple to use <a href=3D"http://en.wikipedia.org/wiki/Wiki" clas=
s=3D"interwiki" target=3D"_blank" title=3D"http://en.wikipedia.org/wiki/Wik=
i" style=3D"background-image: url(/wiki/lib/images/interwiki/wp.gif);" oncl=
ick=3D"return svchk()" onkeypress=3D"return svchk()">
Wiki</a>, mainly aimed at creating documentation of any kind."<br>
<br>
* "desktop for KDE 4.0"<br>
* "creating documention of any kind"<br>
<br>
How on earth could someone new to the project think that KDE 4.0 was
needed or they were free to create documentation based on perceived
need? They'd have to be insane.<br>
<br>
More information about the Panel-devel
mailing list