Project tree organization
Open
Nobody has claimed this yet.
whateverable
- Dominant language
- Raku
- Stars
- 19
- Forks
- 16
- PR merge metrics
- No merged PRs in 30d
Description
My thoughts:
- maintenance directory should be removed. There's only one file there (long-term-storage.p6), and its contents should be moved to the Sakefile.
- All
.pm6files should go tolib/directory that we should create. - build.p6 is unfortunately a very fat script, but I think its contents should be in the Sakefile too.
- Quite possibly we want to have a
bin/directory that will have all.p6files there.
The reason this was not done earlier is because there was no need. Initially there were just three or four files, so all this didn't really matter.
Thoughts?
Contributor guide
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 reviewing maintenance/long-term-storage.p6, build.p6, and the Sakefile, then inventory the repository's .pm6 and .p6 files. The proposed organization uses lib/ for .pm6 files, bin/ for other .p6 files, and moves maintenance and build logic into the Sakefile; done means the old locations are removed and the project still builds.
Written by the indexing model from the issue text.
Assessment
- Domain
- build-system, tooling
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100