Index: openacs-4/packages/download/www/doc/requirements.adp =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/download/www/doc/requirements.adp,v diff -u -r1.2 -r1.3 --- openacs-4/packages/download/www/doc/requirements.adp 26 Aug 2015 18:03:35 -0000 1.2 +++ openacs-4/packages/download/www/doc/requirements.adp 12 Sep 2016 06:04:41 -0000 1.3 @@ -7,14 +7,14 @@ by Joseph Bank based largely on the ACS Repository requirements written by Todd Nightingale -This is a DRAFT +This is a DRAFT

I. Introduction

OpenACS 4.x has a file storage module, so an obvious question -is: "Why do we need a seperate download module?" The download -module is targeted at a different usage pattern and interface. The -intent of the download module is to provide an online repository -for the public (or pseudo-public) distribution of infrequently -modified files. The ACS 3.4 download module, used at +is: "Why do we need a seperate download module?" The +download module is targeted at a different usage pattern and +interface. The intent of the download module is to provide an +online repository for the public (or pseudo-public) distribution of +infrequently modified files. The ACS 3.4 download module, used at http://www.arsdigita.com/download for distribution of software provided by ArsDigita, and the acs-repository, used at http://www.arsdigita.com/acs-repository for distribution of ACS @@ -47,7 +47,7 @@

  • User (downloading and contributing)
  • Administrator
  • -Joe Contributer (currently working for Joe.com +Joe Contributer (currently working for Joe.com ) writes a piece of software used to do knowledge management (KM) for the ACS. He packages his code using the APM @@ -58,22 +58,22 @@ description data are all uploaded (extracted from the .info file).

    Jane Admin who installed and configured the download package chose to not allow users to download versions pending approval. -That forces her to download Joe's package from the admin pages and -install it. She notices that it isn't malicious in any way and -doesn't harm her OpenACS installation so she approves it to go live -on her package repository. Joe is informed via email that his -package was approved (because Jane set this configuration +That forces her to download Joe's package from the admin pages +and install it. She notices that it isn't malicious in any way +and doesn't harm her OpenACS installation so she approves it to +go live on her package repository. Joe is informed via email that +his package was approved (because Jane set this configuration parameter).

    Don Downloader is scanning through the most recently uploaded -APMs on a package repository and finds Joe's KM package. He notices -that many other users have downloaded the package and have made -comments praising the package as well as Joe.com. Since Ben -is a follower by heart, he decides to download the package as well -and install it on his system. (Ben's crafty friend Alyssa later -informs Ben that he could have just had the APM install directly -from the repository url).

    -

    Benny Beancounter loves to learn about who's downloading files -from his site and what reasons they give for downloads. On a +APMs on a package repository and finds Joe's KM package. He +notices that many other users have downloaded the package and have +made comments praising the package as well as Joe.com. +Since Ben is a follower by heart, he decides to download the +package as well and install it on his system. (Ben's crafty +friend Alyssa later informs Ben that he could have just had the APM +install directly from the repository url).

    +

    Benny Beancounter loves to learn about who's downloading +files from his site and what reasons they give for downloads. On a frequent basis, Benny visits the download packages admin pages and views a report of how many downloads occured for each file. He then drills down on a particular file and views a list of the users who @@ -175,9 +175,9 @@

    A logged in user must be able to comment on vendors, packages, and versions.

    -

    VI.C Requirements: Administrator's Interface

    +

    VI.C Requirements: Administrator's Interface

    -The requirement of the administrator's interface is to enable +The requirement of the administrator's interface is to enable administrators to approve or reject package versions as they are uploaded by users. Naturally any site administrator would have rights on all the packages in the repository 200.0 Approval @@ -212,5 +212,5 @@
    -Last modified: $Id: requirements.html,v 1.3 2002/09/13 16:46:34 +Last modified: $‌Id: requirements.html,v 1.3 2002/09/13 16:46:34 jeffd Exp $