Add upstream Notesium remote and document fork relationship #36

New Issue

libretech · 2026-03-04T00:02:11+01:00

libretech commented

2026-03-04 00:02:11 +01:00

Parent

#2 (Epic: Phase 0 — Foundation)

Summary

Configure the upstream Notesium remote and document the fork relationship. This enables future cherry-picking of upstream fixes and makes the fork provenance clear to contributors. The librenotes repo was forked from Notesium (MIT), and this issue ensures that relationship is properly recorded.

Acceptance Criteria

Instructions for adding the upstream Notesium remote are documented (README or CONTRIBUTING)
LICENSE file retains the original Notesium copyright notice alongside the librenotes notice
A NOTICE or ATTRIBUTION section documents the fork origin, upstream repo URL, and the upstream commit hash at fork time
git remote configuration for upstream is documented for contributors

Dependencies

None — this can be done at any time during Phase 0.

Scope Notes

Does NOT include renaming the Go module (see #34)
Does NOT include restructuring the codebase (see #35)
Does NOT include code changes — this is purely about git remote configuration and attribution documentation
Narrows the fork-specific scope from #3 (which also covered reorganization, now handled separately by #34 and #35)

## Parent #2 (Epic: Phase 0 — Foundation) ## Summary Configure the upstream Notesium remote and document the fork relationship. This enables future cherry-picking of upstream fixes and makes the fork provenance clear to contributors. The librenotes repo was forked from Notesium (MIT), and this issue ensures that relationship is properly recorded. ## Acceptance Criteria - [ ] Instructions for adding the upstream Notesium remote are documented (README or CONTRIBUTING) - [ ] LICENSE file retains the original Notesium copyright notice alongside the librenotes notice - [ ] A NOTICE or ATTRIBUTION section documents the fork origin, upstream repo URL, and the upstream commit hash at fork time - [ ] git remote configuration for upstream is documented for contributors ## Dependencies None — this can be done at any time during Phase 0. ## Scope Notes - Does NOT include renaming the Go module (see #34) - Does NOT include restructuring the codebase (see #35) - Does NOT include code changes — this is purely about git remote configuration and attribution documentation - Narrows the fork-specific scope from #3 (which also covered reorganization, now handled separately by #34 and #35)

libretech added the

phase-0

task

infrastructure

labels 2026-03-04 00:02:11 +01:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: public/librenotes#36