From: Benj. Mako Hill Date: Sat, 4 Jun 2005 00:08:45 +0000 (+0000) Subject: Changed the name from the "Free Software Development HOWTO" to the X-Git-Url: https://projects.mako.cc/source/fspm_howto/commitdiff_plain/206b026f6074cb7e9315a6324e025fb29fadfa74?ds=inline;hp=bf69393068734710ae2f9e683ef890ef6786c27a Changed the name from the "Free Software Development HOWTO" to the Author: mako Date: 2001/05/05 16:01:45 Changed the name from the "Free Software Development HOWTO" to the much more specific "Free Software Project Management HOWTO." I like it better and some of the early readers agree that this is an intelligent change. --- diff --git a/FreeSoftwareProjectManagementHOWTO.sgml b/FreeSoftwareProjectManagementHOWTO.sgml index 6d4bd70..c9be43b 100644 --- a/FreeSoftwareProjectManagementHOWTO.sgml +++ b/FreeSoftwareProjectManagementHOWTO.sgml @@ -5,7 +5,7 @@ - Free Software Development HOWTO + Free Software Project Management HOWTO Benjamin @@ -49,10 +49,10 @@ This HOWTO is designed for people with experience in programming and some skills in managing a software project but who are new to the world of free software. This document is meant to act as a - guide to the non-technical aspects of free software development - and was written to be a crash course in the people skills that - aren't taught to commercial coders but that can make or break a - free software project. + guide to the non-technical aspects of free software project + management and was written to be a crash course in the people + skills that aren't taught to commercial coders but that can make + or break a free software project. @@ -216,32 +216,32 @@ - HTML. + HTML. - HTML (single page). + HTML (single page). - plain text. + plain text. - Compressed postscript. + Compressed postscript. - Compressed SGML source. + Compressed SGML source. @@ -365,11 +365,12 @@ fswd!starting - With very little argument, the beginning is the most difficult part - of successful free software development. Laying a firm foundation - will determine whether your project flourishes or withers away and - dies. It is also the subject that is of most immediate interest to - anyone reading this document as a tutorial. + With very little argument, the beginning is the most difficult + period in a project's life to do successful free software project + managment. Laying a firm foundation will determine whether your + project flourishes or withers away and dies. It is also the subject + that is of most immediate interest to anyone reading this document + as a tutorial. @@ -584,7 +585,7 @@ For many developers this may be the single most difficult aspect - of free software development but it is an essential one. It is + of free software project managment but it is an essential one. It is easy to become fired up by an idea and be caught up in the momentum and excitement of a new project. It is often extremely difficult to do but, it is important that any free software @@ -680,9 +681,9 @@ brings up the question of Open Source Software and the debate over the terms Open Source Software and Free Software. However, because I've written the - Free Software Development HOWTO and not the Open Source - Development HOWTO, my own allegiances in this argument are in the - open. + Free Software Project Management HOWTO and not the Open Source + Software Project Management HOWTO, my own allegiances in this + argument are in the open. @@ -1908,7 +1909,7 @@ pages for more information and options. - Other Development issues + Other Project Management issues There are more issues surrounding interaction with developers in a free software project that I can not touch on in great detail in a @@ -2067,7 +2068,7 @@ pages for more information and options. to try and be as responsive as possible. A solid knowledge of the situation recounted above is any free software developer's best tool for shifting his development or leadership style to fit the unique - process of free software development. This chapters will try and + process of free software project management. This chapters will try and introduce some of the more difficult or important points in any projects interactions with users and give some hints on how to tackle these.