Clean up data directory
Nobody has claimed this yet.
- Dominant language
- Module Management System
- Stars
- 3
- Forks
- 72
- Avg merge
- 11h 8m
- Merged PRs (30d)
- 36
Description
The data directory is a mess, likely because numerous directories that should really be subdirectories of other directories are just sitting there. Its confusing to read and navigate through. A bunch of this seems to be directories that really should all reside in an AtB or Stratcon directory. Here are some of the offenders:
- mapgen - is this AtB?
- mapsetup - is this AtB?
- forcegenerator - is this AtB?
- scenariomodifiers - is this AtB?
- scenariotemplates - is this AtB?
- stratconbiomeddefinitions, stratconcontractdefinitions, stratconfacilities - this should have been in a stratcon directory from the beginning.
- terrainconditionodds - no idea what this is but it shouldn't live at the top level even if its the only thing in its class.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by mapping the top-level data directories named in the issue, especially mapgen, mapsetup, forcegenerator, scenariomodifiers, scenariotemplates, and the stratcon definitions. Determine which belong under AtB or Stratcon and where terrainconditionodds fits; done means the directory structure is organized without leaving the listed categories ambiguously placed.
Written by the indexing model from the issue text.
Assessment
- Domain
- tooling
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100