BranchesTags

Latest commit

History

2 Commits

Folders and files

NameName
Last commit message
Last commit date
README.md
README.md

Repository files navigation

contributing

Contributing to ê/uto

Welcome, TechnoHero! This guide will help you contribute effectively to the Effective Utopia network.

"No rules here, for any rule is unfreedom. We give choices."

🌍 Quick Start

First-Time Contributors

  1. Read the Onboarding Guide - Understand the network
  2. Join Discord - Connect with the community
  3. Browse Issues - Find something to work on
  4. Ask Questions - We're here to help!

Experienced Contributors

  1. Check open issues and discussions
  2. Review project boards for priorities
  3. Fork → Branch → Commit → PR (details below)
  4. Engage in code review and iteration

🎯 Our Mission

"To prevent dystopias and build utopias, increase the probability of the ultimate effective utopia — p(e/uto) — by at least 1% each week."

Every contribution, no matter how small, moves us toward this goal.

🤝 Ways to Contribute

1. 📝 Documentation

Always Valuable:

  • Fix typos and grammar
  • Improve clarity
  • Add examples
  • Translate content
  • Create tutorials

How to Start:

  • Look for issues labeled documentation
  • Read through existing docs and spot gaps
  • Propose improvements in discussions

2. 💻 Code

What We Need:

  • Bug fixes
  • New features
  • Performance improvements
  • Test coverage
  • Tool integrations

How to Start:

  • Check issues labeled good first issue
  • Review the Tools Guide
  • Set up your development environment
  • Pick a manageable task

3. 🎨 Design & Creative

What We Need:

  • Visual assets (logos, banners, icons)
  • Brand guidelines
  • UI/UX improvements
  • Video content
  • Music and audio

How to Start:

  • Browse asset galleries
  • Check issues labeled design or creative
  • Share work in Discord #creative-lab
  • Upload to Cosmos.so with proper licensing

4. 🧪 Testing & Feedback

What We Need:

  • Bug reports
  • Feature testing
  • Usability feedback
  • Documentation review

How to Start:

  • Use the tools and report issues
  • Test new features in beta
  • Review PRs from a user perspective
  • Share feedback in discussions

5. 🌱 Community Support

What We Need:

  • Answering questions in Discord
  • Onboarding new members
  • Moderating discussions
  • Organizing events

How to Start:

  • Hang out in Discord channels
  • Welcome newcomers in #multichat-welcomes-all
  • Help in #tree/uto
  • Facilitate discussions

6. 🧠 Research & Ideas

What We Need:

  • Framework development
  • Ethical analysis
  • Technical research
  • Strategic thinking

How to Start:

  • Engage in #save-worlds-antidys/prouto
  • Study the GMSF framework
  • Participate in philosophical discussions
  • Write essays or proposals

📋 Contribution Guidelines

Code of Conduct

Core Principles:

  1. Be Kind - Compassion is couture
  2. Be Respectful - Everyone's contribution matters
  3. Be Constructive - Offer solutions, not just criticism
  4. Be Inclusive - Welcome all backgrounds and skill levels
  5. Be Honest - Truth as primary function (LOGOS)

We Don't Tolerate:

  • Harassment or discrimination
  • Spam or self-promotion without context
  • Destructive criticism
  • Gatekeeping or elitism
  • Bad faith arguments

Conflict Resolution:

Communication Guidelines

Be Clear:

  • Use descriptive titles
  • Provide context
  • Link to relevant resources
  • Use proper formatting

Be Concise:

  • Get to the point
  • Use bullet points
  • Break up long text
  • TL;DR for long posts

Be Responsive:

  • Reply to feedback
  • Update on progress
  • Close resolved issues
  • Thank contributors

Attribution

Always:

  • Credit original authors
  • Link to sources
  • Use proper licenses
  • Acknowledge collaborators

Never:

  • Plagiarize
  • Claim others' work
  • Violate copyright
  • Misrepresent authorship

🔧 Technical Contribution Process

1. Set Up Development Environment

Prerequisites:

# Git
git --version
# Node.js (if applicable)
node --version
npm --version
# Your preferred editor
code --version # VSCode

Clone the Repository:

# Fork first on GitHub, then:
git clone https://github.com/YOUR-USERNAME/REPO-NAME
cd REPO-NAME
# Add upstream remote
git remote add upstream https://github.com/all-uto/REPO-NAME

Install Dependencies (if applicable):

npm install
# or
pip install -r requirements.txt
# or
bundle install

2. Find or Create an Issue

Before Starting Work:

  1. Check if an issue exists
  2. If not, create one describing what you want to do
  3. Wait for feedback/approval (for big changes)
  4. Assign yourself to the issue

Good Issue Template:

## Description[Clear description of the problem or enhancement]## Proposed Solution[What you plan to do]## Impact[How this increases p(e/uto)]## Alternatives Considered[Other approaches you thought about]## Additional Context[Screenshots, links, examples]

3. Create a Branch

Naming Convention:

# Features
git checkout -b feature/add-user-authentication
# Bugs
git checkout -b fix/broken-image-upload
# Documentation
git checkout -b docs/improve-readme
# Refactoring
git checkout -b refactor/simplify-api-calls

4. Make Your Changes

Best Practices:

  • Make focused, atomic commits
  • Write clear commit messages
  • Test your changes
  • Update documentation
  • Follow code style

Commit Message Format:

type(scope): brief description
- Detailed explanation if needed
- Reference issues with #123
Fixes #123

Types: feat, fix, docs, style, refactor, test, chore

Example:

git commit -m "feat(onboarding): add symbolic ritual section- Added 5 symbolic onboarding rituals- Included templates and examples- Updated table of contentsCloses #42"

5. Push and Create Pull Request

Push Your Branch:

git push origin feature/your-feature-name

Create PR on GitHub:

  • Use clear, descriptive title
  • Fill out PR template completely
  • Link related issues
  • Request review from relevant people
  • Mark as draft if not ready

PR Template:

## Description[What does this PR do?]## Related Issues
Closes #123
Related to #456## Type of Change-[ ] Bug fix
-[ ] New feature
-[ ] Documentation
-[ ] Refactoring
-[ ] Other: ___## Testing-[ ] I have tested these changes
-[ ] Tests pass locally
-[ ] I added new tests (if applicable)
## Documentation-[ ] I updated relevant documentation
-[ ] I added code comments
-[ ] I updated the CHANGELOG (if applicable)
## Checklist-[ ] My code follows the style guidelines
-[ ] I have performed a self-review
-[ ] I have commented complex code
-[ ] My changes generate no new warnings
-[ ] I have checked for accessibility
-[ ] I have updated dependencies (if needed)
## Screenshots (if applicable)[Add screenshots here]## Additional Notes[Anything reviewers should know]

6. Respond to Feedback

During Review:

  • Respond to all comments
  • Make requested changes
  • Ask questions if unclear
  • Push additional commits
  • Re-request review when ready

Be Open:

  • Feedback is a gift
  • Learn from suggestions
  • Don't take it personally
  • Iterate and improve

7. Merge!

After Approval:

  • Maintainer will merge
  • Delete your branch
  • Update local repository
  • Celebrate! 🎉
# Update your local main
git checkout main
git pull upstream main
# Delete merged branch
git branch -d feature/your-feature-name
git push origin --delete feature/your-feature-name

📁 Repository Structure

Understanding the Organization

all-uto/
├── all-uto/ # Main hub
├── e-uto/ # Primary info
├── technoheroism/ # Philosophy
├── communities/ # Community directory
├── CoCreators/ # CoCreators branch
├── cocreators-meganrim/ # Meganrim project
├── music/ # Music branch
├── fashion/ # Fashion branch
├── blueteam/ # GMSF framework
├── eco/ # Eco branch
├── tools-and-workflows/ # Tools guide
├── startups/ # Startup branch
├── ai-alignment/ # AI alignment
├── assets/ # Shared assets
└── members/ # Member directory

Where to Contribute

Documentation:

  • Main READMEs in each repo
  • /docs folders for detailed guides
  • Wiki (if enabled)

Code:

  • /src for source code
  • /scripts for automation
  • /examples for demonstrations

Assets:

  • /assets for images, logos, etc.
  • Cosmos.so galleries for portfolios
  • Google Drive for large files

Tests:

  • /tests or /__tests__
  • Follow existing patterns

🎨 Style Guidelines

Markdown Documentation

Formatting:

