# Verso project's schedule (DRAFT)

This plan is based on modifying Gitorious for the project's purposes.

This information will eventually be hold in Trac (or similar) system.

When this doc uses word "implement" the iteration it refers to begins
with word "plan".

## Iteration 1, 1.3.2010 - 12.3.2010

## Note here: Since getting betatesters early is a priority: this
#  iteration can be split to contain the public test blocking tasks
#  in the first week.

Critical application logic: Project creation, detail modifying.

  [1.4] When a project is created the software will generate a home page
        for it. (+++)
    - Ready.
  [2.3] WWW-interface: The project home page has links to repository files
        and commits. (+++)
    - Ready.
  [   ] Limiting the number of repositories in project to one, which will
        be automatically generated.
    - TODO: 'default repository' must be generated automatically.
  [1.3] A user can add and modify a licence of a project. (+++)
  [2.1] A user can create projects. (+++)
    - Ready.
  [1.1] The WWW-interface is in English. (+++)
    - Ready.
  [1.2] The software supports distributed source code management. (+++)
    - Ready.
  [5.1] Project metafiles are located in the repository. (++)
    - TODO: implement own hook that is triggered when pushing
    - TODO: implement YAML reader that reads file from repo
    - TODO: implement a way to get YAML file from a bare repository
    - TODO: implement WWW interface's forms to save YAML files and
            a way to push them to repo

## Iteration 2, 15.3.2010 - 26.3.2010

Aiding systems for updating the repository.

  [   ] A user can update repository contents via uploading a ZIP file
    - TODO: Interface and application logic must be implemented
  [   ] A user can point a repository to be updated from a ZIP URL
        automatically (say, once a day) (++?)
    - TODO: implement inteface and application logic
    - TODO: implement a updating daemon, similar to existing
            Gitorious daemons.
  [   ] A user can point a repository to be updated constantly from
        SVN URL. (++?)
    - TODO: implement interface and application logic
    - TODO: implement a updating daemon, similar to existing
            Gitorious daemons.

## Iteration 3, 29.3.2010 - 9.4.2010

Rights management: Restricting access

  [2.2] A user can set a project as private or public or grant access to the
        project for another user or group. (+++)
    - TODO: Modify Gitorious project access management to support different
            states (public/require group/user only)
        - The group requiring will be first implemented as a dummy and
          space for connecting to LDAP etc. will be added.

## Iteration 4, 12.4.2010 - 23.4.2010

Adding tools to WWW interface. Last iteration of implementing.

  [2.4] A user can add and update repository files. (++)
  [2.5] A user can editi text based files. (++)

## Iteration 5, 26.4.2010 - 7.5.2010 (only 8 days)

No implementation of new features, only documenting and project management.

## Iteration 6, 10.5.2010 - 21.5.2010 (only 9 days)

No planned activities. Though, there'll surely be some.

## Backlog
  [1.5] The software has automated testing tools integrated. (+)
  [2.6] The website offers project management tools. (+)
  [2.7] A user can comment source code. (saved to repo) (+)
  [2.8] A privileged user can give a sertification for source code. (+)
  [2.9] Promoting of existing projects on the front page. (+)
  [4.1] A user can add files to database via email. (+)
  [   ] i18n/Internationalization (Finnish) (+)