Skip to content

Latest commit

 

History

History
105 lines (53 loc) · 9.49 KB

faq.md

File metadata and controls

105 lines (53 loc) · 9.49 KB

Frequently asked questions

What is the program called?

The OpenRoot Developer Program. Its developer participants are OpenRoot builders.

What is OpenRoot?

OpenRoot is primarily a developer program and builder community for useful open-source projects. Program participants are called OpenRoot builders. The newsletter supports this work by sharing projects, builder stories and practical technical ideas. Its coverage of agents, automation, infrastructure and AI-powered 3D does not limit the program: projects can be in any software category that meets the published requirements.

Is it live?

The developer program is live. Applications and the approval-only private portal are available, and approved builders can join the GitHub organization. We are seeking partners to expand the reward pool. Builder milestone claims are open for manual review. See points, milestones and claim instructions; offer terms and funding are agreed per project.

Are rewards cash?

No. The planned rewards are subscriptions, credits, and developer-tool access.

Can any type of project join?

Any software category can be considered. Projects must satisfy the published cohort, rights, safety, and conduct requirements. OpenRoot does not need to invent or direct every project.

Any programming language and repository/documentation language is welcome, including non-English repositories. Bring your own ideas; you choose the stack, roadmap and project direction.

Can I apply without a project idea?

Yes. Check “I’m not sure what I’m going to build yet.” An interests note is optional. OpenRoot reviews undecided applications too, but a specific approved project and agreed milestones are required before reward eligibility. Explicit acceptance of the current application terms and published program policies is required before every submission, separately from privacy consent. Read the application rules.

Can I start with a private repository?

Yes. A private development phase is allowed. The duration and any public-release condition are agreed before enrollment, not applied by an automatic timer. Private development does not itself prove a milestone that requires public release or adoption. Other builders do not automatically get private-code access.

Is there a referral program?

A milestone-based builder referral program is planned. The referred builder must be approved and reach a verified qualifying project milestone before a funded referral claim can be reviewed. Signups alone are not rewarded. No benefits, caps or funded availability are confirmed yet.

Does OpenRoot market my project?

OpenRoot helps promote member projects through its publication and social channels, completely free of charge and as much as it can. Builders manage wider marketing and growth. Coverage, traffic and project success are not guaranteed.

Promotion is not limited to one feature. Projects may appear multiple times in the newsletter and on social channels through project highlights, showcases and in-depth articles. Builders can send releases, substantial updates and user stories to hello@openroot.dev for editorial consideration. This support is completely free of charge and does not require earning or redeeming a reward. Timing and format depend on editorial fit and available capacity; OpenRoot does not guarantee repeat coverage, reach or results.

We are looking for builders creating, or exploring, projects intended for other people to use: software that solves a problem, provides a useful tool or helps its users do something. Any software category, programming language and documentation language is welcome. Your project does not need existing users, and undecided applicants or an agreed private development phase remain welcome.

Hackathon builders are welcome too, whether preparing to enter or continuing a hackathon project. Additional rewards for strong results in eligible, pre-approved hackathons are planned. Eligible events, outcomes, evidence, funding and bonus terms must be published and agreed before a reward-bearing offer begins. A win does not automatically earn OpenRoot points or a reward. No specific eligible hackathons or bonus amounts are announced yet; hackathon bonus claims are not open.

Can I enter hackathons with my project?

Yes. You may participate in hackathons, outside collaborations and other activities. OpenRoot participation is not exclusive. Respect the event's own rules and any project/contributor rights.

What are the initial offers?

One month of DeepLearning.AI, one available until claimed, plus AI model API credits for GPT, Claude, Gemini and Grok, delivered through budget-limited third-party API access, valued at USD 20-10,000. OpenRoot reports strict per-key budgets and no announced quantity cap for API offers. These are not credits transferred to your own model-provider account or official vendor sponsorships. Exact product, permitted distribution, expiry, eligibility and delivery terms remain pending. Manual milestone claims are open; see the published star ladder and claim instructions. Read the offer details.

Does a GitHub star target guarantee a reward?

Only the enrolled cohort's published rules can establish qualification. Attention may have its own track; stronger adoption may unlock a different reward. No numerical target is announced yet; reported offers still require finalized claim and delivery terms.

Can I choose my reward?

That is the intended model: choose among the eligible, available rewards for your cohort and tier. A particular subscription or provider is not guaranteed until confirmed.

Can anyone sign into the portal?

No. You must apply and be approved. Approval creates a program account. Sign-in identifies you; it does not grant membership by itself.

Why enter my exact GitHub username?

It helps locate the correct account. You will also verify control through GitHub linking; merely typing someone else's username cannot claim their projects.

Is the email code MFA?

It is an onboarding email verification check. It should not be presented as strong independent MFA. Any additional passkey/authenticator requirement will be described before access is activated.

Who owns the project, and what if I leave?

The intended policy is that you retain ownership of your own code and lead your project. Your repository is hosted under OpenRoot's GitHub organization and you receive repository-level Admin. Organization owners retain administrative access, so it is not the same as a personally owned repository under your username. Final licensing, maintenance, contribution and departure/transfer terms must be agreed before enrollment.

Can I propose an existing repository?

Yes. Applications are open for manual review. Submit the original URL, your authority to transfer or copy, and dated adoption evidence. Prior achievements count only if the approved cohort's baseline rules allow them. If you apply with an existing project, the accepted project must be hosted under OpenRootdev: transfer the original repository after review, or create an empty organization repository and copy the code there with Git. Do not migrate before the project and migration are approved. Copying code does not copy stars, issues or other GitHub project data. Existing adoption and rewards are reviewed separately. Read the step-by-step builder instructions.

Can I request additional accounts or project teams?

Yes. Include exact GitHub usernames or GitHub App names, their human/machine/integration type, purpose, target repositories and requested roles. Project-specific teams can cover multiple approved repositories without granting organization-wide write access. Never include secrets. Team and automation requests require review.

How are team rewards divided?

The project/team allocation is agreed before enrollment. Repo creation, commit counts, or the final merged PR author do not automatically determine the allocation.

What if sponsors do not provide enough rewards?

Unfunded cohorts cannot promise rewards. Funded cohorts need visible capacity limits and inventory reservations. If an agreed option becomes unavailable, the program follows its disclosed substitution and resolution terms.

How can my company partner?

Read partnerships and contact partner@openroot.dev. The website partner page prepares an email draft locally; nothing is received until you send it from your email app.

For general questions, contact hello@openroot.dev.

A free sandbox. Keep your accounts safe.

OpenRoot is a sandbox for building and collaborating, not a payment request. We will never ask you to send passwords, sign-in or recovery codes, access tokens, API keys, payment details or a fee to join or unlock rewards. Applications need your email and exact GitHub username; enter a sign-in code only on the official portal, never send it to a person. You can invite collaborators and configure repository-scoped apps within your repository permissions; some organization-level actions need an owner. Keep secrets out of repos, applications and messages. Organization hosting is not unlimited free use of paid services.

Questions: hello@openroot.dev. Follow or message OpenRoot on LinkedIn. After accepting the GitHub invitation, read the members-only quick start.