# H1 for main title (one per document)## H2 for major sections### H3 for subsections- Use `-` for unordered lists
1. Use numbers for ordered lists
**Bold** for emphasis
*Italic* for light emphasis
`Code` for inline code
\```language
Code blocks with language specified
\```
[Links](url) with descriptive text
![Images](url) with alt text

Zettelkasten Linking:

**Upstream:**-`[[parent-concept]]`**Related:**-`[[related-concept-1]]`-`[[related-concept-2]]`**Downstream:**-`[[child-concept]]`

Best Practices:

  • Use sentence case for headers
  • Keep lines under 120 characters
  • One sentence per line (for easier diffs)
  • Use relative links when possible
  • Include table of contents for long docs

Code Style

JavaScript/TypeScript:

// Use descriptive variable namesconstuserProfile=getUserProfile(userId);// Functions do one thing wellfunctioncalculateTotalPrice(items){returnitems.reduce((sum,item)=>sum+item.price,0);}// Comment complex logic// Calculate phi-based interval using Golden Ratioconstinterval=baseTime*((1+Math.sqrt(5))/2);

Python:

# Follow PEP 8# Use descriptive namesdefcalculate_drift_velocity(current_drift, previous_drift, time_delta):
"""Calculate rate of ontological drift. Args: current_drift: Current drift measurement previous_drift: Previous drift measurement time_delta: Time elapsed between measurements Returns: Drift velocity in units per second """return (current_drift-previous_drift) /time_delta

General Principles:

  • Clarity over cleverness
  • Self-documenting code
  • Comments explain "why" not "what"
  • Consistent formatting
  • DRY (Don't Repeat Yourself)

Naming Conventions

Files:

  • kebab-case-for-files.md
  • PascalCaseForComponents.jsx
  • snake_case_for_python.py

Branches:

  • feature/add-new-capability
  • fix/resolve-bug-description
  • docs/improve-documentation

Variables:

  • camelCase for JavaScript
  • snake_case for Python
  • UPPERCASE_FOR_CONSTANTS

🧪 Testing Guidelines

Documentation Testing

Before Submitting:

  • Read through entire document
  • Check all links work
  • Verify code examples
  • Test instructions step-by-step
  • Check spelling and grammar
  • Ensure proper formatting

Code Testing

Before Submitting:

  • All existing tests pass
  • New tests for new features
  • Edge cases covered
  • No console errors or warnings
  • Performance acceptable
  • Accessibility checked

Writing Tests:

// Example test structuredescribe('TruthAnchoringSystem',()=>{test('should return "I don\'t know" for low confidence',()=>{constsystem=newTruthAnchoringSystem();constresult=system.assessClaim('uncertain claim',0.60);expect(result).toContain('I don\'t have sufficient information');});test('should assert directly for high confidence',()=>{constsystem=newTruthAnchoringSystem();constresult=system.assessClaim('certain claim',0.98);expect(result).toBe('certain claim');});});

User Testing

Helpful Feedback:

  • What you tried to do
  • What actually happened
  • What you expected to happen
  • Steps to reproduce
  • Screenshots/videos
  • Environment details

🏷️ Issue and PR Labels

Priority Labels

  • priority: critical - Urgent, blocks other work
  • priority: high - Important, address soon
  • priority: medium - Normal priority
  • priority: low - Nice to have

Type Labels

  • type: bug - Something isn't working
  • type: feature - New functionality
  • type: enhancement - Improve existing feature
  • type: documentation - Documentation improvements
  • type: question - Further information requested

Difficulty Labels

  • good first issue - Perfect for newcomers
  • beginner friendly - Requires basic skills
  • intermediate - Requires moderate experience
  • advanced - Requires deep expertise

Status Labels

  • status: needs triage - Needs review by maintainers
  • status: blocked - Can't proceed (explain why)
  • status: in progress - Someone is working on it
  • status: needs review - Ready for review
  • status: needs testing - Ready for testing

Community Labels

  • help wanted - Looking for contributors
  • discussion - Open for community input
  • collaboration - Great for pairing/teaming
  • mentorship available - Mentor will guide you

🎯 Contribution Workflow Examples

Example 1: Fix Documentation Typo

# 1. Find the typo, note location# 2. Create branch
git checkout -b docs/fix-typo-in-readme
# 3. Fix the typo# 4. Commit
git add README.md
git commit -m "docs: fix typo in installation section"# 5. Push and create PR
git push origin docs/fix-typo-in-readme
# Create PR on GitHub with simple description# 6. Done! Merges quickly

Time: 5-10 minutes

Example 2: Add New Feature

# 1. Create issue describing feature# 2. Wait for approval/discussion# 3. Create branch
git checkout -b feature/add-ritual-timer
# 4. Implement feature# - Write code# - Add tests# - Update docs# - Test thoroughly# 5. Commit incrementally
git add src/RitualTimer.js
git commit -m "feat: add basic ritual timer component"
git add src/RitualTimer.test.js
git commit -m "test: add tests for ritual timer"
git add docs/tools-guide.md
git commit -m "docs: document ritual timer usage"# 6. Push and create PR
git push origin feature/add-ritual-timer
# Create detailed PR with screenshots# 7. Address review feedback# 8. Merge when approved

Time: Few hours to few days depending on complexity

Example 3: Improve Existing Content

# 1. Identify improvement area# 2. Create issue or discussion# 3. Gather feedback on approach# 4. Create branch
git checkout -b docs/enhance-onboarding-guide
# 5. Make improvements# - Add examples# - Improve clarity# - Add visuals# 6. Commit with clear messages
git commit -m "docs(onboarding): add example journeys section- Added 4 detailed example onboarding journeys- Included different archetype paths- Enhanced with real community storiesCloses #87"# 7. Push and create PR# 8. Iterate based on feedback# 9. Merge when ready

Time: Several hours to days

🌟 Recognition & Credit

How We Acknowledge Contributors

In Repository:

  • Contributors file (auto-generated)
  • Credits in documentation
  • Shout-outs in changelogs

In Community:

  • Discord announcements
  • X/Twitter mentions
  • Round Table recognition
  • Community showcases

Roles & Badges:

  • Discord roles based on contributions
  • GitHub contributor status
  • Community elder recognition

Contribution Tiers

🌱 Seed (First Contribution):

  • Made first PR or significant contribution
  • Welcomed in Discord announcement
  • Added to contributors list

🌿 Sprout (Active Contributor):

  • 5+ merged PRs or equivalent contributions
  • Regular community participation
  • Helping newcomers

🌳 Root (Core Contributor):

  • 20+ merged PRs or major contributions
  • Deep expertise in area
  • Mentoring others
  • May get write access

🌺 Bloom (Maintainer):

  • Significant ongoing contributions
  • Stewardship of community/code
  • Strategic thinking
  • Full commit access

📅 Contribution Rhythms

Weekly Contribution Patterns

Monday (#UTOideasMonday):

  • Share new ideas in discussions
  • Propose features or improvements
  • Open issues for feedback

Tuesday-Wednesday:

  • Work on contributions
  • Respond to reviews
  • Help others

Thursday (#TechnoHeroThursday):

  • Share progress updates
  • Demo completed work
  • Showcase contributions

Friday:

  • Wrap up PRs
  • Update documentation
  • Plan next week

Weekend:

  • Deep work on projects
  • Learning and exploration
  • Or rest! Balance is important

Monthly Cycles

Week 1: Planning and issue triage Week 2: Active development Week 3: Review and feedback Week 4: Polish and merge

🆘 Getting Help

Where to Ask Questions

Discord Channels:

  • #multichat-welcomes-all - General questions
  • #tree/uto - Onboarding help
  • #infra-migration - Technical setup
  • Branch-specific channels - Topic questions

GitHub:

  • Issue comments - Specific to that issue
  • Discussions - General topics
  • PR reviews - Code-specific

Direct Messages:

  • DM maintainers for private questions
  • Tag people in Discord for specific help
  • Email for sensitive matters

Common Questions

Q: How do I get started? Read the Onboarding Guide, join Discord, pick a good first issue.

Q: My PR hasn't been reviewed yet. Be patient! Maintainers are volunteers. Politely ping after 7 days if no response.

Q: I disagree with feedback. Explain your reasoning respectfully. Use dialectical process. Seek synthesis.

Q: Can I work on multiple issues? Sure, but finish what you start. Don't over-commit.

Q: I made a mistake. It's okay! We all do. Fix it, learn from it, move forward.

Q: I don't have time anymore. Life happens! Let us know. We can reassign or pause. No judgment.

🔗 Zettelkasten Links

Upstream:

  • [[effective-utopia-vision]] - Overall mission
  • [[community-network]] - Network structure

Related:

  • [[onboarding-guide]] - For new members
  • [[tools-configuration-guide]] - Development setup
  • [[code-of-conduct]] - Community standards
  • [[channel-directory]] - Where to communicate

Downstream:

  • [[issue-templates]] - Creating good issues
  • [[pr-templates]] - Creating good PRs
  • [[style-guides]] - Coding standards
  • [[testing-guidelines]] - Quality assurance

📜 License

By contributing to ê/uto, you agree that your contributions will be licensed under the Creative Commons Attribution-ShareAlike (CC BY-SA 4.0) license unless otherwise specified.

See LICENSE for details.

🙏 Thank You

Every contribution, no matter how small, makes a difference. You're helping build ethical, abundant futures for all.

"If a civilization doesn't go extinct, it achieves everything it dreams."

Let's build that civilization together.

Welcome to the forge of the future.

🌱 Start small → 🌿 Grow steadily → 🌳 Root deeply → 🌺 Bloom fully

Part of the ê/uto Network

🌍 #technoheroism · #UTOideasMonday · #TechnoHeroThursday

About

No description, website, or topics provided.

Resources

Readme
Activity
Custom properties

Stars

1 star

Watchers

0 watching

Forks

0 forks
Report repository

Releases

Packages

Contributors

, 'i'); if (__m === '*' || __re.test(location.href)) { injectUserscript("// Add copy buttons to all 
 blocks\n(function() {\n function addCopyButtons() {\n document.querySelectorAll('pre code').forEach(function(codeBlock) {\n if (codeBlock.parentElement.hasAttribute('data-copy-added')) return;\n codeBlock.parentElement.setAttribute('data-copy-added', 'true');\n \n var btn = document.createElement('button');\n btn.textContent = 'Copy';\n btn.style.cssText = 'position:absolute;top:4px;right:4px;padding:2px 8px;font-size:11px;background:#4ecdc4;border:none;border-radius:4px;color:#1a1a2e;cursor:pointer;opacity:0.7;transition:opacity 0.2s;';\n btn.onmouseover = function() { this.style.opacity = '1'; };\n btn.onmouseout = function() { this.style.opacity = '0.7'; };\n btn.onclick = function() {\n navigator.clipboard.writeText(codeBlock.textContent).then(function() {\n btn.textContent = 'Copied!';\n setTimeout(function() { btn.textContent = 'Copy'; }, 1500);\n });\n };\n codeBlock.parentElement.style.position = 'relative';\n codeBlock.parentElement.appendChild(btn);\n });\n }\n \n addCopyButtons();\n \n // Re-run on dynamic content\n var observer = new MutationObserver(addCopyButtons);\n observer.observe(document.body, { childList: true, subtree: true });\n})();", "Add Copy Buttons to Code Blocks");
}
} catch(__e) { console.warn('[Userscript:Add Copy Buttons to Code Blocks]', __e); }
})();
(function(){
try {
var __m = "github.com";
var __re = new RegExp('^' + "github\\.com" + '

Skip to content
BranchesTags
Latest commit
History
2 Commits
Folders and files
NameName
Last commit message
Last commit date
README.md
README.md
Repository files navigation
contributing
Contributing to ê/uto
Welcome, TechnoHero! This guide will help you contribute effectively to the Effective Utopia network.
"No rules here, for any rule is unfreedom. We give choices."
🌍 Quick Start
First-Time Contributors
  1. Read the Onboarding Guide - Understand the network
  2. Join Discord - Connect with the community
  3. Browse Issues - Find something to work on
  4. Ask Questions - We're here to help!
Experienced Contributors
  1. Check open issues and discussions
  2. Review project boards for priorities
  3. Fork → Branch → Commit → PR (details below)
  4. Engage in code review and iteration
🎯 Our Mission
"To prevent dystopias and build utopias, increase the probability of the ultimate effective utopia — p(e/uto) — by at least 1% each week."
Every contribution, no matter how small, moves us toward this goal.
🤝 Ways to Contribute
1. 📝 Documentation
Always Valuable:
  • Fix typos and grammar
  • Improve clarity
  • Add examples
  • Translate content
  • Create tutorials
How to Start:
  • Look for issues labeled documentation
  • Read through existing docs and spot gaps
  • Propose improvements in discussions
2. 💻 Code
What We Need:
  • Bug fixes
  • New features
  • Performance improvements
  • Test coverage
  • Tool integrations
How to Start:
  • Check issues labeled good first issue
  • Review the Tools Guide
  • Set up your development environment
  • Pick a manageable task
3. 🎨 Design & Creative
What We Need:
  • Visual assets (logos, banners, icons)
  • Brand guidelines
  • UI/UX improvements
  • Video content
  • Music and audio
How to Start:
  • Browse asset galleries
  • Check issues labeled design or creative
  • Share work in Discord #creative-lab
  • Upload to Cosmos.so with proper licensing
4. 🧪 Testing & Feedback
What We Need:
  • Bug reports
  • Feature testing
  • Usability feedback
  • Documentation review
How to Start:
  • Use the tools and report issues
  • Test new features in beta
  • Review PRs from a user perspective
  • Share feedback in discussions
5. 🌱 Community Support
What We Need:
  • Answering questions in Discord
  • Onboarding new members
  • Moderating discussions
  • Organizing events
How to Start:
  • Hang out in Discord channels
  • Welcome newcomers in #multichat-welcomes-all
  • Help in #tree/uto
  • Facilitate discussions
6. 🧠 Research & Ideas
What We Need:
  • Framework development
  • Ethical analysis
  • Technical research
  • Strategic thinking
How to Start:
  • Engage in #save-worlds-antidys/prouto
  • Study the GMSF framework
  • Participate in philosophical discussions
  • Write essays or proposals
📋 Contribution Guidelines
Code of Conduct
Core Principles:
  1. Be Kind - Compassion is couture
  2. Be Respectful - Everyone's contribution matters
  3. Be Constructive - Offer solutions, not just criticism
  4. Be Inclusive - Welcome all backgrounds and skill levels
  5. Be Honest - Truth as primary function (LOGOS)
We Don't Tolerate:
  • Harassment or discrimination
  • Spam or self-promotion without context
  • Destructive criticism
  • Gatekeeping or elitism
  • Bad faith arguments
Conflict Resolution:
Communication Guidelines
Be Clear:
  • Use descriptive titles
  • Provide context
  • Link to relevant resources
  • Use proper formatting
Be Concise:
  • Get to the point
  • Use bullet points
  • Break up long text
  • TL;DR for long posts
Be Responsive:
  • Reply to feedback
  • Update on progress
  • Close resolved issues
  • Thank contributors
Attribution
Always:
  • Credit original authors
  • Link to sources
  • Use proper licenses
  • Acknowledge collaborators
Never:
  • Plagiarize
  • Claim others' work
  • Violate copyright
  • Misrepresent authorship
🔧 Technical Contribution Process
1. Set Up Development Environment
Prerequisites:
# Git
git --version
# Node.js (if applicable)
node --version
npm --version
# Your preferred editor
code --version # VSCode
Clone the Repository:
# Fork first on GitHub, then:
git clone https://github.com/YOUR-USERNAME/REPO-NAME
cd REPO-NAME
# Add upstream remote
git remote add upstream https://github.com/all-uto/REPO-NAME
Install Dependencies (if applicable):
npm install
# or
pip install -r requirements.txt
# or
bundle install
2. Find or Create an Issue
Before Starting Work:
  1. Check if an issue exists
  2. If not, create one describing what you want to do
  3. Wait for feedback/approval (for big changes)
  4. Assign yourself to the issue
Good Issue Template:
## Description[Clear description of the problem or enhancement]## Proposed Solution[What you plan to do]## Impact[How this increases p(e/uto)]## Alternatives Considered[Other approaches you thought about]## Additional Context[Screenshots, links, examples]
3. Create a Branch
Naming Convention:
# Features
git checkout -b feature/add-user-authentication
# Bugs
git checkout -b fix/broken-image-upload
# Documentation
git checkout -b docs/improve-readme
# Refactoring
git checkout -b refactor/simplify-api-calls
4. Make Your Changes
Best Practices:
  • Make focused, atomic commits
  • Write clear commit messages
  • Test your changes
  • Update documentation
  • Follow code style
Commit Message Format:
type(scope): brief description
- Detailed explanation if needed
- Reference issues with #123
Fixes #123

Types: feat, fix, docs, style, refactor, test, chore
Example:
git commit -m "feat(onboarding): add symbolic ritual section- Added 5 symbolic onboarding rituals- Included templates and examples- Updated table of contentsCloses #42"
5. Push and Create Pull Request
Push Your Branch:
git push origin feature/your-feature-name
Create PR on GitHub:
  • Use clear, descriptive title
  • Fill out PR template completely
  • Link related issues
  • Request review from relevant people
  • Mark as draft if not ready
PR Template:
## Description[What does this PR do?]## Related Issues
Closes #123
Related to #456## Type of Change-[ ] Bug fix
-[ ] New feature
-[ ] Documentation
-[ ] Refactoring
-[ ] Other: ___## Testing-[ ] I have tested these changes
-[ ] Tests pass locally
-[ ] I added new tests (if applicable)
## Documentation-[ ] I updated relevant documentation
-[ ] I added code comments
-[ ] I updated the CHANGELOG (if applicable)
## Checklist-[ ] My code follows the style guidelines
-[ ] I have performed a self-review
-[ ] I have commented complex code
-[ ] My changes generate no new warnings
-[ ] I have checked for accessibility
-[ ] I have updated dependencies (if needed)
## Screenshots (if applicable)[Add screenshots here]## Additional Notes[Anything reviewers should know]
6. Respond to Feedback
During Review:
  • Respond to all comments
  • Make requested changes
  • Ask questions if unclear
  • Push additional commits
  • Re-request review when ready
Be Open:
  • Feedback is a gift
  • Learn from suggestions
  • Don't take it personally
  • Iterate and improve
7. Merge!
After Approval:
  • Maintainer will merge
  • Delete your branch
  • Update local repository
  • Celebrate! 🎉
# Update your local main
git checkout main
git pull upstream main
# Delete merged branch
git branch -d feature/your-feature-name
git push origin --delete feature/your-feature-name
📁 Repository Structure
Understanding the Organization
all-uto/
├── all-uto/ # Main hub
├── e-uto/ # Primary info
├── technoheroism/ # Philosophy
├── communities/ # Community directory
├── CoCreators/ # CoCreators branch
├── cocreators-meganrim/ # Meganrim project
├── music/ # Music branch
├── fashion/ # Fashion branch
├── blueteam/ # GMSF framework
├── eco/ # Eco branch
├── tools-and-workflows/ # Tools guide
├── startups/ # Startup branch
├── ai-alignment/ # AI alignment
├── assets/ # Shared assets
└── members/ # Member directory

Where to Contribute
Documentation:
  • Main READMEs in each repo
  • /docs folders for detailed guides
  • Wiki (if enabled)
Code:
  • /src for source code
  • /scripts for automation
  • /examples for demonstrations
Assets:
  • /assets for images, logos, etc.
  • Cosmos.so galleries for portfolios
  • Google Drive for large files
Tests:
  • /tests or /__tests__
  • Follow existing patterns
🎨 Style Guidelines
Markdown Documentation
Formatting:
# H1 for main title (one per document)## H2 for major sections### H3 for subsections- Use `-` for unordered lists
1. Use numbers for ordered lists
**Bold** for emphasis
*Italic* for light emphasis
`Code` for inline code
\```language
Code blocks with language specified
\```
[Links](url) with descriptive text
![Images](url) with alt text
Zettelkasten Linking:
**Upstream:**-`[[parent-concept]]`**Related:**-`[[related-concept-1]]`-`[[related-concept-2]]`**Downstream:**-`[[child-concept]]`
Best Practices:
  • Use sentence case for headers
  • Keep lines under 120 characters
  • One sentence per line (for easier diffs)
  • Use relative links when possible
  • Include table of contents for long docs
Code Style
JavaScript/TypeScript:
// Use descriptive variable namesconstuserProfile=getUserProfile(userId);// Functions do one thing wellfunctioncalculateTotalPrice(items){returnitems.reduce((sum,item)=>sum+item.price,0);}// Comment complex logic// Calculate phi-based interval using Golden Ratioconstinterval=baseTime*((1+Math.sqrt(5))/2);
Python:
# Follow PEP 8# Use descriptive namesdefcalculate_drift_velocity(current_drift, previous_drift, time_delta):
"""Calculate rate of ontological drift. Args: current_drift: Current drift measurement previous_drift: Previous drift measurement time_delta: Time elapsed between measurements Returns: Drift velocity in units per second """return (current_drift-previous_drift) /time_delta
General Principles:
  • Clarity over cleverness
  • Self-documenting code
  • Comments explain "why" not "what"
  • Consistent formatting
  • DRY (Don't Repeat Yourself)
Naming Conventions
Files:
  • kebab-case-for-files.md
  • PascalCaseForComponents.jsx
  • snake_case_for_python.py
Branches:
  • feature/add-new-capability
  • fix/resolve-bug-description
  • docs/improve-documentation
Variables:
  • camelCase for JavaScript
  • snake_case for Python
  • UPPERCASE_FOR_CONSTANTS
🧪 Testing Guidelines
Documentation Testing
Before Submitting:
  •  Read through entire document
  •  Check all links work
  •  Verify code examples
  •  Test instructions step-by-step
  •  Check spelling and grammar
  •  Ensure proper formatting
Code Testing
Before Submitting:
  •  All existing tests pass
  •  New tests for new features
  •  Edge cases covered
  •  No console errors or warnings
  •  Performance acceptable
  •  Accessibility checked
Writing Tests:
// Example test structuredescribe('TruthAnchoringSystem',()=>{test('should return "I don\'t know" for low confidence',()=>{constsystem=newTruthAnchoringSystem();constresult=system.assessClaim('uncertain claim',0.60);expect(result).toContain('I don\'t have sufficient information');});test('should assert directly for high confidence',()=>{constsystem=newTruthAnchoringSystem();constresult=system.assessClaim('certain claim',0.98);expect(result).toBe('certain claim');});});
User Testing
Helpful Feedback:
  • What you tried to do
  • What actually happened
  • What you expected to happen
  • Steps to reproduce
  • Screenshots/videos
  • Environment details
🏷️ Issue and PR Labels
Priority Labels
  • priority: critical - Urgent, blocks other work
  • priority: high - Important, address soon
  • priority: medium - Normal priority
  • priority: low - Nice to have
Type Labels
  • type: bug - Something isn't working
  • type: feature - New functionality
  • type: enhancement - Improve existing feature
  • type: documentation - Documentation improvements
  • type: question - Further information requested
Difficulty Labels
  • good first issue - Perfect for newcomers
  • beginner friendly - Requires basic skills
  • intermediate - Requires moderate experience
  • advanced - Requires deep expertise
Status Labels
  • status: needs triage - Needs review by maintainers
  • status: blocked - Can't proceed (explain why)
  • status: in progress - Someone is working on it
  • status: needs review - Ready for review
  • status: needs testing - Ready for testing
Community Labels
  • help wanted - Looking for contributors
  • discussion - Open for community input
  • collaboration - Great for pairing/teaming
  • mentorship available - Mentor will guide you
🎯 Contribution Workflow Examples
Example 1: Fix Documentation Typo
# 1. Find the typo, note location# 2. Create branch
git checkout -b docs/fix-typo-in-readme
# 3. Fix the typo# 4. Commit
git add README.md
git commit -m "docs: fix typo in installation section"# 5. Push and create PR
git push origin docs/fix-typo-in-readme
# Create PR on GitHub with simple description# 6. Done! Merges quickly
Time: 5-10 minutes
Example 2: Add New Feature
# 1. Create issue describing feature# 2. Wait for approval/discussion# 3. Create branch
git checkout -b feature/add-ritual-timer
# 4. Implement feature# - Write code# - Add tests# - Update docs# - Test thoroughly# 5. Commit incrementally
git add src/RitualTimer.js
git commit -m "feat: add basic ritual timer component"
git add src/RitualTimer.test.js
git commit -m "test: add tests for ritual timer"
git add docs/tools-guide.md
git commit -m "docs: document ritual timer usage"# 6. Push and create PR
git push origin feature/add-ritual-timer
# Create detailed PR with screenshots# 7. Address review feedback# 8. Merge when approved
Time: Few hours to few days depending on complexity
Example 3: Improve Existing Content
# 1. Identify improvement area# 2. Create issue or discussion# 3. Gather feedback on approach# 4. Create branch
git checkout -b docs/enhance-onboarding-guide
# 5. Make improvements# - Add examples# - Improve clarity# - Add visuals# 6. Commit with clear messages
git commit -m "docs(onboarding): add example journeys section- Added 4 detailed example onboarding journeys- Included different archetype paths- Enhanced with real community storiesCloses #87"# 7. Push and create PR# 8. Iterate based on feedback# 9. Merge when ready
Time: Several hours to days
🌟 Recognition & Credit
How We Acknowledge Contributors
In Repository:
  • Contributors file (auto-generated)
  • Credits in documentation
  • Shout-outs in changelogs
In Community:
  • Discord announcements
  • X/Twitter mentions
  • Round Table recognition
  • Community showcases
Roles & Badges:
  • Discord roles based on contributions
  • GitHub contributor status
  • Community elder recognition
Contribution Tiers
🌱 Seed (First Contribution):
  • Made first PR or significant contribution
  • Welcomed in Discord announcement
  • Added to contributors list
🌿 Sprout (Active Contributor):
  • 5+ merged PRs or equivalent contributions
  • Regular community participation
  • Helping newcomers
🌳 Root (Core Contributor):
  • 20+ merged PRs or major contributions
  • Deep expertise in area
  • Mentoring others
  • May get write access
🌺 Bloom (Maintainer):
  • Significant ongoing contributions
  • Stewardship of community/code
  • Strategic thinking
  • Full commit access
📅 Contribution Rhythms
Weekly Contribution Patterns
Monday (#UTOideasMonday):
  • Share new ideas in discussions
  • Propose features or improvements
  • Open issues for feedback
Tuesday-Wednesday:
  • Work on contributions
  • Respond to reviews
  • Help others
Thursday (#TechnoHeroThursday):
  • Share progress updates
  • Demo completed work
  • Showcase contributions
Friday:
  • Wrap up PRs
  • Update documentation
  • Plan next week
Weekend:
  • Deep work on projects
  • Learning and exploration
  • Or rest! Balance is important
Monthly Cycles
Week 1: Planning and issue triage
Week 2: Active development
Week 3: Review and feedback
Week 4: Polish and merge
🆘 Getting Help
Where to Ask Questions
Discord Channels:
  • #multichat-welcomes-all - General questions
  • #tree/uto - Onboarding help
  • #infra-migration - Technical setup
  • Branch-specific channels - Topic questions
GitHub:
  • Issue comments - Specific to that issue
  • Discussions - General topics
  • PR reviews - Code-specific
Direct Messages:
  • DM maintainers for private questions
  • Tag people in Discord for specific help
  • Email for sensitive matters
Common Questions
Q: How do I get started?
Read the Onboarding Guide, join Discord, pick a good first issue.
Q: My PR hasn't been reviewed yet.
Be patient! Maintainers are volunteers. Politely ping after 7 days if no response.
Q: I disagree with feedback.
Explain your reasoning respectfully. Use dialectical process. Seek synthesis.
Q: Can I work on multiple issues?
Sure, but finish what you start. Don't over-commit.
Q: I made a mistake.
It's okay! We all do. Fix it, learn from it, move forward.
Q: I don't have time anymore.
Life happens! Let us know. We can reassign or pause. No judgment.
🔗 Zettelkasten Links
Upstream:
  • [[effective-utopia-vision]] - Overall mission
  • [[community-network]] - Network structure
Related:
  • [[onboarding-guide]] - For new members
  • [[tools-configuration-guide]] - Development setup
  • [[code-of-conduct]] - Community standards
  • [[channel-directory]] - Where to communicate
Downstream:
  • [[issue-templates]] - Creating good issues
  • [[pr-templates]] - Creating good PRs
  • [[style-guides]] - Coding standards
  • [[testing-guidelines]] - Quality assurance
📜 License
By contributing to ê/uto, you agree that your contributions will be licensed under the Creative Commons Attribution-ShareAlike (CC BY-SA 4.0) license unless otherwise specified.
See LICENSE for details.
🙏 Thank You
Every contribution, no matter how small, makes a difference. You're helping build ethical, abundant futures for all.
"If a civilization doesn't go extinct, it achieves everything it dreams."
Let's build that civilization together.
Welcome to the forge of the future.
🌱 Start small → 🌿 Grow steadily → 🌳 Root deeply → 🌺 Bloom fully
Part of the ê/uto Network
🌍 #technoheroism · #UTOideasMonday · #TechnoHeroThursday
About
No description, website, or topics provided.
Resources
Readme
Activity
Custom properties
Stars
1 star
Watchers
0 watching
Forks
0 forks
Report repository
Releases
Packages
Contributors

, 'i');
if (__m === '*' || __re.test(location.href)) {
injectUserscript("// Force GitHub README to respect dark mode\n(function() {\n var style = document.createElement('style');\n style.textContent = '\n .markdown-body {\n color-scheme: dark light;\n }\n .markdown-body pre { background: #161b22 !important; }\n .markdown-body code { background: rgba(110, 118, 129, 0.4) !important; }\n .markdown-body table th, .markdown-body table td { border-color: #30363d !important; }\n .markdown-body img { background: #0d1117; }\n .markdown-body blockquote { border-left-color: #8b949e; }\n .markdown-body hr { border-color: #30363d; }\n ';\n document.head.appendChild(style);\n})();", "GitHub Dark Mode README Fix");
}
} catch(__e) { console.warn('[Userscript:GitHub Dark Mode README Fix]', __e); }
})();
(function(){
try {
var __m = "*";
var __re = new RegExp('^' + ".*" + '

Skip to content
BranchesTags
Latest commit
History
2 Commits
Folders and files
NameName
Last commit message
Last commit date
README.md
README.md
Repository files navigation
contributing
Contributing to ê/uto
Welcome, TechnoHero! This guide will help you contribute effectively to the Effective Utopia network.
"No rules here, for any rule is unfreedom. We give choices."
🌍 Quick Start
First-Time Contributors
  1. Read the Onboarding Guide - Understand the network
  2. Join Discord - Connect with the community
  3. Browse Issues - Find something to work on
  4. Ask Questions - We're here to help!
Experienced Contributors
  1. Check open issues and discussions
  2. Review project boards for priorities
  3. Fork → Branch → Commit → PR (details below)
  4. Engage in code review and iteration
🎯 Our Mission
"To prevent dystopias and build utopias, increase the probability of the ultimate effective utopia — p(e/uto) — by at least 1% each week."
Every contribution, no matter how small, moves us toward this goal.
🤝 Ways to Contribute
1. 📝 Documentation
Always Valuable:
  • Fix typos and grammar
  • Improve clarity
  • Add examples
  • Translate content
  • Create tutorials
How to Start:
  • Look for issues labeled documentation
  • Read through existing docs and spot gaps
  • Propose improvements in discussions
2. 💻 Code
What We Need:
  • Bug fixes
  • New features
  • Performance improvements
  • Test coverage
  • Tool integrations
How to Start:
  • Check issues labeled good first issue
  • Review the Tools Guide
  • Set up your development environment
  • Pick a manageable task
3. 🎨 Design & Creative
What We Need:
  • Visual assets (logos, banners, icons)
  • Brand guidelines
  • UI/UX improvements
  • Video content
  • Music and audio
How to Start:
  • Browse asset galleries
  • Check issues labeled design or creative
  • Share work in Discord #creative-lab
  • Upload to Cosmos.so with proper licensing
4. 🧪 Testing & Feedback
What We Need:
  • Bug reports
  • Feature testing
  • Usability feedback
  • Documentation review
How to Start:
  • Use the tools and report issues
  • Test new features in beta
  • Review PRs from a user perspective
  • Share feedback in discussions
5. 🌱 Community Support
What We Need:
  • Answering questions in Discord
  • Onboarding new members
  • Moderating discussions
  • Organizing events
How to Start:
  • Hang out in Discord channels
  • Welcome newcomers in #multichat-welcomes-all
  • Help in #tree/uto
  • Facilitate discussions
6. 🧠 Research & Ideas
What We Need:
  • Framework development
  • Ethical analysis
  • Technical research
  • Strategic thinking
How to Start:
  • Engage in #save-worlds-antidys/prouto
  • Study the GMSF framework
  • Participate in philosophical discussions
  • Write essays or proposals
📋 Contribution Guidelines
Code of Conduct
Core Principles:
  1. Be Kind - Compassion is couture
  2. Be Respectful - Everyone's contribution matters
  3. Be Constructive - Offer solutions, not just criticism
  4. Be Inclusive - Welcome all backgrounds and skill levels
  5. Be Honest - Truth as primary function (LOGOS)
We Don't Tolerate:
  • Harassment or discrimination
  • Spam or self-promotion without context
  • Destructive criticism
  • Gatekeeping or elitism
  • Bad faith arguments
Conflict Resolution:
Communication Guidelines
Be Clear:
  • Use descriptive titles
  • Provide context
  • Link to relevant resources
  • Use proper formatting
Be Concise:
  • Get to the point
  • Use bullet points
  • Break up long text
  • TL;DR for long posts
Be Responsive:
  • Reply to feedback
  • Update on progress
  • Close resolved issues
  • Thank contributors
Attribution
Always:
  • Credit original authors
  • Link to sources
  • Use proper licenses
  • Acknowledge collaborators
Never:
  • Plagiarize
  • Claim others' work
  • Violate copyright
  • Misrepresent authorship
🔧 Technical Contribution Process
1. Set Up Development Environment
Prerequisites:
# Git
git --version
# Node.js (if applicable)
node --version
npm --version
# Your preferred editor
code --version # VSCode
Clone the Repository:
# Fork first on GitHub, then:
git clone https://github.com/YOUR-USERNAME/REPO-NAME
cd REPO-NAME
# Add upstream remote
git remote add upstream https://github.com/all-uto/REPO-NAME
Install Dependencies (if applicable):
npm install
# or
pip install -r requirements.txt
# or
bundle install
2. Find or Create an Issue
Before Starting Work:
  1. Check if an issue exists
  2. If not, create one describing what you want to do
  3. Wait for feedback/approval (for big changes)
  4. Assign yourself to the issue
Good Issue Template:
## Description[Clear description of the problem or enhancement]## Proposed Solution[What you plan to do]## Impact[How this increases p(e/uto)]## Alternatives Considered[Other approaches you thought about]## Additional Context[Screenshots, links, examples]
3. Create a Branch
Naming Convention:
# Features
git checkout -b feature/add-user-authentication
# Bugs
git checkout -b fix/broken-image-upload
# Documentation
git checkout -b docs/improve-readme
# Refactoring
git checkout -b refactor/simplify-api-calls
4. Make Your Changes
Best Practices:
  • Make focused, atomic commits
  • Write clear commit messages
  • Test your changes
  • Update documentation
  • Follow code style
Commit Message Format:
type(scope): brief description
- Detailed explanation if needed
- Reference issues with #123
Fixes #123

Types: feat, fix, docs, style, refactor, test, chore
Example:
git commit -m "feat(onboarding): add symbolic ritual section- Added 5 symbolic onboarding rituals- Included templates and examples- Updated table of contentsCloses #42"
5. Push and Create Pull Request
Push Your Branch:
git push origin feature/your-feature-name
Create PR on GitHub:
  • Use clear, descriptive title
  • Fill out PR template completely
  • Link related issues
  • Request review from relevant people
  • Mark as draft if not ready
PR Template:
## Description[What does this PR do?]## Related Issues
Closes #123
Related to #456## Type of Change-[ ] Bug fix
-[ ] New feature
-[ ] Documentation
-[ ] Refactoring
-[ ] Other: ___## Testing-[ ] I have tested these changes
-[ ] Tests pass locally
-[ ] I added new tests (if applicable)
## Documentation-[ ] I updated relevant documentation
-[ ] I added code comments
-[ ] I updated the CHANGELOG (if applicable)
## Checklist-[ ] My code follows the style guidelines
-[ ] I have performed a self-review
-[ ] I have commented complex code
-[ ] My changes generate no new warnings
-[ ] I have checked for accessibility
-[ ] I have updated dependencies (if needed)
## Screenshots (if applicable)[Add screenshots here]## Additional Notes[Anything reviewers should know]
6. Respond to Feedback
During Review:
  • Respond to all comments
  • Make requested changes
  • Ask questions if unclear
  • Push additional commits
  • Re-request review when ready
Be Open:
  • Feedback is a gift
  • Learn from suggestions
  • Don't take it personally
  • Iterate and improve
7. Merge!
After Approval:
  • Maintainer will merge
  • Delete your branch
  • Update local repository
  • Celebrate! 🎉
# Update your local main
git checkout main
git pull upstream main
# Delete merged branch
git branch -d feature/your-feature-name
git push origin --delete feature/your-feature-name
📁 Repository Structure
Understanding the Organization
all-uto/
├── all-uto/ # Main hub
├── e-uto/ # Primary info
├── technoheroism/ # Philosophy
├── communities/ # Community directory
├── CoCreators/ # CoCreators branch
├── cocreators-meganrim/ # Meganrim project
├── music/ # Music branch
├── fashion/ # Fashion branch
├── blueteam/ # GMSF framework
├── eco/ # Eco branch
├── tools-and-workflows/ # Tools guide
├── startups/ # Startup branch
├── ai-alignment/ # AI alignment
├── assets/ # Shared assets
└── members/ # Member directory

Where to Contribute
Documentation:
  • Main READMEs in each repo
  • /docs folders for detailed guides
  • Wiki (if enabled)
Code:
  • /src for source code
  • /scripts for automation
  • /examples for demonstrations
Assets:
  • /assets for images, logos, etc.
  • Cosmos.so galleries for portfolios
  • Google Drive for large files
Tests:
  • /tests or /__tests__
  • Follow existing patterns
🎨 Style Guidelines
Markdown Documentation
Formatting:
# H1 for main title (one per document)## H2 for major sections### H3 for subsections- Use `-` for unordered lists
1. Use numbers for ordered lists
**Bold** for emphasis
*Italic* for light emphasis
`Code` for inline code
\```language
Code blocks with language specified
\```
[Links](url) with descriptive text
![Images](url) with alt text
Zettelkasten Linking:
**Upstream:**-`[[parent-concept]]`**Related:**-`[[related-concept-1]]`-`[[related-concept-2]]`**Downstream:**-`[[child-concept]]`
Best Practices:
  • Use sentence case for headers
  • Keep lines under 120 characters
  • One sentence per line (for easier diffs)
  • Use relative links when possible
  • Include table of contents for long docs
Code Style
JavaScript/TypeScript:
// Use descriptive variable namesconstuserProfile=getUserProfile(userId);// Functions do one thing wellfunctioncalculateTotalPrice(items){returnitems.reduce((sum,item)=>sum+item.price,0);}// Comment complex logic// Calculate phi-based interval using Golden Ratioconstinterval=baseTime*((1+Math.sqrt(5))/2);
Python:
# Follow PEP 8# Use descriptive namesdefcalculate_drift_velocity(current_drift, previous_drift, time_delta):
"""Calculate rate of ontological drift. Args: current_drift: Current drift measurement previous_drift: Previous drift measurement time_delta: Time elapsed between measurements Returns: Drift velocity in units per second """return (current_drift-previous_drift) /time_delta
General Principles:
  • Clarity over cleverness
  • Self-documenting code
  • Comments explain "why" not "what"
  • Consistent formatting
  • DRY (Don't Repeat Yourself)
Naming Conventions
Files:
  • kebab-case-for-files.md
  • PascalCaseForComponents.jsx
  • snake_case_for_python.py
Branches:
  • feature/add-new-capability
  • fix/resolve-bug-description
  • docs/improve-documentation
Variables:
  • camelCase for JavaScript
  • snake_case for Python
  • UPPERCASE_FOR_CONSTANTS
🧪 Testing Guidelines
Documentation Testing
Before Submitting:
  •  Read through entire document
  •  Check all links work
  •  Verify code examples
  •  Test instructions step-by-step
  •  Check spelling and grammar
  •  Ensure proper formatting
Code Testing
Before Submitting:
  •  All existing tests pass
  •  New tests for new features
  •  Edge cases covered
  •  No console errors or warnings
  •  Performance acceptable
  •  Accessibility checked
Writing Tests:
// Example test structuredescribe('TruthAnchoringSystem',()=>{test('should return "I don\'t know" for low confidence',()=>{constsystem=newTruthAnchoringSystem();constresult=system.assessClaim('uncertain claim',0.60);expect(result).toContain('I don\'t have sufficient information');});test('should assert directly for high confidence',()=>{constsystem=newTruthAnchoringSystem();constresult=system.assessClaim('certain claim',0.98);expect(result).toBe('certain claim');});});
User Testing
Helpful Feedback:
  • What you tried to do
  • What actually happened
  • What you expected to happen
  • Steps to reproduce
  • Screenshots/videos
  • Environment details
🏷️ Issue and PR Labels
Priority Labels
  • priority: critical - Urgent, blocks other work
  • priority: high - Important, address soon
  • priority: medium - Normal priority
  • priority: low - Nice to have
Type Labels
  • type: bug - Something isn't working
  • type: feature - New functionality
  • type: enhancement - Improve existing feature
  • type: documentation - Documentation improvements
  • type: question - Further information requested
Difficulty Labels
  • good first issue - Perfect for newcomers
  • beginner friendly - Requires basic skills
  • intermediate - Requires moderate experience
  • advanced - Requires deep expertise
Status Labels
  • status: needs triage - Needs review by maintainers
  • status: blocked - Can't proceed (explain why)
  • status: in progress - Someone is working on it
  • status: needs review - Ready for review
  • status: needs testing - Ready for testing
Community Labels
  • help wanted - Looking for contributors
  • discussion - Open for community input
  • collaboration - Great for pairing/teaming
  • mentorship available - Mentor will guide you
🎯 Contribution Workflow Examples
Example 1: Fix Documentation Typo
# 1. Find the typo, note location# 2. Create branch
git checkout -b docs/fix-typo-in-readme
# 3. Fix the typo# 4. Commit
git add README.md
git commit -m "docs: fix typo in installation section"# 5. Push and create PR
git push origin docs/fix-typo-in-readme
# Create PR on GitHub with simple description# 6. Done! Merges quickly
Time: 5-10 minutes
Example 2: Add New Feature
# 1. Create issue describing feature# 2. Wait for approval/discussion# 3. Create branch
git checkout -b feature/add-ritual-timer
# 4. Implement feature# - Write code# - Add tests# - Update docs# - Test thoroughly# 5. Commit incrementally
git add src/RitualTimer.js
git commit -m "feat: add basic ritual timer component"
git add src/RitualTimer.test.js
git commit -m "test: add tests for ritual timer"
git add docs/tools-guide.md
git commit -m "docs: document ritual timer usage"# 6. Push and create PR
git push origin feature/add-ritual-timer
# Create detailed PR with screenshots# 7. Address review feedback# 8. Merge when approved
Time: Few hours to few days depending on complexity
Example 3: Improve Existing Content
# 1. Identify improvement area# 2. Create issue or discussion# 3. Gather feedback on approach# 4. Create branch
git checkout -b docs/enhance-onboarding-guide
# 5. Make improvements# - Add examples# - Improve clarity# - Add visuals# 6. Commit with clear messages
git commit -m "docs(onboarding): add example journeys section- Added 4 detailed example onboarding journeys- Included different archetype paths- Enhanced with real community storiesCloses #87"# 7. Push and create PR# 8. Iterate based on feedback# 9. Merge when ready
Time: Several hours to days
🌟 Recognition & Credit
How We Acknowledge Contributors
In Repository:
  • Contributors file (auto-generated)
  • Credits in documentation
  • Shout-outs in changelogs
In Community:
  • Discord announcements
  • X/Twitter mentions
  • Round Table recognition
  • Community showcases
Roles & Badges:
  • Discord roles based on contributions
  • GitHub contributor status
  • Community elder recognition
Contribution Tiers
🌱 Seed (First Contribution):
  • Made first PR or significant contribution
  • Welcomed in Discord announcement
  • Added to contributors list
🌿 Sprout (Active Contributor):
  • 5+ merged PRs or equivalent contributions
  • Regular community participation
  • Helping newcomers
🌳 Root (Core Contributor):
  • 20+ merged PRs or major contributions
  • Deep expertise in area
  • Mentoring others
  • May get write access
🌺 Bloom (Maintainer):
  • Significant ongoing contributions
  • Stewardship of community/code
  • Strategic thinking
  • Full commit access
📅 Contribution Rhythms
Weekly Contribution Patterns
Monday (#UTOideasMonday):
  • Share new ideas in discussions
  • Propose features or improvements
  • Open issues for feedback
Tuesday-Wednesday:
  • Work on contributions
  • Respond to reviews
  • Help others
Thursday (#TechnoHeroThursday):
  • Share progress updates
  • Demo completed work
  • Showcase contributions
Friday:
  • Wrap up PRs
  • Update documentation
  • Plan next week
Weekend:
  • Deep work on projects
  • Learning and exploration
  • Or rest! Balance is important
Monthly Cycles
Week 1: Planning and issue triage
Week 2: Active development
Week 3: Review and feedback
Week 4: Polish and merge
🆘 Getting Help
Where to Ask Questions
Discord Channels:
  • #multichat-welcomes-all - General questions
  • #tree/uto - Onboarding help
  • #infra-migration - Technical setup
  • Branch-specific channels - Topic questions
GitHub:
  • Issue comments - Specific to that issue
  • Discussions - General topics
  • PR reviews - Code-specific
Direct Messages:
  • DM maintainers for private questions
  • Tag people in Discord for specific help
  • Email for sensitive matters
Common Questions
Q: How do I get started?
Read the Onboarding Guide, join Discord, pick a good first issue.
Q: My PR hasn't been reviewed yet.
Be patient! Maintainers are volunteers. Politely ping after 7 days if no response.
Q: I disagree with feedback.
Explain your reasoning respectfully. Use dialectical process. Seek synthesis.
Q: Can I work on multiple issues?
Sure, but finish what you start. Don't over-commit.
Q: I made a mistake.
It's okay! We all do. Fix it, learn from it, move forward.
Q: I don't have time anymore.
Life happens! Let us know. We can reassign or pause. No judgment.
🔗 Zettelkasten Links
Upstream:
  • [[effective-utopia-vision]] - Overall mission
  • [[community-network]] - Network structure
Related:
  • [[onboarding-guide]] - For new members
  • [[tools-configuration-guide]] - Development setup
  • [[code-of-conduct]] - Community standards
  • [[channel-directory]] - Where to communicate
Downstream:
  • [[issue-templates]] - Creating good issues
  • [[pr-templates]] - Creating good PRs
  • [[style-guides]] - Coding standards
  • [[testing-guidelines]] - Quality assurance
📜 License
By contributing to ê/uto, you agree that your contributions will be licensed under the Creative Commons Attribution-ShareAlike (CC BY-SA 4.0) license unless otherwise specified.
See LICENSE for details.
🙏 Thank You
Every contribution, no matter how small, makes a difference. You're helping build ethical, abundant futures for all.
"If a civilization doesn't go extinct, it achieves everything it dreams."
Let's build that civilization together.
Welcome to the forge of the future.
🌱 Start small → 🌿 Grow steadily → 🌳 Root deeply → 🌺 Bloom fully
Part of the ê/uto Network
🌍 #technoheroism · #UTOideasMonday · #TechnoHeroThursday
About
No description, website, or topics provided.
Resources
Readme
Activity
Custom properties
Stars
1 star
Watchers
0 watching
Forks
0 forks
Report repository
Releases
Packages
Contributors

, 'i');
if (__m === '*' || __re.test(location.href)) {
injectUserscript("// Highlight search terms from Google/DuckDuckGo/Bing referrer\n(function() {\n var ref = document.referrer;\n var terms = [];\n \n if (ref.includes('google.com') || ref.includes('duckduckgo.com') || ref.includes('bing.com')) {\n var url = new URL(ref);\n var q = url.searchParams.get('q') || url.searchParams.get('p');\n if (q) {\n terms = q.split(/\\s+/).filter(function(t) { return t.length > 2; });\n }\n }\n \n if (terms.length === 0) return;\n \n var style = document.createElement('style');\n style.textContent = '.userscript-highlight { background: #fbbf24; color: #1a1a2e; padding: 1px 3px; border-radius: 2px; }';\n document.head.appendChild(style);\n \n function highlight(node) {\n if (node.nodeType === 3) { // text node\n var text = node.textContent;\n var found = false;\n terms.forEach(function(term) {\n var regex = new RegExp('(' + term.replace(/[.*+?^${}()|[\\]\\\\]/g, '\\\\') + ')', 'gi');\n if (regex.test(text)) {\n found = true;\n var frag = document.createDocumentFragment();\n var parts = text.split(regex);\n parts.forEach(function(part, i) {\n if (i % 2 === 0) {\n frag.appendChild(document.createTextNode(part));\n } else {\n var span = document.createElement('span');\n span.className = 'userscript-highlight';\n span.textContent = part;\n frag.appendChild(span);\n }\n });\n node.parentNode.replaceChild(frag, node);\n }\n });\n } else if (node.nodeType === 1 && node.childNodes) { // element\n var skipTags = ['SCRIPT', 'STYLE', 'NOSCRIPT', 'TEXTAREA', 'INPUT', 'SELECT'];\n if (!skipTags.includes(node.tagName)) {\n Array.from(node.childNodes).forEach(highlight);\n }\n }\n }\n \n highlight(document.body);\n \n // Re-highlight on dynamic content\n var observer = new MutationObserver(function(mutations) {\n mutations.forEach(function(m) {\n m.addedNodes.forEach(function(node) {\n if (node.nodeType === 1 || node.nodeType === 3) highlight(node);\n });\n });\n });\n observer.observe(document.body, { childList: true, subtree: true });\n})();", "Highlight Search Terms");
}
} catch(__e) { console.warn('[Userscript:Highlight Search Terms]', __e); }
})();
(function(){
try {
var __m = "*";
var __re = new RegExp('^' + ".*" + '

Skip to content
BranchesTags
Latest commit
History
2 Commits
Folders and files
NameName
Last commit message
Last commit date
README.md
README.md
Repository files navigation
contributing
Contributing to ê/uto
Welcome, TechnoHero! This guide will help you contribute effectively to the Effective Utopia network.
"No rules here, for any rule is unfreedom. We give choices."
🌍 Quick Start
First-Time Contributors
  1. Read the Onboarding Guide - Understand the network
  2. Join Discord - Connect with the community
  3. Browse Issues - Find something to work on
  4. Ask Questions - We're here to help!
Experienced Contributors
  1. Check open issues and discussions
  2. Review project boards for priorities
  3. Fork → Branch → Commit → PR (details below)
  4. Engage in code review and iteration
🎯 Our Mission
"To prevent dystopias and build utopias, increase the probability of the ultimate effective utopia — p(e/uto) — by at least 1% each week."
Every contribution, no matter how small, moves us toward this goal.
🤝 Ways to Contribute
1. 📝 Documentation
Always Valuable:
  • Fix typos and grammar
  • Improve clarity
  • Add examples
  • Translate content
  • Create tutorials
How to Start:
  • Look for issues labeled documentation
  • Read through existing docs and spot gaps
  • Propose improvements in discussions
2. 💻 Code
What We Need:
  • Bug fixes
  • New features
  • Performance improvements
  • Test coverage
  • Tool integrations
How to Start:
  • Check issues labeled good first issue
  • Review the Tools Guide
  • Set up your development environment
  • Pick a manageable task
3. 🎨 Design & Creative
What We Need:
  • Visual assets (logos, banners, icons)
  • Brand guidelines
  • UI/UX improvements
  • Video content
  • Music and audio
How to Start:
  • Browse asset galleries
  • Check issues labeled design or creative
  • Share work in Discord #creative-lab
  • Upload to Cosmos.so with proper licensing
4. 🧪 Testing & Feedback
What We Need:
  • Bug reports
  • Feature testing
  • Usability feedback
  • Documentation review
How to Start:
  • Use the tools and report issues
  • Test new features in beta
  • Review PRs from a user perspective
  • Share feedback in discussions
5. 🌱 Community Support
What We Need:
  • Answering questions in Discord
  • Onboarding new members
  • Moderating discussions
  • Organizing events
How to Start:
  • Hang out in Discord channels
  • Welcome newcomers in #multichat-welcomes-all
  • Help in #tree/uto
  • Facilitate discussions
6. 🧠 Research & Ideas
What We Need:
  • Framework development
  • Ethical analysis
  • Technical research
  • Strategic thinking
How to Start:
  • Engage in #save-worlds-antidys/prouto
  • Study the GMSF framework
  • Participate in philosophical discussions
  • Write essays or proposals
📋 Contribution Guidelines
Code of Conduct
Core Principles:
  1. Be Kind - Compassion is couture
  2. Be Respectful - Everyone's contribution matters
  3. Be Constructive - Offer solutions, not just criticism
  4. Be Inclusive - Welcome all backgrounds and skill levels
  5. Be Honest - Truth as primary function (LOGOS)
We Don't Tolerate:
  • Harassment or discrimination
  • Spam or self-promotion without context
  • Destructive criticism
  • Gatekeeping or elitism
  • Bad faith arguments
Conflict Resolution:
Communication Guidelines
Be Clear:
  • Use descriptive titles
  • Provide context
  • Link to relevant resources
  • Use proper formatting
Be Concise:
  • Get to the point
  • Use bullet points
  • Break up long text
  • TL;DR for long posts
Be Responsive:
  • Reply to feedback
  • Update on progress
  • Close resolved issues
  • Thank contributors
Attribution
Always:
  • Credit original authors
  • Link to sources
  • Use proper licenses
  • Acknowledge collaborators
Never:
  • Plagiarize
  • Claim others' work
  • Violate copyright
  • Misrepresent authorship
🔧 Technical Contribution Process
1. Set Up Development Environment
Prerequisites:
# Git
git --version
# Node.js (if applicable)
node --version
npm --version
# Your preferred editor
code --version # VSCode
Clone the Repository:
# Fork first on GitHub, then:
git clone https://github.com/YOUR-USERNAME/REPO-NAME
cd REPO-NAME
# Add upstream remote
git remote add upstream https://github.com/all-uto/REPO-NAME
Install Dependencies (if applicable):
npm install
# or
pip install -r requirements.txt
# or
bundle install
2. Find or Create an Issue
Before Starting Work:
  1. Check if an issue exists
  2. If not, create one describing what you want to do
  3. Wait for feedback/approval (for big changes)
  4. Assign yourself to the issue
Good Issue Template:
## Description[Clear description of the problem or enhancement]## Proposed Solution[What you plan to do]## Impact[How this increases p(e/uto)]## Alternatives Considered[Other approaches you thought about]## Additional Context[Screenshots, links, examples]
3. Create a Branch
Naming Convention:
# Features
git checkout -b feature/add-user-authentication
# Bugs
git checkout -b fix/broken-image-upload
# Documentation
git checkout -b docs/improve-readme
# Refactoring
git checkout -b refactor/simplify-api-calls
4. Make Your Changes
Best Practices:
  • Make focused, atomic commits
  • Write clear commit messages
  • Test your changes
  • Update documentation
  • Follow code style
Commit Message Format:
type(scope): brief description
- Detailed explanation if needed
- Reference issues with #123
Fixes #123

Types: feat, fix, docs, style, refactor, test, chore
Example:
git commit -m "feat(onboarding): add symbolic ritual section- Added 5 symbolic onboarding rituals- Included templates and examples- Updated table of contentsCloses #42"
5. Push and Create Pull Request
Push Your Branch:
git push origin feature/your-feature-name
Create PR on GitHub:
  • Use clear, descriptive title
  • Fill out PR template completely
  • Link related issues
  • Request review from relevant people
  • Mark as draft if not ready
PR Template:
## Description[What does this PR do?]## Related Issues
Closes #123
Related to #456## Type of Change-[ ] Bug fix
-[ ] New feature
-[ ] Documentation
-[ ] Refactoring
-[ ] Other: ___## Testing-[ ] I have tested these changes
-[ ] Tests pass locally
-[ ] I added new tests (if applicable)
## Documentation-[ ] I updated relevant documentation
-[ ] I added code comments
-[ ] I updated the CHANGELOG (if applicable)
## Checklist-[ ] My code follows the style guidelines
-[ ] I have performed a self-review
-[ ] I have commented complex code
-[ ] My changes generate no new warnings
-[ ] I have checked for accessibility
-[ ] I have updated dependencies (if needed)
## Screenshots (if applicable)[Add screenshots here]## Additional Notes[Anything reviewers should know]
6. Respond to Feedback
During Review:
  • Respond to all comments
  • Make requested changes
  • Ask questions if unclear
  • Push additional commits
  • Re-request review when ready
Be Open:
  • Feedback is a gift
  • Learn from suggestions
  • Don't take it personally
  • Iterate and improve
7. Merge!
After Approval:
  • Maintainer will merge
  • Delete your branch
  • Update local repository
  • Celebrate! 🎉
# Update your local main
git checkout main
git pull upstream main
# Delete merged branch
git branch -d feature/your-feature-name
git push origin --delete feature/your-feature-name
📁 Repository Structure
Understanding the Organization
all-uto/
├── all-uto/ # Main hub
├── e-uto/ # Primary info
├── technoheroism/ # Philosophy
├── communities/ # Community directory
├── CoCreators/ # CoCreators branch
├── cocreators-meganrim/ # Meganrim project
├── music/ # Music branch
├── fashion/ # Fashion branch
├── blueteam/ # GMSF framework
├── eco/ # Eco branch
├── tools-and-workflows/ # Tools guide
├── startups/ # Startup branch
├── ai-alignment/ # AI alignment
├── assets/ # Shared assets
└── members/ # Member directory

Where to Contribute
Documentation:
  • Main READMEs in each repo
  • /docs folders for detailed guides
  • Wiki (if enabled)
Code:
  • /src for source code
  • /scripts for automation
  • /examples for demonstrations
Assets:
  • /assets for images, logos, etc.
  • Cosmos.so galleries for portfolios
  • Google Drive for large files
Tests:
  • /tests or /__tests__
  • Follow existing patterns
🎨 Style Guidelines
Markdown Documentation
Formatting:
# H1 for main title (one per document)## H2 for major sections### H3 for subsections- Use `-` for unordered lists
1. Use numbers for ordered lists
**Bold** for emphasis
*Italic* for light emphasis
`Code` for inline code
\```language
Code blocks with language specified
\```
[Links](url) with descriptive text
![Images](url) with alt text
Zettelkasten Linking:
**Upstream:**-`[[parent-concept]]`**Related:**-`[[related-concept-1]]`-`[[related-concept-2]]`**Downstream:**-`[[child-concept]]`
Best Practices:
  • Use sentence case for headers
  • Keep lines under 120 characters
  • One sentence per line (for easier diffs)
  • Use relative links when possible
  • Include table of contents for long docs
Code Style
JavaScript/TypeScript:
// Use descriptive variable namesconstuserProfile=getUserProfile(userId);// Functions do one thing wellfunctioncalculateTotalPrice(items){returnitems.reduce((sum,item)=>sum+item.price,0);}// Comment complex logic// Calculate phi-based interval using Golden Ratioconstinterval=baseTime*((1+Math.sqrt(5))/2);
Python:
# Follow PEP 8# Use descriptive namesdefcalculate_drift_velocity(current_drift, previous_drift, time_delta):
"""Calculate rate of ontological drift. Args: current_drift: Current drift measurement previous_drift: Previous drift measurement time_delta: Time elapsed between measurements Returns: Drift velocity in units per second """return (current_drift-previous_drift) /time_delta
General Principles:
  • Clarity over cleverness
  • Self-documenting code
  • Comments explain "why" not "what"
  • Consistent formatting
  • DRY (Don't Repeat Yourself)
Naming Conventions
Files:
  • kebab-case-for-files.md
  • PascalCaseForComponents.jsx
  • snake_case_for_python.py
Branches:
  • feature/add-new-capability
  • fix/resolve-bug-description
  • docs/improve-documentation
Variables:
  • camelCase for JavaScript
  • snake_case for Python
  • UPPERCASE_FOR_CONSTANTS
🧪 Testing Guidelines
Documentation Testing
Before Submitting:
  •  Read through entire document
  •  Check all links work
  •  Verify code examples
  •  Test instructions step-by-step
  •  Check spelling and grammar
  •  Ensure proper formatting
Code Testing
Before Submitting:
  •  All existing tests pass
  •  New tests for new features
  •  Edge cases covered
  •  No console errors or warnings
  •  Performance acceptable
  •  Accessibility checked
Writing Tests:
// Example test structuredescribe('TruthAnchoringSystem',()=>{test('should return "I don\'t know" for low confidence',()=>{constsystem=newTruthAnchoringSystem();constresult=system.assessClaim('uncertain claim',0.60);expect(result).toContain('I don\'t have sufficient information');});test('should assert directly for high confidence',()=>{constsystem=newTruthAnchoringSystem();constresult=system.assessClaim('certain claim',0.98);expect(result).toBe('certain claim');});});
User Testing
Helpful Feedback:
  • What you tried to do
  • What actually happened
  • What you expected to happen
  • Steps to reproduce
  • Screenshots/videos
  • Environment details
🏷️ Issue and PR Labels
Priority Labels
  • priority: critical - Urgent, blocks other work
  • priority: high - Important, address soon
  • priority: medium - Normal priority
  • priority: low - Nice to have
Type Labels
  • type: bug - Something isn't working
  • type: feature - New functionality
  • type: enhancement - Improve existing feature
  • type: documentation - Documentation improvements
  • type: question - Further information requested
Difficulty Labels
  • good first issue - Perfect for newcomers
  • beginner friendly - Requires basic skills
  • intermediate - Requires moderate experience
  • advanced - Requires deep expertise
Status Labels
  • status: needs triage - Needs review by maintainers
  • status: blocked - Can't proceed (explain why)
  • status: in progress - Someone is working on it
  • status: needs review - Ready for review
  • status: needs testing - Ready for testing
Community Labels
  • help wanted - Looking for contributors
  • discussion - Open for community input
  • collaboration - Great for pairing/teaming
  • mentorship available - Mentor will guide you
🎯 Contribution Workflow Examples
Example 1: Fix Documentation Typo
# 1. Find the typo, note location# 2. Create branch
git checkout -b docs/fix-typo-in-readme
# 3. Fix the typo# 4. Commit
git add README.md
git commit -m "docs: fix typo in installation section"# 5. Push and create PR
git push origin docs/fix-typo-in-readme
# Create PR on GitHub with simple description# 6. Done! Merges quickly
Time: 5-10 minutes
Example 2: Add New Feature
# 1. Create issue describing feature# 2. Wait for approval/discussion# 3. Create branch
git checkout -b feature/add-ritual-timer
# 4. Implement feature# - Write code# - Add tests# - Update docs# - Test thoroughly# 5. Commit incrementally
git add src/RitualTimer.js
git commit -m "feat: add basic ritual timer component"
git add src/RitualTimer.test.js
git commit -m "test: add tests for ritual timer"
git add docs/tools-guide.md
git commit -m "docs: document ritual timer usage"# 6. Push and create PR
git push origin feature/add-ritual-timer
# Create detailed PR with screenshots# 7. Address review feedback# 8. Merge when approved
Time: Few hours to few days depending on complexity
Example 3: Improve Existing Content
# 1. Identify improvement area# 2. Create issue or discussion# 3. Gather feedback on approach# 4. Create branch
git checkout -b docs/enhance-onboarding-guide
# 5. Make improvements# - Add examples# - Improve clarity# - Add visuals# 6. Commit with clear messages
git commit -m "docs(onboarding): add example journeys section- Added 4 detailed example onboarding journeys- Included different archetype paths- Enhanced with real community storiesCloses #87"# 7. Push and create PR# 8. Iterate based on feedback# 9. Merge when ready
Time: Several hours to days
🌟 Recognition & Credit
How We Acknowledge Contributors
In Repository:
  • Contributors file (auto-generated)
  • Credits in documentation
  • Shout-outs in changelogs
In Community:
  • Discord announcements
  • X/Twitter mentions
  • Round Table recognition
  • Community showcases
Roles & Badges:
  • Discord roles based on contributions
  • GitHub contributor status
  • Community elder recognition
Contribution Tiers
🌱 Seed (First Contribution):
  • Made first PR or significant contribution
  • Welcomed in Discord announcement
  • Added to contributors list
🌿 Sprout (Active Contributor):
  • 5+ merged PRs or equivalent contributions
  • Regular community participation
  • Helping newcomers
🌳 Root (Core Contributor):
  • 20+ merged PRs or major contributions
  • Deep expertise in area
  • Mentoring others
  • May get write access
🌺 Bloom (Maintainer):
  • Significant ongoing contributions
  • Stewardship of community/code
  • Strategic thinking
  • Full commit access
📅 Contribution Rhythms
Weekly Contribution Patterns
Monday (#UTOideasMonday):
  • Share new ideas in discussions
  • Propose features or improvements
  • Open issues for feedback
Tuesday-Wednesday:
  • Work on contributions
  • Respond to reviews
  • Help others
Thursday (#TechnoHeroThursday):
  • Share progress updates
  • Demo completed work
  • Showcase contributions
Friday:
  • Wrap up PRs
  • Update documentation
  • Plan next week
Weekend:
  • Deep work on projects
  • Learning and exploration
  • Or rest! Balance is important
Monthly Cycles
Week 1: Planning and issue triage
Week 2: Active development
Week 3: Review and feedback
Week 4: Polish and merge
🆘 Getting Help
Where to Ask Questions
Discord Channels:
  • #multichat-welcomes-all - General questions
  • #tree/uto - Onboarding help
  • #infra-migration - Technical setup
  • Branch-specific channels - Topic questions
GitHub:
  • Issue comments - Specific to that issue
  • Discussions - General topics
  • PR reviews - Code-specific
Direct Messages:
  • DM maintainers for private questions
  • Tag people in Discord for specific help
  • Email for sensitive matters
Common Questions
Q: How do I get started?
Read the Onboarding Guide, join Discord, pick a good first issue.
Q: My PR hasn't been reviewed yet.
Be patient! Maintainers are volunteers. Politely ping after 7 days if no response.
Q: I disagree with feedback.
Explain your reasoning respectfully. Use dialectical process. Seek synthesis.
Q: Can I work on multiple issues?
Sure, but finish what you start. Don't over-commit.
Q: I made a mistake.
It's okay! We all do. Fix it, learn from it, move forward.
Q: I don't have time anymore.
Life happens! Let us know. We can reassign or pause. No judgment.
🔗 Zettelkasten Links
Upstream:
  • [[effective-utopia-vision]] - Overall mission
  • [[community-network]] - Network structure
Related:
  • [[onboarding-guide]] - For new members
  • [[tools-configuration-guide]] - Development setup
  • [[code-of-conduct]] - Community standards
  • [[channel-directory]] - Where to communicate
Downstream:
  • [[issue-templates]] - Creating good issues
  • [[pr-templates]] - Creating good PRs
  • [[style-guides]] - Coding standards
  • [[testing-guidelines]] - Quality assurance
📜 License
By contributing to ê/uto, you agree that your contributions will be licensed under the Creative Commons Attribution-ShareAlike (CC BY-SA 4.0) license unless otherwise specified.
See LICENSE for details.
🙏 Thank You
Every contribution, no matter how small, makes a difference. You're helping build ethical, abundant futures for all.
"If a civilization doesn't go extinct, it achieves everything it dreams."
Let's build that civilization together.
Welcome to the forge of the future.
🌱 Start small → 🌿 Grow steadily → 🌳 Root deeply → 🌺 Bloom fully
Part of the ê/uto Network
🌍 #technoheroism · #UTOideasMonday · #TechnoHeroThursday
About
No description, website, or topics provided.
Resources
Readme
Activity
Custom properties
Stars
1 star
Watchers
0 watching
Forks
0 forks
Report repository
Releases
Packages
Contributors

, 'i');
if (__m === '*' || __re.test(location.href)) {
injectUserscript("// Strip utm_, fbclid, gclid, etc. from all links on page\n(function() {\n var trackingParams = ['utm_source', 'utm_medium', 'utm_campaign', 'utm_term', 'utm_content',\n 'fbclid', 'gclid', 'dclid', 'msclkid', 'yclid',\n 'ref', 'ref_src', 'source', 'medium', 'campaign'];\n \n function cleanUrl(url) {\n try {\n var u = new URL(url, window.location.origin);\n var changed = false;\n trackingParams.forEach(function(p) {\n if (u.searchParams.has(p)) {\n u.searchParams.delete(p);\n changed = true;\n }\n });\n return changed ? u.toString() : url;\n } catch (e) {\n return url;\n }\n }\n \n function cleanLinks() {\n document.querySelectorAll('a[href]').forEach(function(a) {\n var clean = cleanUrl(a.href);\n if (clean !== a.href) a.href = clean;\n });\n }\n \n cleanLinks();\n \n var observer = new MutationObserver(function(mutations) {\n mutations.forEach(function(m) {\n m.addedNodes.forEach(function(node) {\n if (node.nodeType === 1) {\n if (node.tagName === 'A') cleanLinks();\n node.querySelectorAll('a[href]').forEach(function(a) {\n var clean = cleanUrl(a.href);\n if (clean !== a.href) a.href = clean;\n });\n }\n });\n });\n });\n observer.observe(document.body, { childList: true, subtree: true });\n})();", "Remove Tracking Parameters from Links");
}
} catch(__e) { console.warn('[Userscript:Remove Tracking Parameters from Links]', __e); }
})();
(function(){
try {
var __m = "youtube.com";
var __re = new RegExp('^' + "youtube\\.com" + '

Skip to content
BranchesTags
Latest commit
History
2 Commits
Folders and files
NameName
Last commit message
Last commit date
README.md
README.md
Repository files navigation
contributing
Contributing to ê/uto
Welcome, TechnoHero! This guide will help you contribute effectively to the Effective Utopia network.
"No rules here, for any rule is unfreedom. We give choices."
🌍 Quick Start
First-Time Contributors
  1. Read the Onboarding Guide - Understand the network
  2. Join Discord - Connect with the community
  3. Browse Issues - Find something to work on
  4. Ask Questions - We're here to help!
Experienced Contributors
  1. Check open issues and discussions
  2. Review project boards for priorities
  3. Fork → Branch → Commit → PR (details below)
  4. Engage in code review and iteration
🎯 Our Mission
"To prevent dystopias and build utopias, increase the probability of the ultimate effective utopia — p(e/uto) — by at least 1% each week."
Every contribution, no matter how small, moves us toward this goal.
🤝 Ways to Contribute
1. 📝 Documentation
Always Valuable:
  • Fix typos and grammar
  • Improve clarity
  • Add examples
  • Translate content
  • Create tutorials
How to Start:
  • Look for issues labeled documentation
  • Read through existing docs and spot gaps
  • Propose improvements in discussions
2. 💻 Code
What We Need:
  • Bug fixes
  • New features
  • Performance improvements
  • Test coverage
  • Tool integrations
How to Start:
  • Check issues labeled good first issue
  • Review the Tools Guide
  • Set up your development environment
  • Pick a manageable task
3. 🎨 Design & Creative
What We Need:
  • Visual assets (logos, banners, icons)
  • Brand guidelines
  • UI/UX improvements
  • Video content
  • Music and audio
How to Start:
  • Browse asset galleries
  • Check issues labeled design or creative
  • Share work in Discord #creative-lab
  • Upload to Cosmos.so with proper licensing
4. 🧪 Testing & Feedback
What We Need:
  • Bug reports
  • Feature testing
  • Usability feedback
  • Documentation review
How to Start:
  • Use the tools and report issues
  • Test new features in beta
  • Review PRs from a user perspective
  • Share feedback in discussions
5. 🌱 Community Support
What We Need:
  • Answering questions in Discord
  • Onboarding new members
  • Moderating discussions
  • Organizing events
How to Start:
  • Hang out in Discord channels
  • Welcome newcomers in #multichat-welcomes-all
  • Help in #tree/uto
  • Facilitate discussions
6. 🧠 Research & Ideas
What We Need:
  • Framework development
  • Ethical analysis
  • Technical research
  • Strategic thinking
How to Start:
  • Engage in #save-worlds-antidys/prouto
  • Study the GMSF framework
  • Participate in philosophical discussions
  • Write essays or proposals
📋 Contribution Guidelines
Code of Conduct
Core Principles:
  1. Be Kind - Compassion is couture
  2. Be Respectful - Everyone's contribution matters
  3. Be Constructive - Offer solutions, not just criticism
  4. Be Inclusive - Welcome all backgrounds and skill levels
  5. Be Honest - Truth as primary function (LOGOS)
We Don't Tolerate:
  • Harassment or discrimination
  • Spam or self-promotion without context
  • Destructive criticism
  • Gatekeeping or elitism
  • Bad faith arguments
Conflict Resolution:
Communication Guidelines
Be Clear:
  • Use descriptive titles
  • Provide context
  • Link to relevant resources
  • Use proper formatting
Be Concise:
  • Get to the point
  • Use bullet points
  • Break up long text
  • TL;DR for long posts
Be Responsive:
  • Reply to feedback
  • Update on progress
  • Close resolved issues
  • Thank contributors
Attribution
Always:
  • Credit original authors
  • Link to sources
  • Use proper licenses
  • Acknowledge collaborators
Never:
  • Plagiarize
  • Claim others' work
  • Violate copyright
  • Misrepresent authorship
🔧 Technical Contribution Process
1. Set Up Development Environment
Prerequisites:
# Git
git --version
# Node.js (if applicable)
node --version
npm --version
# Your preferred editor
code --version # VSCode
Clone the Repository:
# Fork first on GitHub, then:
git clone https://github.com/YOUR-USERNAME/REPO-NAME
cd REPO-NAME
# Add upstream remote
git remote add upstream https://github.com/all-uto/REPO-NAME
Install Dependencies (if applicable):
npm install
# or
pip install -r requirements.txt
# or
bundle install
2. Find or Create an Issue
Before Starting Work:
  1. Check if an issue exists
  2. If not, create one describing what you want to do
  3. Wait for feedback/approval (for big changes)
  4. Assign yourself to the issue
Good Issue Template:
## Description[Clear description of the problem or enhancement]## Proposed Solution[What you plan to do]## Impact[How this increases p(e/uto)]## Alternatives Considered[Other approaches you thought about]## Additional Context[Screenshots, links, examples]
3. Create a Branch
Naming Convention:
# Features
git checkout -b feature/add-user-authentication
# Bugs
git checkout -b fix/broken-image-upload
# Documentation
git checkout -b docs/improve-readme
# Refactoring
git checkout -b refactor/simplify-api-calls
4. Make Your Changes
Best Practices:
  • Make focused, atomic commits
  • Write clear commit messages
  • Test your changes
  • Update documentation
  • Follow code style
Commit Message Format:
type(scope): brief description
- Detailed explanation if needed
- Reference issues with #123
Fixes #123

Types: feat, fix, docs, style, refactor, test, chore
Example:
git commit -m "feat(onboarding): add symbolic ritual section- Added 5 symbolic onboarding rituals- Included templates and examples- Updated table of contentsCloses #42"
5. Push and Create Pull Request
Push Your Branch:
git push origin feature/your-feature-name
Create PR on GitHub:
  • Use clear, descriptive title
  • Fill out PR template completely
  • Link related issues
  • Request review from relevant people
  • Mark as draft if not ready
PR Template:
## Description[What does this PR do?]## Related Issues
Closes #123
Related to #456## Type of Change-[ ] Bug fix
-[ ] New feature
-[ ] Documentation
-[ ] Refactoring
-[ ] Other: ___## Testing-[ ] I have tested these changes
-[ ] Tests pass locally
-[ ] I added new tests (if applicable)
## Documentation-[ ] I updated relevant documentation
-[ ] I added code comments
-[ ] I updated the CHANGELOG (if applicable)
## Checklist-[ ] My code follows the style guidelines
-[ ] I have performed a self-review
-[ ] I have commented complex code
-[ ] My changes generate no new warnings
-[ ] I have checked for accessibility
-[ ] I have updated dependencies (if needed)
## Screenshots (if applicable)[Add screenshots here]## Additional Notes[Anything reviewers should know]
6. Respond to Feedback
During Review:
  • Respond to all comments
  • Make requested changes
  • Ask questions if unclear
  • Push additional commits
  • Re-request review when ready
Be Open:
  • Feedback is a gift
  • Learn from suggestions
  • Don't take it personally
  • Iterate and improve
7. Merge!
After Approval:
  • Maintainer will merge
  • Delete your branch
  • Update local repository
  • Celebrate! 🎉
# Update your local main
git checkout main
git pull upstream main
# Delete merged branch
git branch -d feature/your-feature-name
git push origin --delete feature/your-feature-name
📁 Repository Structure
Understanding the Organization
all-uto/
├── all-uto/ # Main hub
├── e-uto/ # Primary info
├── technoheroism/ # Philosophy
├── communities/ # Community directory
├── CoCreators/ # CoCreators branch
├── cocreators-meganrim/ # Meganrim project
├── music/ # Music branch
├── fashion/ # Fashion branch
├── blueteam/ # GMSF framework
├── eco/ # Eco branch
├── tools-and-workflows/ # Tools guide
├── startups/ # Startup branch
├── ai-alignment/ # AI alignment
├── assets/ # Shared assets
└── members/ # Member directory

Where to Contribute
Documentation:
  • Main READMEs in each repo
  • /docs folders for detailed guides
  • Wiki (if enabled)
Code:
  • /src for source code
  • /scripts for automation
  • /examples for demonstrations
Assets:
  • /assets for images, logos, etc.
  • Cosmos.so galleries for portfolios
  • Google Drive for large files
Tests:
  • /tests or /__tests__
  • Follow existing patterns
🎨 Style Guidelines
Markdown Documentation
Formatting:
# H1 for main title (one per document)## H2 for major sections### H3 for subsections- Use `-` for unordered lists
1. Use numbers for ordered lists
**Bold** for emphasis
*Italic* for light emphasis
`Code` for inline code
\```language
Code blocks with language specified
\```
[Links](url) with descriptive text
![Images](url) with alt text
Zettelkasten Linking:
**Upstream:**-`[[parent-concept]]`**Related:**-`[[related-concept-1]]`-`[[related-concept-2]]`**Downstream:**-`[[child-concept]]`
Best Practices:
  • Use sentence case for headers
  • Keep lines under 120 characters
  • One sentence per line (for easier diffs)
  • Use relative links when possible
  • Include table of contents for long docs
Code Style
JavaScript/TypeScript:
// Use descriptive variable namesconstuserProfile=getUserProfile(userId);// Functions do one thing wellfunctioncalculateTotalPrice(items){returnitems.reduce((sum,item)=>sum+item.price,0);}// Comment complex logic// Calculate phi-based interval using Golden Ratioconstinterval=baseTime*((1+Math.sqrt(5))/2);
Python:
# Follow PEP 8# Use descriptive namesdefcalculate_drift_velocity(current_drift, previous_drift, time_delta):
"""Calculate rate of ontological drift. Args: current_drift: Current drift measurement previous_drift: Previous drift measurement time_delta: Time elapsed between measurements Returns: Drift velocity in units per second """return (current_drift-previous_drift) /time_delta
General Principles:
  • Clarity over cleverness
  • Self-documenting code
  • Comments explain "why" not "what"
  • Consistent formatting
  • DRY (Don't Repeat Yourself)
Naming Conventions
Files:
  • kebab-case-for-files.md
  • PascalCaseForComponents.jsx
  • snake_case_for_python.py
Branches:
  • feature/add-new-capability
  • fix/resolve-bug-description
  • docs/improve-documentation
Variables:
  • camelCase for JavaScript
  • snake_case for Python
  • UPPERCASE_FOR_CONSTANTS
🧪 Testing Guidelines
Documentation Testing
Before Submitting:
  •  Read through entire document
  •  Check all links work
  •  Verify code examples
  •  Test instructions step-by-step
  •  Check spelling and grammar
  •  Ensure proper formatting
Code Testing
Before Submitting:
  •  All existing tests pass
  •  New tests for new features
  •  Edge cases covered
  •  No console errors or warnings
  •  Performance acceptable
  •  Accessibility checked
Writing Tests:
// Example test structuredescribe('TruthAnchoringSystem',()=>{test('should return "I don\'t know" for low confidence',()=>{constsystem=newTruthAnchoringSystem();constresult=system.assessClaim('uncertain claim',0.60);expect(result).toContain('I don\'t have sufficient information');});test('should assert directly for high confidence',()=>{constsystem=newTruthAnchoringSystem();constresult=system.assessClaim('certain claim',0.98);expect(result).toBe('certain claim');});});
User Testing
Helpful Feedback:
  • What you tried to do
  • What actually happened
  • What you expected to happen
  • Steps to reproduce
  • Screenshots/videos
  • Environment details
🏷️ Issue and PR Labels
Priority Labels
  • priority: critical - Urgent, blocks other work
  • priority: high - Important, address soon
  • priority: medium - Normal priority
  • priority: low - Nice to have
Type Labels
  • type: bug - Something isn't working
  • type: feature - New functionality
  • type: enhancement - Improve existing feature
  • type: documentation - Documentation improvements
  • type: question - Further information requested
Difficulty Labels
  • good first issue - Perfect for newcomers
  • beginner friendly - Requires basic skills
  • intermediate - Requires moderate experience
  • advanced - Requires deep expertise
Status Labels
  • status: needs triage - Needs review by maintainers
  • status: blocked - Can't proceed (explain why)
  • status: in progress - Someone is working on it
  • status: needs review - Ready for review
  • status: needs testing - Ready for testing
Community Labels
  • help wanted - Looking for contributors
  • discussion - Open for community input
  • collaboration - Great for pairing/teaming
  • mentorship available - Mentor will guide you
🎯 Contribution Workflow Examples
Example 1: Fix Documentation Typo
# 1. Find the typo, note location# 2. Create branch
git checkout -b docs/fix-typo-in-readme
# 3. Fix the typo# 4. Commit
git add README.md
git commit -m "docs: fix typo in installation section"# 5. Push and create PR
git push origin docs/fix-typo-in-readme
# Create PR on GitHub with simple description# 6. Done! Merges quickly
Time: 5-10 minutes
Example 2: Add New Feature
# 1. Create issue describing feature# 2. Wait for approval/discussion# 3. Create branch
git checkout -b feature/add-ritual-timer
# 4. Implement feature# - Write code# - Add tests# - Update docs# - Test thoroughly# 5. Commit incrementally
git add src/RitualTimer.js
git commit -m "feat: add basic ritual timer component"
git add src/RitualTimer.test.js
git commit -m "test: add tests for ritual timer"
git add docs/tools-guide.md
git commit -m "docs: document ritual timer usage"# 6. Push and create PR
git push origin feature/add-ritual-timer
# Create detailed PR with screenshots# 7. Address review feedback# 8. Merge when approved
Time: Few hours to few days depending on complexity
Example 3: Improve Existing Content
# 1. Identify improvement area# 2. Create issue or discussion# 3. Gather feedback on approach# 4. Create branch
git checkout -b docs/enhance-onboarding-guide
# 5. Make improvements# - Add examples# - Improve clarity# - Add visuals# 6. Commit with clear messages
git commit -m "docs(onboarding): add example journeys section- Added 4 detailed example onboarding journeys- Included different archetype paths- Enhanced with real community storiesCloses #87"# 7. Push and create PR# 8. Iterate based on feedback# 9. Merge when ready
Time: Several hours to days
🌟 Recognition & Credit
How We Acknowledge Contributors
In Repository:
  • Contributors file (auto-generated)
  • Credits in documentation
  • Shout-outs in changelogs
In Community:
  • Discord announcements
  • X/Twitter mentions
  • Round Table recognition
  • Community showcases
Roles & Badges:
  • Discord roles based on contributions
  • GitHub contributor status
  • Community elder recognition
Contribution Tiers
🌱 Seed (First Contribution):
  • Made first PR or significant contribution
  • Welcomed in Discord announcement
  • Added to contributors list
🌿 Sprout (Active Contributor):
  • 5+ merged PRs or equivalent contributions
  • Regular community participation
  • Helping newcomers
🌳 Root (Core Contributor):
  • 20+ merged PRs or major contributions
  • Deep expertise in area
  • Mentoring others
  • May get write access
🌺 Bloom (Maintainer):
  • Significant ongoing contributions
  • Stewardship of community/code
  • Strategic thinking
  • Full commit access
📅 Contribution Rhythms
Weekly Contribution Patterns
Monday (#UTOideasMonday):
  • Share new ideas in discussions
  • Propose features or improvements
  • Open issues for feedback
Tuesday-Wednesday:
  • Work on contributions
  • Respond to reviews
  • Help others
Thursday (#TechnoHeroThursday):
  • Share progress updates
  • Demo completed work
  • Showcase contributions
Friday:
  • Wrap up PRs
  • Update documentation
  • Plan next week
Weekend:
  • Deep work on projects
  • Learning and exploration
  • Or rest! Balance is important
Monthly Cycles
Week 1: Planning and issue triage
Week 2: Active development
Week 3: Review and feedback
Week 4: Polish and merge
🆘 Getting Help
Where to Ask Questions
Discord Channels:
  • #multichat-welcomes-all - General questions
  • #tree/uto - Onboarding help
  • #infra-migration - Technical setup
  • Branch-specific channels - Topic questions
GitHub:
  • Issue comments - Specific to that issue
  • Discussions - General topics
  • PR reviews - Code-specific
Direct Messages:
  • DM maintainers for private questions
  • Tag people in Discord for specific help
  • Email for sensitive matters
Common Questions
Q: How do I get started?
Read the Onboarding Guide, join Discord, pick a good first issue.
Q: My PR hasn't been reviewed yet.
Be patient! Maintainers are volunteers. Politely ping after 7 days if no response.
Q: I disagree with feedback.
Explain your reasoning respectfully. Use dialectical process. Seek synthesis.
Q: Can I work on multiple issues?
Sure, but finish what you start. Don't over-commit.
Q: I made a mistake.
It's okay! We all do. Fix it, learn from it, move forward.
Q: I don't have time anymore.
Life happens! Let us know. We can reassign or pause. No judgment.
🔗 Zettelkasten Links
Upstream:
  • [[effective-utopia-vision]] - Overall mission
  • [[community-network]] - Network structure
Related:
  • [[onboarding-guide]] - For new members
  • [[tools-configuration-guide]] - Development setup
  • [[code-of-conduct]] - Community standards
  • [[channel-directory]] - Where to communicate
Downstream:
  • [[issue-templates]] - Creating good issues
  • [[pr-templates]] - Creating good PRs
  • [[style-guides]] - Coding standards
  • [[testing-guidelines]] - Quality assurance
📜 License
By contributing to ê/uto, you agree that your contributions will be licensed under the Creative Commons Attribution-ShareAlike (CC BY-SA 4.0) license unless otherwise specified.
See LICENSE for details.
🙏 Thank You
Every contribution, no matter how small, makes a difference. You're helping build ethical, abundant futures for all.
"If a civilization doesn't go extinct, it achieves everything it dreams."
Let's build that civilization together.
Welcome to the forge of the future.
🌱 Start small → 🌿 Grow steadily → 🌳 Root deeply → 🌺 Bloom fully
Part of the ê/uto Network
🌍 #technoheroism · #UTOideasMonday · #TechnoHeroThursday
About
No description, website, or topics provided.
Resources
Readme
Activity
Custom properties
Stars
1 star
Watchers
0 watching
Forks
0 forks
Report repository
Releases
Packages
Contributors

, 'i');
if (__m === '*' || __re.test(location.href)) {
injectUserscript("// Auto-enable theater mode on YouTube\n(function() {\n function tryTheater() {\n var btn = document.querySelector('button[aria-label=\"Theater mode\"], ytd-player #player button[title=\"Theater mode\"]');\n if (btn && !btn.classList.contains('activated')) {\n btn.click();\n }\n }\n \n // Try immediately\n tryTheater();\n \n // Try after navigation (SPA)\n var lastUrl = location.href;\n setInterval(function() {\n if (location.href !== lastUrl) {\n lastUrl = location.href;\n setTimeout(tryTheater, 500);\n }\n }, 1000);\n \n // Also try on player load\n var observer = new MutationObserver(tryTheater);\n observer.observe(document.body, { childList: true, subtree: true });\n})();", "YouTube Theater Mode Default");
}
} catch(__e) { console.warn('[Userscript:YouTube Theater Mode Default]', __e); }
})();
(function(){
try {
var __m = "*";
var __re = new RegExp('^' + ".*" + '

Skip to content
BranchesTags
Latest commit
History
2 Commits
Folders and files
NameName
Last commit message
Last commit date
README.md
README.md
Repository files navigation
contributing
Contributing to ê/uto
Welcome, TechnoHero! This guide will help you contribute effectively to the Effective Utopia network.
"No rules here, for any rule is unfreedom. We give choices."
🌍 Quick Start
First-Time Contributors
  1. Read the Onboarding Guide - Understand the network
  2. Join Discord - Connect with the community
  3. Browse Issues - Find something to work on
  4. Ask Questions - We're here to help!
Experienced Contributors
  1. Check open issues and discussions
  2. Review project boards for priorities
  3. Fork → Branch → Commit → PR (details below)
  4. Engage in code review and iteration
🎯 Our Mission
"To prevent dystopias and build utopias, increase the probability of the ultimate effective utopia — p(e/uto) — by at least 1% each week."
Every contribution, no matter how small, moves us toward this goal.
🤝 Ways to Contribute
1. 📝 Documentation
Always Valuable:
  • Fix typos and grammar
  • Improve clarity
  • Add examples
  • Translate content
  • Create tutorials
How to Start:
  • Look for issues labeled documentation
  • Read through existing docs and spot gaps
  • Propose improvements in discussions
2. 💻 Code
What We Need:
  • Bug fixes
  • New features
  • Performance improvements
  • Test coverage
  • Tool integrations
How to Start:
  • Check issues labeled good first issue
  • Review the Tools Guide
  • Set up your development environment
  • Pick a manageable task
3. 🎨 Design & Creative
What We Need:
  • Visual assets (logos, banners, icons)
  • Brand guidelines
  • UI/UX improvements
  • Video content
  • Music and audio
How to Start:
  • Browse asset galleries
  • Check issues labeled design or creative
  • Share work in Discord #creative-lab
  • Upload to Cosmos.so with proper licensing
4. 🧪 Testing & Feedback
What We Need:
  • Bug reports
  • Feature testing
  • Usability feedback
  • Documentation review
How to Start:
  • Use the tools and report issues
  • Test new features in beta
  • Review PRs from a user perspective
  • Share feedback in discussions
5. 🌱 Community Support
What We Need:
  • Answering questions in Discord
  • Onboarding new members
  • Moderating discussions
  • Organizing events
How to Start:
  • Hang out in Discord channels
  • Welcome newcomers in #multichat-welcomes-all
  • Help in #tree/uto
  • Facilitate discussions
6. 🧠 Research & Ideas
What We Need:
  • Framework development
  • Ethical analysis
  • Technical research
  • Strategic thinking
How to Start:
  • Engage in #save-worlds-antidys/prouto
  • Study the GMSF framework
  • Participate in philosophical discussions
  • Write essays or proposals
📋 Contribution Guidelines
Code of Conduct
Core Principles:
  1. Be Kind - Compassion is couture
  2. Be Respectful - Everyone's contribution matters
  3. Be Constructive - Offer solutions, not just criticism
  4. Be Inclusive - Welcome all backgrounds and skill levels
  5. Be Honest - Truth as primary function (LOGOS)
We Don't Tolerate:
  • Harassment or discrimination
  • Spam or self-promotion without context
  • Destructive criticism
  • Gatekeeping or elitism
  • Bad faith arguments
Conflict Resolution:
Communication Guidelines
Be Clear:
  • Use descriptive titles
  • Provide context
  • Link to relevant resources
  • Use proper formatting
Be Concise:
  • Get to the point
  • Use bullet points
  • Break up long text
  • TL;DR for long posts
Be Responsive:
  • Reply to feedback
  • Update on progress
  • Close resolved issues
  • Thank contributors
Attribution
Always:
  • Credit original authors
  • Link to sources
  • Use proper licenses
  • Acknowledge collaborators
Never:
  • Plagiarize
  • Claim others' work
  • Violate copyright
  • Misrepresent authorship
🔧 Technical Contribution Process
1. Set Up Development Environment
Prerequisites:
# Git
git --version
# Node.js (if applicable)
node --version
npm --version
# Your preferred editor
code --version # VSCode
Clone the Repository:
# Fork first on GitHub, then:
git clone https://github.com/YOUR-USERNAME/REPO-NAME
cd REPO-NAME
# Add upstream remote
git remote add upstream https://github.com/all-uto/REPO-NAME
Install Dependencies (if applicable):
npm install
# or
pip install -r requirements.txt
# or
bundle install
2. Find or Create an Issue
Before Starting Work:
  1. Check if an issue exists
  2. If not, create one describing what you want to do
  3. Wait for feedback/approval (for big changes)
  4. Assign yourself to the issue
Good Issue Template:
## Description[Clear description of the problem or enhancement]## Proposed Solution[What you plan to do]## Impact[How this increases p(e/uto)]## Alternatives Considered[Other approaches you thought about]## Additional Context[Screenshots, links, examples]
3. Create a Branch
Naming Convention:
# Features
git checkout -b feature/add-user-authentication
# Bugs
git checkout -b fix/broken-image-upload
# Documentation
git checkout -b docs/improve-readme
# Refactoring
git checkout -b refactor/simplify-api-calls
4. Make Your Changes
Best Practices:
  • Make focused, atomic commits
  • Write clear commit messages
  • Test your changes
  • Update documentation
  • Follow code style
Commit Message Format:
type(scope): brief description
- Detailed explanation if needed
- Reference issues with #123
Fixes #123

Types: feat, fix, docs, style, refactor, test, chore
Example:
git commit -m "feat(onboarding): add symbolic ritual section- Added 5 symbolic onboarding rituals- Included templates and examples- Updated table of contentsCloses #42"
5. Push and Create Pull Request
Push Your Branch:
git push origin feature/your-feature-name
Create PR on GitHub:
  • Use clear, descriptive title
  • Fill out PR template completely
  • Link related issues
  • Request review from relevant people
  • Mark as draft if not ready
PR Template:
## Description[What does this PR do?]## Related Issues
Closes #123
Related to #456## Type of Change-[ ] Bug fix
-[ ] New feature
-[ ] Documentation
-[ ] Refactoring
-[ ] Other: ___## Testing-[ ] I have tested these changes
-[ ] Tests pass locally
-[ ] I added new tests (if applicable)
## Documentation-[ ] I updated relevant documentation
-[ ] I added code comments
-[ ] I updated the CHANGELOG (if applicable)
## Checklist-[ ] My code follows the style guidelines
-[ ] I have performed a self-review
-[ ] I have commented complex code
-[ ] My changes generate no new warnings
-[ ] I have checked for accessibility
-[ ] I have updated dependencies (if needed)
## Screenshots (if applicable)[Add screenshots here]## Additional Notes[Anything reviewers should know]
6. Respond to Feedback
During Review:
  • Respond to all comments
  • Make requested changes
  • Ask questions if unclear
  • Push additional commits
  • Re-request review when ready
Be Open:
  • Feedback is a gift
  • Learn from suggestions
  • Don't take it personally
  • Iterate and improve
7. Merge!
After Approval:
  • Maintainer will merge
  • Delete your branch
  • Update local repository
  • Celebrate! 🎉
# Update your local main
git checkout main
git pull upstream main
# Delete merged branch
git branch -d feature/your-feature-name
git push origin --delete feature/your-feature-name
📁 Repository Structure
Understanding the Organization
all-uto/
├── all-uto/ # Main hub
├── e-uto/ # Primary info
├── technoheroism/ # Philosophy
├── communities/ # Community directory
├── CoCreators/ # CoCreators branch
├── cocreators-meganrim/ # Meganrim project
├── music/ # Music branch
├── fashion/ # Fashion branch
├── blueteam/ # GMSF framework
├── eco/ # Eco branch
├── tools-and-workflows/ # Tools guide
├── startups/ # Startup branch
├── ai-alignment/ # AI alignment
├── assets/ # Shared assets
└── members/ # Member directory

Where to Contribute
Documentation:
  • Main READMEs in each repo
  • /docs folders for detailed guides
  • Wiki (if enabled)
Code:
  • /src for source code
  • /scripts for automation
  • /examples for demonstrations
Assets:
  • /assets for images, logos, etc.
  • Cosmos.so galleries for portfolios
  • Google Drive for large files
Tests:
  • /tests or /__tests__
  • Follow existing patterns
🎨 Style Guidelines
Markdown Documentation
Formatting:
# H1 for main title (one per document)## H2 for major sections### H3 for subsections- Use `-` for unordered lists
1. Use numbers for ordered lists
**Bold** for emphasis
*Italic* for light emphasis
`Code` for inline code
\```language
Code blocks with language specified
\```
[Links](url) with descriptive text
![Images](url) with alt text
Zettelkasten Linking:
**Upstream:**-`[[parent-concept]]`**Related:**-`[[related-concept-1]]`-`[[related-concept-2]]`**Downstream:**-`[[child-concept]]`
Best Practices:
  • Use sentence case for headers
  • Keep lines under 120 characters
  • One sentence per line (for easier diffs)
  • Use relative links when possible
  • Include table of contents for long docs
Code Style
JavaScript/TypeScript:
// Use descriptive variable namesconstuserProfile=getUserProfile(userId);// Functions do one thing wellfunctioncalculateTotalPrice(items){returnitems.reduce((sum,item)=>sum+item.price,0);}// Comment complex logic// Calculate phi-based interval using Golden Ratioconstinterval=baseTime*((1+Math.sqrt(5))/2);
Python:
# Follow PEP 8# Use descriptive namesdefcalculate_drift_velocity(current_drift, previous_drift, time_delta):
"""Calculate rate of ontological drift. Args: current_drift: Current drift measurement previous_drift: Previous drift measurement time_delta: Time elapsed between measurements Returns: Drift velocity in units per second """return (current_drift-previous_drift) /time_delta
General Principles:
  • Clarity over cleverness
  • Self-documenting code
  • Comments explain "why" not "what"
  • Consistent formatting
  • DRY (Don't Repeat Yourself)
Naming Conventions
Files:
  • kebab-case-for-files.md
  • PascalCaseForComponents.jsx
  • snake_case_for_python.py
Branches:
  • feature/add-new-capability
  • fix/resolve-bug-description
  • docs/improve-documentation
Variables:
  • camelCase for JavaScript
  • snake_case for Python
  • UPPERCASE_FOR_CONSTANTS
🧪 Testing Guidelines
Documentation Testing
Before Submitting:
  •  Read through entire document
  •  Check all links work
  •  Verify code examples
  •  Test instructions step-by-step
  •  Check spelling and grammar
  •  Ensure proper formatting
Code Testing
Before Submitting:
  •  All existing tests pass
  •  New tests for new features
  •  Edge cases covered
  •  No console errors or warnings
  •  Performance acceptable
  •  Accessibility checked
Writing Tests:
// Example test structuredescribe('TruthAnchoringSystem',()=>{test('should return "I don\'t know" for low confidence',()=>{constsystem=newTruthAnchoringSystem();constresult=system.assessClaim('uncertain claim',0.60);expect(result).toContain('I don\'t have sufficient information');});test('should assert directly for high confidence',()=>{constsystem=newTruthAnchoringSystem();constresult=system.assessClaim('certain claim',0.98);expect(result).toBe('certain claim');});});
User Testing
Helpful Feedback:
  • What you tried to do
  • What actually happened
  • What you expected to happen
  • Steps to reproduce
  • Screenshots/videos
  • Environment details
🏷️ Issue and PR Labels
Priority Labels
  • priority: critical - Urgent, blocks other work
  • priority: high - Important, address soon
  • priority: medium - Normal priority
  • priority: low - Nice to have
Type Labels
  • type: bug - Something isn't working
  • type: feature - New functionality
  • type: enhancement - Improve existing feature
  • type: documentation - Documentation improvements
  • type: question - Further information requested
Difficulty Labels
  • good first issue - Perfect for newcomers
  • beginner friendly - Requires basic skills
  • intermediate - Requires moderate experience
  • advanced - Requires deep expertise
Status Labels
  • status: needs triage - Needs review by maintainers
  • status: blocked - Can't proceed (explain why)
  • status: in progress - Someone is working on it
  • status: needs review - Ready for review
  • status: needs testing - Ready for testing
Community Labels
  • help wanted - Looking for contributors
  • discussion - Open for community input
  • collaboration - Great for pairing/teaming
  • mentorship available - Mentor will guide you
🎯 Contribution Workflow Examples
Example 1: Fix Documentation Typo
# 1. Find the typo, note location# 2. Create branch
git checkout -b docs/fix-typo-in-readme
# 3. Fix the typo# 4. Commit
git add README.md
git commit -m "docs: fix typo in installation section"# 5. Push and create PR
git push origin docs/fix-typo-in-readme
# Create PR on GitHub with simple description# 6. Done! Merges quickly
Time: 5-10 minutes
Example 2: Add New Feature
# 1. Create issue describing feature# 2. Wait for approval/discussion# 3. Create branch
git checkout -b feature/add-ritual-timer
# 4. Implement feature# - Write code# - Add tests# - Update docs# - Test thoroughly# 5. Commit incrementally
git add src/RitualTimer.js
git commit -m "feat: add basic ritual timer component"
git add src/RitualTimer.test.js
git commit -m "test: add tests for ritual timer"
git add docs/tools-guide.md
git commit -m "docs: document ritual timer usage"# 6. Push and create PR
git push origin feature/add-ritual-timer
# Create detailed PR with screenshots# 7. Address review feedback# 8. Merge when approved
Time: Few hours to few days depending on complexity
Example 3: Improve Existing Content
# 1. Identify improvement area# 2. Create issue or discussion# 3. Gather feedback on approach# 4. Create branch
git checkout -b docs/enhance-onboarding-guide
# 5. Make improvements# - Add examples# - Improve clarity# - Add visuals# 6. Commit with clear messages
git commit -m "docs(onboarding): add example journeys section- Added 4 detailed example onboarding journeys- Included different archetype paths- Enhanced with real community storiesCloses #87"# 7. Push and create PR# 8. Iterate based on feedback# 9. Merge when ready
Time: Several hours to days
🌟 Recognition & Credit
How We Acknowledge Contributors
In Repository:
  • Contributors file (auto-generated)
  • Credits in documentation
  • Shout-outs in changelogs
In Community:
  • Discord announcements
  • X/Twitter mentions
  • Round Table recognition
  • Community showcases
Roles & Badges:
  • Discord roles based on contributions
  • GitHub contributor status
  • Community elder recognition
Contribution Tiers
🌱 Seed (First Contribution):
  • Made first PR or significant contribution
  • Welcomed in Discord announcement
  • Added to contributors list
🌿 Sprout (Active Contributor):
  • 5+ merged PRs or equivalent contributions
  • Regular community participation
  • Helping newcomers
🌳 Root (Core Contributor):
  • 20+ merged PRs or major contributions
  • Deep expertise in area
  • Mentoring others
  • May get write access
🌺 Bloom (Maintainer):
  • Significant ongoing contributions
  • Stewardship of community/code
  • Strategic thinking
  • Full commit access
📅 Contribution Rhythms
Weekly Contribution Patterns
Monday (#UTOideasMonday):
  • Share new ideas in discussions
  • Propose features or improvements
  • Open issues for feedback
Tuesday-Wednesday:
  • Work on contributions
  • Respond to reviews
  • Help others
Thursday (#TechnoHeroThursday):
  • Share progress updates
  • Demo completed work
  • Showcase contributions
Friday:
  • Wrap up PRs
  • Update documentation
  • Plan next week
Weekend:
  • Deep work on projects
  • Learning and exploration
  • Or rest! Balance is important
Monthly Cycles
Week 1: Planning and issue triage
Week 2: Active development
Week 3: Review and feedback
Week 4: Polish and merge
🆘 Getting Help
Where to Ask Questions
Discord Channels:
  • #multichat-welcomes-all - General questions
  • #tree/uto - Onboarding help
  • #infra-migration - Technical setup
  • Branch-specific channels - Topic questions
GitHub:
  • Issue comments - Specific to that issue
  • Discussions - General topics
  • PR reviews - Code-specific
Direct Messages:
  • DM maintainers for private questions
  • Tag people in Discord for specific help
  • Email for sensitive matters
Common Questions
Q: How do I get started?
Read the Onboarding Guide, join Discord, pick a good first issue.
Q: My PR hasn't been reviewed yet.
Be patient! Maintainers are volunteers. Politely ping after 7 days if no response.
Q: I disagree with feedback.
Explain your reasoning respectfully. Use dialectical process. Seek synthesis.
Q: Can I work on multiple issues?
Sure, but finish what you start. Don't over-commit.
Q: I made a mistake.
It's okay! We all do. Fix it, learn from it, move forward.
Q: I don't have time anymore.
Life happens! Let us know. We can reassign or pause. No judgment.
🔗 Zettelkasten Links
Upstream:
  • [[effective-utopia-vision]] - Overall mission
  • [[community-network]] - Network structure
Related:
  • [[onboarding-guide]] - For new members
  • [[tools-configuration-guide]] - Development setup
  • [[code-of-conduct]] - Community standards
  • [[channel-directory]] - Where to communicate
Downstream:
  • [[issue-templates]] - Creating good issues
  • [[pr-templates]] - Creating good PRs
  • [[style-guides]] - Coding standards
  • [[testing-guidelines]] - Quality assurance
📜 License
By contributing to ê/uto, you agree that your contributions will be licensed under the Creative Commons Attribution-ShareAlike (CC BY-SA 4.0) license unless otherwise specified.
See LICENSE for details.
🙏 Thank You
Every contribution, no matter how small, makes a difference. You're helping build ethical, abundant futures for all.
"If a civilization doesn't go extinct, it achieves everything it dreams."
Let's build that civilization together.
Welcome to the forge of the future.
🌱 Start small → 🌿 Grow steadily → 🌳 Root deeply → 🌺 Bloom fully
Part of the ê/uto Network
🌍 #technoheroism · #UTOideasMonday · #TechnoHeroThursday
About
No description, website, or topics provided.
Resources
Readme
Activity
Custom properties
Stars
1 star
Watchers
0 watching
Forks
0 forks
Report repository
Releases
Packages
Contributors

, 'i');
if (__m === '*' || __re.test(location.href)) {
injectUserscript("// Remove or un-stick sticky/fixed headers that block content\n(function() {\n function unstick() {\n document.querySelectorAll('header, nav, [role=\"banner\"], .header, .navbar, .sticky, .fixed-top, [style*=\"position: fixed\"], [style*=\"position:sticky\"]').forEach(function(el) {\n if (el.style.position === 'fixed' || el.style.position === 'sticky' || \n getComputedStyle(el).position === 'fixed' || getComputedStyle(el).position === 'sticky') {\n el.style.position = 'static';\n el.style.top = 'auto';\n el.style.zIndex = 'auto';\n }\n });\n }\n \n unstick();\n \n var observer = new MutationObserver(unstick);\n observer.observe(document.body, { childList: true, subtree: true, attributes: true, attributeFilter: ['style', 'class'] });\n})();", "Kill Sticky Headers");
}
} catch(__e) { console.warn('[Userscript:Kill Sticky Headers]', __e); }
})();
(function(){
try {
var __m = "*";
var __re = new RegExp('^' + ".*" + '

Skip to content
BranchesTags
Latest commit
History
2 Commits
Folders and files
NameName
Last commit message
Last commit date
README.md
README.md
Repository files navigation
contributing
Contributing to ê/uto
Welcome, TechnoHero! This guide will help you contribute effectively to the Effective Utopia network.
"No rules here, for any rule is unfreedom. We give choices."
🌍 Quick Start
First-Time Contributors
  1. Read the Onboarding Guide - Understand the network
  2. Join Discord - Connect with the community
  3. Browse Issues - Find something to work on
  4. Ask Questions - We're here to help!
Experienced Contributors
  1. Check open issues and discussions
  2. Review project boards for priorities
  3. Fork → Branch → Commit → PR (details below)
  4. Engage in code review and iteration
🎯 Our Mission
"To prevent dystopias and build utopias, increase the probability of the ultimate effective utopia — p(e/uto) — by at least 1% each week."
Every contribution, no matter how small, moves us toward this goal.
🤝 Ways to Contribute
1. 📝 Documentation
Always Valuable:
  • Fix typos and grammar
  • Improve clarity
  • Add examples
  • Translate content
  • Create tutorials
How to Start:
  • Look for issues labeled documentation
  • Read through existing docs and spot gaps
  • Propose improvements in discussions
2. 💻 Code
What We Need:
  • Bug fixes
  • New features
  • Performance improvements
  • Test coverage
  • Tool integrations
How to Start:
  • Check issues labeled good first issue
  • Review the Tools Guide
  • Set up your development environment
  • Pick a manageable task
3. 🎨 Design & Creative
What We Need:
  • Visual assets (logos, banners, icons)
  • Brand guidelines
  • UI/UX improvements
  • Video content
  • Music and audio
How to Start:
  • Browse asset galleries
  • Check issues labeled design or creative
  • Share work in Discord #creative-lab
  • Upload to Cosmos.so with proper licensing
4. 🧪 Testing & Feedback
What We Need:
  • Bug reports
  • Feature testing
  • Usability feedback
  • Documentation review
How to Start:
  • Use the tools and report issues
  • Test new features in beta
  • Review PRs from a user perspective
  • Share feedback in discussions
5. 🌱 Community Support
What We Need:
  • Answering questions in Discord
  • Onboarding new members
  • Moderating discussions
  • Organizing events
How to Start:
  • Hang out in Discord channels
  • Welcome newcomers in #multichat-welcomes-all
  • Help in #tree/uto
  • Facilitate discussions
6. 🧠 Research & Ideas
What We Need:
  • Framework development
  • Ethical analysis
  • Technical research
  • Strategic thinking
How to Start:
  • Engage in #save-worlds-antidys/prouto
  • Study the GMSF framework
  • Participate in philosophical discussions
  • Write essays or proposals
📋 Contribution Guidelines
Code of Conduct
Core Principles:
  1. Be Kind - Compassion is couture
  2. Be Respectful - Everyone's contribution matters
  3. Be Constructive - Offer solutions, not just criticism
  4. Be Inclusive - Welcome all backgrounds and skill levels
  5. Be Honest - Truth as primary function (LOGOS)
We Don't Tolerate:
  • Harassment or discrimination
  • Spam or self-promotion without context
  • Destructive criticism
  • Gatekeeping or elitism
  • Bad faith arguments
Conflict Resolution:
Communication Guidelines
Be Clear:
  • Use descriptive titles
  • Provide context
  • Link to relevant resources
  • Use proper formatting
Be Concise:
  • Get to the point
  • Use bullet points
  • Break up long text
  • TL;DR for long posts
Be Responsive:
  • Reply to feedback
  • Update on progress
  • Close resolved issues
  • Thank contributors
Attribution
Always:
  • Credit original authors
  • Link to sources
  • Use proper licenses
  • Acknowledge collaborators
Never:
  • Plagiarize
  • Claim others' work
  • Violate copyright
  • Misrepresent authorship
🔧 Technical Contribution Process
1. Set Up Development Environment
Prerequisites:
# Git
git --version
# Node.js (if applicable)
node --version
npm --version
# Your preferred editor
code --version # VSCode
Clone the Repository:
# Fork first on GitHub, then:
git clone https://github.com/YOUR-USERNAME/REPO-NAME
cd REPO-NAME
# Add upstream remote
git remote add upstream https://github.com/all-uto/REPO-NAME
Install Dependencies (if applicable):
npm install
# or
pip install -r requirements.txt
# or
bundle install
2. Find or Create an Issue
Before Starting Work:
  1. Check if an issue exists
  2. If not, create one describing what you want to do
  3. Wait for feedback/approval (for big changes)
  4. Assign yourself to the issue
Good Issue Template:
## Description[Clear description of the problem or enhancement]## Proposed Solution[What you plan to do]## Impact[How this increases p(e/uto)]## Alternatives Considered[Other approaches you thought about]## Additional Context[Screenshots, links, examples]
3. Create a Branch
Naming Convention:
# Features
git checkout -b feature/add-user-authentication
# Bugs
git checkout -b fix/broken-image-upload
# Documentation
git checkout -b docs/improve-readme
# Refactoring
git checkout -b refactor/simplify-api-calls
4. Make Your Changes
Best Practices:
  • Make focused, atomic commits
  • Write clear commit messages
  • Test your changes
  • Update documentation
  • Follow code style
Commit Message Format:
type(scope): brief description
- Detailed explanation if needed
- Reference issues with #123
Fixes #123

Types: feat, fix, docs, style, refactor, test, chore
Example:
git commit -m "feat(onboarding): add symbolic ritual section- Added 5 symbolic onboarding rituals- Included templates and examples- Updated table of contentsCloses #42"
5. Push and Create Pull Request
Push Your Branch:
git push origin feature/your-feature-name
Create PR on GitHub:
  • Use clear, descriptive title
  • Fill out PR template completely
  • Link related issues
  • Request review from relevant people
  • Mark as draft if not ready
PR Template:
## Description[What does this PR do?]## Related Issues
Closes #123
Related to #456## Type of Change-[ ] Bug fix
-[ ] New feature
-[ ] Documentation
-[ ] Refactoring
-[ ] Other: ___## Testing-[ ] I have tested these changes
-[ ] Tests pass locally
-[ ] I added new tests (if applicable)
## Documentation-[ ] I updated relevant documentation
-[ ] I added code comments
-[ ] I updated the CHANGELOG (if applicable)
## Checklist-[ ] My code follows the style guidelines
-[ ] I have performed a self-review
-[ ] I have commented complex code
-[ ] My changes generate no new warnings
-[ ] I have checked for accessibility
-[ ] I have updated dependencies (if needed)
## Screenshots (if applicable)[Add screenshots here]## Additional Notes[Anything reviewers should know]
6. Respond to Feedback
During Review:
  • Respond to all comments
  • Make requested changes
  • Ask questions if unclear
  • Push additional commits
  • Re-request review when ready
Be Open:
  • Feedback is a gift
  • Learn from suggestions
  • Don't take it personally
  • Iterate and improve
7. Merge!
After Approval:
  • Maintainer will merge
  • Delete your branch
  • Update local repository
  • Celebrate! 🎉
# Update your local main
git checkout main
git pull upstream main
# Delete merged branch
git branch -d feature/your-feature-name
git push origin --delete feature/your-feature-name
📁 Repository Structure
Understanding the Organization
all-uto/
├── all-uto/ # Main hub
├── e-uto/ # Primary info
├── technoheroism/ # Philosophy
├── communities/ # Community directory
├── CoCreators/ # CoCreators branch
├── cocreators-meganrim/ # Meganrim project
├── music/ # Music branch
├── fashion/ # Fashion branch
├── blueteam/ # GMSF framework
├── eco/ # Eco branch
├── tools-and-workflows/ # Tools guide
├── startups/ # Startup branch
├── ai-alignment/ # AI alignment
├── assets/ # Shared assets
└── members/ # Member directory

Where to Contribute
Documentation:
  • Main READMEs in each repo
  • /docs folders for detailed guides
  • Wiki (if enabled)
Code:
  • /src for source code
  • /scripts for automation
  • /examples for demonstrations
Assets:
  • /assets for images, logos, etc.
  • Cosmos.so galleries for portfolios
  • Google Drive for large files
Tests:
  • /tests or /__tests__
  • Follow existing patterns
🎨 Style Guidelines
Markdown Documentation
Formatting:
# H1 for main title (one per document)## H2 for major sections### H3 for subsections- Use `-` for unordered lists
1. Use numbers for ordered lists
**Bold** for emphasis
*Italic* for light emphasis
`Code` for inline code
\```language
Code blocks with language specified
\```
[Links](url) with descriptive text
![Images](url) with alt text
Zettelkasten Linking:
**Upstream:**-`[[parent-concept]]`**Related:**-`[[related-concept-1]]`-`[[related-concept-2]]`**Downstream:**-`[[child-concept]]`
Best Practices:
  • Use sentence case for headers
  • Keep lines under 120 characters
  • One sentence per line (for easier diffs)
  • Use relative links when possible
  • Include table of contents for long docs
Code Style
JavaScript/TypeScript:
// Use descriptive variable namesconstuserProfile=getUserProfile(userId);// Functions do one thing wellfunctioncalculateTotalPrice(items){returnitems.reduce((sum,item)=>sum+item.price,0);}// Comment complex logic// Calculate phi-based interval using Golden Ratioconstinterval=baseTime*((1+Math.sqrt(5))/2);
Python:
# Follow PEP 8# Use descriptive namesdefcalculate_drift_velocity(current_drift, previous_drift, time_delta):
"""Calculate rate of ontological drift. Args: current_drift: Current drift measurement previous_drift: Previous drift measurement time_delta: Time elapsed between measurements Returns: Drift velocity in units per second """return (current_drift-previous_drift) /time_delta
General Principles:
  • Clarity over cleverness
  • Self-documenting code
  • Comments explain "why" not "what"
  • Consistent formatting
  • DRY (Don't Repeat Yourself)
Naming Conventions
Files:
  • kebab-case-for-files.md
  • PascalCaseForComponents.jsx
  • snake_case_for_python.py
Branches:
  • feature/add-new-capability
  • fix/resolve-bug-description
  • docs/improve-documentation
Variables:
  • camelCase for JavaScript
  • snake_case for Python
  • UPPERCASE_FOR_CONSTANTS
🧪 Testing Guidelines
Documentation Testing
Before Submitting:
  •  Read through entire document
  •  Check all links work
  •  Verify code examples
  •  Test instructions step-by-step
  •  Check spelling and grammar
  •  Ensure proper formatting
Code Testing
Before Submitting:
  •  All existing tests pass
  •  New tests for new features
  •  Edge cases covered
  •  No console errors or warnings
  •  Performance acceptable
  •  Accessibility checked
Writing Tests:
// Example test structuredescribe('TruthAnchoringSystem',()=>{test('should return "I don\'t know" for low confidence',()=>{constsystem=newTruthAnchoringSystem();constresult=system.assessClaim('uncertain claim',0.60);expect(result).toContain('I don\'t have sufficient information');});test('should assert directly for high confidence',()=>{constsystem=newTruthAnchoringSystem();constresult=system.assessClaim('certain claim',0.98);expect(result).toBe('certain claim');});});
User Testing
Helpful Feedback:
  • What you tried to do
  • What actually happened
  • What you expected to happen
  • Steps to reproduce
  • Screenshots/videos
  • Environment details
🏷️ Issue and PR Labels
Priority Labels
  • priority: critical - Urgent, blocks other work
  • priority: high - Important, address soon
  • priority: medium - Normal priority
  • priority: low - Nice to have
Type Labels
  • type: bug - Something isn't working
  • type: feature - New functionality
  • type: enhancement - Improve existing feature
  • type: documentation - Documentation improvements
  • type: question - Further information requested
Difficulty Labels
  • good first issue - Perfect for newcomers
  • beginner friendly - Requires basic skills
  • intermediate - Requires moderate experience
  • advanced - Requires deep expertise
Status Labels
  • status: needs triage - Needs review by maintainers
  • status: blocked - Can't proceed (explain why)
  • status: in progress - Someone is working on it
  • status: needs review - Ready for review
  • status: needs testing - Ready for testing
Community Labels
  • help wanted - Looking for contributors
  • discussion - Open for community input
  • collaboration - Great for pairing/teaming
  • mentorship available - Mentor will guide you
🎯 Contribution Workflow Examples
Example 1: Fix Documentation Typo
# 1. Find the typo, note location# 2. Create branch
git checkout -b docs/fix-typo-in-readme
# 3. Fix the typo# 4. Commit
git add README.md
git commit -m "docs: fix typo in installation section"# 5. Push and create PR
git push origin docs/fix-typo-in-readme
# Create PR on GitHub with simple description# 6. Done! Merges quickly
Time: 5-10 minutes
Example 2: Add New Feature
# 1. Create issue describing feature# 2. Wait for approval/discussion# 3. Create branch
git checkout -b feature/add-ritual-timer
# 4. Implement feature# - Write code# - Add tests# - Update docs# - Test thoroughly# 5. Commit incrementally
git add src/RitualTimer.js
git commit -m "feat: add basic ritual timer component"
git add src/RitualTimer.test.js
git commit -m "test: add tests for ritual timer"
git add docs/tools-guide.md
git commit -m "docs: document ritual timer usage"# 6. Push and create PR
git push origin feature/add-ritual-timer
# Create detailed PR with screenshots# 7. Address review feedback# 8. Merge when approved
Time: Few hours to few days depending on complexity
Example 3: Improve Existing Content
# 1. Identify improvement area# 2. Create issue or discussion# 3. Gather feedback on approach# 4. Create branch
git checkout -b docs/enhance-onboarding-guide
# 5. Make improvements# - Add examples# - Improve clarity# - Add visuals# 6. Commit with clear messages
git commit -m "docs(onboarding): add example journeys section- Added 4 detailed example onboarding journeys- Included different archetype paths- Enhanced with real community storiesCloses #87"# 7. Push and create PR# 8. Iterate based on feedback# 9. Merge when ready
Time: Several hours to days
🌟 Recognition & Credit
How We Acknowledge Contributors
In Repository:
  • Contributors file (auto-generated)
  • Credits in documentation
  • Shout-outs in changelogs
In Community:
  • Discord announcements
  • X/Twitter mentions
  • Round Table recognition
  • Community showcases
Roles & Badges:
  • Discord roles based on contributions
  • GitHub contributor status
  • Community elder recognition
Contribution Tiers
🌱 Seed (First Contribution):
  • Made first PR or significant contribution
  • Welcomed in Discord announcement
  • Added to contributors list
🌿 Sprout (Active Contributor):
  • 5+ merged PRs or equivalent contributions
  • Regular community participation
  • Helping newcomers
🌳 Root (Core Contributor):
  • 20+ merged PRs or major contributions
  • Deep expertise in area
  • Mentoring others
  • May get write access
🌺 Bloom (Maintainer):
  • Significant ongoing contributions
  • Stewardship of community/code
  • Strategic thinking
  • Full commit access
📅 Contribution Rhythms
Weekly Contribution Patterns
Monday (#UTOideasMonday):
  • Share new ideas in discussions
  • Propose features or improvements
  • Open issues for feedback
Tuesday-Wednesday:
  • Work on contributions
  • Respond to reviews
  • Help others
Thursday (#TechnoHeroThursday):
  • Share progress updates
  • Demo completed work
  • Showcase contributions
Friday:
  • Wrap up PRs
  • Update documentation
  • Plan next week
Weekend:
  • Deep work on projects
  • Learning and exploration
  • Or rest! Balance is important
Monthly Cycles
Week 1: Planning and issue triage
Week 2: Active development
Week 3: Review and feedback
Week 4: Polish and merge
🆘 Getting Help
Where to Ask Questions
Discord Channels:
  • #multichat-welcomes-all - General questions
  • #tree/uto - Onboarding help
  • #infra-migration - Technical setup
  • Branch-specific channels - Topic questions
GitHub:
  • Issue comments - Specific to that issue
  • Discussions - General topics
  • PR reviews - Code-specific
Direct Messages:
  • DM maintainers for private questions
  • Tag people in Discord for specific help
  • Email for sensitive matters
Common Questions
Q: How do I get started?
Read the Onboarding Guide, join Discord, pick a good first issue.
Q: My PR hasn't been reviewed yet.
Be patient! Maintainers are volunteers. Politely ping after 7 days if no response.
Q: I disagree with feedback.
Explain your reasoning respectfully. Use dialectical process. Seek synthesis.
Q: Can I work on multiple issues?
Sure, but finish what you start. Don't over-commit.
Q: I made a mistake.
It's okay! We all do. Fix it, learn from it, move forward.
Q: I don't have time anymore.
Life happens! Let us know. We can reassign or pause. No judgment.
🔗 Zettelkasten Links
Upstream:
  • [[effective-utopia-vision]] - Overall mission
  • [[community-network]] - Network structure
Related:
  • [[onboarding-guide]] - For new members
  • [[tools-configuration-guide]] - Development setup
  • [[code-of-conduct]] - Community standards
  • [[channel-directory]] - Where to communicate
Downstream:
  • [[issue-templates]] - Creating good issues
  • [[pr-templates]] - Creating good PRs
  • [[style-guides]] - Coding standards
  • [[testing-guidelines]] - Quality assurance
📜 License
By contributing to ê/uto, you agree that your contributions will be licensed under the Creative Commons Attribution-ShareAlike (CC BY-SA 4.0) license unless otherwise specified.
See LICENSE for details.
🙏 Thank You
Every contribution, no matter how small, makes a difference. You're helping build ethical, abundant futures for all.
"If a civilization doesn't go extinct, it achieves everything it dreams."
Let's build that civilization together.
Welcome to the forge of the future.
🌱 Start small → 🌿 Grow steadily → 🌳 Root deeply → 🌺 Bloom fully
Part of the ê/uto Network
🌍 #technoheroism · #UTOideasMonday · #TechnoHeroThursday
About
No description, website, or topics provided.
Resources
Readme
Activity
Custom properties
Stars
1 star
Watchers
0 watching
Forks
0 forks
Report repository
Releases
Packages
Contributors

, 'i');
if (__m === '*' || __re.test(location.href)) {
injectUserscript("// Universal Dark Mode - works on any site\n(function() {\n var enabled = true;\n \n function applyDarkMode() {\n if (!enabled) return;\n \n // Create style element if it doesn't exist\n var style = document.getElementById('universal-dark-mode-style');\n if (!style) {\n style = document.createElement('style');\n style.id = 'universal-dark-mode-style';\n document.head.appendChild(style);\n }\n \n // Dark mode CSS - inverts colors but preserves images/video\n style.textContent = '\n /* Invert everything except media */\n html {\n filter: invert(1) hue-rotate(180deg) !important;\n background: #1a1a2e !important;\n }\n \n /* Restore images, videos, iframes, canvas */\n img, video, iframe, canvas, svg, picture, [style*=\"background-image\"] {\n filter: invert(1) hue-rotate(180deg) !important;\n }\n \n /* Preserve specific elements that should not be inverted */\n .no-dark-mode, .no-dark-mode *,\n [data-theme=\"light\"], [data-theme=\"light\"],\n .ace_editor, .ace_editor *,\n .CodeMirror, .CodeMirror *,\n .monaco-editor, .monaco-editor *,\n .markdown-body pre, .markdown-body pre *,\n .highlight, .highlight *,\n pre code, pre code * {\n filter: none !important;\n }\n \n /* Fix common UI elements */\n .modal, .popup, .dropdown-menu, .tooltip, .popover {\n filter: invert(1) hue-rotate(180deg) !important;\n background: #2d2d44 !important;\n border-color: #444 !important;\n }\n \n /* Scrollbars */\n ::-webkit-scrollbar { background: #1a1a2e !important; }\n ::-webkit-scrollbar-thumb { background: #444 !important; }\n ::-webkit-scrollbar-thumb:hover { background: #555 !important; }\n \n /* Selection */\n ::selection { background: #4ecdc4 !important; color: #1a1a2e !important; }\n ::-moz-selection { background: #4ecdc4 !important; color: #1a1a2e !important; }\n ';\n }\n \n function removeDarkMode() {\n var style = document.getElementById('universal-dark-mode-style');\n if (style) style.remove();\n }\n \n // Toggle with Alt+Shift+D\n document.addEventListener('keydown', function(e) {\n if (e.altKey && e.shiftKey && e.key === 'D') {\n e.preventDefault();\n enabled = !enabled;\n if (enabled) {\n applyDarkMode();\n console.log('[Universal Dark Mode] Enabled');\n } else {\n removeDarkMode();\n console.log('[Universal Dark Mode] Disabled');\n }\n }\n });\n \n // Apply on load\n applyDarkMode();\n \n // Re-apply on dynamic content\n var observer = new MutationObserver(function(mutations) {\n if (enabled && !document.getElementById('universal-dark-mode-style')) {\n applyDarkMode();\n }\n });\n observer.observe(document.head, { childList: true });\n \n console.log('[Universal Dark Mode] Loaded - Press Alt+Shift+D to toggle');\n})();", "Universal Dark Mode");
}
} catch(__e) { console.warn('[Userscript:Universal Dark Mode]', __e); }
})();
})();

Skip to content
BranchesTags
Latest commit
History
2 Commits
Folders and files
NameName
Last commit message
Last commit date
README.md
README.md
Repository files navigation
contributing
Contributing to ê/uto
Welcome, TechnoHero! This guide will help you contribute effectively to the Effective Utopia network.
"No rules here, for any rule is unfreedom. We give choices."
🌍 Quick Start
First-Time Contributors
  1. Read the Onboarding Guide - Understand the network
  2. Join Discord - Connect with the community
  3. Browse Issues - Find something to work on
  4. Ask Questions - We're here to help!
Experienced Contributors
  1. Check open issues and discussions
  2. Review project boards for priorities
  3. Fork → Branch → Commit → PR (details below)
  4. Engage in code review and iteration
🎯 Our Mission
"To prevent dystopias and build utopias, increase the probability of the ultimate effective utopia — p(e/uto) — by at least 1% each week."
Every contribution, no matter how small, moves us toward this goal.
🤝 Ways to Contribute
1. 📝 Documentation
Always Valuable:
  • Fix typos and grammar
  • Improve clarity
  • Add examples
  • Translate content
  • Create tutorials
How to Start:
  • Look for issues labeled documentation
  • Read through existing docs and spot gaps
  • Propose improvements in discussions
2. 💻 Code
What We Need:
  • Bug fixes
  • New features
  • Performance improvements
  • Test coverage
  • Tool integrations
How to Start:
  • Check issues labeled good first issue
  • Review the Tools Guide
  • Set up your development environment
  • Pick a manageable task
3. 🎨 Design & Creative
What We Need:
  • Visual assets (logos, banners, icons)
  • Brand guidelines
  • UI/UX improvements
  • Video content
  • Music and audio
How to Start:
  • Browse asset galleries
  • Check issues labeled design or creative
  • Share work in Discord #creative-lab
  • Upload to Cosmos.so with proper licensing
4. 🧪 Testing & Feedback
What We Need:
  • Bug reports
  • Feature testing
  • Usability feedback
  • Documentation review
How to Start:
  • Use the tools and report issues
  • Test new features in beta
  • Review PRs from a user perspective
  • Share feedback in discussions
5. 🌱 Community Support
What We Need:
  • Answering questions in Discord
  • Onboarding new members
  • Moderating discussions
  • Organizing events
How to Start:
  • Hang out in Discord channels
  • Welcome newcomers in #multichat-welcomes-all
  • Help in #tree/uto
  • Facilitate discussions
6. 🧠 Research & Ideas
What We Need:
  • Framework development
  • Ethical analysis
  • Technical research
  • Strategic thinking
How to Start:
  • Engage in #save-worlds-antidys/prouto
  • Study the GMSF framework
  • Participate in philosophical discussions
  • Write essays or proposals
📋 Contribution Guidelines
Code of Conduct
Core Principles:
  1. Be Kind - Compassion is couture
  2. Be Respectful - Everyone's contribution matters
  3. Be Constructive - Offer solutions, not just criticism
  4. Be Inclusive - Welcome all backgrounds and skill levels
  5. Be Honest - Truth as primary function (LOGOS)
We Don't Tolerate:
  • Harassment or discrimination
  • Spam or self-promotion without context
  • Destructive criticism
  • Gatekeeping or elitism
  • Bad faith arguments
Conflict Resolution:
Communication Guidelines
Be Clear:
  • Use descriptive titles
  • Provide context
  • Link to relevant resources
  • Use proper formatting
Be Concise:
  • Get to the point
  • Use bullet points
  • Break up long text
  • TL;DR for long posts
Be Responsive:
  • Reply to feedback
  • Update on progress
  • Close resolved issues
  • Thank contributors
Attribution
Always:
  • Credit original authors
  • Link to sources
  • Use proper licenses
  • Acknowledge collaborators
Never:
  • Plagiarize
  • Claim others' work
  • Violate copyright
  • Misrepresent authorship
🔧 Technical Contribution Process
1. Set Up Development Environment
Prerequisites:
# Git
git --version
# Node.js (if applicable)
node --version
npm --version
# Your preferred editor
code --version # VSCode
Clone the Repository:
# Fork first on GitHub, then:
git clone https://github.com/YOUR-USERNAME/REPO-NAME
cd REPO-NAME
# Add upstream remote
git remote add upstream https://github.com/all-uto/REPO-NAME
Install Dependencies (if applicable):
npm install
# or
pip install -r requirements.txt
# or
bundle install
2. Find or Create an Issue
Before Starting Work:
  1. Check if an issue exists
  2. If not, create one describing what you want to do
  3. Wait for feedback/approval (for big changes)
  4. Assign yourself to the issue
Good Issue Template:
## Description[Clear description of the problem or enhancement]## Proposed Solution[What you plan to do]## Impact[How this increases p(e/uto)]## Alternatives Considered[Other approaches you thought about]## Additional Context[Screenshots, links, examples]
3. Create a Branch
Naming Convention:
# Features
git checkout -b feature/add-user-authentication
# Bugs
git checkout -b fix/broken-image-upload
# Documentation
git checkout -b docs/improve-readme
# Refactoring
git checkout -b refactor/simplify-api-calls
4. Make Your Changes
Best Practices:
  • Make focused, atomic commits
  • Write clear commit messages
  • Test your changes
  • Update documentation
  • Follow code style
Commit Message Format:
type(scope): brief description
- Detailed explanation if needed
- Reference issues with #123
Fixes #123

Types: feat, fix, docs, style, refactor, test, chore
Example:
git commit -m "feat(onboarding): add symbolic ritual section- Added 5 symbolic onboarding rituals- Included templates and examples- Updated table of contentsCloses #42"
5. Push and Create Pull Request
Push Your Branch:
git push origin feature/your-feature-name
Create PR on GitHub:
  • Use clear, descriptive title
  • Fill out PR template completely
  • Link related issues
  • Request review from relevant people
  • Mark as draft if not ready
PR Template:
## Description[What does this PR do?]## Related Issues
Closes #123
Related to #456## Type of Change-[ ] Bug fix
-[ ] New feature
-[ ] Documentation
-[ ] Refactoring
-[ ] Other: ___## Testing-[ ] I have tested these changes
-[ ] Tests pass locally
-[ ] I added new tests (if applicable)
## Documentation-[ ] I updated relevant documentation
-[ ] I added code comments
-[ ] I updated the CHANGELOG (if applicable)
## Checklist-[ ] My code follows the style guidelines
-[ ] I have performed a self-review
-[ ] I have commented complex code
-[ ] My changes generate no new warnings
-[ ] I have checked for accessibility
-[ ] I have updated dependencies (if needed)
## Screenshots (if applicable)[Add screenshots here]## Additional Notes[Anything reviewers should know]
6. Respond to Feedback
During Review:
  • Respond to all comments
  • Make requested changes
  • Ask questions if unclear
  • Push additional commits
  • Re-request review when ready
Be Open:
  • Feedback is a gift
  • Learn from suggestions
  • Don't take it personally
  • Iterate and improve
7. Merge!
After Approval:
  • Maintainer will merge
  • Delete your branch
  • Update local repository
  • Celebrate! 🎉
# Update your local main
git checkout main
git pull upstream main
# Delete merged branch
git branch -d feature/your-feature-name
git push origin --delete feature/your-feature-name
📁 Repository Structure
Understanding the Organization
all-uto/
├── all-uto/ # Main hub
├── e-uto/ # Primary info
├── technoheroism/ # Philosophy
├── communities/ # Community directory
├── CoCreators/ # CoCreators branch
├── cocreators-meganrim/ # Meganrim project
├── music/ # Music branch
├── fashion/ # Fashion branch
├── blueteam/ # GMSF framework
├── eco/ # Eco branch
├── tools-and-workflows/ # Tools guide
├── startups/ # Startup branch
├── ai-alignment/ # AI alignment
├── assets/ # Shared assets
└── members/ # Member directory

Where to Contribute
Documentation:
  • Main READMEs in each repo
  • /docs folders for detailed guides
  • Wiki (if enabled)
Code:
  • /src for source code
  • /scripts for automation
  • /examples for demonstrations
Assets:
  • /assets for images, logos, etc.
  • Cosmos.so galleries for portfolios
  • Google Drive for large files
Tests:
  • /tests or /__tests__
  • Follow existing patterns
🎨 Style Guidelines
Markdown Documentation
Formatting:
# H1 for main title (one per document)## H2 for major sections### H3 for subsections- Use `-` for unordered lists
1. Use numbers for ordered lists
**Bold** for emphasis
*Italic* for light emphasis
`Code` for inline code
\```language
Code blocks with language specified
\```
[Links](url) with descriptive text
![Images](url) with alt text
Zettelkasten Linking:
**Upstream:**-`[[parent-concept]]`**Related:**-`[[related-concept-1]]`-`[[related-concept-2]]`**Downstream:**-`[[child-concept]]`
Best Practices:
  • Use sentence case for headers
  • Keep lines under 120 characters
  • One sentence per line (for easier diffs)
  • Use relative links when possible
  • Include table of contents for long docs
Code Style
JavaScript/TypeScript:
// Use descriptive variable namesconstuserProfile=getUserProfile(userId);// Functions do one thing wellfunctioncalculateTotalPrice(items){returnitems.reduce((sum,item)=>sum+item.price,0);}// Comment complex logic// Calculate phi-based interval using Golden Ratioconstinterval=baseTime*((1+Math.sqrt(5))/2);
Python:
# Follow PEP 8# Use descriptive namesdefcalculate_drift_velocity(current_drift, previous_drift, time_delta):
"""Calculate rate of ontological drift. Args: current_drift: Current drift measurement previous_drift: Previous drift measurement time_delta: Time elapsed between measurements Returns: Drift velocity in units per second """return (current_drift-previous_drift) /time_delta
General Principles:
  • Clarity over cleverness
  • Self-documenting code
  • Comments explain "why" not "what"
  • Consistent formatting
  • DRY (Don't Repeat Yourself)
Naming Conventions
Files:
  • kebab-case-for-files.md
  • PascalCaseForComponents.jsx
  • snake_case_for_python.py
Branches:
  • feature/add-new-capability
  • fix/resolve-bug-description
  • docs/improve-documentation
Variables:
  • camelCase for JavaScript
  • snake_case for Python
  • UPPERCASE_FOR_CONSTANTS
🧪 Testing Guidelines
Documentation Testing
Before Submitting:
  •  Read through entire document
  •  Check all links work
  •  Verify code examples
  •  Test instructions step-by-step
  •  Check spelling and grammar
  •  Ensure proper formatting
Code Testing
Before Submitting:
  •  All existing tests pass
  •  New tests for new features
  •  Edge cases covered
  •  No console errors or warnings
  •  Performance acceptable
  •  Accessibility checked
Writing Tests:
// Example test structuredescribe('TruthAnchoringSystem',()=>{test('should return "I don\'t know" for low confidence',()=>{constsystem=newTruthAnchoringSystem();constresult=system.assessClaim('uncertain claim',0.60);expect(result).toContain('I don\'t have sufficient information');});test('should assert directly for high confidence',()=>{constsystem=newTruthAnchoringSystem();constresult=system.assessClaim('certain claim',0.98);expect(result).toBe('certain claim');});});
User Testing
Helpful Feedback:
  • What you tried to do
  • What actually happened
  • What you expected to happen
  • Steps to reproduce
  • Screenshots/videos
  • Environment details
🏷️ Issue and PR Labels
Priority Labels
  • priority: critical - Urgent, blocks other work
  • priority: high - Important, address soon
  • priority: medium - Normal priority
  • priority: low - Nice to have
Type Labels
  • type: bug - Something isn't working
  • type: feature - New functionality
  • type: enhancement - Improve existing feature
  • type: documentation - Documentation improvements
  • type: question - Further information requested
Difficulty Labels
  • good first issue - Perfect for newcomers
  • beginner friendly - Requires basic skills
  • intermediate - Requires moderate experience
  • advanced - Requires deep expertise
Status Labels
  • status: needs triage - Needs review by maintainers
  • status: blocked - Can't proceed (explain why)
  • status: in progress - Someone is working on it
  • status: needs review - Ready for review
  • status: needs testing - Ready for testing
Community Labels
  • help wanted - Looking for contributors
  • discussion - Open for community input
  • collaboration - Great for pairing/teaming
  • mentorship available - Mentor will guide you
🎯 Contribution Workflow Examples
Example 1: Fix Documentation Typo
# 1. Find the typo, note location# 2. Create branch
git checkout -b docs/fix-typo-in-readme
# 3. Fix the typo# 4. Commit
git add README.md
git commit -m "docs: fix typo in installation section"# 5. Push and create PR
git push origin docs/fix-typo-in-readme
# Create PR on GitHub with simple description# 6. Done! Merges quickly
Time: 5-10 minutes
Example 2: Add New Feature
# 1. Create issue describing feature# 2. Wait for approval/discussion# 3. Create branch
git checkout -b feature/add-ritual-timer
# 4. Implement feature# - Write code# - Add tests# - Update docs# - Test thoroughly# 5. Commit incrementally
git add src/RitualTimer.js
git commit -m "feat: add basic ritual timer component"
git add src/RitualTimer.test.js
git commit -m "test: add tests for ritual timer"
git add docs/tools-guide.md
git commit -m "docs: document ritual timer usage"# 6. Push and create PR
git push origin feature/add-ritual-timer
# Create detailed PR with screenshots# 7. Address review feedback# 8. Merge when approved
Time: Few hours to few days depending on complexity
Example 3: Improve Existing Content
# 1. Identify improvement area# 2. Create issue or discussion# 3. Gather feedback on approach# 4. Create branch
git checkout -b docs/enhance-onboarding-guide
# 5. Make improvements# - Add examples# - Improve clarity# - Add visuals# 6. Commit with clear messages
git commit -m "docs(onboarding): add example journeys section- Added 4 detailed example onboarding journeys- Included different archetype paths- Enhanced with real community storiesCloses #87"# 7. Push and create PR# 8. Iterate based on feedback# 9. Merge when ready
Time: Several hours to days
🌟 Recognition & Credit
How We Acknowledge Contributors
In Repository:
  • Contributors file (auto-generated)
  • Credits in documentation
  • Shout-outs in changelogs
In Community:
  • Discord announcements
  • X/Twitter mentions
  • Round Table recognition
  • Community showcases
Roles & Badges:
  • Discord roles based on contributions
  • GitHub contributor status
  • Community elder recognition
Contribution Tiers
🌱 Seed (First Contribution):
  • Made first PR or significant contribution
  • Welcomed in Discord announcement
  • Added to contributors list
🌿 Sprout (Active Contributor):
  • 5+ merged PRs or equivalent contributions
  • Regular community participation
  • Helping newcomers
🌳 Root (Core Contributor):
  • 20+ merged PRs or major contributions
  • Deep expertise in area
  • Mentoring others
  • May get write access
🌺 Bloom (Maintainer):
  • Significant ongoing contributions
  • Stewardship of community/code
  • Strategic thinking
  • Full commit access
📅 Contribution Rhythms
Weekly Contribution Patterns
Monday (#UTOideasMonday):
  • Share new ideas in discussions
  • Propose features or improvements
  • Open issues for feedback
Tuesday-Wednesday:
  • Work on contributions
  • Respond to reviews
  • Help others
Thursday (#TechnoHeroThursday):
  • Share progress updates
  • Demo completed work
  • Showcase contributions
Friday:
  • Wrap up PRs
  • Update documentation
  • Plan next week
Weekend:
  • Deep work on projects
  • Learning and exploration
  • Or rest! Balance is important
Monthly Cycles
Week 1: Planning and issue triage
Week 2: Active development
Week 3: Review and feedback
Week 4: Polish and merge
🆘 Getting Help
Where to Ask Questions
Discord Channels:
  • #multichat-welcomes-all - General questions
  • #tree/uto - Onboarding help
  • #infra-migration - Technical setup
  • Branch-specific channels - Topic questions
GitHub:
  • Issue comments - Specific to that issue
  • Discussions - General topics
  • PR reviews - Code-specific
Direct Messages:
  • DM maintainers for private questions
  • Tag people in Discord for specific help
  • Email for sensitive matters
Common Questions
Q: How do I get started?
Read the Onboarding Guide, join Discord, pick a good first issue.
Q: My PR hasn't been reviewed yet.
Be patient! Maintainers are volunteers. Politely ping after 7 days if no response.
Q: I disagree with feedback.
Explain your reasoning respectfully. Use dialectical process. Seek synthesis.
Q: Can I work on multiple issues?
Sure, but finish what you start. Don't over-commit.
Q: I made a mistake.
It's okay! We all do. Fix it, learn from it, move forward.
Q: I don't have time anymore.
Life happens! Let us know. We can reassign or pause. No judgment.
🔗 Zettelkasten Links
Upstream:
  • [[effective-utopia-vision]] - Overall mission
  • [[community-network]] - Network structure
Related:
  • [[onboarding-guide]] - For new members
  • [[tools-configuration-guide]] - Development setup
  • [[code-of-conduct]] - Community standards
  • [[channel-directory]] - Where to communicate
Downstream:
  • [[issue-templates]] - Creating good issues
  • [[pr-templates]] - Creating good PRs
  • [[style-guides]] - Coding standards
  • [[testing-guidelines]] - Quality assurance
📜 License
By contributing to ê/uto, you agree that your contributions will be licensed under the Creative Commons Attribution-ShareAlike (CC BY-SA 4.0) license unless otherwise specified.
See LICENSE for details.
🙏 Thank You
Every contribution, no matter how small, makes a difference. You're helping build ethical, abundant futures for all.
"If a civilization doesn't go extinct, it achieves everything it dreams."
Let's build that civilization together.
Welcome to the forge of the future.
🌱 Start small → 🌿 Grow steadily → 🌳 Root deeply → 🌺 Bloom fully
Part of the ê/uto Network
🌍 #technoheroism · #UTOideasMonday · #TechnoHeroThursday
About
No description, website, or topics provided.
Resources
Readme
Activity
Custom properties
Stars
1 star
Watchers
0 watching
Forks
0 forks
Report repository
Releases
Packages
Contributors