Question on contributor help for wolfXmonitor’s integration-heavy surface area

[flyoung588]

I read through the README and noticed wolfXmonitor is not just “ping a URL every minute.” The surface area is already pretty broad: incident deduplication, public /status pages, Brevo email, Telegram via @wolfXmonitor_bot, Twilio WhatsApp, Discord webhooks, per-user alert destinations, admin-managed credentials, and Paystack/M-Pesa billing.

One outside observation: for a project like this, the hard contributor work probably is not isolated UI polish. A useful contributor would need to understand where monitor state, alert delivery, billing limits, and user-owned integrations meet. That makes “good first issue” style contribution harder than usual, even though the repo is open source.

I’m Ray, a founder working in an adjacent space, and this is a genuine question, not a pitch:

When you need help on wolfXmonitor, is finding contributors/builders for that kind of integration-heavy work something you already handle manually through DMs/posts/community channels, or has it not been a real pain yet?

A short reply is plenty.

[WOLVAREX]

You're actually right. Finding contributors has been one of the harder parts so far. Most of the development is currently done by me, and because features like monitoring, alerting, integrations, and billing are connected, onboarding new contributors takes more effort than in a typical project. I'm working on improving documentation and breaking work into smaller pieces, but attracting and retaining contributors is still a challenge.

Out of curiosity, what made you ask? Have you run into similar challenges in your own projects?