FAQ // FREQUENT_QUERIES
QUESTIONSanswered plainly_
Everything newcomers ask before their first clone — who we are, what we maintain, how to contribute, and how to reach us for support or security reports.
What is Smart Team?
Smart Team is an open-source collective operating across three GitHub organizations — thesmarter (core platform), AdaaSystem (ERP and business systems), and DetaElectPro (medical and electrophysiology). We build practical, production-grade software and publish it openly so anyone can inspect, reuse, and improve it.
Where is the team based?
We are a distributed, remote-first collective with roots in Sudan and collaborators across multiple time zones. All coordination happens in the open on GitHub — issues, discussions, and pull requests are our headquarters.
What kinds of projects do you maintain?
Forty public repositories spanning developer tooling, Astro/Tailwind starters, ERP modules (HR, inventory, accounting), medical signal tooling, mobile apps, and automation scripts. Each repository page lists its language, topics, stars, and live links so you can judge fit in seconds.
How can I contribute?
Pick an issue labelled good-first-issue, fork the repo, create a focused branch, and open a pull request. Clone with git clone, push your branch, then run gh pr create. Maintainers review every PR — small, well-tested changes merge fastest.
What licenses do you use?
Most projects use permissive licenses (MIT or Apache-2.0) so you can use them commercially with attribution. A few ERP and medical packages use copyleft or custom terms where data-safety demands it. Every repository declares its license in its root LICENSE file and on its repo page.
Do you offer commercial support?
Yes. For deployment, customization, training, and SLAs — especially around AdaaSystem ERP and DetaElectPro clinical tooling — open an issue or discussion on the relevant repository with the tag commercial-support. We scope fixed-price and retainer engagements in the open wherever possible.
How do I report a security issue?
Do not open a public issue for vulnerabilities. Email the maintainers via the address listed in the repository SECURITY.md, or use GitHub private vulnerability reporting. Include reproduction steps, affected versions, and impact. We acknowledge reports within 72 hours and publish fixes with credit.
Still stuck?
Open a discussion on any repository, or browse the full catalog to find the right codebase.