[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-devel
Subject:    Re: Open question to all developers.
From:       AnneWilson <cannewilson () googlemail ! com>
Date:       2008-06-27 6:38:25
Message-ID: 200806270738.26449.anne () lydgate ! org
[Download RAW message or body]

On Friday 27 June 2008 00:26:06 Eligio Becerra Zavala wrote:
> Hi there, I hope you don't mind if I join.
>
> 2008/6/26 Cornelius Schumacher <schumacher@kde.org>:
> > On Thursday 26 June 2008 20:38:11 Aaron J. Seigo wrote:
> > > a user info centric wiki run like techbase is would, imho, work
> > > wonderfully. unlike wiki.kde.org (where the software works fine, but
> > > the content doesn't)
> >
> > I completely agree with that. If we could get a wiki for non-development
> > content started guided by a group of people who feel responsible for
> > organization of the content, quite some of the issues which were
> > mentioned in
> > the original post could be addressed.
>
> I'd like this solution, since information about features/bugs is already in
> the TODO/changelog on SVN.
> I volunteer right now, but we just need to define how will this information
> be structucted.
> Since it's aimed for non-developer user I think the the best way is create
> a wiki with relevant information about apps: current version, known bugs,
> corrected bugs, new features, coming features, next release. I think this
> will cover the information that Tom will want to know.
>
> Something like this
> Plasma:
>
> Version X.Y.Z
>
> Know Bugs
> blah blah blah
>
> Corrected Bugs
> blah blah blah
>
I've mentioned several times that I want to be part of such a project.  After 
the last mention, on Wednesday, I have had an email from a contributor who is 
happy to work with me on this.  There's absolutely no point in duplicating 
effort, so the solution would be for those of us interested to be one team, 
with one wiki project.

Needs that have been identified so far are

a glossary - the language of KDE4 is new and completely baffling without such 
help

a FAQ page - which we can publicise on MLs, to take away some of the incessant 
repeats (yes, I know that many will ask before reading).  I think your idea 
of a status table would link to/from this.

The ability of the group to act as an intermediary with devs.  The intention 
of this is that we should be able to ask devs directly about anything we 
can't resolve from elsewhere, on the principle that they are asked once, 
politely, and we take ownership after that.  It should save the devs some 
considerable trouble.

Does this fit in with your view of the need?

Anne
 
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
[prev in list] [next in list] [prev in thread] [next in thread]