Data: backfill SoC (System-on-Chip) values
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- javascript
- Domain
- data
Research direction
Start by reviewing the sourcing policy and the existing soc data, then compare the Axis datasheets and Thingino/OpenIPC device lists mentioned in the issue. First resolve how community-sourced values should be labeled separately from official sources; #284 is also relevant. Done means a sourcing approach is agreed before bulk additions, with values individually supported and no SoC inferred across a product series.
Written by the indexing model from the issue text.
Description
Sub-issue of #22 — the SoC data (the original Thingino ask).
socis 46 / 11,421 populated (was 0/2230) — still effectively empty. The 46 are the reliably-sourceable ones: Axis datasheet-stated (Axis publishes its ARTPEC SoC — a goldmine) plus a few budget/Wyze models via Thingino.- Needs values like
Ingenic T31,HiSilicon Hi3516,Ambarella S3Lto enable Thingino/OpenIPC compatibility matching.
⚠️ Sourcing caveat (still the blocker): SoC is rarely in official datasheets — it's mostly community-sourced (Thingino/OpenIPC wikis, teardowns). Hikvision/Dahua SoCs are teardown-only (no public statement) → effectively a dead end for the bulk. This needs a labeled community-sourced treatment, separate from the repo's official-sources gate. Scope that sourcing decision before any bulk add.
Practical path: harvest Axis (datasheet-stated) and the Thingino/OpenIPC device lists (budget brands) under a soc_source: community style label; do not sibling-infer a SoC across a series. See also #284.
Status: ❌ open.
- Dominant language
- JavaScript
- Stars
- 267
- Forks
- 21
- Avg merge
- 4h 18m
- Merged PRs (30d)
- 14
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing 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.
More from ch-bas/cctv-camera-database
-
Config works: revodata-i706-p-hsPossibly taken @ch-bas claimed this 2 days ago. Openconfig-report via-web
Difficulty 1/5 Under an hour Newbie friendliness 25/100
ch-bas/cctv-camera-database#405 · 1 assignee ·
Maintainers usually reply within 1 day
-
help wanted
Difficulty 4/5 3-5 days Newbie friendliness 52/100
ch-bas/cctv-camera-database#399 ·
Maintainers usually reply within 1 day
-
help wanted question
Difficulty 2/5 1-3 hours Newbie friendliness 48/100
ch-bas/cctv-camera-database#378 · 4 comments ·
Maintainers usually reply within 1 day
-
help wanted question
Difficulty 2/5 1-3 hours Newbie friendliness 57/100
ch-bas/cctv-camera-database#377 · 2 comments ·
Maintainers usually reply within 1 day
-
good first issue help wanted
Difficulty 5/5 Over a week Newbie friendliness 25/100
ch-bas/cctv-camera-database#348 ·
Maintainers usually reply within 1 day
All issues in ch-bas/cctv-camera-database
Similar issues
-
needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
melodic-software/claude-code-plugins#9619 ·
Maintainers usually reply within 1 day
-
bug Frontend P2-medium UI UX
Difficulty 1/5 Under an hour Newbie friendliness 76/100
Deepak3699/Ai_Mentor#427 ·
Maintainers usually reply within 1 day
-
area: core
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
venn: a name that starts with set-, union-, text- or style- followed by a letter is a parse errorOpen
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
obsidianmd/pele#65 ·
Maintainers usually reply within 3 days
-
needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
11ty/buildawesome#4407 · 1 reaction ·
Maintainers usually reply within 1 day