shift-org / shift-org/shift-docs
legacy detail cleanup
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 30
- Forks
- 25
- Avg merge
- 9m
- Merged PRs (30d)
- 1
Description
- Do we need PHP files anymore?
- docker-compose.yml can go.
- TODO can probably go.
- archive Docs for old setup?
- any legacy directories like
/legacywe can remove? - remove
./shiftscript?
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
Inventory the PHP files, docker-compose.yml, TODO, old setup Docs, /legacy directories, and ./shift script named in the issue. First determine which items are still used and whether the old setup should be archived; done requires an agreed list of safe removals or archival, but the issue does not define that list.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker-compose, php
- Domain
- documentation, tooling
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100