I was reading through Rolebase and noticed how much of the work sits at the intersection of product details and governance practice: roles, subjects, meetings, tasks, decision logs, deleted-account handling, etc. Even the open issues reflect that — things like “Journal des décisions”, default meeting templates per role, Nextcloud integration, showing slugs instead of UUIDs, and the small UX bugs around calendar slots or subject indicators.
My outside read is that this is harder to contribute to than a typical TypeScript SaaS bug list, because a useful contributor needs some feel for how Holacracy/Sociocracy-style orgs actually use the product, not just the stack.
I’m Ray, a founder working in an adjacent space. This is a genuine question, not a pitch: when you need help from new contributors on Rolebase, do you mostly find them through existing users/governance communities rather than through GitHub issues?
A short reply is plenty.
I was reading through Rolebase and noticed how much of the work sits at the intersection of product details and governance practice: roles, subjects, meetings, tasks, decision logs, deleted-account handling, etc. Even the open issues reflect that — things like “Journal des décisions”, default meeting templates per role, Nextcloud integration, showing slugs instead of UUIDs, and the small UX bugs around calendar slots or subject indicators.
My outside read is that this is harder to contribute to than a typical TypeScript SaaS bug list, because a useful contributor needs some feel for how Holacracy/Sociocracy-style orgs actually use the product, not just the stack.
I’m Ray, a founder working in an adjacent space. This is a genuine question, not a pitch: when you need help from new contributors on Rolebase, do you mostly find them through existing users/governance communities rather than through GitHub issues?
A short reply is plenty.