mirror of
https://github.com/runbear-io/beardrive.git
synced 2026-08-25 08:08:08 +02:00
Snow LeeandClaude Fable 5
00eee2c5ed
GTM reviewer round 1 (baseline: positioning 6, funnel 4, open-paid 8,
community 3, launch 3, metrics 2; 3 blockers + 3 majors, all repo-fixable):
- TRUTH: removed the false 'no server required' claim (x3 on the
website) and stale 'S3/GCS directly' sync claims in both plugin
manifests — hub-only since v0.3.0
- POSITIONING: one line everywhere ('the open-source Google Drive for
AI agents' + the attribution/read-analytics wedge) across README,
website, marketplace.json, plugin.json, SKILL.md; third 'Why' card
and AGPL-why rationale; nav CTA → Star on GitHub
- COMMUNITY: CONTRIBUTING.md, issue forms + PR template, public dated
ROADMAP.md, CHANGELOG.md seeded from all 8 releases
- DEMO ASSETS: real product screenshots captured from the seeded demo
hub (Insights treemap, browse-with-heat, public share page) embedded
in README + website — no fabricated content anywhere
- DOCS: self-hosting quickstart, metrics plan (north star: active
shared brains), launch-plan drafts (Show HN/PH/launch week), and
docs/gtm-handoff.md — the prioritized external-action checklist
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01P5cxPQdSGJnjXCYY9GeWXt
1.6 KiB
1.6 KiB
BearDrive roadmap
Last updated: 2026-07-15. This is the direction, not a contract — items move as we learn. Comments and PRs welcome; items marked help wanted are deliberately scoped for outside contributors.
Now (next release or two)
- Time travel / restore —
bdrive restore <path>@<time>: every blob is already retained forever, so restore is re-putting an old blob as a new op. The history UI and blob API already exist; this is the CLI and revert UX. - Demo assets & docs — 60-second demo, richer self-hosting guide.
Next
- Journal compaction & blob GC policies — bounded storage for long-lived, high-churn volumes (opt-in; today everything is retained).
- Per-path access scopes — multi-agent setups where an agent can be limited to a subtree of a project. help wanted (design discussion first — this touches the org/permission model).
- More agent platforms in
bdrive hooks install— the hook engine is platform-generic; adding a platform is a small adapter + matcher set. help wanted.
Later / exploring
- FUSE / NFS mount mode — lazy-loading huge volumes instead of full materialization.
- Search across the hub — full-text + wikilink graph over a project.
- Webhooks / notifications — "a file changed in
reports/" pushed to Slack or similar (hub-side).
Recently shipped
See CHANGELOG.md: React web UI (v0.6.0), read-heat
Insights and agent read attribution (v0.4.0), bdrive url internal links
(v0.7.0), SQL metadata backends incl. Postgres/Supabase (v0.3.0).