Changes between Initial Version and Version 10 of Ticket #280


Ignore:
Timestamp:
01/29/11 00:06:02 (8 years ago)
Author:
barra_parpg
Comment:

Reworded as user story

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #280

    • Property Status changed from new to reopened
    • Property Type changed from enhancement to user story
    • Property Component changed from scripts to misc
    • Property Summary changed from Reorganize Directory Hierarchy to Reorganize directory hierarchy
    • Property Milestone changed from Techdemo 2 to Product backlog
    • Property Blocking changed from to 275
  • Ticket #280 – Description

    initial v10  
    1 == Enhancement Description == 
    2 * rename scripts to core 
    3 * move game/packaging to root of trunk and rename to build 
    4  
    5 == Rationale == 
    6 A reorganized directory hierarchy would facilitate in easing the creation of a build system PARPG, which may increase the chances of PARPG becoming a binary package in the package managers of Linux Distributions. Also, having a directory structure that mimics other projects might reduce the barrier to entry for new contributors because it would feel "less alien" to them. 
    7  
    8 == Pros and Cons == 
    9 Pros: 
    10 * arguably neater structure 
    11 * reduces the size of installs 
    12 * the aesthetics of imports improve IMHO. 
    13  
    14 Cons: 
    15 * may break relative imports of some modules, though obviously the implementation of this enhancement should account for that 
    16 * seasoned developers would have to get used to the new structure 
     1As a developer, I want to have a logical directory structure so that I don't waste time looking for files, and deciding where to put new files.