Linux Today: Linux News On Internet Time.
Search Linux Today
search.internet.com
Linux News Sections:  Blog -  Developer -  High Performance -  Infrastructure -  IT Management -  Security -  Storage -
Linux Today Navigation
LT Home
Preferences
Contribute
Link to Us
Search
Linux Jobs

Become a Marketplace Partner

internet.commerce
Be a Commerce Partner














The Linux Channel at internet.com
Linux Today
Enterprise Linux Today
Apache Today
JustLinux.com
Linux Planet
PHPBuilder
All Linux Devices
Technology Jobs

JustTechJobs.com

LinuxToday Newsletters
Subscribe News
Subscribe PR
Subscribe Security

internet.com
IT
Developer
Internet News
Small Business
Personal Technology

Search internet.com
Advertise
Corporate Info
Newsletters
Tech Jobs
E-mail Offers

 






Current Newswire:

Editor's Note: Making Multi-Channel Firewire Music With Linux

Amaya: A Simple, Yet Useful Alternative to Dreamweaver

Windows 7 Sales Up, But is it Really a Hit?

Over clocking intel i7 on a Gigabyte EX58-Extreme

Novell cuts 3 percent of its workforce, plus benefits

SECURITY: Debunking the Growing Use of Misleading Claims and False Truisms in Cybersecurity

Mavizen's 130 MPH TTX02 Electric Motorcycle Runs on Linux

October 2009 OS stats: Windows 7 passes Snow Leopard, Linux

Linux-Kongress 2009: New filesystems, optimised programming

Google privacy controls: Most people won't care




Server Support Specialist I
The Computer Merchant, Ltd
US-OK-Oklahoma City

Justtechjobs.com Post A Job | Post A Resume
:Advogato: 'Best Practices' for Open Source?
Advogato: 'Best Practices' for Open Source?
Mar 25, 2001, 13 :46 UTC (2 Talkback[s]) (2733 reads)

(Other stories by Stephen Hindle)

"I've been thinking about project management methods & coding standards for use with Open Source Projects. Most programmers would agree that some form of management, and some standards are necessary. Its the which ones part we have problems with. Traditional 'best practices' need a little tweaking to fit with OSS development. So here's my attempt - I would love feedback & suggestions...."

"The main problems with traditional methods/methodologies stem from the fact that they were developed to support scarce resources. A result of this scarcity was that these resources were also expensive. Not only were programmer time, & machine time expensive, distribution was as well. The cost of distribution was not just limited to physically moving the code from one place to another, but often incurred additional expenses such as technicians to install the code. This made frequent releases of development code impractical. A side effect of this was that 'end user' input was often unavailable until the project was nearly completed. As software was so expensive to develop, it was paramount that it be maintainable otherwise there was no hope of recouping the cost of development. These conditions resulted in strict methods that required in-depth requirements docs up front. Users were forced to determine all their needs in advance, with little feedback as development progressed. Detailed specs & designs were produced from the requirements, along with detailed schedules. The entire process was documented heavily, with numerous 'sign-offs' meant to ensure everyone agreed on what needed to be done and how it was to be accomplished. Once implementation was begun, formal coding standards were used to increase code readability, maintainability and shorten the learning curve for new developers. While the methods could be 'heavy' in terms of startup cost, the anticipation was they would reduce the overall project cost & improve the quality of the resultant product."

Complete Story

Related Stories:
Advogato: How to Write Maintainable Code(Mar 18, 2001)
freshmeat.net: A Year of Learning [Leading an Open Source project](Mar 10, 2001)
Advogato: CVS mixed-tagging for massive Open Source Project Management(Feb 21, 2001)
osOpinion: The Coding Compromise: Open Objects(Feb 21, 2001)
Advogato: Thoughts on the world of GUI's(Feb 18, 2001)
Advogato: Semantics and Computing(Feb 13, 2001)
Kuro5hin: Open source considered(Jan 28, 2001)
Career Magazine: Contributing to Open Source Projects(Jan 21, 2001)
First Monday: Internet, Innovation, and Open Source: Actors in the Network(Jan 14, 2001)
32BitsOnline: A look at the Linux Market: Survival of the Fittest (Dec 17, 2000)
First Monday: Essence of Distributed Work: The Case of the Linux Kernel(Nov 13, 2000)
Advogato: Free Source Project Management(Nov 06, 2000)
First Monday: Linux: A Bazaar at the Edge of Chaos(Mar 09, 2000)
Collab.Net: Collab.Net & Opendesk.com Sponsor Development of New Open Source Project Management Spec(May 24, 2000)


Index Mode   |   Flat Mode   |   Thread Mode   |   Thread Flat  
  Talkback(s) Name  and Date
I have a theory.

I think all recent K ...   a theory   
me
Mar 25, 2001, 17:47:03
 
> I have a theory.
> 
> I think all re ...   Re: a theory   
Rick James
Mar 25, 2001, 19:48:10
 
  Home | Search Talkbacks | Customize View    Top of Page  



Enter your comments below:

* Your Name:

* Your Email Address:

* Subject:

CC: [will also send this talkback to an E-Mail address]

* Comments:

Tags allowed:<I>,<B> and <U>. See our talkback-policy for more about talkback content.

Fields marked with * are required!






..............................




All times are recorded in UTC.
Linux is a trademark of Linus Torvalds.
Powered by Linux, Apache and PHP

internet.commediabistro.comJusttechjobs.comGraphics.com

Search:

WebMediaBrands Corporate Info

Legal Notices, Licensing, Reprints, Permissions, Privacy Policy.
Advertise | Newsletters | Shopping | E-mail Offers | Freelance Jobs