GenericSetup export of KARL2 sample data checked in
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
KARL3 |
Fix Released
|
Medium
|
claytron |
Bug Description
For export import, we need an example of KARL2 export data. This data should not contain any actual OSI or other customer content. We do, though, need the data available in the KARL3 source tree, so we can run it, run tests, etc.
For this task:
1) Get a KARL2 buildout running.
2) Get some users and communities entered. (Later we can get more data, like offices and tags.)
3) Create a GenericSetup export tree.
4) tgz the tree into a tarball, hopefully not too big.
5) Check the tgz into the area in KARL3 where you plan to work.
6) Mark this ticket as "Fix Committed" when checked in.
Where to Work
===============
The source tree in karl3 has some namespaces in the src:
src/karl - the "core"
src/karl.content - the various tools that can be added to a community (blog, wiki, etc.)
src/osi - the parts that are specific to each customer
We currently have the bulkloader in src/osi/osi/scripts along with some sample data. Thus, src/osi/osi seems like a natural place. As far as I care, src/osi/
For any questions, feel free to reply to the email for this bug report.
Changed in karl3: | |
assignee: | nobody → clayton-sixfeetup |
importance: | Undecided → Medium |
milestone: | none → m7 |
Changed in karl3: | |
status: | New → In Progress |
Changed in karl3: | |
status: | Fix Committed → Fix Released |
Triage to M8.