Contributing
Introduction
Reepolee is proprietary commercial software. Alpha participants receive the source under the applicable license for use and modification within their licensed organization; it is not open source and may not be redistributed or published.
The reason is simple. We want to spend as much time as humanly possible building Reepolee itself, and the most reliable way to do that is to keep the surface area we owe to the outside world small. A framework that drifts under the weight of community patches becomes unstable; a framework with a small, deliberate group of authors stays coherent. We are optimising for the second outcome.
There Is No Issue Tracker
Reepolee does not have a public issue tracker you can freely post to. Bug reports, feature requests, and "this should be different" tickets do not have a queue to land in.
We know this is unusual. The trade-off is honest about what an issue tracker actually demands of the people running it - constant triage, repeated context, and a backlog that grows faster than it shrinks. Removing it gives us the room to build.
Contact Us First
Email hello@reepolee.com with bug reports, feature requests, or feedback. Security reports should go to security@reepolee.com.
A useful discussion looks like:
- A concrete problem you've actually run into, not a hypothetical. "I tried to do X, the result was Y, I expected Z" beats "Reepolee should support X."
- The smallest reproduction you can manage when the topic is a bug - ideally a single route or template, not a full project.
- Your Reepolee and Bun versions - the
versionfield inpackage.jsonand the output ofbun --version. - What you've already tried, so the thread doesn't retread ground you've covered.
If we find your input valuable, we will promote the discussion into an item on our roadmap. That is how something becomes work we commit to. A discussion that doesn't get promoted is not a rejection of you - it is a statement that the issue, as framed, isn't something we plan to take on. You are welcome to keep using the discussion thread to talk it through with other readers.
Modify Your Licensed Copy
Reepolee is structured so that every line of code lives in your project's user land. There is no node_modules/reepolee to monkey-patch around. The lib/, routes/, components/, and config/ directories are yours from the moment you clone the starter.
If you need behaviour Reepolee doesn't ship - a different session encoder, a custom queue driver, a route convention that suits your team - you may change your licensed copy for your own use. Do not publish or share Reepolee source changes outside your organization; see the license supplied with the alpha bundle.
The implication is that "Reepolee doesn't do X" is rarely a blocker for you. It is a blocker for the next person who wants X to be there by default, which is what discussions and the roadmap are for.
Security Issues
Security reports are the one exception to the no-public-channel rule. Email security@reepolee.com directly rather than opening a discussion. We will acknowledge within a few days and coordinate disclosure privately.
Building and Running Locally
After receiving the private alpha bundle, follow the included installation instructions. For a local development installation:
bun install
cp .env.example .env
bun dev
The dev server runs on http://localhost:2338. Edit any file under lib/, routes/, or components/ and hot-reload picks up the change.
License
Reepolee is governed by the proprietary license included with the alpha bundle. It permits use and modification within the licensed organization, but does not permit redistribution, public source sharing, or competing products.