Skip to content

Commit 6594263

Browse files
ParacciParacci
committed
feat: initial LDR standard v0.1.0
0 parents  commit 6594263

32 files changed

Lines changed: 7293 additions & 0 deletions

‎.github/ISSUE_TEMPLATE/brand_registration.md‎

Lines changed: 41 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,41 @@
1+
---
2+
name: Brand Registration Request
3+
about: Register your brand logo with the LDR network
4+
title: '[BRAND] '
5+
labels: brand-registration
6+
assignees: ''
7+
---
8+
9+
## Brand Information
10+
11+
**Brand name:**
12+
**Website:**
13+
**Country of registration:**
14+
15+
## Logo Details
16+
17+
**Logo file:** <!-- Attach your logo file -->
18+
**Logo format:** [ ] SVG [ ] PNG [ ] Both
19+
20+
## Integration Plan
21+
22+
**Target platforms:**
23+
24+
- [ ] iOS app (app scheme: `______://`)
25+
- [ ] Android app (app scheme: `______://`)
26+
- [ ] Web only
27+
28+
**Primary web URL:**
29+
**Fallback URL:**
30+
31+
## Verification
32+
33+
- [ ] I confirm I am an authorized representative of this brand
34+
- [ ] I have attached official trademark registration documentation
35+
- [ ] I agree to the LDR Open Standard terms
36+
37+
## Routing Rules (Optional)
38+
<!-- Describe any context-based routing rules you want -->
39+
<!-- Example: Morning hours → breakfast menu, Evening → dinner menu -->
40+
41+
## Additional Notes

‎.github/ISSUE_TEMPLATE/bug_report.md‎

Lines changed: 34 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,34 @@
1+
---
2+
name: Bug Report
3+
about: Something is broken
4+
title: '[BUG] '
5+
labels: bug
6+
assignees: ''
7+
---
8+
9+
## What happened?
10+
<!-- Clear description of the bug -->
11+
12+
## What did you expect?
13+
<!-- What should have happened -->
14+
15+
## Steps to reproduce
16+
17+
```text
18+
1.
19+
2.
20+
3.
21+
```
22+
23+
## Environment
24+
25+
- OS:
26+
- Platform: [ ] iOS [ ] Android [ ] Web
27+
- LDR version:
28+
- Browser (if web):
29+
30+
## Logs / Screenshots
31+
<!-- Paste any relevant output -->
32+
33+
## Additional context
34+
<!-- Anything else that might help -->

‎.github/ISSUE_TEMPLATE/feature_request.md‎

Lines changed: 27 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,27 @@
1+
---
2+
name: Feature Request
3+
about: Suggest a new feature or improvement
4+
title: '[FEAT] '
5+
labels: enhancement
6+
assignees: ''
7+
---
8+
9+
## What problem does this solve?
10+
<!-- Why is this needed? -->
11+
12+
## Proposed solution
13+
<!-- How should it work? -->
14+
15+
## Affected component
16+
17+
- [ ] Visual recognition engine
18+
- [ ] Registry
19+
- [ ] Rule engine
20+
- [ ] SDK
21+
- [ ] Documentation
22+
- [ ] Other
23+
24+
## Alternatives considered
25+
<!-- What else did you think about? -->
26+
27+
## Additional context

‎.github/ISSUE_TEMPLATE/rfc.md‎

Lines changed: 45 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,45 @@
1+
---
2+
name: Standard Change (RFC)
3+
about: Propose a change to STANDARD.md
4+
title: '[RFC] '
5+
labels: rfc, standard
6+
assignees: ''
7+
---
8+
9+
## RFC Title
10+
<!-- Short descriptive title -->
11+
12+
## Summary
13+
<!-- One paragraph: what are you proposing? -->
14+
15+
## Motivation
16+
<!-- Why is this change needed? What problem does it solve? -->
17+
18+
## Technical Detail
19+
<!-- How exactly would it work? Include JSON/code examples if relevant -->
20+
21+
```json
22+
{
23+
"example": "here"
24+
}
25+
```
26+
27+
## Backward Compatibility
28+
<!-- Does this break existing implementations? -->
29+
30+
- [ ] Fully backward compatible
31+
- [ ] Requires migration (describe below)
32+
- [ ] Breaking change (justify below)
33+
34+
## Alternatives Considered
35+
<!-- What other approaches did you think about? -->
36+
37+
## Open Questions
38+
<!-- What is still undecided? -->
39+
40+
## Implementation Checklist
41+
42+
- [ ] STANDARD.md updated
43+
- [ ] Reference implementation updated
44+
- [ ] Tests written
45+
- [ ] Documentation updated

‎.github/ISSUE_TEMPLATE/use_case.md‎

