PearOS01
LIVE · READ ONLYOnly configured, verified sources. Missing data stays visible.

02 / BUILD PEAR

Build something
worth contributing to.

Help build the community, design something useful or improve the software. Agree on scope and rewards with the owner, share your work and get it reviewed. No token holdings required.

A GOOD FIRST CONTRIBUTION

You don’t need to be a developer.

Read the quick guide

Community tasks can be completed with a document, images or screenshots. The X / Twitter and Discord proposals below need your ideas first; the owner reviews the plan and confirms rewards before assigning paid work.

New to GitHub? Start here
  1. Choose a task. Open its step-by-step instructions and download the plain-text proposal template. You can fill it in with any text editor.
  2. Create a free account. Sign up for GitHub , then verify your email. You won’t need Git commands, a code editor or a pull request for community tasks.
  3. Introduce yourself. “Open proposal on GitHub” opens a prefilled conversation. Add a little about yourself and your plan, then click Submit new issue. For an already assigned task, use its existing conversation instead.
  4. Wait for confirmation. The owner confirms your assignment, scope and exact reward amount/asset before you begin paid work. Planning cards aren’t funded bounty offers.
  5. Share your work. Return to the same conversation, write a comment and attach your document or paste a link. Community deliverables do not require a pull request. The owner reviews them and may request changes before approval and manual payment.

A GitHub “issue” is simply a task conversation. If the link shows 404, ask the owner for repository access; contributors need read access and Issues must be enabled. Never put passwords or recovery codes in a public comment.

Browse task conversations

2 tasks in CommunityClear filters

Planning
Community / Owner review required

Build a community-run X / Twitter presence

Help shape PearOS's voice and a community editorial process. Start with a proposal; the owner approves the account, contributors and posts before anything goes public.

No coding needed · Start with a document

How to help, step by step
  1. Read the project homepage and download the proposal template below. No coding is needed.
  2. Suggest an account name, a short bio, community guidelines and a simple process for reviewing posts.
  3. Draft five example posts and a one-week content plan in a document. Keep drafts private until reviewed.
  4. Open the prefilled task conversation and introduce yourself. Share your proposal or a document link; wait for the owner to confirm scope, assignment and the exact reward.
  5. After approval, help the owner set up the account using delegated access where supported. Submit the drafts for review before publishing.

What to deliver

  • One proposal document with account/bio suggestions and editorial guidelines.
  • Five draft posts and a one-week content plan.
  • An owner-approved setup and handoff checklist.

How the owner reviews it

  • A clear voice, bio and community conduct policy match PearOS's identity.
  • Five draft posts and a one-week plan include a named owner approval step before publication.
  • The handoff explains how community members suggest posts and how access is granted and removed.
  • No posts promise returns or imply Apple, Robinhood or platform endorsement.

Do not register an official account, post as PearOS or share account passwords before owner approval. Rewards and any paid assignment must be confirmed before paid work begins.

RewardTo be confirmedThe owner confirms the amount and asset before paid work begins. A proposal is not an assigned bounty.
Download proposal template Open proposal on GitHub

Opens a draft conversation. Sign in, add your introduction and click Submit new issue. No code or pull request needed.

Planning
Community / Owner review required

Build a welcoming PearOS Discord

Design a friendly home for introductions, project updates and contribution help. The owner reviews the plan, server permissions and moderation approach before opening it to the community.

No coding needed · Start with a document

How to help, step by step
  1. Download the proposal template and sketch a small channel list: welcome, announcements, general chat and contribution help.
  2. Write a welcome message, rules and a short guide for joining a task. A document or screenshots are enough; no code is needed.
  3. Propose member/moderator roles, permission settings and a simple moderation process.
  4. Open the prefilled task conversation, introduce yourself and attach your plan. Wait for the owner to confirm assignment, scope and the exact reward.
  5. After approval, configure an owner-controlled server and test access with a normal member account. Ask the owner to review it before publishing an invite.

What to deliver

  • A channel/role plan plus welcome text, rules and moderation guidance.
  • Screenshots or a checklist showing normal-member permission tests after approved setup.
  • An owner-approved handoff and invitation checklist.

How the owner reviews it

  • A small channel structure, welcome message and contribution guide are clear to a first-time visitor.
  • Announcements are restricted to approved maintainers; moderator permissions follow the reviewed plan.
  • Rules and moderation guidance cover spam, impersonation and unsolicited wallet/account requests.
  • The owner controls the server and approves the permissions, bot choices and public invite.

Do not publish an official invite, install paid bots or grant administrator access before owner approval. Rewards and any paid assignment must be confirmed before paid work begins.

RewardTo be confirmedThe owner confirms the amount and asset before paid work begins. A proposal is not an assigned bounty.
Download proposal template Open proposal on GitHub

Opens a draft conversation. Sign in, add your introduction and click Submit new issue. No code or pull request needed.

01Pick a task & introduce yourself
02Agree scope & exact reward
03Share your work for review
04Owner approval & manual payment