LivelyKernel / LivelyKernel/lively4-core
should we allow nested repositories under https://lively-kernel.org/lively4/
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 89
- Forks
- 25
- PR merge metrics
- No merged PRs in 30d
Description
we have a flat list of repositories... hosted under https://lively-kernel.org/lively4/
content, experimental, user repositories... everything.
Should we allow or force a two level scheme (such as in linux or the home directory in unix?)
That would allow us to group them better.... and delete them if not longer needed.
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 reviewing the current flat repository layout at https://lively-kernel.org/lively4/ and the issue's proposed two-level scheme. Determine whether nested repositories should be allowed or required, and define how grouping and deletion of obsolete repositories would work; done means a documented decision and agreed structure.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100