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

List:       kde-www
Subject:    Re: Development
From:       Marcos Fouces <mfouces () yahoo ! es>
Date:       2005-04-04 6:45:45
Message-ID: 200504040845.46234.mfouces () yahoo ! es
[Download RAW message or body]

On Monday 04 April 2005 06:53, Carlos Leonhard Woelz wrote:
> On Mon, 04 Apr 2005 01:08:12 +0200, "Marcos Fouces" <mfouces@yahoo.es>
>
> said:
> > I agree. There is jobs info at quality.kde.org at kde.org/jobs...
> >
> > Perhaps something like http://jobs.kde.org with a database of jobs for
> > each
> > oficial app do the point.
> >
> > Each app needs the following:
> >
> > - Programmers
> > - Doc Maintainers
> > - Artists
> > - Usability reports
> > - Accesibility reports
> > - Beta testing
> > - Bug management
> > - Promotion
> > - i18n
> >
> > There's also teams non related to apps dev (events, women...) that could
> > also
> > have specific needs.
>
> The problem with specific jobs (non general tasks) is that someone has
> to maintain the lists of available tasks. The developers do not want to
> do it (I don't blame them: let them code). 

This is exactly why i purposed to create a webteam: to avoid devs dealing with 
those issues.

> I maintain (well, at least 
> used to, and intend to update) the task pages for kdepim. It is done on
> the wiki, to make it easier to change. It worked for some time, until I
> stopped working on it, and it really attracted new volunteers. But you
> have to know the applications involved and the tasks. See the quality
> page to see what I mean:
> http://wiki.kdenews.org/tiki-index.php?page=Quality+Team+KDE+PIM

That's a good starting point but is too tedious to introduce changes by hand. 
I think is better using a database and a litle PHP, something like: 

- http://savannah.gnu.org/people/?group=tasklist

It should also be posible to extract jobs by category, by team, by app...



> From my personal experience, a page like jobs.kde.org won't work,
> unless:
>
> 1) It is a epository for general "jobs descriptions with requirements"
> like the quality page: http://quality.kde.org/develop/modules/
> and / or
> 2) It is a general framework for volunteers to add updated info about
> apps and tasks.


The first point is already done, i said that on a past post, but not the 
second...

> But then again, isn't option 1 already done in the quality pages, and 2
> using the wiki? Why a new framework? 

The wiki need to be edited by hand to update it and visited to know which jobs 
are open. With a database framework it will be posible for project managers 
(or whatever else) to ask for help through a simple form also it can be a 
tailored litle board (combo box or the likes) to show open tasks.

You can see an example at the right bottom of the http://savannah.gnu.org/ 
page. In the box called "Help Wanted".

> Moreover: if you go for (2), I 
> guess you will end up with out of date jobs info, as nobody will update
> it...

Umh.. As explained above, people avoid to do tedious tasks, but IMHO selecting 
3 or 4 options in a form isn't such a case.

Greetings.
_______________________________________________
kde-www mailing list
kde-www@kde.org
https://mail.kde.org/mailman/listinfo/kde-www
[prev in list] [next in list] [prev in thread] [next in thread]