public/librenotes
2
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases 1 Wiki Activity

Add upstream Notesium remote and document fork relationship #36

New Issue
Closed
opened 2026-03-04 00:02:11 +01:00 by libretech · 0 comments
libretech commented 2026-03-04 00:02:11 +01:00
Owner
Copy Link
Copy Source

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 - [x] Instructions for adding the upstream Notesium remote are documented (README or CONTRIBUTING) - [x] LICENSE file retains the original Notesium copyright notice alongside the librenotes notice - [x] A NOTICE or ATTRIBUTION section documents the fork origin, upstream repo URL, and the upstream commit hash at fork time - [x] 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-0taskinfrastructure labels 2026-03-04 00:02:11 +01:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
backend
Backend changes
 database
Database changes
 documentation
Documentation improvements
 epic
frontend
Frontend changes
 infrastructure
Infrastructure and deployment
 launch
Launch and release tasks
 phase-0
phase-1
phase-2
phase-3
phase-4
phase-5
phase-6
security
Security-related
 task
Actionable task
No labels infrastructure phase-0 task
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
libretech (Michael Czechowski) libretech-bot
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: public/librenotes#36