Lines changed: 31 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,31 @@
1+
---
2+
name: New Use Case
3+
about: Propose a new sector scenario for USE_CASES.md
4+
title: '[USECASE] '
5+
labels: use-case
6+
assignees: ''
7+
---
8+
9+
## Sector
10+
<!-- Which industry / sector? -->
11+
12+
## Scenario name
13+
<!-- Short descriptive name -->
14+
15+
## How it works
16+
17+
```text
18+
Logo scanned
19+
→ Condition 1: Result 1
20+
→ Condition 2: Result 2
21+
→ Default: Default result
22+
```
23+
24+
## Why is this valuable?
25+
<!-- Who benefits and how? -->
26+
27+
## Security considerations
28+
<!-- Any special security requirements for this scenario? -->
29+
30+
## Real-world examples
31+
<!-- Any existing implementations or similar systems? -->

‎.github/PULL_REQUEST_TEMPLATE/pull_request_template.md‎

Lines changed: 42 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,42 @@
1+
## What does this PR do?
2+
<!-- Clear summary of the change -->
3+
4+
## Type of change
5+
6+
- [ ] Bug fix
7+
- [ ] New feature
8+
- [ ] Documentation
9+
- [ ] Standard change (RFC)
10+
- [ ] Security fix
11+
- [ ] Use case addition
12+
- [ ] Refactor
13+
14+
## Related issue
15+
16+
Closes #
17+
18+
## How was this tested?
19+
<!-- Describe testing done -->
20+
21+
## Checklist
22+
23+
- [ ] I have read `CONTRIBUTING.md`
24+
- [ ] My changes follow the project's code standards
25+
- [ ] I have added/updated tests where needed
26+
- [ ] I have updated documentation where needed
27+
- [ ] This change does not collect or transmit user data
28+
- [ ] Security implications have been considered
29+
30+
## For Standard Changes
31+
32+
- [ ] Backward compatible
33+
- [ ] RFC issue was discussed first
34+
- [ ] `STANDARD.md` version number updated
35+
36+
## For Security-Related Changes
37+
38+
- [ ] Reviewed by at least two maintainers required
39+
- [ ] `SECURITY.md` updated if needed
40+
41+
## Screenshots / Examples
42+
<!-- If relevant, add before/after examples -->

‎.github/labels.yml‎

Lines changed: 95 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,95 @@
1+
# LDR GitHub Labels
2+
# Apply with: gh label create or a labels sync tool
3+
4+
labels:
5+
# Type
6+
- name: bug
7+
color: "d73a4a"
8+
description: Something is broken
9+
10+
- name: enhancement
11+
color: "a2eeef"
12+
description: New feature or improvement
13+
14+
- name: documentation
15+
color: "0075ca"
16+
description: Documentation changes
17+
18+
- name: security
19+
color: "e4e669"
20+
description: Security related
21+
22+
- name: rfc
23+
color: "7057ff"
24+
description: Standard change proposal
25+
26+
- name: use-case
27+
color: "008672"
28+
description: New sector scenario
29+
30+
- name: brand-registration
31+
color: "e99695"
32+
description: Brand logo registration request
33+
34+
# Status
35+
- name: good first issue
36+
color: "7057ff"
37+
description: Good for newcomers
38+
39+
- name: help wanted
40+
color: "008672"
41+
description: Extra attention needed
42+
43+
- name: in progress
44+
color: "fbca04"
45+
description: Actively being worked on
46+
47+
- name: stale
48+
color: "cfd3d7"
49+
description: Inactive for 60+ days
50+
51+
- name: pinned
52+
color: "0052cc"
53+
description: Keep open indefinitely
54+
55+
- name: wont-fix
56+
color: "ffffff"
57+
description: Will not be addressed
58+
59+
# Component
60+
- name: core/recognition
61+
color: "bfd4f2"
62+
description: Visual recognition engine
63+
64+
- name: core/registry
65+
color: "bfd4f2"
66+
description: Registry system
67+
68+
- name: core/rules
69+
color: "bfd4f2"
70+
description: Rule engine
71+
72+
- name: sdk/ios
73+
color: "d4c5f9"
74+
description: iOS SDK
75+
76+
- name: sdk/android
77+
color: "d4c5f9"
78+
description: Android SDK
79+
80+
- name: sdk/web
81+
color: "d4c5f9"
82+
description: Web SDK
83+
84+
# Priority
85+
- name: priority/critical
86+
color: "b60205"
87+
description: Must fix immediately
88+
89+
- name: priority/high
90+
color: "e4e669"
91+
description: Important
92+
93+
- name: priority/low
94+
color: "cfd3d7"
95+
description: Nice to have

0 commit comments

Comments
 (0)