Move console scripts from osi to karl

[Chris Rossi]

Most, if not all, console scripts currently in osi.scripts can probably be moved to karl.

[Chris Rossi (chris-archimedeanco)]

This is part of a series of tickets that will involve looking at various "customizations" that have been performed in the osi package for Karl3. Many of these are things that are probably more generally useful than just for osi and the hope is that many of these things can be moved into the karl or karl.content packages as appropriate. The idea here is to pare down to a bare minimum the amount of code that actually lives in the osi package so we can have a better idea of what customizations will be necessary for accomodating other pilots.

For each of these items there will be a judgment call in terms of assigning to one of these categories:

o It is truly a customization and should only ever live in the osi package.

o It is generally useful, should be part of core Karl and can be moved to either karl or karl.content.

o It is generally useful but has some small osi tweak and so should be refactored such that the really useful bits live in karl and osi has only a small tweak, either through configuration or subclassing or some other means.

The hope is most of these will be in the second category.

[Chris Rossi (chris-archimedeanco)]

Hi Shane, do you want to take this one? It's not super important to me whether the entry points continue to live in osi or if they also move to Karl. Use your judgment on that one.

[Chris Rossi (chris-archimedeanco)]

Another week, another milestone.

[Shane Hathaway (shane-hathawaymix)]

I moved as many as I could without any redesign work. Scripts left over:

- The scripts involved in the Karl 2 -> Karl 3 migration, since OSI is the only org that ever had Karl 2 (as far as I know). These include aclimport, bulkgenerator, bulkloader, fix_userids, importer, local_roles_report, and scrub_content. Perhaps we should just delete these now that the Karl 2 migration is over.

- evolve and startover, which are generic ideas but they refer to OSI-specific code. Making them generic would require some redesign. They are small and not used often, so I think it's better to leave them alone for now.

[Chris Rossi (chris-archimedeanco)]

On Tue, Jun 30, 2009 at 1:37 AM, Shane Hathaway <email address hidden>wrote:

> I moved as many as I could without any redesign work. Scripts left over:
>
> - The scripts involved in the Karl 2 -> Karl 3 migration, since OSI is
> the only org that ever had Karl 2 (as far as I know). These include
> aclimport, bulkgenerator, bulkloader, fix_userids, importer,
> local_roles_report, and scrub_content. Perhaps we should just delete
> these now that the Karl 2 migration is over.
>

Actually, Six Feet Up will be migrating Oxfam and Eurasia from Karl2 to
Karl3 in July, using this code.

>
> - evolve and startover, which are generic ideas but they refer to OSI-
> specific code. Making them generic would require some redesign. They are
> small and not used often, so I think it's better to leave them alone for
> now.
>
>
Right. We'll need to duplicate these for other pilots with pilot specific
code.

Thanks,
Chris

[Shane Hathaway (shane-hathawaymix)]

After discussion, we decided scripts that require a config file belong in the osi package after all. So we moved the body of the larger scripts to the karl package and added tests.