This forum has been archived. All content is frozen. Please use KDE Discuss instead.
The Discussions and Opinions forum is a place for open discussion regarding everything related to KDE, within the boundaries of KDE Code of Conduct. If you have a question or need a solution for a KDE problem, please post in the apppropriate forum instead.

FOSS development.

Tags: None
(comma "," separated)
User avatar
Dante Ashton
Registered Member
Posts
525
Karma
3
OS

FOSS development.

Sun Jun 28, 2009 2:03 pm
Hey all, in an attempt to better understand FOSS, I've decided to see how the FOSS development cycle works, compared to the propitiatory software development cycle. If anybody would care to tell me about it, or even just link me to an article, I'd be very grateful :)

-Dante
User avatar
ivan
KDE Developer
Posts
918
Karma
14
OS

Re: FOSS development.

Sun Jun 28, 2009 4:12 pm
Hi,

The development cycle depends more on the project and its staff than its type (Free/Libre Software or proprietary).

In both worlds you have projects that are one-man-show, released-when-ready, released-by-schedule, feature-release-based...
User avatar
anda_skoa
KDE Developer
Posts
783
Karma
4
OS

Re: FOSS development.

Sun Jun 28, 2009 4:14 pm
There isn't necessarily a difference.

Sure, proprietary software is often developed in long cycles, with little or no feedback from users in between. But often doesn't mean always and not all FOSS development is based on release-early-release-often.

Cheers,
_
User avatar
Dante Ashton
Registered Member
Posts
525
Karma
3
OS

Re: FOSS development.

Sun Jun 28, 2009 10:43 pm
As I've come to understand it, a propitery software development cycle seems to dispense with community feedback, rather they are far more interested in development that increases the company's value and chances of survival, even if this means they exploit certain aspects of it and stop developing others.
john_hudson
Registered Member
Posts
549
Karma
2
OS

Re: FOSS development.

Mon Jun 29, 2009 8:39 pm
Historically everything was developed in a waterfall; development went towards a goal with no feedback; then in the 1980s the idea of cycles became popular as this brought feedback into the development at about the time that continuous improvement became one of the themes in quality management.

However, as already pointed out, most people in FOSS were not brought up in this environment and so have developed a wider range of models - some of which are like continuous improvement models but others of which involve parallel development in which separate branches are developed and then merged. None of this is normally planned; everything is much more evolutionary.

NB There is some interesting strategic management research which says that planning makes no difference in good times, only in bad times, when those who have thought about the direction in which they are going appear to do better BUT how they do this is irrelevant. What is significant is that they have a clear goal that enables them to focus on what they need to do in bad times.
User avatar
Dante Ashton
Registered Member
Posts
525
Karma
3
OS

Re: FOSS development.

Tue Jul 07, 2009 4:58 pm
I think it's safe to say that in FOSS, reinventing the wheel isnt done 'quite' as often as in other models.


Bookmarks



Who is online

Registered users: abc72656, Bing [Bot], daret, Google [Bot], Sogou [Bot], Yahoo [Bot]