gmane.comp.kde.devel.core

Reorganising techbase around "Contributor Paths".

Hi,

As far as I know, the focus of techbase is for documentation, information,
policies, schedules etc around producing KDE products, and bringing new
contributors into that. Aspects include coding, translation, documentation,
art, bugfixing etc.

However, currently techbase is mostly structured around development. Other
aspects have been added in places but the main navigation structure of it
does not really reflect that.

http://techbase.kde.org/Welcome_to_KDE_TechBase

On the homepage we have 

* Setting up a KDE development environment (/Getting_Started)
* Developing with KDE (/Development)
* KDE System Administration (/KDE_System_Adminitration) (Should be on
userbase I think)
* Join the KDE Team and Contribute (/Contribute) (This is all about dev, but
with a link to kde.org/getinvolved.)
* ISV Information (/ISV) (Some of this is way out of date. Should it be on a
wiki at all, or is www.kde.org better for this stuff)
* KDE projects (/Projects)

Techbase might have started out being all about development, and we now have
a lot of good development tutorials. We also have a lot of other great
tutorials on internationalization and documentation etc, but the
organization of techbase doesn't make them easy to find.

(Continue reading)

headers

Aaron J. Seigo | 2 Oct 05:51

Re: Reorganising techbase around "Contributor Paths".

On Wednesday 01 October 2008, Stephen Kelly wrote:
> As far as I know, the focus of techbase is for documentation, information,
> policies, schedules etc around producing KDE products, and bringing new
> contributors into that.

not just contributors, but yes.

> Aspects include coding, translation, documentation,
> art, bugfixing etc.

the focus to date has been on technical aspets: coding and system 
administration.

> However, currently techbase is mostly structured around development.

yes, and that's been, at least to this point, purposeful.

> http://techbase.kde.org/Welcome_to_KDE_TechBase
>
> On the homepage we have
>
> * Setting up a KDE development environment (/Getting_Started)
> * Developing with KDE (/Development)
> * KDE System Administration (/KDE_System_Adminitration) (Should be on
> userbase I think)

userbase is about end user information and community.

the sys admin stuff on techb ase is really about more "pro-level" topics.

(Continue reading)

headers

Stephen Kelly | 9 Oct 03:59

Re: Reorganising techbase around "Contributor Paths".

Twice so far I've written this message, and twice kontact has crashed in
response. Each time I rewrite it it gets cut in length by half and the gold
within is lost. I've forgotten a lot of what I wrote the first time. :(
Sorry if this one is blunt.

Aaron J. Seigo wrote:
> On Wednesday 01 October 2008, Stephen Kelly wrote:
> i love this concept, though really it's what http://kde.org/getinvolved/
> is. so the question is: where does it belong?
> 
> moving it to techbase makes sense for two particular reasons, imo: it's a
> wiki so it's easier for people to build up around and we have the
> Contribute/ area.
> 
> so if we took http://kde.org/getinvolved/ and migrated it to Contribute/,
> and then forward http://kde.org/getinvolved/ to Contribute that could make
> sense.

Yes, that would be preferable. Currently getinvolved seems way out of date
and contains many dead links (kde-artists for example). Hopefully it's
something Sam Duff and co will discuss on Friday.

> 
>> The /Schedules, /Projects, /Policies structure probably doesn't need to
>> change imo. /Developer/Tutorials could be moved to /Tutorials and kept as
>> an index of all tutorials.
> 
> so that developers run into art, and artists run into developer tutorials?
> shouldn't we be separating the tutorials into target audiences?

(Continue reading)