devel-ideal-proj.rst
changeset 1063 fdc5ed189bd3
parent 1048 409aab81f818
parent 1061 4c3c9b4f8d73
child 1064 3199465de3c3
child 1065 40c825357158
equal deleted inserted replaced
1048:409aab81f818 1063:fdc5ed189bd3
     1 -*- mode: outline; coding: utf-8; -*-
       
     2 
       
     3 * Ideal software development model.
       
     4 
       
     5 This file mainly discuss about open source software project.
       
     6 
       
     7 * Open source.
       
     8 
       
     9 Open source software project have freedom how develop project and which
       
    10 development toolchains use.
       
    11 
       
    12 * Close source.
       
    13 
       
    14 Close source projects have proprietary nature because of:
       
    15 
       
    16  * interest to make money (another parties can not easily reproduce project or
       
    17    steal realisation ideas/code, allowing another party get same product and get
       
    18    company money)
       
    19  * low code quality (to stop stain company good name or to stop malicious
       
    20    attacks based on code analysis)
       
    21  * security consideration (to hide protocols and data format to make harder
       
    22    malicious attack)
       
    23  * business model (closed data formats allow vendor lock)
       
    24 
       
    25 Disadvantage of closed source project (in many case):
       
    26 
       
    27  * you can not directly contact with developers (only through support)
       
    28  * low support quality
       
    29  * paid support (and you have no enough money)
       
    30  * can not access to product bug tracing system (you only can submit bug via
       
    31    crash report application or technical support, publicly appear internal bug
       
    32    tracing can damage product reputation
       
    33 
       
    34 * Component of software project.
       
    35 
       
    36  * Src (sources).
       
    37  * Doc (documentation).
       
    38  * VCS (version control system).
       
    39  * BTS (bug tracking).
       
    40  * News (project news/history/changelog).
       
    41 
       
    42 * Docs.
       
    43 
       
    44 TODO
       
    45 
       
    46 * Project home page.
       
    47 
       
    48 Project home page must provide:
       
    49 
       
    50  * project name
       
    51  * short info about project goal
       
    52  * project license
       
    53  * current project status
       
    54  * links to binary release
       
    55  * links to source release, how to get latest source from VCS
       
    56  * links to online/printed docs
       
    57  * how report bug (BUGS)
       
    58  * where send patch
       
    59  * contact info
       
    60 
       
    61 Additionally:
       
    62 
       
    63  * help welcome, requirement to join to project
       
    64  * mail/news list for users/developers, how to subscribe/unsubscribe, where
       
    65    find archive, how search for keyword in archive
       
    66  * project history (NEWS, ChangeLog)
       
    67  * project policy (HACKING)
       
    68  * how build project (README, INSTALL)
       
    69  * list of contributor with contact info (MAINTAINERS, AUTHORS)
       
    70  * who use project
       
    71 
       
    72 * VCS.
       
    73 
       
    74 TAGS: VCS, version control system, SCM, source code management, DVCS,
       
    75       distributed version control system.
       
    76 
       
    77  * CVS
       
    78  * SVN
       
    79  * Mercurial (hg)
       
    80  * git
       
    81  * bazaar
       
    82