starsetbyte/peregrine
Watch
1
0
Fork
You've already forked peregrine
 0
Code Issues 14 Pull requests 1 Projects Releases Packages Wiki Activity Actions

Archaeology pass: turn long-term plans into current roadmap issues #88

New issue
Open
opened 2026-07-11 21:43:35 +00:00 by starsetbyte · 0 comments
starsetbyte commented 2026-07-11 21:43:35 +00:00
Owner
Copy link

Goal

Review the historical plans/specs under docs/ and convert still-relevant long-term work into current, deduplicated Forgejo issues. Do not blindly execute unchecked boxes from old implementation plans; many describe work that has already shipped.

Initial candidates to classify

  • Notifications auto-refresh and refresh-on-tab-entry.
  • Server-side feed-preference synchronization.
  • Durable composer drafts beyond the first segment, attachments, and alt-text editing/status.
  • Search/discovery expansions such as feed/list search and trending topics.
  • Accessibility/TalkBack smoke coverage and device-only release gates.
  • Threading/interactions polish and remaining media/quote moderation follow-ups.
  • Existing performance plans, video work (#56), and other already-open issues.

Acceptance criteria

  • Inventory the plans and classify each as shipped, superseded, deferred, or still actionable.
  • Link existing issues instead of creating duplicates.
  • Create separate issues for actionable work with scope, dependencies, and acceptance criteria.
  • Add status headers or an index so future contributors do not treat stale plans as current instructions.
## Goal Review the historical plans/specs under `docs/` and convert still-relevant long-term work into current, deduplicated Forgejo issues. Do not blindly execute unchecked boxes from old implementation plans; many describe work that has already shipped. ## Initial candidates to classify - Notifications auto-refresh and refresh-on-tab-entry. - Server-side feed-preference synchronization. - Durable composer drafts beyond the first segment, attachments, and alt-text editing/status. - Search/discovery expansions such as feed/list search and trending topics. - Accessibility/TalkBack smoke coverage and device-only release gates. - Threading/interactions polish and remaining media/quote moderation follow-ups. - Existing performance plans, video work (#56), and other already-open issues. ## Acceptance criteria - Inventory the plans and classify each as shipped, superseded, deferred, or still actionable. - Link existing issues instead of creating duplicates. - Create separate issues for actionable work with scope, dependencies, and acceptance criteria. - Add status headers or an index so future contributors do not treat stale plans as current instructions.
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
fix/profile-feed-context-attribution
docs/repo-cleanup-pass
feat/moderation
worktree-feat+moderation
No results found.
Labels
Clear labels   
auth
Authentication and OAuth

  
bug
Something is broken

  
composer
Post composition and drafts

  
correctness
Logic and state correctness

  
database
Room, migrations, persistence

  
durability
Data safety, persistence, recovery

  
enhancement
New feature or request

  
feeds
Feed management and preferences

  
interactions
Like, repost, reply interactions

  
notifications
Notification system

  
performance
Performance issues

  
reliability
Resilience against interruptions

  
safety
User safety and trust

  
security
Security concerns

No labels
auth
bug
composer
correctness
database
durability
enhancement
feeds
interactions
notifications
performance
reliability
safety
security
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
starsetbyte/peregrine#88
No description provided.