Banjo is an open source project powered by Assembla

Assembla offers free public and private SVN/Git repositories and project hosting with bug/issue tracking and collaboration tools.

Arrow_left   Arrow_right
 
  #3

Make the installation process easier

    • Created on: Fri, 13 Mar 2009 (almost 3 years ago)
    • Reported by: Richard Esplin
    • Assigned to: -
    • Milestone: -
    • Status: New
    • Priority: Normal (3)
    • Component: -
    Here are my suggestions for making Banjo more maintainable and more accessible to future users:
    • There should be a bias towards using released versions of projects. This makes it easier to install a version that works, and it makes it easier to monitor the libraries for security updates.
    • If a dependency project doesn't have an active community, Banjo should consider folding that code into the Banjo core.
    • Even if a dependency project does have an active community, if it isn't likely to get distributed by an OS package manager, Banjo should consider including the project with the banjo source in a libs subdirectory.
    • The maintainers should consider putting all the various Banjo and Satchmo libraries into a single package. In addition to making this easier to find and install, it also makes it easier to maintain. Currently they are scattered across various source repositories, issue trackers, and project home pages. This fragments an already small community.
    • The necessary Satchmo libraries should be factored out of Satchmo and put into the shared libraries package as soon as possible—it will only get harder with time. Banjo shouldn't require the installation of a full blown shopping cart, and the Satchmo users will benefit from the larger community using their libraries. Satchmo and Banjo can then select which version of the libraries to depend on for each release, which will simplify both projects.
    • Though the multi–site capabilities are excellent, I think the defaults can be improved so that it doesn't get in the way of a simple single–site deployment. It doesn't currently prevent single site deployment, but it makes it harder than it needs to be.
  • Followers
     
    Ico-users Richard Esplin 
     
    Attachments
    No attachments
    Associations
     
    No associations
    Activity
     
    User picture

          on Mar 13, 2009 @ 04:49PM UTC * By Richard Esplin

    Description changed from Include some stable librari... to Here are my suggestions for...
    Time Expenditure
    Loading