## Action
= Action Open Source =

## The persons assigned to the action
 Assigned:: KFC
 Prev assigned::
 Tasks adressed:: None
 Time estimated:: not done
 Time used:: not known
 Priority:: ?
 Status:: In Progress
 Iteration:: 06,07,08
 Notes:: Complete the opensourcing of the DOMS projekt.


## Detailed description of wanted output from the work to be carried out.
## E.g. Implement a utility class for writing data to a disk. The data must be base64 encoded before being written.

This action was introduced in [[Iteration6]] and then postponed, so it is also part of [[Iteration7]],[[Iteration8]],[[Iteration9]] and [[Iteration10]].

 * Create a GForge project
   * This involves creating the project, asking Tom to accept it, and setting up the parts of GForge we wish to use
 * (1mh for one who has done it before) Create a new wiki
   * This involves asking Tom to make the wiki, and editing the wikiconfig.py to suit our needs
 * (1md (uncertain estimate)) Add licenses to third-party libraries that do not yet have them.
 * (1mh) Check that every source file has the LGPL header, and add it if it isn't there.
 * (1md) Move SVN contents
   * First, identify items which can '''not''' be moved, i.e. internal data. Pay particular attention to {{{test/data/legacy}}}. Internal data is defined as datafiles only, for example image files and text files from out internal collections.
   * Second, replace these with alternative constructed test data.
   * Third, check the project in to GForge SVN.
 * (at least 1md) Move wiki pages to the new wiki
   * Start by locking the wiki in wikiconfig.py
   * Find wiki pages without internal data
     * Put #acl-statement in these pages to unlock them. At least front page and WBS. The #acl statement should look like
     {{{
#acl all:read
     }}}
     * Pages with internal data should also be marked with a #acl-statement. The statement should look like
     {{{
#acl DOMSDevelopersGroup:read,write,delete,revert,admin All:
     }}}
  * Move all pages in a bundle to new wiki.

## Targeted WBS Tasks and Assigned Developers can be found on the iteration page for this action.