packagecontrol / packagecontrol/thecrawl
Align repo, crawlers, and schemas for packages and libraries
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 19
- Forks
- 7
- Avg merge
- 4h 53m
- Merged PRs (30d)
- 14
Description
I don't know enough details to fully describe the discussion. The meat of it though, as I understand it right now, is ...
- packages are still on the v3 schema because the old website doesn't know any better (and cannot be updated)
- libraries are however already on v4.
- thecrawl crawls packages, https://github.com/packagecontrol/channel crawls libraries (?)
- there is crawler-like tech in the PC client package to resolve package
Perhaps more. But there is some consolidation that can happen here, especially once the old site is no 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 reading the issue alongside thecrawl, packagecontrol/channel, the old website, and the crawler-like code in the PC client package. Map where package and library schemas are defined and consumed, then document the consolidation boundary and confirm that both crawling paths and schema versions remain compatible.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend, data
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100