├── .editorconfig ├── .gitattributes ├── .github ├── CODEOWNERS └── workflows │ ├── auto-add-to-project.yml │ ├── compliance.yml │ ├── development.yml │ ├── pizza-action.yml │ ├── release.yml │ └── triage.yml ├── .gitignore ├── .nojekyll ├── .npmrc ├── .nvmrc ├── .sauced.yaml ├── CHANGELOG.md ├── CODEOWNERS ├── Dockerfile ├── LICENSE ├── README.md ├── babel.config.js ├── blog ├── 2023 │ ├── 2023-04-17-writing-your-first-pull-request-tips-best-practices-and-ai-powered-tools-for-success.md │ ├── 2023-04-20-how-vercel-is-using-github-discussions-to-build-a-strong-nextjs-community.md │ ├── 2023-04-24-managing-community-health-files-and-templates-with-a-github-repository.md │ ├── 2023-04-26-what-is-bluesky-social-network-and-why-are-developers-excited-about-it.md │ ├── 2023-05-01-beyond-content-creation-how-open-source-contributions-can-help-you-get-noticed.md │ ├── 2023-05-01-the-power-of-pair-programming-benefits-types-and-tips.md │ ├── 2023-05-03-how-to-contribute-to-open-source-without-knowing-how-to-code-a-guide-with-project-suggestions.md │ ├── 2023-05-08-open-source-terminology-101-a-primer-for-new-contributors.md │ ├── 2023-05-10-how-to-write-a-good-issue-tips-for-effective-communication-in-open-source.md │ ├── 2023-05-15-choose-your-own-adventure-in-open-source-paths-to-success.md │ ├── 2023-05-22-what-happens-after-you-submit-a-pr-to-an-open-source-project.md │ ├── 2023-05-30-exploring-imaginary-worlds.md │ ├── 2023-06-01-understanding-why-pull-requests-get-rejected-in-open-source-projects.md │ ├── 2023-06-05-fueling-innovation-and-collaborative-storytelling.md │ ├── 2023-06-12-from-inspiration-to-impact.md │ ├── 2023-06-14-how-to-start-an-open-source-project-with-vs-code.md │ ├── 2023-06-21-open-source-101-a-beginners-guide-to-getting-started.md │ ├── 2023-06-26-building-your-devrel-resume-with-open-source.md │ ├── 2023-07-03-devex-and-oss--elevating-developer-experience-through-open-source-collaboration.md │ ├── 2023-07-10-how-to-talk-about-your-open-source-experience-in-a-tech-interview.md │ ├── 2023-07-12-100daysofoss-growing-skills-and-real-world-experience.md │ ├── 2023-07-17-the-power-of-git-a-guide-to-collaborative-version-control.md │ ├── 2023-07-24-setting-goals-for-your-open-source-contributions.md │ ├── 2023-07-27-open-source-abcs-bug.md │ ├── 2023-07-31-keeping-your-branch-up-to-date-and-handling-merge-conflicts-while-waiting-for-pr-reviews.md │ ├── 2023-08-01-open-source-abcs-collaboration.md │ ├── 2023-08-03-open-source-abcs-documentation.md │ ├── 2023-08-07-you-dont-need-a-mentor-embracing-the-power-of-community.md │ ├── 2023-08-08-open-source-abcs-evolution.md │ ├── 2023-08-09-caching-git-repos.md │ ├── 2023-08-10-open-source-abcs-fork.md │ ├── 2023-08-14-what-does-an-open-source-triage-team-do.md │ ├── 2023-08-15-open-source-abcs-git.md │ ├── 2023-08-21-open-source-abcs-issues.md │ ├── 2023-08-22-navigating-open-source-my-journey-to-contributing-and-getting-my-first-freecodecamp-pr-accepted.md │ ├── 2023-08-23-open-source-abcs-javascript.md │ ├── 2023-08-28-open-source-abcs-kernel.md │ ├── 2023-09-04-open-source-abcs-meritocracy.md │ ├── 2023-09-05-how-to-participate-in-hacktoberfest.md │ ├── 2023-09-06-open-source-abcs-network.md │ ├── 2023-09-11-open-source-abcs-open-data.md │ ├── 2023-09-12-navigating-spammy-and-low-quality-prs-a-guide-for-maintainers.md │ ├── 2023-09-13-open-source-abcs-pull-request.md │ ├── 2023-09-14-how-we-made-our-go-microservice-24x-faster.md │ ├── 2023-09-18-open-source-abcs-quality-assurance.md │ ├── 2023-09-19-the-role-of-docs.md │ ├── 2023-09-20-open-source-abcs-repository.md │ ├── 2023-09-21-supercharge-your-repository-with-code-owners.md │ ├── 2023-09-27-open-source-abcs-transparency.md │ ├── 2023-10-02-open-source-abcs-upstream.md │ ├── 2023-10-03-how-to-be-a-top-contributor-this-hacktoberfest.md │ ├── 2023-10-04-open-source-abcs-version-control.md │ ├── 2023-10-09-open-source-abcs-workflow.md │ ├── 2023-10-12-open-source-abcs-xenial-xerus.md │ ├── 2023-10-16-open-source-abcs-yaml--yml.md │ ├── 2023-10-17-setting-up-your-first-github-action.md │ ├── 2023-10-18-open-source-abcs-zsh.md │ ├── 2023-10-31-github-actions-a-maintainers-best-friend.md │ ├── 2023-11-01-how-to-get-your-pull-request-reviewed.md │ ├── 2023-11-07-a-complete-guide-to-getting-started-in-open-source.md │ ├── 2023-11-14-boost-productivity-with-the-github-cli.md │ ├── 2023-11-21-so-youre-interested-in-being-an-open-source-maintainer.md │ ├── 2023-11-28-strategies-for-successful-contributor-onboarding.md │ ├── 2023-11-30-job-seekers-worksheet-build-your-resume-with-open-source.md │ ├── 2023-11-30-what-to-do-when-your-pr-fails.md │ ├── 2023-12-05-so-what-does-a-maintainer-do-anyway.md │ └── 2023-12-14-migrating-from-jest-to-vitest-for-your-react-application.md ├── 2024 │ ├── 2024-01-09-take-the-first-step-the-open-source-game.md │ ├── 2024-01-23-the-native-browser-dialog-element.md │ ├── 2024-02-01-game-development-and-multimedia-godot-engine-a-game-changer-in-game-development.md │ ├── 2024-02-02-game-development-and-multimedia-theatrejs-unleashing-creativity-in-animation-and-motion-design.md │ ├── 2024-02-03-game-development-and-multimedia-audacity-the-sound-of-creativity.md │ ├── 2024-02-04-development-tools-and-platforms-open-source-saas-and-boxyhq.md │ ├── 2024-02-05-development-tools-and-platforms-a-closer-look-at-api-testing-with-hoppscotch.md │ ├── 2024-02-06-challenging-the-skeptics-unveiling-the-undeniable-goodness-of-tailwind-css.md │ ├── 2024-02-06-development-tools-and-platforms-create-your-devto--pipedream-automation-in-under-20-minutes.md │ ├── 2024-02-07-documenso-v-docusign-the-showdown.md │ ├── 2024-02-08-getting-user-feedback-for-success-tips-and-tools.md │ ├── 2024-02-09-why-would-you-use-backend-as-a-service-baas.md │ ├── 2024-02-10-researchhub-the-github-of-scientific-research.md │ ├── 2024-02-11-transforming-lives-through-code-freecodecamp.md │ ├── 2024-02-12-three-open-source-alternatives-to-calendly.md │ ├── 2024-02-13-transforming-productivity-with-open-source-gamification-habitica.md │ ├── 2024-02-14-modernizing-file-management-with-spacedrive--is-it-worth-it.md │ ├── 2024-02-15-what-do-you-use-for-a-second-brain.md │ ├── 2024-02-17-what-design-tool-should-i-use.md │ ├── 2024-02-18-the-open-source-slack-alternative.md │ ├── 2024-02-19-dev-medium-and-hashnode-choosing-your-digital-stage.md │ ├── 2024-02-20-whats-the-right-newsletter-platform-for-you-open-source-spotlight-on-ghost.md │ ├── 2024-02-21-whats-a-headless-cms.md │ ├── 2024-02-22-from-messy-to-memorable-shorten-your-links-boost-your-brand.md │ ├── 2024-02-23-sending-emails-with-react.md │ ├── 2024-02-24-what-would-your-dream-home-automation-look-like.md │ ├── 2024-02-25-open-source-ai-glasses-would-you-wear-them.md │ ├── 2024-02-26-exploring-supabase-the-open-source-backend-for-developers.md │ ├── 2024-02-27-would-you-use-an-open-source-personal-finance-app.md │ ├── 2024-02-28-chatgpt-google-gemini-or-huggingchats-open-source-option.md │ ├── 2024-02-29-opensauced-nurturing-open-source-collaboration-and-growth.md │ ├── 2024-03-05-collaborate-conquer-grow-mastering-the-art-of-issue-management-for-open-source-projects.md │ ├── 2024-03-14-stuck-in-the-middle-with-you-an-intro-to-middleware.md │ ├── 2024-03-19-how-to-build-your-open-source-dream-team-a-guide.md │ ├── 2024-03-26-whats-the-difference-between-new-and-beginner-open-source-contributors.md │ ├── 2024-04-02-form-and-function-how-i-lost-my-submit-button-got-it-back.md │ ├── 2024-04-04-meet-the-new-ai-engineers-devin-devika-and-opendevin.md │ ├── 2024-04-16-creating-an-og-image-using-react-and-netlify-edge-functions.md │ ├── 2024-04-18-the-missing-piece-why-your-project-needs-a-maintainer-onboarding-process.md │ ├── 2024-04-23-the-secret-recipe-to-getting-your-pull-requests-reviewed-and-merged-faster.md │ ├── 2024-04-30-building-bridges-not-walls-the-importance-of-documentation-in-open-source-projects.md │ ├── 2024-05-02-we-made-a-copilot-tool-for-you-to-unlock-the-power-of-git-history.md │ ├── 2024-05-06-maintainer-monday-community-care.md │ ├── 2024-05-09-streamline-your-contributions-mastering-issue-forms-and-pr-templates.md │ ├── 2024-05-13-maintainer-monday.md │ ├── 2024-05-20-nurturing-the-future-of-open-source-maintainers.md │ ├── 2024-05-21-pour-one-out-for-create-react-app-whats-next.md │ ├── 2024-05-23-creating-open-source-connections.md │ ├── 2024-05-28-how-to-assess-your-skill-level-before-contributing-to-open-source.md │ ├── 2024-06-03-how-to-find-open-source-projects-to-contribute-to.md │ ├── 2024-06-17-valibot-a-new-approach-to-data-validation-in-javascript.md │ ├── 2024-07-15-the-react-useref-hook-not-just-for-html-elements.md │ ├── 2024-08-05-open-source-challenge.md │ ├── 2024-08-06-introducing-ossf-scorecard.md │ ├── 2024-08-08-ossf-scorecard-technical-deep-dive.md │ └── 2024-08-19-supercharge-your-github-profile.md └── authors.yml ├── docs ├── community │ ├── 100-days-of-oss.md │ ├── hacktoberfest.md │ └── welcome-to-the-community.md ├── contributing │ ├── code-of-conduct.md │ ├── introduction-to-contributing.md │ ├── opensauced-maintainers-guide │ │ ├── community-maintainers-guide.md │ │ └── maintainers-guide.md │ ├── opensauced-writers-guide │ │ └── how-to-add-your-post.md │ ├── set-up-authentication.md │ ├── technical │ │ ├── resolve-merge-conflicts.md │ │ └── setup-repo-with-git.md │ └── triage-guide.md ├── contributors │ └── contributors-guide.md ├── features │ ├── contributor-insights.md │ ├── dev-card.md │ ├── highlights.md │ ├── repo-insights.md │ ├── repo-pages.md │ ├── star-search.md │ └── workspaces.md ├── introduction.md ├── maintainers │ ├── maintainers-guide.md │ ├── understanding-contrib-insights.md │ └── understanding-repo-insights.md ├── opensauced-guides │ ├── job-seekers-guide │ │ ├── categorize-contributions.md │ │ └── introduction.md │ ├── oscr-score-guide │ │ └── oscr-introduction.md │ └── students-guide │ │ └── students-guide.md ├── opensauced-packages │ ├── check-engines.md │ ├── conventional-commit.md │ └── semantic-release.md ├── tools │ ├── chrome-extension │ │ ├── highlights.md │ │ ├── introduction-to-the-chrome-extension.md │ │ └── viewing-insights-and-invitations.md │ ├── hot-opensauced.md │ └── pizza-cli │ │ ├── codeowners.md │ │ ├── pizza-action.md │ │ └── pizza-cli.md └── welcome │ ├── faqs.md │ ├── glossary.md │ ├── key-metrics-guide.md │ └── opensauced-intro.md ├── docusaurus.config.js ├── netlify.toml ├── npm-shrinkwrap.json ├── package.json ├── sidebars.js ├── src └── css │ └── custom.css └── static ├── android-chrome-192x192.png ├── android-chrome-512x512.png ├── apple-touch-icon.png ├── favicon-16x16.png ├── favicon-32x32.png ├── favicon.ico ├── gif ├── connections.gif ├── contributors-sync-list.gif ├── highlight.gif ├── insight-page-demo.gif ├── pr-code-explain.gif ├── pr-code-refactor.gif ├── pr-code-test.gif ├── pr-description.gif ├── team-sync-insights.gif └── team-sync.gif ├── icon-144x144.png ├── icon-192x192.png ├── icon-72x72.png ├── icon-96x96.png ├── img ├── DevCard.png ├── a-dev-card.png ├── access-workspace.png ├── activity-repos-insights.png ├── add-to-workspace.png ├── contrib-insight-new.png ├── contributing-avatar-top-right.png ├── contributing-copy-auth-token.png ├── contributing-maintainers-create-repository.png ├── contributing-maintainers-env.png ├── contributing-maintainers-merge-protections.png ├── contributing-maintainers-merge-settings.png ├── contributing-resolve-merge-conflicts-commit-message.png ├── contributing-resolve-merge-conflicts-dont-do.png ├── contributing-resolve-merge-conflicts-merge-conflicts.png ├── contributing-resolve-merge-conflicts-merge-success.png ├── contributing-resolve-merge-conflicts-ready-to-merge.png ├── contributing-resolve-merge-conflicts-review-conflicts.png ├── contributing-resolve-merge-conflicts-view-merge-commit.png ├── contributing-token-printed-to-console.png ├── contributors-insights.png ├── crossplane-scorecard.png ├── extension-invite.png ├── extension-links.png ├── extension-popup.png ├── extension-view.png ├── favicon.ico ├── files-changed-tab.png ├── future-scorecard-workspaces.png ├── future-scorecard.png ├── get-dev-card.png ├── highlights.png ├── kubernetes-scorecard.png ├── list-graph.png ├── lists-page.png ├── logo.svg ├── logo_darkmode.png ├── logo_lightmode.png ├── ml-explore-page.png ├── openSauced-icon.png ├── popular-repos-hot-opensauced.png ├── pr-velocity-example.png ├── profile.png ├── repos-insights.png ├── settings.png ├── star-search.png ├── sync-branch-GH.png ├── upvoted-repos-hot-opensauced.png ├── what-is-opensauced.jpg ├── what-is-opensauced.png ├── workspace-access.png ├── workspace-sidebar.png ├── workspace-switcher.png └── workspace.png ├── manifest.json └── robots.txt /.editorconfig: -------------------------------------------------------------------------------- 1 | root = true 2 | 3 | [*] 4 | indent_style = space 5 | indent_size = 2 6 | end_of_line = lf 7 | charset = utf-8 8 | max_line_length = 120 9 | trim_trailing_whitespace = true 10 | insert_final_newline = true 11 | 12 | [*.md] 13 | max_line_length = 0 14 | trim_trailing_whitespace = false 15 | -------------------------------------------------------------------------------- /.gitattributes: -------------------------------------------------------------------------------- 1 | *.pbxproj -text 2 | * text eol=lf 3 | 4 | ## DOCKER 5 | *.dockerignore text 6 | Dockerfile text 7 | 8 | ## DOCUMENTATION 9 | *.markdown text 10 | *.md text 11 | *.mdwn text 12 | *.mdown text 13 | *.mkd text 14 | *.mkdn text 15 | *.mdtxt text 16 | *.mdtext text 17 | *.txt text 18 | AUTHORS text 19 | CHANGELOG text 20 | CHANGES text 21 | CONTRIBUTING text 22 | COPYING text 23 | copyright text 24 | *COPYRIGHT* text 25 | INSTALL text 26 | license text 27 | LICENSE text 28 | NEWS text 29 | readme text 30 | *README* text 31 | TODO text 32 | 33 | ## CONFIGS 34 | *.bowerrc text 35 | *.cnf text 36 | *.conf text 37 | *.config text 38 | .browserslistrc text 39 | .editorconfig text 40 | .gitattributes text 41 | .gitconfig text 42 | .htaccess text 43 | *.npmignore text 44 | *.yaml text 45 | *.yml text 46 | browserslist text 47 | Makefile text 48 | makefile text 49 | 50 | ## GRAPHICS 51 | *.ai binary 52 | *.bmp binary 53 | *.eps binary 54 | *.gif binary 55 | *.ico binary 56 | *.jng binary 57 | *.jp2 binary 58 | *.jpg binary 59 | *.jpeg binary 60 | *.jpx binary 61 | *.jxr binary 62 | *.pdf binary 63 | *.png binary 64 | *.psb binary 65 | *.psd binary 66 | *.svg text 67 | *.svgz binary 68 | *.tif binary 69 | *.tiff binary 70 | *.wbmp binary 71 | *.webp binary 72 | 73 | ## FONTS 74 | *.ttf binary 75 | *.eot binary 76 | *.otf binary 77 | *.woff binary 78 | *.woff2 binary 79 | -------------------------------------------------------------------------------- /.github/CODEOWNERS: -------------------------------------------------------------------------------- 1 | * @open-sauced/docs 2 | -------------------------------------------------------------------------------- /.github/workflows/auto-add-to-project.yml: -------------------------------------------------------------------------------- 1 | name: Adds all issues opened in the /docs repo to the Team Dashboard 2 | 3 | on: 4 | issues: 5 | types: 6 | - opened 7 | 8 | jobs: 9 | add-to-project: 10 | name: Add issue to project 11 | runs-on: ubuntu-latest 12 | steps: 13 | - name: Generate token 14 | id: generate_token 15 | uses: tibdex/github-app-token@v1 16 | with: 17 | app_id: ${{ secrets.OS_GITHUB_APP_ID }} 18 | private_key: ${{ secrets.OS_GITHUB_APP_PRIVATE_KEY }} 19 | 20 | - name: add issue to team dashboard 21 | uses: actions/add-to-project@v0.5.0 22 | with: 23 | project-url: https://github.com/orgs/open-sauced/projects/25 24 | github-token: ${{ steps.generate_token.outputs.token }} 25 | -------------------------------------------------------------------------------- /.github/workflows/compliance.yml: -------------------------------------------------------------------------------- 1 | name: "Compliance" 2 | 3 | on: 4 | pull_request_target: 5 | types: 6 | - opened 7 | - edited 8 | - synchronize 9 | 10 | permissions: 11 | pull-requests: write 12 | 13 | jobs: 14 | compliance: 15 | uses: open-sauced/hot/.github/workflows/compliance.yml@main 16 | -------------------------------------------------------------------------------- /.github/workflows/development.yml: -------------------------------------------------------------------------------- 1 | name: "Development" 2 | 3 | on: 4 | pull_request: 5 | types: 6 | - opened 7 | - edited 8 | - synchronize 9 | - reopened 10 | 11 | jobs: 12 | test: 13 | uses: open-sauced/hot/.github/workflows/development.yml@main 14 | -------------------------------------------------------------------------------- /.github/workflows/pizza-action.yml: -------------------------------------------------------------------------------- 1 | name: OpenSauced Pizza Action 2 | 3 | on: 4 | schedule: 5 | # Run once a week on Sunday at 00:00 UTC 6 | - cron: "0 0 * * 0" 7 | workflow_dispatch: # Allow manual triggering 8 | 9 | jobs: 10 | pizza-action: 11 | runs-on: ubuntu-latest 12 | steps: 13 | - name: Pizza Action 14 | uses: open-sauced/pizza-action@v2.3.0 15 | with: 16 | cli-version: "v2.2.0" 17 | commit-and-pr: "true" 18 | pr-title: "chore: update repository codeowners" 19 | -------------------------------------------------------------------------------- /.github/workflows/triage.yml: -------------------------------------------------------------------------------- 1 | name: Triage 2 | 3 | on: 4 | issue_comment: 5 | types: 6 | - created 7 | - edited 8 | workflow_call: 9 | 10 | jobs: 11 | take-issue: 12 | name: Take issue 13 | runs-on: ubuntu-latest 14 | permissions: 15 | issues: write 16 | timeout-minutes: 10 17 | steps: 18 | - name: take an issue 19 | uses: bdougie/take-action@main 20 | with: 21 | message: Thanks for taking this on! If you have not already, join the conversation in our [Community](https://github.com/orgs/open-sauced/discussions/1) 22 | issueCurrentlyAssignedMessage: Thanks for being interested in this issue. It looks like this ticket is already assigned to a contributor. Please communicate with the assigned contributor to confirm the status of the issue. 23 | trigger: .take 24 | token: ${{ secrets.GITHUB_TOKEN }} 25 | -------------------------------------------------------------------------------- /.gitignore: -------------------------------------------------------------------------------- 1 | # Dependencies 2 | /node_modules 3 | 4 | # Production 5 | /build 6 | 7 | # Generated files 8 | .docusaurus 9 | .cache-loader 10 | 11 | # Misc 12 | .DS_Store 13 | .env 14 | .env.local 15 | .env.development.local 16 | .env.test.local 17 | .env.production.local 18 | .prettierignore 19 | 20 | npm-debug.log* 21 | yarn-debug.log* 22 | yarn-error.log* 23 | 24 | 25 | # custom 26 | config.json 27 | -------------------------------------------------------------------------------- /.nojekyll: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/open-sauced/docs/81b05471f63b289ecc61fb116c68682d1199c78c/.nojekyll -------------------------------------------------------------------------------- /.npmrc: -------------------------------------------------------------------------------- 1 | save-exact=false 2 | audit=false 3 | audit-level="moderate" 4 | loglevel="info" 5 | progress=false 6 | timing=false 7 | engine-strict=true 8 | legacy-peer-deps=true 9 | -------------------------------------------------------------------------------- /.nvmrc: -------------------------------------------------------------------------------- 1 | 18.17.0 2 | -------------------------------------------------------------------------------- /.sauced.yaml: -------------------------------------------------------------------------------- 1 | # Configuration for attributing commits with emails to individual entities. 2 | # Used during "pizza generate codeowners". 3 | attribution: 4 | 5 | # Keys can be GitHub usernames. For the "--github-codeowners" style codeowners 6 | # generation, these keys must be valid GitHub usernames. 7 | brandonroberts: 8 | - robertsbt@gmail.com 9 | jpmcb: 10 | - john@opensauced.pizza 11 | - jpmmcbride@gmail.com 12 | nickytonline: 13 | - nick@nickyt.co 14 | - nick@opensauced.pizza 15 | bdougie: 16 | - bdougie@users.noreply.github.com 17 | zeucapua: 18 | - coding@zeu.dev 19 | BekahHW: 20 | - rhawrot@gmail.com 21 | - 34313413+BekahHW@users.noreply.github.com 22 | adiati98: 23 | - 45172775+adiati98@users.noreply.github.com 24 | attribution-fallback: 25 | - open-sauced/docs -------------------------------------------------------------------------------- /CODEOWNERS: -------------------------------------------------------------------------------- 1 | # This file is generated automatically by OpenSauced pizza-cli. DO NOT EDIT. Stay saucy! 2 | # 3 | # Generated with command: 4 | # $ pizza generate codeowners docs/ --tty-disable true 5 | 6 | .github/workflows/pizza-action.yml @BekahHW @nickytonline 7 | .gitignore 8 | .sauced.yaml @BekahHW 9 | CODEOWNERS @BekahHW 10 | blog/2023/2023-09-19-the-role-of-docs.md @BekahHW 11 | blog/2023/2023-09-21-supercharge-your-repository-with-code-owners.md 12 | blog/2023/2023-10-31-github-actions-a-maintainers-best-friend.md 13 | blog/2023/2023-11-14-boost-productivity-with-the-github-cli.md 14 | blog/2023/2023-12-14-migrating-from-jest-to-vitest-for-your-react-application.md 15 | blog/2024/2024-01-23-the-native-browser-dialog-element.md 16 | blog/2024/2024-02-06-challenging-the-skeptics-unveiling-the-undeniable-goodness-of-tailwind-css.md 17 | blog/2024/2024-02-12-three-open-source-alternatives-to-calendly.md @BekahHW 18 | blog/2024/2024-03-05-collaborate-conquer-grow-mastering-the-art-of-issue-management-for-open-source-projects.md @adiati98 19 | blog/2024/2024-03-14-stuck-in-the-middle-with-you-an-intro-to-middleware.md 20 | blog/2024/2024-04-02-form-and-function-how-i-lost-my-submit-button-got-it-back.md 21 | blog/2024/2024-04-16-creating-an-og-image-using-react-and-netlify-edge-functions.md 22 | blog/2024/2024-04-18-the-missing-piece-why-your-project-needs-a-maintainer-onboarding-process.md @adiati98 23 | blog/2024/2024-04-23-the-secret-recipe-to-getting-your-pull-requests-reviewed-and-merged-faster.md @adiati98 24 | blog/2024/2024-04-30-building-bridges-not-walls-the-importance-of-documentation-in-open-source-projects.md @adiati98 25 | blog/2024/2024-05-09-streamline-your-contributions-mastering-issue-forms-and-pr-templates.md @adiati98 26 | blog/2024/2024-08-19-supercharge-your-github-profile.md @BekahHW 27 | blog/authors.yml @adiati98 @BekahHW 28 | docs/community/100-days-of-oss.md @BekahHW 29 | docs/contributing/opensauced-writers-guide/how-to-add-your-post.md 30 | docs/contributors/contributors-guide.md @BekahHW 31 | docs/features/connections.md @BekahHW 32 | docs/features/contributor-insights.md @BekahHW 33 | docs/features/repo-insights.md @BekahHW 34 | docs/features/repo-pages.md @BekahHW 35 | docs/features/workspaces.md @BekahHW 36 | docs/maintainers/maintainers-guide.md @BekahHW 37 | docs/maintainers/understanding-repo-insights.md 38 | docs/opensauced-guides/oscr-score-guide/oscr-introduction.md 39 | docs/opensauced-guides/students-guide/students-guide.md @BekahHW 40 | docs/tools/chrome-extension/code-explanation.md @BekahHW 41 | docs/tools/chrome-extension/highlights.md @BekahHW 42 | docs/tools/chrome-extension/pr-description.md @BekahHW 43 | docs/tools/chrome-extension/refactoring-and-testing.md @BekahHW 44 | docs/tools/hot-opensauced.md @BekahHW 45 | docs/tools/pizza-cli.md @BekahHW 46 | docs/tools/pizza-cli/codeowners.md @BekahHW 47 | docs/tools/pizza-cli/pizza-action.md @BekahHW 48 | docs/welcome/faqs.md 49 | docs/welcome/glossary.md @BekahHW 50 | docs/welcome/key-metrics-guide.md 51 | docusaurus.config.js @BekahHW @zeucapua 52 | npm-shrinkwrap.json @BekahHW @zeucapua 53 | package.json @BekahHW @zeucapua 54 | sidebars.js @BekahHW 55 | -------------------------------------------------------------------------------- /Dockerfile: -------------------------------------------------------------------------------- 1 | FROM node:18.17.0-alpine as development 2 | 3 | WORKDIR /app 4 | 5 | COPY package.json ./ 6 | COPY npm-shrinkwrap.json ./ 7 | COPY .npmrc ./ 8 | 9 | RUN npm i -g npm@latest 10 | RUN npm ci 11 | 12 | COPY docs ./docs 13 | COPY src ./src 14 | COPY static ./static 15 | COPY docusaurus.config.js ./ 16 | COPY sidebars.js ./ 17 | 18 | CMD [ "npm", "start"] 19 | 20 | FROM development as builder 21 | 22 | RUN npm run build 23 | 24 | FROM nginx:1.21-alpine as production 25 | 26 | COPY --from=builder /app/build /usr/share/nginx/html 27 | -------------------------------------------------------------------------------- /LICENSE: -------------------------------------------------------------------------------- 1 | MIT License 2 | 3 | Copyright (c) 2024 OpenSauced 4 | 5 | Permission is hereby granted, free of charge, to any person obtaining a copy 6 | of this software and associated documentation files (the "Software"), to deal 7 | in the Software without restriction, including without limitation the rights 8 | to use, copy, modify, merge, publish, distribute, sublicense, and/or sell 9 | copies of the Software, and to permit persons to whom the Software is 10 | furnished to do so, subject to the following conditions: 11 | 12 | The above copyright notice and this permission notice shall be included in all 13 | copies or substantial portions of the Software. 14 | 15 | THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR 16 | IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, 17 | FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE 18 | AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER 19 | LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, 20 | OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE 21 | SOFTWARE. 22 | -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 |
2 |
3 | 4 | [![OpenSauced](https://github.com/open-sauced/assets/blob/main/logos/logo-on-dark.png)](https://opensauced.pizza) 5 | 6 | # 🍕 OpenSauced Docs 🍕 7 | > The path to your next Open Source contribution 8 | 9 | [![Code Size](https://img.shields.io/github/languages/code-size/open-sauced/docs.opensauced.pizza?style=flat)](https://github.com/open-sauced/docs.opensauced.pizza/pulse) 10 | [![Commits](https://img.shields.io/github/commit-activity/w/open-sauced/docs.opensauced.pizza?style=flat)](https://github.com/open-sauced/docs.opensauced.pizza/pulse) 11 | [![Issues](https://img.shields.io/github/issues/open-sauced/docs.opensauced.pizza.svg?style=flat)](https://github.com/open-sauced/docs.opensauced.pizza/issues) 12 | [![Releases](https://img.shields.io/github/v/release/open-sauced/docs.opensauced.pizza.svg?style=flat)](https://github.com/open-sauced/docs.opensauced.pizza/releases) 13 | [![Twitter](https://img.shields.io/twitter/follow/saucedopen?label=Follow&style=social)](https://twitter.com/saucedopen) 14 |
15 | 16 | 17 | ## 🤝 Contributing 18 | 19 | We encourage you to contribute to OpenSauced! All contributors are required to abide by our [Code of Conduct](https://github.com/open-sauced/.github/blob/main/CODE_OF_CONDUCT.md). Please check out the [Contributing guide](https://opensauced.pizza/docs/contributing/introduction-to-contributing/) for guidelines about how to proceed with your contribution. 20 | 21 | 22 | 23 | ## 🖥️ Development 24 | 25 | ```sh 26 | npm ci 27 | npm start 28 | ``` 29 | 30 | ## 🍕 Community 31 | 32 | Got Questions? Join the conversation in our [Community](https://github.com/orgs/open-sauced/discussions/1). 33 | Find OpenSauced videos and release overviews on our [YouTube Channel](https://www.youtube.com/channel/UCklWxKrTti61ZCROE1e5-MQ). 34 | 35 | ## ⚖️ LICENSE 36 | 37 | MIT © [OpenSauced](LICENSE) 38 | -------------------------------------------------------------------------------- /babel.config.js: -------------------------------------------------------------------------------- 1 | module.exports = { 2 | presets: [require.resolve("@docusaurus/core/lib/babel/preset")], 3 | }; 4 | -------------------------------------------------------------------------------- /blog/2023/2023-04-20-how-vercel-is-using-github-discussions-to-build-a-strong-nextjs-community.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: How Vercel is Using GitHub Discussions to Build a Strong Next.js Community 3 | tags: [] 4 | authors: BekahHW 5 | slug: how-vercel-is-using-github-discussions-to-build-a-strong-nextjs-community 6 | description: "Learn how Next.js, a flexible React framework, is leveraging GitHub discussions to strengthen its community, promote job opportunities, and showcase companies using Next.js." 7 | --- 8 | 9 | Communication is key to maintaining a healthy open source project. It’s even more important if one of your projects has more than 100,000 stars. Using a tool like GitHub discussions provides an opportunity for communication for more than bug reports, show and tell, or product announcements. It can provide a path to support and connect the community, and that’s exactly how Vercel is using discussions on their [Next.js repository](https://github.com/vercel/next.js/discussions). 10 | 11 | 12 | 13 | ## What is Next.js? 14 | > Next.js is a flexible React framework that gives you building blocks to create fast web applications. 15 | 16 | Vercel, the company behind Next.js, provides a platform for deploying and hosting Next.js applications, as well as a range of other tools and services for building and scaling web applications. 17 | 18 | ## How does Next.js use their discussions? 19 | At first glance, the list of discussion features for Next.js looks pretty ordinary, well except maybe the squirrel with the hat as the icon for the Show and Tell section. Next.js takes it a step further and leverages GitHub discussions to provide its community with a space for participation and interaction. The project prioritizes community building by pinning important discussions at the top of the page: Companies/Sites using Next.js, Who’s hiring (April 2023), Who wants to be hired (April 2023). 20 | 21 | ### Companies/Sites using Next.js 22 | This discussion lists companies that are using Next.js, allows folks to respond to the post with their site that’s built with Next.js, and also links to their [showcase](https://nextjs.org/showcase) as well. So if you have a Next.js site, and you’re not already showing it off, add it to [this discussion](https://github.com/vercel/next.js/discussions/10640)! 23 | 24 | ### Who’s hiring 25 | This monthly post provides a space for companies to advertise job openings for individuals with Next.js experience, and for job seekers to find opportunities. I checked out their posts all the way back to November 2021, and loved seeing how many included this line: “At least one company has hired someone as a result of it!” 26 | 27 | [https://twitter.com/nutlope/status/1610667757565083648?s=20](https://twitter.com/nutlope/status/1610667757565083648?s=20) 28 | 29 | 30 | ### Who wants to be hired 31 | 32 | This pinned post is for job seekers with Next.js experience to showcase their skills and experience. Companies looking to hire can browse the post for potential candidates. This gives a nice glimpse into the Next.js community and provides support for job seekers and does my favorite thing: offers to send swag to anyone who was hired through the post. 33 | 34 | ![Screenshot of Who wants to be hired (April 2023) post](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/ug608pczuotc58ag8i6f.png) 35 | 36 | It’s great to see Next.js building a strong and supportive community through discussions. If you’re a Next.js developer looking for work and you have contributions you’d like to highlight, you can add them to your [OpenSauced highlights](https://insights.opensauced.pizza/feed) and link them to your post. 37 | 38 | 39 | header image created using [midjourney](https://www.midjourney.com/app/jobs/53c570b9-3cc2-48c5-9fe0-8d855cfbeb34/). 40 | -------------------------------------------------------------------------------- /blog/2023/2023-04-24-managing-community-health-files-and-templates-with-a-github-repository.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: Managing Community Health Files and Templates with a .github Repository 3 | tags: [github] 4 | authors: BekahHW 5 | slug: managing-community-health-files-and-templates-with-a-github-repository 6 | description: "I collect open source projects like some people collect discord servers. To be accurate, I have 525." 7 | --- 8 | 9 | I collect open source projects like some people collect discord servers. To be accurate, I have 525 repositories. Now, before you yell at me, many of those are from my bootcamp lessons when I was learning to code. But I’ve been known to start and stop projects more than once. What I _have_ learned through that experience is the importance of consistency. If you’re in an organization that has multiple repositories, you might find yourself adding the same files over and over–files like the CODE_OF_CONDUCT.md, Pull Request (PR) and Issue templates, and CONTRIBUTING.md. As developers, adding these files repeatedly starts to feel like we’re violating [DRY code principles](https://en.wikipedia.org/wiki/Don%27t_repeat_yourself). Fortunately, the .github repository can help solve this problem. 10 | 11 | 12 | 13 | ## What is a `.github` Repo? 14 | A `.github` repository is a special type of repository in GitHub that allows maintainers to store community health files and templates for their projects. 15 | 16 | > Community Health files promote the well-being of the community and focus on communication, documentation, supporting members through a code of conduct, and community recognition. 17 | 18 | The `.github` repository–found at `https://github.com//.github`- can house the community health files for your organization as the default files. According to [GitHub](https://github.blog/changelog/2019-02-21-organization-wide-community-health-files/), “While the file itself won’t appear in the file browser or Git history for each repository, it will be surfaced throughout developers’ workflows, such as when opening a new issue or when viewing the Community Profile, just as if it were committed to the repository directly.” 19 | 20 | 21 | ![Screenshot of the open-sauced/.github repo](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/i41566ytubxwkz60kjh7.png) 22 | 23 | Using a `.github` repository, allows maintainers to efficiently manage the files and templates that are important for their project's workflow and community and ensure consistency throughout the organization's repositories. So what do you add to the `.github` repository? One example is a Pull Request Template since they’re often standard across repos. 24 | 25 | ## How to Add a PR Template 26 | 27 | Adding a PR template to your `.github`repository is straightforward. First, navigate to the repository in question and click on the "Create new file" button. Next, in the file name field, type `.github/PULL_REQUEST_TEMPLATE.md`. 28 | 29 | In the main text field, you can add the content of your PR template. This can include prompts for information such as the purpose of the PR, the changes made, any potential issues or concerns, and any additional context or resources that may be helpful–check out ours [here](https://github.com/open-sauced/.github/blob/main/.github/PULL_REQUEST_TEMPLATE.md). You can also use markdown to format the template, making it more readable and easier to understand. 30 | 31 | Once you have added your PR template, click the "Commit new file" button to save it to your repository. Now, every time a contributor opens a new PR, they will be prompted to use the template you created. 32 | 33 | ## Considerations for Maintainers 34 | 35 | When creating a PR template, keep in mind that the template is easy to read and understand. Remember, the template is supposed to make things easier for you and the contributors. What information do you need to be able to review the PR more efficiently? What information can guide a new contributor through writing a PR for the first time? 36 | 37 | Finally, the beauty of using one template for all your repositories is that if you decide to update it, you only need to do that in one location. As your project evolves and new requirements emerge, you may find that the template needs to be revised or you might feedback from contributors and other maintainers, and make changes as needed to ensure that the PR template remains effective and useful. If you're interested in more content on PRs, check out [Writing Your First Pull Request: Tips, Best Practices, and AI-Powered Tools for Success](https://dev.to/opensauced/writing-your-first-pull-request-tips-best-practices-and-ai-powered-tools-for-success-3bg9) and [How to Create a Good Pull Request Template (and Why You Should Add Gifs)](https://dev.to/opensauced/how-to-create-a-good-pull-request-template-and-why-you-should-add-gifs-4i0l). -------------------------------------------------------------------------------- /blog/2023/2023-05-01-the-power-of-pair-programming-benefits-types-and-tips.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: "The Power of Pair Programming: Benefits, Types, and Tips" 3 | tags: [] 4 | authors: BekahHW 5 | slug: the-power-of-pair-programming-benefits-types-and-tips 6 | description: "Learn about the benefits, types, and tips of pair programming in software development, including increased code quality, collaboration, and learning opportunities. Join the Virtual Coffee challenge this May and improve your pairing skills!" 7 | --- 8 | 9 | Pairing is more than just coding with someone else. Pairing is about communication, teaching, learning, positive reinforcements, and growing. This is why at Virtual Coffee, we’re challenging our members to practice their pairing in the month of May and we’re inviting everyone at Dev to join us too! 10 | 11 | Before you start, we recommend you take a look at [Martin Fowler’s article On Pair Programming](https://martinfowler.com/articles/on-pair-programming.html). 12 | 13 | 14 | 15 | ## What is Pair Programming? 16 | Pair programming is a technique used in software development where two or more programmers work together on the same task. The two programmers switch between two roles: the driver, who is actively writing the code, and the navigator, who is observing the driver's work and providing guidance, feedback, and ideas. 17 | 18 | The value of pair programming comes from continuously communicating with each other, discussing the code being written, suggesting improvements, and debugging any issues together. Increased code quality, reduced errors, improved collaboration and communication, and enhanced learning opportunities are some of the benefits of pairing up. 19 | 20 | ### Types of Pair Programming 21 | There’s more than one way to pair program, so if you’ve tried one way and didn’t find it helpful, there are other approaches you can take, including: 22 | 23 | - Driver-Navigator Pair Programming: The most common type of pair programming, where one person (the driver) writes the code while the other person (the navigator) reviews the code and provides feedback. 24 | - Ping-Pong Pair Programming: In this type of pair programming, one person writes a test case and the other person writes the code to pass the test. The partners then swap roles and repeat the exercise. 25 | - Mob programming: a collaborative pairing approach where a group of developers work together on a single task. In mob programming, one person usually acts as the driver, writing the code, while the rest of the group act as navigators, providing feedback, suggesting improvements, and discussing ideas. The group continuously collaborates, switching roles frequently and communicating throughout the process. (At Virtual Coffee, we might call this co-working room pairing 😉) 26 | - Chaos programming: Everyone works on a codebase at the same time, using tools like VSCode Live. Not ideal for most work environments, this can be the quickest way to produce code under a time constraint like a hackathon. 27 | 28 | ## Ways to get started 29 | If you want to pair, but you're not sure what to pair on, here are some ideas to get you started: 30 | 31 | - **A project that you need some help on.** By pairing with someone else, you can share ideas, troubleshoot issues, and gain a fresh perspective. 32 | - **An open source issue.** Pairing on an open-source issue can be a great way to contribute to the community and improve your coding skills. It can also be an opportunity to work with experienced developers who can offer valuable feedback. 33 | - **A LeetCode problem.** LeetCode is a platform that offers coding challenges to improve your algorithmic problem-solving skills. Pairing on a LeetCode problem is a fun and challenging way to improve your coding skills and work with someone else. 34 | 35 | ## Pair Programming Resources 36 | ### Live Coding Tools 37 | - [Duckly](https://duckly.com/) 38 | - [Tuple](https://tuple.app/) 39 | - [VSCode liveshare](https://code.visualstudio.com/blogs/2017/11/15/live-share) 40 | - Zoom Screen sharing 41 | 42 | ### Live Collaboration/Whiteboarding Tools 43 | - [Excalidraw](https://excalidraw.com/) 44 | - [Miro](https://miro.com/) 45 | 46 | Pair programming is an effective way to improve code quality, foster collaboration, and promote continuous learning. By challenging ourselves to improve our pairing skills this month, we can grow as developers and improve our coding skills. If you'd like to recommend a resource for pair programming, you can add them to [this discussion](https://github.com/Virtual-Coffee/virtualcoffee.io/discussions/516). If you’d like to participate along with us, let us know in the comments below and we’ll tag you in our check-ins! 47 | -------------------------------------------------------------------------------- /blog/2023/2023-05-30-exploring-imaginary-worlds.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: Exploring Imaginary Worlds 3 | tags: [] 4 | authors: BekahHW 5 | slug: exploring-imaginary-worlds 6 | description: "Discover the link between open source and science fiction in our blog series. Join us as we delve into the imaginative worlds crafted by authors, the impact of open source on collaborative world-building, and the creative contributions of fans. Explore the convergence of fiction and technology, and uncover the transformative power of open source in shaping science fiction narratives." 7 | --- 8 | 9 | Before coming into tech, I spent ten years teaching college English. I've also written a couple of science fiction screenplays. To say that I'm fascinated by the power of storytelling would be an understatement. It's no surprise to me that science fiction has made an impact on open source and vice versa. So every Monday for the next three weeks, I'll have a post inspired by that relationship to hopefully inspire you. 10 | 11 | 12 | 13 | Science fiction has the remarkable ability to transport us to imaginary worlds filled with advanced technology, new societies, and inspiring ideas. For this post, let's take a look at some notable science fiction works embracing the concept of open source-from post-scarcity societies to virtual reality realms. 14 | 15 | ## Virtual Reality: Inspired by *Snow Crash* 16 | Neal Stephenson's novel *Snow Crash* introduced the concept of the Metaverse, a virtual reality universe accessible to all used for gaming, work, and socializing. The Metaverse-as we might know it in real life-is a virtual world being built by a variety of companies, including Facebook, Microsoft, and Sony. This visionary idea has influenced the development of open source virtual reality platforms like [Mozilla Hubs](https://hubs.mozilla.com/). Many of the OSS projects inspired by *Snow Crash* create immersive and collaborative virtual spaces that can be explored, built upon, and customized by users. 17 | 18 | ## Artificial Intelligence: Inspired by *The Culture* 19 | In Iain M. Banks' *Culture* series, artificial intelligence governs a post-scarcity society. The Minds, highly advanced AIs, serve as benevolent overseers, managing resources and ensuring a harmonious existence. This vision inspired open source AI projects like [TensorFlow](https://github.com/tensorflow). Many of these initiatives seek to democratize AI technology and create an accessible and positive space, like the AI-driven society in *The Culture*. 20 | 21 | ## Holographic Displays: Inspired by Star Wars 22 | The iconic holographic displays seen in the Star Wars saga have influenced the development of open source holographic projection technologies. Projects like [Looking Glass](https://lookingglassfactory.com/) and [Holovect](https://lookingglassfactory.com/) aim to bring 3D holographic displays into our everyday lives. By leveraging OSS principles, these projects allow for collaboration and innovation. 23 | 24 | ## Voice Recognition and Virtual Assistants: Inspired by Star Trek 25 | The voice-activated computer systems and virtual assistants seen in the Star Trek series have inspired real-life open source projects like [Mycroft AI](https://github.com/MycroftAI) and OpenAI's GPT models. These initiatives focus on creating open source voice recognition and virtual assistant technologies that can be freely accessed, modified, and integrated into various applications. The aim of these projects, like the Star Trek computer, is to create an interactive, natural, and intuitive technological experience. 26 | 27 | ## Robotics: Inspired by Isaac Asimov's Works 28 | Isaac Asimov's science fiction stories, particularly his Robot series, introduced the concept of humanoid robots governed by the Three Laws of Robotics. These narratives have influenced open source robotic platforms like ROS (Robot Operating System) and Arduino. These projects provide a framework for developing and controlling robots, fostering growth in the robotics community. 29 | 30 | Science fiction inspires and shapes our technological advancements. From virtual reality to artificial intelligence, holographic displays to voice recognition, and robotics to virtual assistants, science fiction has not only ignited our imagination but also motivated open source communities to bring these ideas to life. If you want to find more open source projects inspired by AI, check out OpenSauced's [Open Source AI insights](https://insights.opensauced.pizza/ai/) and check out the series. -------------------------------------------------------------------------------- /blog/2023/2023-06-01-understanding-why-pull-requests-get-rejected-in-open-source-projects.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: Understanding Why Pull Requests Get Rejected in Open Source Projects 3 | tags: [] 4 | authors: BekahHW 5 | slug: understanding-why-pull-requests-get-rejected-in-open-source-projects 6 | description: "Uncover the common reasons why pull requests face rejection in open source projects. Explore misalignment with project goals, code quality issues, testing shortcomings, communication challenges, licensing violations, and the impact of duplicative or outdated changes. Enhance your understanding of open source collaboration and increase the chances of having your contributions accepted." 7 | --- 8 | 9 | One of the reasons I love open source is because of the collaboration, community, and growth that often happens. Part of that growth includes having your pull request (PR) rejected. In fact, I think we should embrace this as part of the learning experience. To fully learn, you need to understand why your PR was rejected and what you can do to increase your chances of having your contributions accepted the next time you submit a PR. Below you'll find some of the reasons PRs are rejected. 10 | 11 | 12 | 13 | ## Misalignment with Project Goals 14 | I like to think of open source projects like a puzzle. Pull requests that are out of sync with the project's objectives are like a misplaced puzzle. Each pull request should contribute meaningfully to the larger picture the project is trying to achieve. Make sure you take the time to understand the project's scope, roadmap, and guidelines, so your changes fit into the project's vision. 15 | 16 | ## Lack of Code Quality 17 | Sometimes our code isn't strong enough to be merged in. Think of it like a foundation of a building. You want quality materials, and strong craftsmanship to ensure the strength of the building. Code that doesn't follow established conventions, lacks proper documentation, or contains bugs can undermine the stability and maintainability of the project. To build a solid structure write clean, readable code, adhere to coding standards, and provide comprehensive documentation if necessary. 18 | 19 | ## Insufficient Testing 20 | Often, projects require passing tests before a PR can be merged in. Submitting a pull request without testing is like releasing a product without quality control checks. Testing ensures the reliability of your changes and helps identify and prevent potential issues. Think of testing as stress-testing your contribution to guarantee it can hold up to real-world scenarios. 21 | 22 | ## Poor Communication 23 | Communication holds open source projects together. Submitting a pull request without a clear description or failing to address reviewer feedback is like sending a letter without an address or not responding to an email. Your ability to communicate demonstrates whether or not you'd be a good teammate, repeat contributor, or community member. Some tips for maintaining positive community include: provide context for your changes, respond to comments constructively, and demonstrate your willingness to collaborate effectively. 24 | 25 | ## Violation of Licensing or Legal Issues 26 | Including code that violates licensing restrictions or raises legal concerns in your pull request will result in an automatic rejection. Although I haven't personally seen this happen, it's worth noting and emphasizing the importance of respecting the project's chosen license and any legal requirements. 27 | 28 | ## Duplicate PRs or Outdated Changes 29 | This is one of the most common reasons I've seen issues or PRs rejected. Before creating a PR, ask to be assigned an issue to avoid both circumstances. If you want to raise an issue, check the project's existing issues and pull requests. Stay up to date on the repository and keep your fork up-to-date with the main branch of the project. 30 | 31 | It's ok to not have your PR merged in. It might not feel great, but it's part of the journey. And thinking of it as a learning experience that will guide your next PR or the revisions of your current PR, is an important part of that process. If you have questions about the open source journey, check out [opensauced.pizza](https://opensauced.pizza/) or check out our [Intro to Open Source course](https://github.com/open-sauced/intro) today. -------------------------------------------------------------------------------- /blog/2023/2023-06-12-from-inspiration-to-impact.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: From Inspiration to Impact 3 | tags: [] 4 | authors: BekahHW 5 | slug: from-inspiration-to-impact 6 | description: "Explore the relationship between open source and science fiction. From bringing sci-fi gadgets to life with open source hardware to blurring the lines between fiction and interactive gaming experiences, discover how these two realms inspire and shape each other." 7 | --- 8 | 9 | Welcome back to our final post in this series about Open Source in Science Fiction. We've looked at imaginary worlds inspiring real-world innovation, and real-life concepts inspiring science fiction. In this last post, we'll dive into the impact of open source in science fiction and the influence on the genre and tech landscape. 10 | 11 | 12 | 13 | ## Collaborative World-Building: Transforming the Science Fiction Landscape 14 | 15 | Science fiction has long been a genre of creativity, with authors crafting intricate worlds and universes. But in many cases, it's been a solitary experience. If we apply open source principles, we can open up new worlds together. 16 | 17 | Collaborative platforms like [World Anvil](https://www.worldanvil.com/) allow writers and contributors to collaborate to build shared universes. These platforms allow for crowd-sourced contributions, where writers, artists, and fans collaborate to develop detailed mythologies, create expansive maps, and flesh out the intricate histories of their fictional worlds. Open source storytelling tools like [Twine](https://twinery.org/) provide accessible platforms for interactive storytelling, enabling anyone to contribute to the narrative tapestry. Through open source world-building, science fiction has become a collective endeavor, resulting in richer and more immersive fictional universes. 18 | 19 | ## Open Source Fan Fiction: A Creative Continuation 20 | 21 | I don't know about you, but I know some really passionate science fiction fans. So passionate, in fact, that they're eager to contribute to the story. Open source has taken fan fiction to new heights, empowering fans to engage in creative collaborations and expand upon existing science fiction narratives. 22 | 23 | Projects like [Star Wars Uncut](https://www.starwarsuncut.com/) are a great example of open source fan fiction. In this ambitious undertaking, Star Wars fans from around the world were invited to recreate the original Star Wars movie scene by scene. Each contributor brought their unique style, interpretation, and creativity to the project, resulting in a stunning mosaic of fan-made scenes that captured the collective love for the franchise. Open source fan fiction allows fans to not only explore their creativity but also to contribute to the ongoing development of science fiction worlds. 24 | 25 | ## Ethical Considerations in Open Source Science Fiction 26 | 27 | With the fast-paced technology landscape, we need to be continually mindful about the ethical considerations that arise. While open source fosters collaboration and innovation, it also raises important questions about copyright, intellectual property, and inclusivity within the genre. 28 | 29 | How do creators navigate the fine line between encouraging fan participation and protecting their original work? Open source fan fiction often operates in a legal gray area, and it is essential for creators and fans to respect the boundaries set by copyright laws while finding ways to embrace collaboration. 30 | 31 | My past experience as a college English teacher collided with my life in tech for this series, and I couldn't be more excited to see the continued collisions between open source and science fiction in the future. If you're ready to start your own journey into open source and make an impact, get started with [OpenSauced](https://insights.opensauced.pizza/) today. 32 | 33 | -------------------------------------------------------------------------------- /blog/2023/2023-07-27-open-source-abcs-bug.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: "Open Source ABCs: Bug" 3 | tags: [] 4 | authors: BekahHW 5 | slug: open-source-abcs-bug-1god 6 | description: "Join our #100DaysOfOSS blog series as we explore the world of Open Source Software (OSS) from A to Z! Every week, we'll discuss two new letters of the English alphabet. Share your thoughts, ideas, and favorite OSS projects for each letter. Let's celebrate the power of open source together! " 7 | --- 8 | 9 | Welcome to Day 5 of our [#100DaysOfOSS series](https://dev.to/opensauced/100daysofoss-growing-skills-and-real-world-experience-3o5k). Until October 31, we'll be doing Open Source Software (OSS) terms from A to Z. We'll be diving into a different letter of the English alphabet, uncovering OSS concepts, and sharing our thoughts on them. 10 | 11 | Today, we're covering the letter "B" for Bug. 12 | 13 | 14 | 15 | **Bug**: A bug refers is an error, flaw, or defect in code that impacts the proper functioning of the software. Open-source projects often rely on community contributions to identify and fix bugs. 16 | 17 | Now, we want to hear from you! What other OSS terms can you think of that start with the letter "B"? 18 | 19 | Remember to use the hashtag #100DaysOfOSS if you share on social media, and don't forget to tag us [@saucedopen](https://twitter.com/saucedopen) so we can follow along. 20 | -------------------------------------------------------------------------------- /blog/2023/2023-08-01-open-source-abcs-collaboration.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: "Open Source ABCs: Collaboration" 3 | tags: [] 4 | authors: BekahHW 5 | slug: open-source-abcs-collaboration 6 | description: "Join our #100DaysOfOSS blog series as we explore the world of Open Source Software (OSS) from A to Z! Every week, we'll discuss two new letters of the English alphabet. Share your thoughts, ideas, and favorite OSS projects for each letter. Let's celebrate the power of open source together! " 7 | --- 8 | 9 | Welcome to Day 9 of our [#100DaysOfOSS series](https://dev.to/opensauced/100daysofoss-growing-skills-and-real-world-experience-3o5k). Until October 31, we'll be doing Open Source Software (OSS) terms from A to Z. We'll be diving into a different letter of the English alphabet, uncovering OSS concepts, and sharing our thoughts on them. 10 | 11 | Today, we're covering the letter "C" for Collaboration. 12 | 13 | 14 | 15 | **Collaboration**: Collaboration is at the heart of open source. It's the cooperative effort among developers, contributors, and users to improve and enhance open source projects through shared knowledge and contributions. 16 | 17 | Now, we want to hear from you! What other OSS terms can you think of that start with the letter "C"? 18 | 19 | Remember to use the hashtag #100DaysOfOSS if you share on social media, and don't forget to tag us [@saucedopen](https://twitter.com/saucedopen) so we can follow along. 20 | -------------------------------------------------------------------------------- /blog/2023/2023-08-03-open-source-abcs-documentation.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: "Open Source ABCs: Documentation" 3 | tags: [] 4 | authors: BekahHW 5 | slug: open-source-abcs-documentation 6 | description: "Join our #100DaysOfOSS blog series as we explore the world of Open Source Software (OSS) from A to Z! Every week, we'll discuss two new letters of the English alphabet. Share your thoughts, ideas, and favorite OSS projects for each letter. Let's celebrate the power of open source together! " 7 | --- 8 | 9 | Welcome to Day 11 of our [#100DaysOfOSS series](https://dev.to/opensauced/100daysofoss-growing-skills-and-real-world-experience-3o5k). Until October 31, we'll be doing Open Source Software (OSS) terms from A to Z. We'll be diving into a different letter of the English alphabet, uncovering OSS concepts, and sharing our thoughts on them. 10 | 11 | Today, we're covering the letter "D" for Documentation. 12 | 13 | 14 | 15 | **Documentation**: Documentation plays an important role in open-source projects. It includes guidelines, tutorials, and explanations that help users and developers understand and utilize the software effectively. 16 | 17 | Now, we want to hear from you! What other OSS terms can you think of that start with the letter "D"? 18 | 19 | Remember to use the hashtag #100DaysOfOSS if you share on social media, and don't forget to tag us [@saucedopen](https://twitter.com/saucedopen) so we can follow along. 20 | -------------------------------------------------------------------------------- /blog/2023/2023-08-08-open-source-abcs-evolution.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: "Open Source ABCs: Evolution" 3 | tags: [] 4 | authors: BekahHW 5 | slug: open-source-abcs-evolution 6 | description: "Join our #100DaysOfOSS blog series as we explore the world of Open Source Software (OSS) from A to Z! Every week, we'll discuss two new letters of the English alphabet. Share your thoughts, ideas, and favorite OSS projects for each letter. Let's celebrate the power of open source together! " 7 | --- 8 | 9 | Welcome to our [#100DaysOfOSS series](https://dev.to/opensauced/100daysofoss-growing-skills-and-real-world-experience-3o5k). Until October 31, we'll be doing Open Source Software (OSS) terms from A to Z. We'll be diving into a different letter of the English alphabet, uncovering OSS concepts, and sharing our thoughts on them. 10 | 11 | Today, we're covering the letter "E" for Evolution. 12 | 13 | 14 | 15 | **Evolution**: Open-source projects are known for their evolutionary nature. As more contributors join, the software evolves over time, incorporating new features, improvements, and bug fixes. 16 | 17 | Now, we want to hear from you! What other OSS terms can you think of that start with the letter "E"? 18 | 19 | Remember to use the hashtag #100DaysOfOSS if you share on social media, and don't forget to tag us [@saucedopen](https://twitter.com/saucedopen) so we can follow along. -------------------------------------------------------------------------------- /blog/2023/2023-08-10-open-source-abcs-fork.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: "Open Source ABCs: Fork" 3 | tags: [] 4 | authors: BekahHW 5 | slug: open-source-abcs-fork 6 | description: "Join our #100DaysOfOSS blog series as we explore the world of Open Source Software (OSS) from A to Z! Every week, we'll discuss two new letters of the English alphabet. Share your thoughts, ideas, and favorite OSS projects for each letter. Let's celebrate the power of open source together! " 7 | --- 8 | 9 | Welcome to our [#100DaysOfOSS series](https://dev.to/opensauced/100daysofoss-growing-skills-and-real-world-experience-3o5k). Until October 31, we'll be doing Open Source Software (OSS) terms from A to Z. We'll be diving into a different letter of the English alphabet, uncovering OSS concepts, and sharing our thoughts on them. 10 | 11 | Today, we're covering the letter "F" for Fork. 12 | 13 | 14 | 15 | **Fork**: Forking is the process of creating a new independent project from an existing open-source project. It allows developers to take the existing codebase in a new direction or make modifications while maintaining the original project's core principles. 16 | 17 | Now, we want to hear from you! What other OSS terms can you think of that start with the letter "F"? 18 | 19 | Remember to use the hashtag #100DaysOfOSS if you share on social media, and don't forget to tag us [@saucedopen](https://twitter.com/saucedopen) so we can follow along. -------------------------------------------------------------------------------- /blog/2023/2023-08-15-open-source-abcs-git.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: "Open Source ABCs: Git" 3 | tags: [] 4 | authors: BekahHW 5 | slug: open-source-abcs-git 6 | description: "Join our #100DaysOfOSS blog series as we explore the world of Open Source Software (OSS) from A to Z! Every week, we'll discuss two new letters of the English alphabet. Share your thoughts, ideas, and favorite OSS projects for each letter. Let's celebrate the power of open source together! " 7 | --- 8 | 9 | Welcome to our [#100DaysOfOSS series](https://dev.to/opensauced/100daysofoss-growing-skills-and-real-world-experience-3o5k). Until October 31, we'll be doing Open Source Software (OSS) terms from A to Z. We'll be diving into a different letter of the English alphabet, uncovering OSS concepts, and sharing our thoughts on them. 10 | 11 | Today, we're covering the letter "G" for Git. 12 | 13 | 14 | 15 | **Git**: Git is a popular distributed version control system widely used in open-source projects. It enables developers to collaborate, track changes, and manage source code efficiently. 16 | 17 | If you want to learn more about what you can do with Git, check out my [Git it! Series](https://dev.to/bekahhw/series/2398). 18 | 19 | Now, we want to hear from you! What other OSS terms can you think of that start with the letter "G"? 20 | 21 | Remember to use the hashtag #100DaysOfOSS if you share on social media, and don't forget to tag us [@saucedopen](https://twitter.com/saucedopen) so we can follow along. -------------------------------------------------------------------------------- /blog/2023/2023-08-21-open-source-abcs-issues.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: "Open Source ABCs: Issues" 3 | tags: [] 4 | authors: BekahHW 5 | slug: open-source-abcs-issues 6 | description: "Join our #100DaysOfOSS blog series as we explore the world of Open Source Software (OSS) from A to Z! Every week, we'll discuss two new letters of the English alphabet. Share your thoughts, ideas, and favorite OSS projects for each letter. Let's celebrate the power of open source together! " 7 | --- 8 | 9 | Welcome to our [#100DaysOfOSS series](https://dev.to/opensauced/100daysofoss-growing-skills-and-real-world-experience-3o5k). Until October 31, we'll be doing Open Source Software (OSS) terms from A to Z. We'll be diving into a different letter of the English alphabet, uncovering OSS concepts, and sharing our thoughts on them. 10 | 11 | Today, we're covering the letter "I" for Issues. 12 | 13 | 14 | 15 | **Issues**: An issue is a problem, suggestion, or task related to a repository that is tracked and managed using issue tracking systems. 16 | 17 | An issue can have a wide range of topics, including: 18 | 19 | **Bugs**: A bug report documents when software behaves unexpectedly, crashes, or produces incorrect results. Bug reports help developers identify, replicate, and fix the issues. 20 | 21 | **Feature Requests**: Users or contributors can propose new features, enhancements, or changes to the code or software. These requests are used to discuss and prioritize potential additions to the project. 22 | 23 | **Enhancements**: Similar to feature requests, these suggestions aim to improve the software's functionality, performance, or user experience. They might not introduce entirely new features but can involve refining existing ones. 24 | 25 | **Documentation**: Issues related to improving or clarifying the software's documentation. This could involve fixing errors, adding missing information, or making instructions more understandable. 26 | 27 | Now, we want to hear from you! What other OSS terms can you think of that start with the letter "I"? 28 | 29 | Remember to use the hashtag #100DaysOfOSS if you share on social media, and don't forget to tag us [@saucedopen](https://twitter.com/saucedopen) so we can follow along. -------------------------------------------------------------------------------- /blog/2023/2023-08-23-open-source-abcs-javascript.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: "Open Source ABCs: JavaScript" 3 | tags: [] 4 | authors: BekahHW 5 | slug: open-source-abcs-javascript 6 | description: "Join our #100DaysOfOSS blog series as we explore the world of Open Source Software (OSS) from A to Z! Every week, we'll discuss two new letters of the English alphabet. Share your thoughts, ideas, and favorite OSS projects for each letter. Let's celebrate the power of open source together! " 7 | --- 8 | 9 | Welcome to our [#100DaysOfOSS series](https://dev.to/opensauced/100daysofoss-growing-skills-and-real-world-experience-3o5k). Until October 31, we'll be doing Open Source Software (OSS) terms from A to Z. We'll be diving into a different letter of the English alphabet, uncovering OSS concepts, and sharing our thoughts on them. 10 | 11 | Today, we're covering the letter "J" for JavaScript. 12 | 13 | 14 | 15 | **JavaScript**: JavaScript is a widely used programming language in open-source, front-end web development. It allows developers to add behavior, interactivity, and functionality to web pages, making them more engaging and responsive. 16 | 17 | Now, we want to hear from you! What other OSS terms can you think of that start with the letter "J"? 18 | 19 | Remember to use the hashtag #100DaysOfOSS if you share on social media, and don't forget to tag us [@saucedopen](https://twitter.com/saucedopen) so we can follow along. -------------------------------------------------------------------------------- /blog/2023/2023-08-28-open-source-abcs-kernel.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: "Open Source ABCs: Kernel" 3 | tags: [] 4 | authors: BekahHW 5 | slug: open-source-abcs-kernel 6 | description: "Join our #100DaysOfOSS blog series as we explore the world of Open Source Software (OSS) from A to Z! Every week, we'll discuss two new letters of the English alphabet. Share your thoughts, ideas, and favorite OSS projects for each letter. Let's celebrate the power of open source together! " 7 | --- 8 | 9 | Welcome to our [#100DaysOfOSS series](https://dev.to/opensauced/100daysofoss-growing-skills-and-real-world-experience-3o5k). Until October 31, we'll be doing Open Source Software (OSS) terms from A to Z. We'll be diving into a different letter of the English alphabet, uncovering OSS concepts, and sharing our thoughts on them. 10 | 11 | Today, we're covering the letter "K" for Kernel. 12 | 13 | 14 | 15 | **Kernel**: The kernel is the core component of an operating system. Several open-source operating systems, such as Linux, have a kernel that allows developers to contribute and modify the system's functionality. 16 | 17 | Now, we want to hear from you! What other OSS terms can you think of that start with the letter "K"? 18 | 19 | Remember to use the hashtag #100DaysOfOSS if you share on social media, and don't forget to tag us [@saucedopen](https://twitter.com/saucedopen) so we can follow along. -------------------------------------------------------------------------------- /blog/2023/2023-09-04-open-source-abcs-meritocracy.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: "Open Source ABCs: Meritocracy" 3 | tags: [] 4 | authors: BekahHW 5 | slug: open-source-abcs-meritocracy 6 | description: "Join our #100DaysOfOSS blog series as we explore the world of Open Source Software (OSS) from A to Z! Every week, we'll discuss two new letters of the English alphabet. Share your thoughts, ideas, and favorite OSS projects for each letter. Let's celebrate the power of open source together! " 7 | --- 8 | 9 | Welcome to our [#100DaysOfOSS series](https://dev.to/opensauced/100daysofoss-growing-skills-and-real-world-experience-3o5k). Until October 31, we'll be doing Open Source Software (OSS) terms from A to Z. We'll be diving into a different letter of the English alphabet, uncovering OSS concepts, and sharing our thoughts on them. 10 | 11 | Today, we're covering the letter "M" for Meritocracy. 12 | 13 | 14 | 15 | **Meritocracy**: Open-source communities often operate on a meritocratic model, where contributors' influence and decision-making authority are based on their demonstrated skills, knowledge, and contributions to the project. 16 | 17 | Now, we want to hear from you! What other OSS terms can you think of that start with the letter "M"? 18 | 19 | Remember to use the hashtag #100DaysOfOSS if you share on social media, and don't forget to tag us [@saucedopen](https://twitter.com/saucedopen) so we can follow along. -------------------------------------------------------------------------------- /blog/2023/2023-09-06-open-source-abcs-network.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: "Open Source ABCs: Network" 3 | tags: [] 4 | authors: BekahHW 5 | slug: open-source-abcs-network 6 | description: "Join our #100DaysOfOSS blog series as we explore the world of Open Source Software (OSS) from A to Z! Every week, we'll discuss two new letters of the English alphabet. Share your thoughts, ideas, and favorite OSS projects for each letter. Let's celebrate the power of open source together! " 7 | --- 8 | 9 | Welcome to our [#100DaysOfOSS series](https://dev.to/opensauced/100daysofoss-growing-skills-and-real-world-experience-3o5k). Until October 31, we'll be doing Open Source Software (OSS) terms from A to Z. We'll be diving into a different letter of the English alphabet, uncovering OSS concepts, and sharing our thoughts on them. 10 | 11 | Today, we're covering the letter "N" for Network. 12 | 13 | 14 | 15 | **Network**: Open source is a connected community of developers, users, and contributors who share ideas, exchange knowledge, mentor each other, and collaborate on improving the software. 16 | 17 | Now, we want to hear from you! What other OSS terms can you think of that start with the letter "N"? 18 | 19 | Remember to use the hashtag #100DaysOfOSS if you share on social media, and don't forget to tag us [@saucedopen](https://twitter.com/saucedopen) so we can follow along. -------------------------------------------------------------------------------- /blog/2023/2023-09-11-open-source-abcs-open-data.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: "Open Source ABCs: open data" 3 | tags: [] 4 | authors: BekahHW 5 | slug: open-source-abcs-open-data 6 | description: "Join our #100DaysOfOSS blog series as we explore the world of Open Source Software (OSS) from A to Z! Every week, we'll discuss two new letters of the English alphabet. Share your thoughts, ideas, and favorite OSS projects for each letter. Let's celebrate the power of open source together! " 7 | --- 8 | 9 | Welcome to our [#100DaysOfOSS series](https://dev.to/opensauced/100daysofoss-growing-skills-and-real-world-experience-3o5k). Until October 31, we'll be doing Open Source Software (OSS) terms from A to Z. We'll be diving into a different letter of the English alphabet, uncovering OSS concepts, and sharing our thoughts on them. 10 | 11 | I thought about using [OpenSauced](https://opensauced.pizza/) and talking about how we're redefining contributions in open source, how we're supporting maintainers creating healthy projects, and how we're fostering a healthy ecosystem for open source, but instead I'll go with open data for the letter "o". 12 | 13 | 14 | **Open Data**: Open-source projects sometimes produce open data, which refers to freely accessible and shareable datasets. Open data enables researchers, analysts, and other developers to use and build upon existing information. 15 | 16 | Now, we want to hear from you! What other OSS terms can you think of that start with the letter "o"? 17 | 18 | Remember to use the hashtag #100DaysOfOSS if you share on social media, and don't forget to tag us [@saucedopen](https://twitter.com/saucedopen) so we can follow along. -------------------------------------------------------------------------------- /blog/2023/2023-09-13-open-source-abcs-pull-request.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: "Open Source ABCs: Pull Request" 3 | tags: [] 4 | authors: BekahHW 5 | slug: open-source-abcs-pull-request 6 | description: "Join our #100DaysOfOSS blog series as we explore the world of Open Source Software (OSS) from A to Z! Every week, we'll discuss two new letters of the English alphabet. Share your thoughts, ideas, and favorite OSS projects for each letter. Let's celebrate the power of open source together! " 7 | --- 8 | 9 | Welcome to our [#100DaysOfOSS series](https://dev.to/opensauced/100daysofoss-growing-skills-and-real-world-experience-3o5k). Until October 31, we'll be doing Open Source Software (OSS) terms from A to Z. We'll be diving into a different letter of the English alphabet, uncovering OSS concepts, and sharing our thoughts on them. 10 | 11 | Today, we're covering the letter "P" for Pull Request. 12 | 13 | 14 | **Pull Request**: In open-source development, a pull request is a proposed code change submitted by a contributor. It allows others to review, discuss, and potentially merge the changes into the main codebase. 15 | 16 | If you want to learn more about Pull Requests, check out some of our resources: 17 | - [Understanding Why Pull Requests Get Rejected in Open Source Projects](https://dev.to/opensauced/understanding-why-pull-requests-get-rejected-in-open-source-projects-1jd0) 18 | - [Writing Your First Pull Request: Tips, Best Practices, and AI-Powered Tools for Success](https://dev.to/opensauced/writing-your-first-pull-request-tips-best-practices-and-ai-powered-tools-for-success-3bg9) 19 | - [How to Create a Good Pull Request Template (and Why You Should Add Gifs)](https://dev.to/opensauced/how-to-create-a-good-pull-request-template-and-why-you-should-add-gifs-4i0l) 20 | - [Tips for getting your Pull Request reviewed on GitHub](https://dev.to/opensauced/tip-for-getting-your-pull-request-reviewed-on-github-2b7c) 21 | 22 | Now, we want to hear from you! What other OSS terms can you think of that start with the letter "P"? 23 | 24 | Remember to use the hashtag #100DaysOfOSS if you share on social media, and don't forget to tag us [@saucedopen](https://twitter.com/saucedopen) so we can follow along. -------------------------------------------------------------------------------- /blog/2023/2023-09-18-open-source-abcs-quality-assurance.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: "Open Source ABCs: Quality Assurance" 3 | tags: [] 4 | authors: BekahHW 5 | slug: open-source-abcs-quality-assurance 6 | description: "Join our #100DaysOfOSS blog series as we explore the world of Open Source Software (OSS) from A to Z! Every week, we'll discuss two new letters of the English alphabet. Share your thoughts, ideas, and favorite OSS projects for each letter. Let's celebrate the power of open source together! " 7 | --- 8 | 9 | Welcome to our [#100DaysOfOSS series](https://dev.to/opensauced/100daysofoss-growing-skills-and-real-world-experience-3o5k). Until October 31, we'll be doing Open Source Software (OSS) terms from A to Z. We'll be diving into a different letter of the English alphabet, uncovering OSS concepts, and sharing our thoughts on them. 10 | 11 | Today, we're covering the letter "Q" for Quality Assurance. 12 | 13 | 14 | 15 | **Quality assurance** in open-source projects involves testing, reviewing, and ensuring the software meets the desired standards. Community members often contribute to testing and reporting issues to improve the software's quality. 16 | 17 | Now, we want to hear from you! What other OSS terms can you think of that start with the letter "Q"? 18 | 19 | Remember to use the hashtag #100DaysOfOSS if you share on social media, and don't forget to tag us [@saucedopen](https://twitter.com/saucedopen) so we can follow along. -------------------------------------------------------------------------------- /blog/2023/2023-09-20-open-source-abcs-repository.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: "Open Source ABCs: Repository" 3 | tags: [] 4 | authors: BekahHW 5 | slug: open-source-abcs-repository 6 | description: "Join our #100DaysOfOSS blog series as we explore the world of Open Source Software (OSS) from A to Z! Every week, we'll discuss two new letters of the English alphabet. Share your thoughts, ideas, and favorite OSS projects for each letter. Let's celebrate the power of open source together! " 7 | --- 8 | 9 | Welcome to our [#100DaysOfOSS series](https://dev.to/opensauced/100daysofoss-growing-skills-and-real-world-experience-3o5k). Until October 31, we'll be doing Open Source Software (OSS) terms from A to Z. We'll be diving into a different letter of the English alphabet, uncovering OSS concepts, and sharing our thoughts on them. 10 | 11 | Today, we're covering the letter "R" for Repository. 12 | 13 | 14 | 15 | **Repository**: A repository is a central location where open-source projects store their source code, documentation, and related files. Platforms like GitHub and GitLab provide hosting services for repositories. 16 | 17 | If you want to practice creating your own repository, check out [Practice Contributing with VS Code](https://opensauced.pizza/learn/#/04-tools-to-be-successful?id=practicing-contributing-with-vs-code) in our intro to open source course. 18 | 19 | Now, we want to hear from you! What other OSS terms can you think of that start with the letter "R"? 20 | 21 | Remember to use the hashtag #100DaysOfOSS if you share on social media, and don't forget to tag us [@saucedopen](https://twitter.com/saucedopen) so we can follow along. -------------------------------------------------------------------------------- /blog/2023/2023-09-27-open-source-abcs-transparency.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: "Open Source ABCs: Transparency" 3 | tags: [] 4 | authors: BekahHW 5 | slug: open-source-abcs-transparency 6 | description: "Join our #100DaysOfOSS blog series as we explore the world of Open Source Software (OSS) from A to Z! Every week, we'll discuss two new letters of the English alphabet. Share your thoughts, ideas, and favorite OSS projects for each letter. Let's celebrate the power of open source together! " 7 | --- 8 | 9 | Welcome to our [#100DaysOfOSS series](https://dev.to/opensauced/100daysofoss-growing-skills-and-real-world-experience-3o5k). Until October 31, we'll be doing Open Source Software (OSS) terms from A to Z. We'll be diving into a different letter of the English alphabet, uncovering OSS concepts, and sharing our thoughts on them. 10 | 11 | 12 | 13 | Today, we're covering the letter "T" for Transparency. 14 | 15 | **Transparency**: Transparency helps to build trust in open source. Because open source is a collaborative effort, with people from all over the world coming together to develop and maintain projects, transparency is one of the most important strengths of the open source community. 16 | 17 | Now, we want to hear from you! What other OSS terms can you think of that start with the letter "T"? 18 | 19 | Remember to use the hashtag #100DaysOfOSS if you share on social media, and don't forget to tag us [@saucedopen](https://twitter.com/saucedopen) so we can follow along. -------------------------------------------------------------------------------- /blog/2023/2023-10-02-open-source-abcs-upstream.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: "Open Source ABCs: Upstream" 3 | tags: [] 4 | authors: BekahHW 5 | slug: open-source-abcs-upstream 6 | description: "Join our #100DaysOfOSS blog series as we explore the world of Open Source Software (OSS) from A to Z! Every week, we'll discuss two new letters of the English alphabet. Share your thoughts, ideas, and favorite OSS projects for each letter. Let's celebrate the power of open source together! " 7 | --- 8 | 9 | Welcome to our [#100DaysOfOSS series](https://dev.to/opensauced/100daysofoss-growing-skills-and-real-world-experience-3o5k). Until October 31, we'll be doing Open Source Software (OSS) terms from A to Z. We'll be diving into a different letter of the English alphabet, uncovering OSS concepts, and sharing our thoughts on them. 10 | 11 | Today, we're covering the letter "U" for Upstream. 12 | 13 | 14 | 15 | 16 | **Upstream**: The original project or source from which a particular fork is taken. Contributing back to the upstream project is often considered a best practice. 17 | 18 | Now, we want to hear from you! What other OSS terms can you think of that start with the letter "U"? 19 | 20 | Remember to use the hashtag #100DaysOfOSS if you share on social media, and don't forget to tag us [@saucedopen](https://twitter.com/saucedopen) so we can follow along. -------------------------------------------------------------------------------- /blog/2023/2023-10-03-how-to-be-a-top-contributor-this-hacktoberfest.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: How to be a Top Contributor this Hacktoberfest 3 | tags: [] 4 | authors: BekahHW 5 | slug: how-to-be-a-top-contributor-this-hacktoberfest 6 | description: "Discover how to be a top new contributor this Hacktoberfest. " 7 | --- 8 | 9 | If you’ve read any of my previous posts, you know that I’m a fan of redefining contributions. But during Hacktoberfest, there’s more competition for the magic four pull requests (PRs). If we think of it like [Moneyball for engineers](https://opensauced.pizza/blog/moneyball-for-engineers), except limiting it to Hacktoberfest, we realize it's not about hitting home runs; it's about getting on base consistently and making strategic plays that contribute to the overall win. So, how do you become a top contributor during Hacktoberfest? 10 | 11 | 12 | 13 | ![Ham yelling play ball](https://media.giphy.com/media/QtoG24OvehcYUhf7mI/giphy.gif) 14 | 15 | ## Five Pillars of Hacktoberfest Contribution 16 | 1. Deep Dives Over Quick Fixes 17 | Take time to look through the repository’s issues. It doesn’t matter if you get a PR in the first week or all four on October 31. Take time to plan your approach and to understand the repository. Look at issues with the `help wanted` tag or issues that are in the backlog. It’s also important to think about the time that you have to devote to Hacktoberfest. If you know that you only have time to dive deeply into one issue, then plan around that. Also, consider submitting to the same open source organization to reduce the cognitive load of navigating different contribution guidelines. Engaging deeply with a project and its codebase will make you stand out. 18 | 19 | 2. Think Like a Maintainer 20 | Put yourself in the shoes of a maintainer. Your PR isn’t just code; it's work that someone else has to review, test, and integrate. Make their life easy by following the guidelines, writing documentation as necessary, and testing thoroughly before submitting. Consider making your PR a `draft` PR until you’ve thoroughly reviewed your contribution. I recommend taking a day away from your PR and then coming back to it with a fresh perspective, looking it over and retesting before asking for a review. As part of that, increase your communication with maintainers by providing clear commit messages and staying within the scope of your issue. Lastly, don’t nitpick your way into a PR. For example, don’t change the structure of part of the documentation or codebase just for the sake of getting a PR. 21 | 22 | 3. Be Proactive, Not Reactive 23 | Don't wait for someone to tag an issue as help wanted. Remember, [good first issues don’t exist](https://opensauced.pizza/blog/good-first-issues-dont-exist), but writing your own can be the best solution. Before you do that, though, make sure you search existing issues to ensure that it hasn’t been raised before. Proactive could also mean that you’re answering questions in the community, triaging issues, and providing feedback on PRs if that help is wanted. 24 | 25 | 4. Build, Don’t Break 26 | Avoid changing parts of a project just because you think they could be better. Instead, focus on building upon existing structures and improving them in a way that aligns with the project’s vision and current codebase. 27 | 28 | 5. Broaden Your Horizon 29 | Contributing to open source isn’t just about code. Engage with the community, write insightful issues, or craft blog posts that help others understand the project better. Features like [OpenSauced's highlights](https://insights.opensauced.pizza/feed) can help you showcase these broader contributions. 30 | 31 | ## Your Soft Skills Checklist 32 | - Active Listening: Before diving in, read the project's documentation, understand its goals, and understand the process. 33 | - Communication: Take time to check-in with maintainers, especially if you’re struggling or know that there’s a timeline that you can’t make. If you have a question and you’ve been unable to find the answer after looking, ask for help. 34 | - Receptiveness to Feedback: You’ll likely receive comments on your pull requests. Feedback is a learning opportunity. Make necessary changes and iterate based on the feedback. Check out [Understanding Why Pull Requests Get Rejected in Open Source Projects](https://dev.to/opensauced/understanding-why-pull-requests-get-rejected-in-open-source-projects-1jd0) and [Writing Your First Pull Request: Tips, Best Practices, and AI-Powered Tools for Success](https://dev.to/opensauced/writing-your-first-pull-request-tips-best-practices-and-ai-powered-tools-for-success-3bg9) for more best practices on submitting PRs. 35 | 36 | If there’s one takeaway from becoming a top contributor during Hacktoberfest, it’s that it’s important to be thoughtful as a contributor. Take the time to understand, think through your process, and clearly communicate with maintainers. 37 | -------------------------------------------------------------------------------- /blog/2023/2023-10-04-open-source-abcs-version-control.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: "Open Source ABCs: Version Control" 3 | tags: [] 4 | authors: BekahHW 5 | slug: open-source-abcs-version-control 6 | description: "Join our #100DaysOfOSS blog series as we explore the world of Open Source Software (OSS) from A to Z! Every week, we'll discuss two new letters of the English alphabet. Share your thoughts, ideas, and favorite OSS projects for each letter. Let's celebrate the power of open source together! " 7 | --- 8 | 9 | Welcome to our [#100DaysOfOSS series](https://dev.to/opensauced/100daysofoss-growing-skills-and-real-world-experience-3o5k). Until October 31, we'll be doing Open Source Software (OSS) terms from A to Z. We'll be diving into a different letter of the English alphabet, uncovering OSS concepts, and sharing our thoughts on them. 10 | 11 | Today, we're covering the letter "V" for Version Control. 12 | 13 | 14 | 15 | 16 | **Version Control**: Version control ensures code changes are tracked and managed efficiently. Version control systems like Git allow multiple contributors to work on the same codebase without conflicts. It helps in maintaining the history of the project, making it easier to understand past decisions, roll back changes, and contribute meaningfully. 17 | 18 | Now, we want to hear from you! What other OSS terms can you think of that start with the letter "V"? 19 | 20 | Remember to use the hashtag #100DaysOfOSS if you share on social media, and don't forget to tag us [@saucedopen](https://twitter.com/saucedopen) so we can follow along. -------------------------------------------------------------------------------- /blog/2023/2023-10-09-open-source-abcs-workflow.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: "Open Source ABCs: Workflow" 3 | tags: [] 4 | authors: BekahHW 5 | slug: open-source-abcs-workflow 6 | description: "Join our #100DaysOfOSS blog series as we explore the world of Open Source Software (OSS) from A to Z! Every week, we'll discuss two new letters of the English alphabet. Share your thoughts, ideas, and favorite OSS projects for each letter. Let's celebrate the power of open source together! " 7 | --- 8 | 9 | Welcome to our [#100DaysOfOSS series](https://dev.to/opensauced/100daysofoss-growing-skills-and-real-world-experience-3o5k). Until October 31, we'll be doing Open Source Software (OSS) terms from A to Z. We'll be diving into a different letter of the English alphabet, uncovering OSS concepts, and sharing our thoughts on them. 10 | 11 | Today, we're covering the letter "W" for Workflow. 12 | 13 | 14 | 15 | 16 | **Workflow**: The process and steps involved in contributing to or maintaining an open-source project. This can include issue tracking, code reviews, merge requests, project management, and deployment. 17 | 18 | Now, we want to hear from you! What other OSS terms can you think of that start with the letter "W"? 19 | 20 | Remember to use the hashtag #100DaysOfOSS if you share on social media, and don't forget to tag us [@saucedopen](https://twitter.com/saucedopen) so we can follow along. -------------------------------------------------------------------------------- /blog/2023/2023-10-12-open-source-abcs-xenial-xerus.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: "Open Source ABCs: Xenial Xerus" 3 | tags: [] 4 | authors: BekahHW 5 | slug: open-source-abcs-xenial-xerus 6 | description: "Join our #100DaysOfOSS blog series as we explore the world of Open Source Software (OSS) from A to Z! Every week, we'll discuss two new letters of the English alphabet. Share your thoughts, ideas, and favorite OSS projects for each letter. Let's celebrate the power of open source together! " 7 | --- 8 | 9 | Welcome to our [#100DaysOfOSS series](https://dev.to/opensauced/100daysofoss-growing-skills-and-real-world-experience-3o5k). Until October 31, we'll be doing Open Source Software (OSS) terms from A to Z. We'll be diving into a different letter of the English alphabet, uncovering OSS concepts, and sharing our thoughts on them. 10 | 11 | Today, we're covering the letter "X" for Xenial Xerus. 12 | 13 | 14 | 15 | 16 | **Xenial Xerus**: Ubuntu versions are named alphabetically with an adjective and an animal, and "Xenial Xerus" is the name for the 16.04 release. 17 | 18 | This was a hard one! Now, we want to hear from you! What other OSS terms can you think of that start with the letter "X"? 19 | 20 | Remember to use the hashtag #100DaysOfOSS if you share on social media, and don't forget to tag us [@saucedopen](https://twitter.com/saucedopen) so we can follow along. -------------------------------------------------------------------------------- /blog/2023/2023-10-16-open-source-abcs-yaml--yml.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: "Open Source ABCs: YAML & YML" 3 | tags: [] 4 | authors: BekahHW 5 | slug: open-source-abcs-yaml-yml 6 | description: "Join our #100DaysOfOSS blog series as we explore the world of Open Source Software (OSS) from A to Z! Every week, we'll discuss two new letters of the English alphabet. Share your thoughts, ideas, and favorite OSS projects for each letter. Let's celebrate the power of open source together! " 7 | --- 8 | 9 | Welcome to our [#100DaysOfOSS series](https://dev.to/opensauced/100daysofoss-growing-skills-and-real-world-experience-3o5k). Until October 31, we'll be doing Open Source Software (OSS) terms from A to Z. We'll be diving into a different letter of the English alphabet, uncovering OSS concepts, and sharing our thoughts on them. 10 | 11 | Today, we're covering the letter "Y" and the difference between YAML and YML. 12 | 13 | 14 | 15 | 16 | - **YAML**: Stands for "YAML Ain't Markup Language." YAML refers to the data serialization standard itself. When you're talking about the language or the format, "YAML" is the term to use. 17 | 18 | - **YML**: A file extension commonly used for files that contain YAML-formatted data. 19 | 20 | You might see .yml or .yaml as file extensions. Both indicate that the file contains YAML-formatted data. 21 | Both .yml and .yaml are acceptable file extensions, and there's no difference in functionality. It's generally a good practice to stay consistent with the file extension you choose for a given project. 22 | 23 | Now, we want to hear from you! What other OSS terms can you think of that start with the letter "Y"? 24 | 25 | Remember to use the hashtag #100DaysOfOSS if you share on social media, and don't forget to tag us [@saucedopen](https://twitter.com/saucedopen) so we can follow along. -------------------------------------------------------------------------------- /blog/2023/2023-10-18-open-source-abcs-zsh.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: "Open Source ABCs: Zsh" 3 | tags: [] 4 | authors: BekahHW 5 | slug: open-source-abcs-zsh 6 | description: "Join our #100DaysOfOSS blog series as we explore the world of Open Source Software (OSS) from A to Z! Every week, we'll discuss two new letters of the English alphabet. Share your thoughts, ideas, and favorite OSS projects for each letter. Let's celebrate the power of open source together! " 7 | --- 8 | 9 | Welcome to our [#100DaysOfOSS series](https://dev.to/opensauced/100daysofoss-growing-skills-and-real-world-experience-3o5k). With this post, we've officially gone from A to Z! 10 | 11 | Today, we're covering the letter "Z." 12 | 13 | 14 | 15 | 16 | - **Zsh**: Zsh, also known as the Z Shell, is an interactive login shell for Unix-like operating systems. It includes many features to improve productivity, such as advanced tab completion, spelling correction, and a flexible plugin and theming system. Zsh is often favored by developers for its customization capabilities and is commonly used in open source software development environments. 17 | 18 | Now, we want to hear from you! What other OSS terms can you think of that start with the letter "Z"? 19 | 20 | Remember to use the hashtag #100DaysOfOSS if you share on social media, and don't forget to tag us [@saucedopen](https://twitter.com/saucedopen) so we can follow along. -------------------------------------------------------------------------------- /blog/2024/2024-01-09-take-the-first-step-the-open-source-game.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: "Take the First Step: the Open Source Game" 3 | tags: [] 4 | authors: BekahHW 5 | slug: take-the-first-step-the-open-source-game 6 | description: "Getting started in open source is like learning a strategy game. It takes time to get started, but if you start small, you'll make progress." 7 | --- 8 | 9 | There's been a lot of talk recently about how to get into open source. I think part of the challenge of breaking into open source is overthinking it. 10 | 11 | [https://x.com/BekahHW/status/1742920548353745068?s=20](https://x.com/BekahHW/status/1742920548353745068?s=20) 12 | 13 | We need to reframe how we think about starting with contributing. Getting started with open source can feel intimidating, but it's just like learning a new game with complex rules. You wouldn't jump straight into a game without reading the instructions. In the same way, you shouldn't overwhelm yourself with open source. Take it step-by-step. 14 | 15 | 16 | 17 | 18 | ## Step 1: Reading the Rulebook (Understanding Basics) 19 | 20 | Think of it like mastering a new strategy board game. First, you'd read the rules and understand the basic mechanics. In open source, this is like reading the project's README or CONTRIBUTING files. The rulebook guides you on how to play the game, and these files provide share specifics on how to get started, what's expected, and how to contribute effectively. 21 | 22 | 23 | [![open source repos for beginners](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/jm20g8x7wy774y0hb52y.png)](https://app.opensauced.pizza/pages/BekahHW/655/dashboard) 24 | 25 | 26 | 27 | ## Step 2: Setting Up the Board (Environment Setup) 28 | 29 | Next, you'd set up the board, making sure everything is in place. In open source, this means setting up your environment – installing the project, configuring your development setup, and ensuring everything is in place and working as expected. It's like correctly placing all the pieces on the board, so you can play the right way. 30 | 31 | ## Step 3: Observing and Learning (Studying and Engaging) 32 | 33 | Before jumping into the game, it can be helpful to observe others playing. Take some time to watch experienced players and see how they strategize, move their pieces, and respond to the game's dynamics. This is like studying code examples, reviewing past contributions, and understanding the project's history in open source. Engaging with the community through forums, discussions, and tutorials is like sitting next to seasoned players and learning from their moves and strategies. 34 | 35 | ## Step 4: Practice Rounds (Making Initial Contributions) 36 | 37 | Now you're ready for a practice round. In open source, these are your initial contributions. They might be microcontributions – asking a clarifying question in an issue, answering questions in the community, writing a blog post about the project, or adding an issue when you find a bug. Each of these steps is like moving a piece on the board, getting a feel for the game, and understanding how your actions affect the overall project. 38 | 39 | Don't be discouraged if it takes a few "practice rounds" before you feel comfortable. Every time you contribute, you'll refine your strategies, understand the game's deeper goals (contributing to the project's mission), and build your confidence. 40 | 41 | ## Step 5: Refining Strategies (Growing Your Skills) 42 | 43 | The more you play, the better you get. Each contribution helps you understand the project's deeper goals, like each move in the game helps you to understand better how to win. You'll start to learn how to anticipate issues, collaborate effectively, and contribute more meaningfully. As your confidence grows, so will your impact on the project. 44 | 45 | ## Step 6: Versatility and Adaptability (Exploring Other Projects) 46 | 47 | And just like in board games, where players might take breaks or try different games, in open source, you check out other projects. But the skills you've learned – collaboration, problem-solving, coding – stay with you, making you a more versatile and adaptable contributor. 48 | 49 | ## A Community of Players (Open Source Community) 50 | 51 | Remember, you're not playing alone. The open source community has players of all levels, from beginners to experts, and everyone plays a part in the game's progression. There's always room for new players, and the community grows with contributors of all levels. For more ways to get started, check out our [#100DaysOfOSS Challenge](https://opensauced.pizza/docs/community/100-days-of-oss/). 52 | -------------------------------------------------------------------------------- /blog/2024/2024-02-24-what-would-your-dream-home-automation-look-like.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: What would your dream home automation look like? 3 | tags: [] 4 | authors: BekahHW 5 | slug: create-your-dream-home-automation-freedom-flexibility-with-home-assistant 6 | description: " Home Assistant offers freedom, flexibility & privacy for your smart home. Automate anything, integrate everything, & join a vibrant community." 7 | --- 8 | 9 | *Today is day 24 of my 29 Days of Open Source Alternatives series, where I'll be exploring open source alternatives to proprietary software in the categories of Game Development and Multimedia, Development Tools and Platforms, Productivity and Collaboration Tools, and more. If you'd like to see the list of the open source alternatives I'll be covering this month, head over to my [29 Days of Open Source Alts Page](https://oss.fyi/oss-alts).* 10 | 11 |
12 | 13 | I don't know about you, but when I was a kid I was into science fictions and imagined I'd be living in a Jetson's world. 14 | 15 | 16 | 17 | 18 | ![Jetsons's Gif](https://media.giphy.com/media/v1.Y2lkPTc5MGI3NjExczIxc213Y2x6MXBzd2p5cTQ5c3YxYTl4d250dG4zejRzYXMxdmRsYiZlcD12MV9pbnRlcm5hbF9naWZfYnlfaWQmY3Q9Zw/20Mr9uJLkWfqWDs6Ul/giphy.gif) 19 | 20 | That hasn't exactly happened, but that doesn't mean that science fiction hasn't become a reality in our lives today. Now that we have so many automation tools out there, our tools can anticipate our needs. Take our homes, for example. You can have automations for adjusting your lights, temperature, and even entertainment systems depending on the time of day. This is just the beginning. Imagine some of these scenarios: 21 | 22 | - A morning routine that gently wakes you up by gradually increasing light and playing soothing music. 23 | - A security system that automatically arms when you leave and disarms when you return, including real-time notifications. 24 | - A movie night experience that dims the lights, sets the perfect temperature, and even starts your streaming service of choice. 25 | 26 | ## Comparisons 27 | 28 | | Feature | Home Assistant | SmartThings | Hubitat | Amazon Alexa | Google Home | 29 | |--------------------------|----------------|-------------|---------|--------------|-------------| 30 | | Open-source | Yes | No | Yes | No | No | 31 | | Local-first | Yes | No | Yes | No | No | 32 | | Number of supported devices | 1000+ | 200+ | 1700+ | Many | Many | 33 | | Custom automations | Yes | Yes | Yes | Limited | Limited | 34 | | Voice control | Yes | Yes | Yes | Yes | Yes | 35 | | Price | Free | $12/month | $12/month | Free | Free | 36 | 37 | 38 | ## Why Open Source Home Automation is Important 39 | 40 | - Freedom: You're not by limited by a single product's offerings. 41 | - Customization: You can create automations that match your lifestyle. 42 | - Privacy: You can keep your data on your own devices, not in the cloud. 43 | - Beyond the Basics: You can make your dreams come true but building your own projects. For example, you can build custom dashboards to monitor your home's energy usage or create voice commands for your smart devices or connect and personalize your Home Assistant to third-party services, from weather forecasts to traffic updates. 44 | 45 | ## Spotlight: Home Assistant 46 | 47 | Home Assistant is open source, giving you complete control over your data and devices. They also have a thriving and lively community of contributors. 48 | 49 | ![Home Assistant Dashboard](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/3qerc3wpzibjxvadfn88.png) 50 | 51 | You can see over the last thirty days how evenly distributed the contributors are: 52 | 53 | 54 | ![Contributor graph](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/qcrzivvtx0q9rj5jgpd9.png) 55 | 56 | We also see a lot of open source activity from their community members, with the top repository being home-assistant/core 57 | 58 | 59 | ![Contributor activity](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/a6wteai9mbds7h0p9awy.png) 60 | 61 | *You can check out the full contributor insight page [here](https://app.opensauced.pizza/lists/53ddbc37-285f-481b-ad82-9a608e8957f3/activity)* 62 | 63 | ### All Time Stats 64 | 65 | With their all time stats, we can see there are a lot of contributors and users of the product. According to their GitHub page, they have 2.3k users. 66 | 67 | - Stars: 67.4k stars 68 | - Watching: 1.3k 69 | - Forks: 27.2k 70 | 71 | ## Last thoughts 72 | 73 | Are you using home automation? What types of automations do you have set up? What devices are you using? 74 | 75 | I can't find the video right now, but one of my favorite use-cases is for opening up a chicken coop door to let the chickens out when the sun comes up. -------------------------------------------------------------------------------- /blog/2024/2024-02-25-open-source-ai-glasses-would-you-wear-them.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: "Open Source AI Glasses: Would you wear them?" 3 | tags: [] 4 | authors: BekahHW 5 | slug: open-source-ai-glasses-would-you-wear-them 6 | description: "Open Source AI glasses, Frame has potential to be an interesting product in the AR world. But does it hold up?" 7 | --- 8 | 9 | *Today is day 25 of my 29 Days of Open Source Alternatives series, where I'll be exploring open source alternatives to proprietary software in the categories of Game Development and Multimedia, Development Tools and Platforms, Productivity and Collaboration Tools, and more. If you'd like to see the list of the open source alternatives I'll be covering this month, head over to my [29 Days of Open Source Alts Page](https://oss.fyi/oss-alts).* 10 | 11 |
12 | 13 | There have been some really exciting launches in the AR/VR world lately. These are exciting times to rethink how we learn, interact, work, and find entertainment. But of course there are questions of cost, privacy, isolation, and more. For most of the world, a new AR/VR Tool probably won't be in our house any time soon. But what about the open source competition. Is it *really* competition or something you should be keeping your eye on? Today we're looking at Frame by Brilliant.xyz. 14 | 15 | 16 | 17 | 18 | ## Community Projects 19 | 20 | From what I can tell from their documentation and their app, the features are largely dependent on the users. Brilliant supplies the hardware and the API for both their glasses and monocle and it's up to you to decide where to take it. Some notable projects include: 21 | 22 | - [Teleprompter for Google Slides](https://github.com/milesprovus/Monocle-Teleprompter) by milesprovus 23 | - [A heads up display workout app](https://github.com/simonevetere/monocle) by simonevetere and jdc-cunningham 24 | - [An app to curate questions during Q&A sessions and display to AR lens](https://github.com/ironmanfpv/Question-Visualizer-for-Monocle) by ironmanfpv 25 | 26 | You'll notice that all of these are for their Monocle Device. Their Frame product is currently on pre-order only, shipping starting next month. 27 | 28 | > Frame is designed to be worn as a pair of glasses with a suite of AI capabilities out of the box. Whether your daily pair of specs or workbench prototyping tool, Frame is ready for the journey. 29 | 30 | As a glasses wearer, myself, it was nice to see that they have options to fit your prescription (although my vision is so bad that they don't have an option :sob:) 31 | 32 | ## Open Source Advantage? 33 | 34 | We don't see a ton of open source support over the last 30 days. 35 | 36 | ![Brilliant repo dashboards](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/wcvzkyy50x0ig8y78wu6.png) 37 | 38 | Because there doesn't seem to be one central repo, it's a little hard to judge the popularity, but throughout the repos, we see that there are only 2 contributors. So let's take a look at what they're up to in the Brilliant Repos. 39 | 40 | ![Contributor Graphs](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/gf470rsf9bgkbj0lwfkx.png) 41 | 42 | [Their activity overview](https://app.opensauced.pizza/lists/bb61b5e0-eee3-4a3a-a648-bd035b5db3e7/activity) zoomed in on the Brilliant repos shows some engagement in 5 repositories. This means there haven't been many substantial updates in any of the repositories over the last month. 43 | 44 | ## Takeaways 45 | 46 | There hasn't been a lot of movement across their open source projects, but does that mean we shouldn't watch what they're doing? No. With their new product shipping in April, it will be interesting to see if there's more activity and engagement then. There's a lot of things still coming soon with their product, including documentation. Hopefully, that will give a clearer picture of what to expect with their new releases and how to get involved in their open source projects. 47 | 48 | 49 | 50 | -------------------------------------------------------------------------------- /blog/2024/2024-02-27-would-you-use-an-open-source-personal-finance-app.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: Would you use an open source personal finance app? 3 | tags: [] 4 | authors: BekahHW 5 | slug: would-you-use-an-open-source-personal-finance-app 6 | description: Open Source personal finance apps provide transparency and community, but would you use them? 7 | --- 8 | 9 | *Today is day 27 of my 29 Days of Open Source Alternatives series, where I'll be exploring open source alternatives to proprietary software in the categories of Game Development and Multimedia, Development Tools and Platforms, Productivity and Collaboration Tools, and more. If you'd like to see the list of the open source alternatives I'll be covering this month, head over to my [29 Days of Open Source Alts Page](https://oss.fyi/oss-alts).* 10 | 11 | On January 1, 2024, Mint, the personal finance app - acquired by Intuit in 2009 - shut down. If you're not familiar with Mint, it allowed users to see multiple accounts, to track spending, savings, and create budgets. Mint was one of the top personal finance apps, and despite Intuit encouraging users to move over to their other product, Credit Karma, the broken trust didn't exactly sit well with a lot of users. Although there are other alternatives, like YNAB, Pocketguard, and Oportun, choosing a personal finance app is, well, a personal decision, and not one to be taken lightly. All of these are closed-source, which lack the transparency that you might want from a finance app. Maybe Finance becomes and interesting alternative because of it's open source nature. 12 | 13 | 14 | 15 | ## Maybe Finance 16 | 17 | > [https://github.com/maybe-finance/maybe](https://github.com/maybe-finance/maybe) 18 | 19 | 20 | It's worth starting with the state of Maybe Finance right now. If you go to their website, you're greeted with this message. 21 | 22 | ![Message from Maybe about open sourcing](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/7bjj4m63ty7pqpe3ah3v.png) 23 | 24 | I'm not sure if that conveys confidence or if it sends up red flags for users - that's for you to decide. Let's look at some reasons that you might want to use an open source finance product. 25 | 26 | 1. **Privacy & Security**: Open source code allows you to see how the app works and ensures your data isn't being used for hidden purposes. 27 | 2. **Customization & Control**: You can potentially modify the app's code to fit your specific needs and preferences. 28 | 3. **Community & Collaboration**: There's an active community where users can contribute ideas, report bugs, and help improve the app together. 29 | 4. **Cost-Effective**: For Maybe Finance, specifically, "The goal is to let you run the app yourself, for free, and use it to manage your own finances and eventually offer a hosted version of the app for a small monthly fee." 30 | 31 | Of course, there are reasons you may not want to use an open source personal finance app, including: 32 | 33 | 1. Limited support 34 | 2. Required technical knowledge 35 | 3. Concerns over stability and reliability 36 | 37 | But what kind of open source project is Maybe? Let's take a look: 38 | 39 | ![Maybe Dashboard](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/0rnsc7hza5viagbtua34.png) 40 | 41 | *Check out the full dashboard [here](https://app.opensauced.pizza/pages/BekahHW/1229/dashboard).* 42 | 43 | We see a high activity rate over the last thirty days, with about an average size PR velocity. Although their star history seems to be leveling out, you can see from this chart that they've built kind of a staircase, so it's worth watching to see what's coming next. I imagine those spikes correspond with an announcement or activity. 44 | 45 | [![Star History Chart](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/w0k91uyg7yhf3c4hfev4.png)](https://star-history.com/#maybe-finance/maybe&Date) 46 | 47 | Metrics for their project over its lifespan include: 48 | 49 | - Stars: 25k 50 | - Watching: 148 51 | - Forks: 1.9k 52 | Contributors: 59 53 | 54 | We can take a look at what the breakdown over the last thirty days looks like as well: 55 | 56 | ![last thirty days metrics](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/fykgsk1i5ufrcitzzzo2.png) 57 | 58 | What's most interesting to me, is that we see an equal stars to forks ratio over the last thirty days. That tells me that not only are people interested in following the project to see how it progresses, but people are also interested in contributing, which is ideal. 59 | 60 | So what do you think? Would you use an open source personal finance app? 61 | -------------------------------------------------------------------------------- /blog/2024/2024-03-26-whats-the-difference-between-new-and-beginner-open-source-contributors.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: What's the Difference Between New and Beginner Open Source Contributors? 3 | tags: [] 4 | authors: BekahHW 5 | slug: whats-the-difference-between-new-and-beginner-open-source-contributors 6 | description: Understanding the difference between new and beginner contributors is important for both project maintainers and the contributors themselves. This post identifies some of the unique challenges and needs of these two types of contributors. 7 | --- 8 | 9 | There's a difference between new contributors and beginner contributors to open source, and it's important to understand the difference because it impacts the support needed for those contributors and the types of issues created. 10 | 11 | 12 | Before moving on, let's define the difference: 13 | 14 | **Beginner Contributor**: Someone who is new to open source and tech. Some of their challenges to contributing may include: a steep learning curve, understanding open source culture and best practices, completing pull requests in a timely manner. 15 | 16 | **New Contributor**: Someone who has never contributed to your repository before, but could be at any technical level. Some of the challenges they may face are unfamiliarity with the project's codebase, guidelines, and processes. 17 | 18 | ## Retaining Contributors 19 | 20 | One of the challenges facing open source maintainers is retaining contributors. But the *type* of contributor you retain is also important, and largely depends on the project's needs and bandwidth. 21 | 22 | ### Retaining Beginner Contributors 23 | 24 | Contributors who are beginners require more time and effort to support and sustain. Things you need to consider when retaining beginners are: 25 | 26 | 1. Do you have good, beginner-friendly issues? These are sometimes labeled as `good first issue` or `beginner-friendly`. 27 | 2. Does your project lend itself to issues for beginners? Sometimes a project's complexity or technical hurdles for running the project make it difficult to bring in beginners without substantial support. 28 | 3. Do you have the bandwidth to support beginners? More often than not, beginners will require more support. They'll need more feedback on their pull requests or on the issues they write. If you don't have the time to support them, it's okay to let them know. 29 | 30 | ### Retaining New Contributors 31 | 32 | New contributors have a variety of motivations for contributing, including: to learn something new, to solve a problem they have, to build their reputation, or because they're interested in the project. 33 | 34 | Things you should consider for retaining new contributors: 35 | 36 | 1. Do you have clear paths of communication? They should know how to contribute and who to talk to if they have questions. 37 | 2. Are their issues they can work on? More than once, I've had a maintainer ask me how to make their project more appealing to contributors and I've check out their projects that have no issues. Write issues that are clear and organized. They shouldn't be too large, and there should be a clear path to completion. 38 | 3. Do you have a community that's engaging? One of the big reasons contributors stick around is because they enjoy interacting with the maintainers or other community members. 39 | 40 | ## Understanding Your Bandwidth 41 | 42 | I've talked to a number of maintainers who have said they're looking for a solid 3-5 repeat contributors for their projects, and they don't want to advertise widely because they don't have the bandwidth to support beginner contributors. 43 | 44 | First of all, that's 100% ok. Not every project needs to support beginners. In fact, trying to support beginners when you don't have the bandwidth leads to burnout and frustration on both the maintainer and contributor side. 45 | 46 | There are plenty of projects out there that can and do support beginner contributors, and there are courses, like our [Intro to Contributing Course](https://opensauced.pizza/learn/#/) that provide learning opportunities to new contributors. 47 | 48 | Here's [a great post by @adiatiayu on involving external contributors with issues](https://dev.to/opensauced/collaborate-conquer-grow-mastering-the-art-of-issue-management-for-open-source-projects-49gi). 49 | 50 | ## Final Thoughts 51 | 52 | We all want to make sure that maintainers don't burnout, so we need to be aware of the challenges that occur with new and beginner contributors. The key is clearly communicating the needs of the project and for the maintainer and self-awareness on the part of contributors. 53 | 54 | What other considerations should open source projects look at when determining if they can support new or beginner contributors? -------------------------------------------------------------------------------- /blog/2024/2024-05-02-we-made-a-copilot-tool-for-you-to-unlock-the-power-of-git-history.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: We Made a Copilot Tool for you to Unlock the Power of Git History 3 | tags: [] 4 | authors: BekahHW 5 | slug: introducing-starsearch-unlock-the-copilot-for-git-history 6 | description: Copilot but for git history 7 | --- 8 | 9 | At OpenSauced, we are thrilled to announce our latest feature: **StarSearch**. It's not just about the commits; it's about the community, the contributions, and the connections in the open source ecosystem - and you can [join the waitlist now](https://app.opensauced.pizza/star-search/waitlist)! 10 | 11 | 12 | 13 | 14 | [![starsearch](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/9kie77pwx0q4b4rulg1p.png)](https://app.opensauced.pizza/star-search/waitlist) 15 | 16 | 17 | 18 | **StarSearch** is our AI-powered feature that provides in-depth insights into contributor history and activities, bringing transparency and a new depth of knowledge about open source projects. 19 | 20 | 21 | ## What Can You Discover with StarSearch? 22 | 23 | - Contributor Activities: Learn the details of contributions and contributors. 24 | - Key Contributors: Identify the key contributors to projects and ecosystems. 25 | - Work-Based Connections: Find potential collaborators based on their contributions to specific projects 26 | - Hidden Experts: Discover untapped talent in the ecosystem. 27 | 28 | ### A Solution to Sourcing Talent 29 | 30 | Recently, Adam Wathan of Tailwind CSS expressed a challenge: attracting applicants well-versed in a niche combination (Rust and Tailwind) despite offering competitive salaries. 31 | 32 | Inspired by this challenge, we asked ourselves, "Wouldn't it be cool if we built something to find this persona?" StarSearch allows you to get answers to your questions even when you don't have the context. The context for this question: most of the developers on the list work on front-end focused teams with an interest in developer performance. 33 | We’re not just another tool; we're here to redefine the meaning of open source. 34 | 35 | Let's uncover the stories behind the code together - [Join the Waitlist Today](https://oss.fyi/starsearch-waitlist) and share with your friends. 36 | -------------------------------------------------------------------------------- /blog/2024/2024-05-06-maintainer-monday-community-care.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: "Maintainer Monday: Community Care" 3 | tags: [] 4 | authors: BekahHW 5 | slug: maintainer-monday-community-care 6 | description: It's maintainer month and we're celebrating some of our favorite maintainers! 7 | --- 8 | 9 | Last week, we kicked off Maintainer Month with [Enhancing Support for Open Source Maintainers](https://opensauced.pizza/blog/enhancing-support-for-open-source-maintainers). Now, we're continuing our love of maintainers with our Maintainer Monday post, shouting out some of our favorite maintainers and their projects. 10 | 11 | 12 | 13 | 14 | This week, I'm choosing two maintainers from the X Spaces I've been doing for OpenSauced. I really learn a lot from my conversations with maintainers, but in both of these conversations I've returned to the wisdom they shared over and over again. Thank you, @danielroe and @bholmesdev for being guests and supporting the open source community. 15 | 16 | 17 | ## [Daniel Roe](https://oss.fyi/danielroe) 18 | 19 | Daniel brings his experience as a maintainer to Nuxt.js as leader of the core team. When we chatted, I really appreciated his focus on equipping other people to be able to grow and to support the project in different ways. Another part of the conversation that stood out to me was his desire to empower contributors. As part of that, he even offers time for contributors to book a call with him! 20 | 21 | - You can still listen to the space [here](https://x.com/saucedopen/status/1724448595158474836?s=46). 22 | - You can learn more about Nuxt, [here](https://oss.fyi/Nuxt) 23 | 24 | [![Nuxt stars, forks, PRs, and issues over 30 days](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/3rmbfy7fbcni0t6kjqc5.png)](https://oss.fyi/Nuxt) 25 | 26 | 27 | ## [Ben Holmes](https://oss.fyi/benholmes) 28 | 29 | Ben talked about being a Core maintainer for Astro and how he found that role. He shared a lot about how he sees the community and the importance of leaving a positive impact on the open source ecosystem. He shared his experience of shipping your personal open source projects without waiting for perfection. 30 | 31 | 32 | - You can still listen to the space [here](https://x.com/saucedopen/status/1704140208663355765?s=46) 33 | - You can learn more about Astro [here](https://oss.fyi/astro) 34 | 35 | [![Astro stars, forks, PRs, and issues over 30 days](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/w15hbse3xpoewp999ee7.png)](https://oss.fyi/astro) 36 | 37 | **Let us know who your favorite maintainers are so we can feature them this month!** 38 | 39 | ## Sneak Peek - Watching: 40 | 41 | We're about to launch a new feature called StarSearch - your copilot for git history - and you can see what it said about Daniel Roe in the teaser below or view the full gif [here](https://www.canva.com/design/DAGEG_vtojg/sHHNjMcKQEqrT4hLlcmWLw/edit?utm_content=DAGEG_vtojg&utm_campaign=designshare&utm_medium=link2&utm_source=sharebutton), and if you're interesting in beta testing, you can [sign up for the waiting list](https://oss.fyi/starsearch-waitlist) and share with your friends. 42 | 43 | ![gif of StarSearch reporting on Daniel Roe](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/v5s98rh5izq7nwbrvbyy.gif) -------------------------------------------------------------------------------- /blog/2024/2024-05-13-maintainer-monday.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: Maintainer Monday 3 | tags: [] 4 | authors: BekahHW 5 | slug: maintainer-monday 6 | description: It's maintainer month and we're celebrating some of our favorite maintainers! 7 | --- 8 | 9 | Last week, we kicked off Maintainer Month with [Enhancing Support for Open Source Maintainers](https://opensauced.pizza/blog/enhancing-support-for-open-source-maintainers). Now, we're continuing our love of maintainers with our Maintainer Monday post, shouting out some of our favorite maintainers and their projects. 10 | 11 | 12 | 13 | This week, I'm choosing another two maintainers from the X Spaces I've been doing for OpenSauced. Thank you, Amy Dutton and Nate Wienert for being guests and supporting the open source community. 14 | 15 | ## [Amy Dutton](https://oss.fyi/amydutton) 16 | 17 | Amy is a multi-talented Lead Maintainer on the RedwoodJS Core Team. She's kind, knowledgeable, and well-spoken, and a fantastic leader in the community. During our conversation, Amy shared the new [RedwoodJS Release that includes React Server Components](https://redwoodjs.com/blog/rsc-now-in-redwoodjs). She gave her insights on the importance of good developer experience and getting feedback from your users. She also talked about creating demos and projects as part of her work as a way to showcase what you can do with RedwoodJS. 18 | 19 | - You can still listen to the space [here](https://x.com/saucedopen/status/1772653649551921624?s=46). 20 | - You can learn more about Redwood, [here](https://oss.fyi/zMzSyFm). 21 | 22 | [![Redwood stars, forks, PRs, and issues over 30 days](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/rnsaajx3mtavdekhpqj2.png)](https://oss.fyi/zMzSyFm) 23 | 24 | ## [Nate Wienert](https://oss.fyi/natew) 25 | 26 | Nate is the creative force behind Tamagui, a fun and innovative UI kit. He combines his technical skills with a playful approach to design, making Tamagui a delightful experience for users and developers alike. In our chat, Nate discussed the challenges and joys of building and maintaining Tamagui, including finding sponsors for his project. He shared the importance of building something useful, being consistent, and the sharing the interesting things you learn along the way. 27 | 28 | - You can still listen to the space [here](https://twitter.com/i/spaces/1ynJOyvNNykKR). 29 | - You can learn more about Tamagui [here](https://app.opensauced.pizza/s/tamagui/tamagui) 30 | - You can check out the site for Tamagui [here](https://tamagui.dev/). 31 | 32 | [![Tamagui stars, forks, PRs, and issues over 30 days](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/805hdb0hi1xoz149ecxm.png)](https://app.opensauced.pizza/s/tamagui/tamagui?range=90) 33 | 34 | Thank you Amy and Nate for your support of the open source community! 35 | 36 | **Let us know who your favorite maintainers are so we can feature them this month!** 37 | 38 | We have some big events coming up next week with OpenSauced, including a Product Hunt Launch for [StarSearch](https://oss.fyi/starsearch-waitlist). Stay tuned for an exciting Maintainer month! 39 | 40 | -------------------------------------------------------------------------------- /blog/2024/2024-05-23-creating-open-source-connections.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: Creating Open Source Connections 3 | tags: [] 4 | authors: BekahHW 5 | slug: creating-open-source-connections 6 | description: Explore how StarSearch revolutionizes open source collaboration by connecting projects with top talent using AI-driven insights into GitHub events and contributor activities. 7 | --- 8 | 9 | As it stands today, the open source ecosystem can feel disconnected. Theoretically, we know that there are maintainers, contributors, and projects out there that are incredibly talented and innovative, but finding them can feel like searching for stars in a cloudy night sky. Sometimes you need to have that information – and fast – to be able to maintain your own projects. 10 | 11 | 12 | 13 | 14 | ## The Challenge of Open Source Connections 15 | 16 | Imagine you're at a tech company using cutting-edge technology. You need to upstream some important changes to ensure future compatibility but you find yourself hitting a wall. Who exactly should you reach out to? Who are the key contributors with the right expertise? Traditionally, this process would involve a lot of guesswork and detective work, looking through commit histories or issue discussions. Enter [StarSearch](https://app.opensauced.pizza/star-search), designed to change how we discover and connect with others in the open-source universe. With StarSearch, in just a few clicks, you’re able to identify key contributors skilled in that technology and maintainers who may have the answers you need. StarSearch isn’t just a tool; it’s your entry point into a more intimate, interconnected open-source community. 17 | 18 | 19 | ## Introducing StarSearch 20 | 21 | StarSearch leverages advanced analytics and AI, all fueled by real-time data from GitHub Events. StarSearch isn’t just about identifying who committed what; it’s about understanding the dynamics and interactions within the open source community. 22 | 23 | > **We’re live on [Product Hunt](https://www.producthunt.com/products/opensauced)! Join the conversation and share your thoughts.** 24 | 25 | ### Connecting with StarSearch 26 | 27 | Here’s how StarSearch addresses some of the common queries and needs within the community: 28 | 29 | - What type of pull requests has `{username}` worked on? 30 | - Who are the best developers that know `{technology}` and are interested in `{technology}`? 31 | - Who are the most prevalent contributors to the `{technology}` ecosystem? 32 | - Show me the lottery factor for contributors in the `{repository}` project? 33 | 34 | These questions can be the starting point for building stronger projects and communities, allowing us to find people with passion and expertise that we may have never connected with before. 35 | 36 | ## Learn More About StarSearch 37 | 38 | You can check out more about our approach and process, as well as the resources: 39 | 40 | - [Building a Copilot for Git History with pgvector and Timescale](https://www.timescale.com/blog/how-opensauced-is-building-a-copilot-for-git-history-with-pgvector-and-timescale/) 41 | - [How We Saved Thousands with Open Source AI Technologies](https://opensauced.pizza/blog/how-we-saved-thousands-of-dollars-deploying-low-cost-open-source-ai-technologies) 42 | - [Meet StarSearch: Your New Open Source Navigator](https://opensauced.pizza/blog/meet-starsearch) 43 | - [StarSearch Docs](https://opensauced.pizza/docs/features/star-search/) 44 | 45 | ### Watch our "What is StarSearch" Video 46 | [![what is starsearch](https://cdn.sanity.io/images/r7m53vrk/production/4e056c9d8482c034f03615093788099611ee8757-256x141.png?w=450)](https://www.youtube.com/watch?v=I3cS-u_gmDE) 47 | 48 | ## The Future of StarSearch 49 | 50 | StarSearch provides a nuanced view of the open-source landscape. It’s more than a tool; it’s a new way to navigate the open-source ecosystem, bringing clarity, connections, and community to our tooling and making the open source ecosystem feel more like a tightly knit community where everyone knows your name – and your code. And we're just getting started. We have big plans for the future of StarSearch. 51 | 52 | If you’re ready to find a new way to connect, [sign up for OpenSauced](https://app.opensauced.pizza/) and be among the first to explore the future of open-source collaboration with StarSearch today. 53 | 54 | -------------------------------------------------------------------------------- /blog/2024/2024-08-05-open-source-challenge.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: "The Unexpected Power of 100 Days in Open Source" 3 | tags: ["open source", "open source contributor", "open source challenge", "how to contribute to open source"] 4 | authors: BekahHW 5 | slug: 100-days-of-oss-challenge 6 | description: "Join us for #100DaysOfOSS, where we'll create opportunities to collaborate and learn more about open source over the next 100 days." 7 | --- 8 | 9 | In theory, I'm not sure that open source should *work*. Think about it: Companies usually keep their best ideas secret. But in open source, everyone shares their code openly. You'd expect most people to just use the free software without giving anything back. Not to mention trying to organize thousands of volunteers from all over the world to build something complex. But despite all these reasons why it shouldn't work, open source not only survives – it thrives. It's powering a huge part of the technology we use every day. But for many people, the idea of actually contributing to open source still feels pretty scary. Why? And more importantly, how can we change that? 10 | 11 | 12 | 13 | Let's start with a personal story. When I first thought of contributing to an open source project, I was afraid. The fear of making a mistake in front of the entire internet was overwhelming. Sound familiar? If so, you're not alone. Research shows that this fear of public failure is a significant barrier to open source participation. 14 | 15 | But here's the interesting part: studies also show that the most effective way to overcome this fear is through community support. When we're part of a group, our fear of failure decreases, and our willingness to take risks increases. This is where the magic happens. 16 | 17 | ## #100DaysOfOSS Challenge 18 | Our [#100DaysOfOSS Challenge](https://opensauced.pizza/docs/community/100-days-of-oss/), isn't about coding for 100 days. It's about leveraging the power of community to transform hesitation into action. 19 | 20 | Here's why I think this approach works: 21 | 22 | 1. Structured Progress: The challenge provides a clear pathway, breaking down contributing to open source into manageable weekly tasks. 23 | 24 | 2. Community Support: By connecting participants, the challenge creates a supportive peer group. This not only can reduce anxiety but also increase accountability and motivation. 25 | 26 | 3. Learning by Doing: The challenge emphasizes practical contributions, aligning with the principles of experiential learning - you don't have to know how to code to contribute. 27 | 28 | 4. Flexibility: Participants can tailor the challenge to their interests, which research shows increases intrinsic motivation and long-term engagement. 29 | 30 | This year, we have support from GitHub Education to enhance the challenge and we're introducing [weekly structured posts](https://github.com/orgs/open-sauced/discussions/36) and increased community engagement opportunities. It's an experiment in scaling the benefits of community-supported learning. 31 | 32 | So, here's my call to action: If you've ever been curious about open source but hesitated to jump in, join us for [#100DaysOfOSS](https://opensauced.pizza/docs/community/100-days-of-oss/) with your [intro](https://github.com/orgs/open-sauced/discussions/36#discussioncomment-10152170) today - we already have over 100 people! 33 | 34 | P.S. If you're participating, you can also sign up for the [OpenSauced newsletter](https://news.opensauced.pizza/#/portal/signup) for biweekly updates on Open Source topics to help you along your journey. 35 | -------------------------------------------------------------------------------- /blog/authors.yml: -------------------------------------------------------------------------------- 1 | BekahHW: 2 | name: Bekah Hawrot Weigel 3 | title: Developer Experience Lead 4 | image_url: https://github.com/BekahHW.png 5 | email: Bekah@opensauced.pizza 6 | socials: 7 | x: bekahhw 8 | linkedin: bekah-hawrot-weigel 9 | github: bekahhw 10 | site: https://www.bekahhw.com/ 11 | page: true 12 | 13 | nickytonline: 14 | name: Nick Taylor 15 | title: AI Engineer 16 | image_url: https://github.com/nickytonline.png 17 | email: nick@opensauced.pizza 18 | socials: 19 | x: nickytonline 20 | linkedin: nickytonline 21 | github: nickytonline 22 | site: https://www.nickyt.co/ 23 | page: true 24 | 25 | jpmcb: 26 | name: John McBride 27 | title: Sr Software Engineer | AI Engineer 28 | image_url: https://github.com/jpmcb.png 29 | email: john@opensauced.pizza 30 | socials: 31 | x: johncodezzz 32 | linkedin: jpmcb 33 | github: jpmcb 34 | site: https://johncodes.com/ 35 | page: true 36 | 37 | AdiatiAyu: 38 | name: Ayu Adiati 39 | title: Tech Blogger | Virtual Coffee Documentation and Monthly Challenge Team Lead 40 | image_url: https://github.com/adiati98.png 41 | socials: 42 | x: AdiatiAyu 43 | linkedin: adiatiayu 44 | github: adiati98 45 | site: https://adiati.com/ 46 | page: true 47 | -------------------------------------------------------------------------------- /docs/community/hacktoberfest.md: -------------------------------------------------------------------------------- 1 | --- 2 | id: hacktoberfest 3 | title: "Join us for Hacktoberfest! 🎃" 4 | sidebar_label: "Join us for Hacktoberfest! 🎃" 5 | keywords: 6 | - "hacktoberfest" 7 | - "Open source contributions for Hacktoberfest" 8 | - "Hacktoberfest participation guide" 9 | - "Open source collaboration in October" 10 | - "Hacktoberfest beginner-friendly projects" 11 | - "How to get involved in Hacktoberfest" 12 | --- 13 | 14 | At OpenSauced, we love open source just as much as pizza! That's why we are participating in Hacktoberfest! 🎃 15 | 16 | ## What is Hacktoberfest? 17 | 18 | From October 1st-31st, people around the globe do a challenge where they submit four pull requests participating projects. Here's how to join: 19 | 20 | 1. Go to [the official Hacktoberfest website](https://hacktoberfest.com/) 21 | 1. Click on the Register Now! button 22 | 1. Sign in with your [GitHub](https://github.com/) and/or [GitLab](https://gitlab.com/users/sign_in) accounts. 23 | 24 | ## Why Should I Participate in Hacktoberfest? 25 | 26 | This event is a great way to jumpstart your journey in open source, to meet other people in the tech community, and build your skills. Curious to learn more about the value of contributing to open source? Check out these resources: 27 | 28 | - [Hacktoberfest 2023: Beyond Green Squares](https://dev.to/opensauced/hacktoberfest-2023-beyond-green-squares-4d6j) to learn how to make this a meaningful Hacktoberfest focused on growth, impact, and building relationships. 29 | - [Setting Goals for Your Open Source Contributions](https://dev.to/opensauced/setting-goals-for-your-open-source-contributions-349b) for resources on how to grow your experience through open source. 30 | 31 | ## I want to join Hacktoberfest, but I have no idea what open source is 32 | 33 | No problem! 😄 Here is a list of resources we recommend for first-time contributors: 34 | 35 | - Take our [Intro to Open Source](https://opensauced.pizza/learn/#/) course to learn the history of open source, the tools to succeed in the community, and how to showcase your contributions. 36 | - Check out GitHub's [introductory course](https://github.com/skills/introduction-to-github) to learn how to use the platform when making open source contributions. 37 | - Read our [The Power of Git](https://dev.to/opensauced/the-power-of-git-a-guide-to-collaborative-version-control-dl6) blog post to learn how to harness the power of Git, your trusty weapon in Hacktoberfest. 38 | 39 | ## What should I expect during Hacktoberfest? 40 | 41 | During Hacktoberfest, expect to feel excited and a bit competitive on your quest to submit your four pull requests. While those feelings are understandable, it's important to remember the following: 42 | 43 | - Think first, work later: It's best to share your ideas and/or request to work on an issue before submitting a pull request. It'll make it easier for maintainers to assess whether your suggestion fits in with their project. It will also help you develop your communication skills. 44 | - Be patient: Maintainers are people with lives outside of open source, so avoid constantly messaging them about when your pull request be reviewed and merged. 45 | - Try new things: While revising typos is helpful, it's best to diversify contributions. This would help expand your skills, which is very useful if you plan on using your Hacktoberfest contributions as samples for your portfolio. 46 | 47 | ## I'm ready for Hacktoberfest 48 | 49 | Great! 😄 If you're looking for a project to contribute to, check out [this list of beginner-friendly projects for Hacktoberfest](https://insights.opensauced.pizza/pages/BekahHW/655/repositories). 50 | 51 | Happy Contributing! 😄 52 | -------------------------------------------------------------------------------- /docs/community/welcome-to-the-community.md: -------------------------------------------------------------------------------- 1 | --- 2 | id: welcome-to-the-community 3 | title: "Welcome to the OpenSauced Community" 4 | sidebar_label: "Welcome to the Community" 5 | keywords: 6 | - "welcome to the community" 7 | - "The community welcomes you" 8 | - "Get involved in the community" 9 | - "Join our community" 10 | - "Greetings from the community" 11 | --- 12 | 13 | Welcome to the OpenSauced community! At OpenSauced, we strive to bring collaboration and inspiration to every open source contributor and help build a global community of open source developers, empowering you to grow, innovate, and achieve greatness in the open. 14 | 15 | ## Community Guidelines 16 | 17 | We pledge to create a welcoming and inclusive community for everyone at OpenSauced. We have a few guidelines to help us achieve this goal: 18 | 19 | - Be respectful and kind to others in the community. 20 | - Be patient with others and help them learn. 21 | - Be open to feedback and constructive criticism. 22 | - Adhere to the [Code of Conduct](../contributing/code-of-conduct.md). 23 | 24 | ## Keeping Up with OpenSauced 25 | 26 | The OpenSauced community is a group of open source enthusiasts who are passionate about making open source more accessible to everyone. Here are some ways you can keep up with what we're doing: 27 | 28 | - Follow us on X [@SaucedOpen](https://twitter.com/saucedopen) for announcements and our frequent X Spaces. 29 | - Join our [Community](https://github.com/orgs/open-sauced/discussions/1) and hang out with us during our weekly office hours. 30 | - Subscribe to our [YouTube channel](https://www.youtube.com/@OpenSauced) for the latest updates and video content for OpenSauced. 31 | - 📰 Subscribe to our [newsletter](https://news.opensauced.pizza/#/portal/signup) for all things OpenSauced and open source. 32 | - 🗓️ Check out the [calendar](https://calendar.google.com/calendar/u/0?cid=Y19kYWRhODM2MjlhZDg4ZWM2M2IxZGFmMTE5MDIyMDg0MjU2ZmQ4NmNjNWNhYmMxMjk5MDhjMGUxOTY3NjY4ZTg0QGdyb3VwLmNhbGVuZGFyLmdvb2dsZS5jb20) for our next weekly community chat. 33 | 34 | ## How to Get Involved 35 | 36 | You can get involved in the OpenSauced community in a few ways: 37 | 38 | - Share your contributions! We love to see what you're working on. Highlight your contributions on [OpenSauced](https://app.opensauced.pizza/feed). 39 | - Open an issue or ask to be assigned to an existing issue on any of our [OpenSauced repositories](https://github.com/open-sauced). 40 | - Share what you're working on, ask questions, or mentor new contributors in our [Community](https://github.com/orgs/open-sauced/discussions/1). 41 | - Provide feedback on our [GitHub Discussions](https://github.com/orgs/open-sauced/discussions). 42 | 43 | ## Resources on Getting Started with Open Source 44 | 45 | Getting started with open source can be challenging, so we've put together some resources to help you get started. 46 | 47 | - 📝 Check out our [blog on Dev.to](https://dev.to/opensauced), where we provide resources for open source contributors. 48 | - 📖 Take our [Intro to Open Source Course](https://opensauced.pizza/learn/#/) to help you start with open source. 49 | - 📅 Join our [#100DaysOfOSS Challenge](100-days-of-oss.md) to help you grow your skills and gain real-world experience in open source. 50 | -------------------------------------------------------------------------------- /docs/contributing/code-of-conduct.md: -------------------------------------------------------------------------------- 1 | --- 2 | id: code-of-conduct 3 | title: "Code of Conduct" 4 | sidebar_label: "Code of Conduct" 5 | keywords: 6 | - "code of conduct" 7 | - "Community guidelines" 8 | - "Guidelines for behavior" 9 | - "Interaction guidelines" 10 | - "rules and guidelines" 11 | - "Behavioral expectations" 12 | --- 13 | 14 | ## Our Pledge 15 | 16 | In the interest of fostering an open and welcoming environment, we as 17 | contributors and maintainers pledge to make participation in our project and our community a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, gender identity and expression, level of experience, nationality, personal appearance, race, religion, or sexual identity and orientation. 18 | 19 | ## Our Standards 20 | 21 | Examples of behavior that contributes to creating a positive environment 22 | include: 23 | 24 | - Using welcoming and inclusive language. 25 | - Being respectful of differing viewpoints and experiences. 26 | - Gracefully accepting constructive criticism. 27 | - Focusing on what is best for the community. 28 | - Showing empathy towards other community members. 29 | 30 | Examples of unacceptable behavior by participants include: 31 | 32 | - The use of sexualized language or imagery and unwelcome sexual attention or advances. 33 | - Trolling, insulting/derogatory comments, and personal or political attacks. 34 | - Public or private harassment. 35 | - Publishing others' confidential information, such as a physical or electronic address, without explicit permission. 36 | - Other conduct that could reasonably be considered inappropriate in a professional setting. 37 | 38 | ## Our Responsibilities 39 | 40 | Project maintainers are responsible for clarifying the standards of acceptable behavior and are expected to take appropriate and fair corrective action in response to any instances of unacceptable behavior. 41 | 42 | Project maintainers have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned with this Code of Conduct or to ban temporarily or permanently any contributor for other behaviors that they deem inappropriate, threatening, offensive, or harmful. 43 | 44 | ## Scope 45 | 46 | This Code of Conduct applies both within project spaces and in public spaces when an individual is representing the project or its community. Examples of representing a project or community include: 47 | 48 | - Using an official project e-mail address. 49 | - Posting via an official social media account. 50 | - Acting as an appointed representative at an online or offline event. 51 | 52 | Representation of a project may be further defined and clarified by project maintainers. 53 | 54 | ## Enforcement 55 | 56 | Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team at hello@briandouglas.me. All complaints will be reviewed and investigated and will result in a response that is deemed necessary and appropriate to the circumstances. The project team is obligated to maintain confidentiality with regard to the reporter of an incident. 57 | Further details of specific enforcement policies may be posted separately. 58 | 59 | Project maintainers who do not follow or enforce the Code of Conduct in good faith may face temporary or permanent repercussions as determined by other members of the project's leadership. 60 | 61 | ## Attribution 62 | 63 | This Code of Conduct is adapted from the [Contributor Covenant][homepage] version 1.4, 64 | available at [https://contributor-covenant.org/version/1/4][version]. 65 | 66 | [homepage]: https://contributor-covenant.org 67 | [version]: https://contributor-covenant.org/version/1/4/ 68 | -------------------------------------------------------------------------------- /docs/contributing/opensauced-maintainers-guide/maintainers-guide.md: -------------------------------------------------------------------------------- 1 | --- 2 | id: maintainers-guide 3 | title: "OpenSauced Maintainers Guide" 4 | sidebar_label: "OpenSauced Maintainers Guide" 5 | keywords: 6 | - "maintainers guide" 7 | - "open source maintainers guide" 8 | - "open source maintainer" 9 | - "open source project management" 10 | - "community management in open-source" 11 | --- 12 | 13 | Welcome to the OpenSauced Maintainers Guide for contributors who are interested in being part of the maintainer team for OpenSauced repositories. 14 | 15 | At OpenSauced, we empower contributors to work in the open and support maintainers to make data-driven decisions for their projects. 16 | 17 | It's important to us that we maintain a healthy environment for contributors and maintainers of our projects. 18 | 19 | ## How to Join the Maintainers Team 20 | 21 | - Sign up for [opensauced.pizza](https://opensauced.pizza/). 22 | - Join our [Community](https://github.com/orgs/open-sauced/discussions/1). 23 | - Prove your pizza's worth! 24 | 25 | ## What does the Maintainers Team do? 26 | 27 | Well, like all things in tech, it depends. We have different maintainer teams for each of the repositories. So, it's important that you communicate with the admin maintainer if you have any questions. 28 | 29 | ### Core Responsibilities 30 | 31 | Your responsibilities may include: 32 | 33 | - Reviewing and merging pull requests (PRs). 34 | - Providing comments and responses on PRs, issues, discussions, and Discord messages. 35 | - [Triage issues](../triage-guide.md#triage-process) and bug reports. 36 | - Maintaining project documentation. 37 | - Collaborating with the community. 38 | 39 | **Creating a positive space for contributors at all stages is one of your most important responsibilities.** 40 | 41 | As a maintainer, you must: 42 | 43 | - adhere to our [Code of Conduct](../code-of-conduct.md) and be an example for treating contributors with respect, 44 | - communicate with the other maintainers in a timely and reasonable manner, 45 | - understand and adhere to project standards. 46 | 47 | ## Committing and Merging Changes 48 | 49 | 1. For commit and pull request standards, please refer to the [introduction to contributing](../introduction-to-contributing.md). 50 | 2. Before merging in changes, always run the project locally if UI changes were made. 51 | 3. **Squash and merge commits** when you merge in a PR. 52 | 53 | Thank you for being so interested in becoming a maintainer! Please reach out in our [team discussions](https://github.com/open-sauced/docs/discussions/categories/team-discussions) if you need help, guidance, or clarification at any time. 54 | -------------------------------------------------------------------------------- /docs/contributing/set-up-authentication.md: -------------------------------------------------------------------------------- 1 | --- 2 | id: set-up-authentication 3 | title: "Set Up Authentication" 4 | sidebar_label: "Set Up Authentication" 5 | keywords: 6 | - "set up authentication" 7 | - "Authentication setup guide" 8 | - "Setting up secure login" 9 | - "User authentication configuration" 10 | - "Authentication system setup" 11 | - "Authentication implementation steps" 12 | - "Authentication setup tutorial" 13 | - "Setting up user authorization" 14 | - "Authentication best practices" 15 | --- 16 | 17 | You need to obtain an authentication token to interact with the OpenSauced public API as an authenticated user. 18 | 19 | The following steps outline how to obtain an authentication token from the [hot.opensauced.pizza](https://hot.opensauced.pizza) website: 20 | 21 | 1. Click on your avatar in the top right corner of the page. This will open a dropdown menu. 22 | 23 | ![Avatar in top right corner of the page](../../static/img/contributing-avatar-top-right.png) 24 | 25 | 2. Click on the "Copy auth token" option to copy your auth token to clipboard. 26 | 27 | ![Copy Auth Token](../../static/img/contributing-copy-auth-token.png) 28 | 29 | 3. You can now use this token to make authenticated requests to the OpenSauced public API by including it in the Authorization header of your requests. For example: 30 | 31 | ```javascript 32 | const response = await fetch( 33 | "https://api.opensauced.pizza/v2/auth/session", 34 | { 35 | method: "GET", 36 | headers: { 37 | Authorization: `Bearer ${token}`, 38 | }, 39 | } 40 | ); 41 | ``` 42 | -------------------------------------------------------------------------------- /docs/contributing/technical/setup-repo-with-git.md: -------------------------------------------------------------------------------- 1 | --- 2 | id: setup-repo-with-git 3 | title: "Setting Up a Repository with Git and GitHub" 4 | sidebar_label: "Setting Up a Repository with Git and GitHub" 5 | keywords: 6 | - "setting up a repository with Git and GitHub" 7 | - "working with git and github" 8 | - "GitHub repository creation" 9 | - "GitHub repository workflow" 10 | - "GitHub repository initialization" 11 | - "GitHub repository hosting" 12 | - "GitHub repository collaboration" 13 | - "GitHub repository version control" 14 | - "GitHub repository deployment" 15 | - "GitHub repository setup" 16 | --- 17 | 18 | 19 | ## Using the GitHub CLI 20 | 21 | ### How to Install the GitHub CLI 22 | 23 | The [GitHub CLI](https://cli.github.com/) allows you to fork repositories, create issues, pull requests, and more from the command line. 24 | 25 | Follow these [instructions to install GitHub CLI](https://github.com/cli/cli#installation) on Mac, Windows, or Linux. 26 | 27 | ### How to Authenticate with the GitHub CLI 28 | 29 | From the terminal, you will need to authenticate with the GitHub CLI. You can do this by running the following command: 30 | 31 | ```shell 32 | gh auth login 33 | ``` 34 | 35 | Then, follow the prompts to authenticate with the GitHub CLI. 36 | 37 | ### How to Fork and Clone a Repository with the GitHub CLI 38 | 39 | A fork is a remote copy of a repository, allowing you to experiment freely with changes without affecting the original project. 40 | 41 | A clone is a local copy of a repository that includes all the files, branches and commits. 42 | 43 | To fork and clone a repository with the GitHub CLI, run the following command: 44 | 45 | ```shell 46 | gh repo fork open-sauced/ 47 | ``` 48 | 49 | The GitHub CLI will fork the project in your GitHub account and will ask you if you want to clone the repository on your local machine. 50 | 51 | ### How to Add a Remote Repository 52 | 53 | Adding a remote repository allows you to pull in changes from the original repository and keep your forked copy of the repository up to date. 54 | 55 | To add a remote repository, run the following command: 56 | 57 | ```shell 58 | git remote add upstream https://github.com/open-sauced/app.git 59 | ``` 60 | 61 | ### How to View the Remote Repositories Locally 62 | 63 | To view the remote repositories that your local repository is connected to, run the following command: 64 | 65 | ```shell 66 | git remote -v 67 | ``` 68 | 69 | You should see the following output: 70 | 71 | ```shell 72 | origin git@github.com:YOUR_GITHUB_USERNAME/app.git (fetch) 73 | origin git@github.com:YOUR_GITHUB_USERNAME/app.git (push) 74 | upstream git@github.com:open-sauced/app.git (fetch) 75 | upstream git@github.com:open-sauced/app.git (push) 76 | ``` 77 | 78 | ## Using the GitHub Website and the Command Line 79 | 80 | If you prefer to set up your repository using the GitHub website and the command line, follow this detailed guide from the [official GitHub documentation](https://docs.github.com/en/get-started/quickstart/fork-a-repo). 81 | -------------------------------------------------------------------------------- /docs/contributing/triage-guide.md: -------------------------------------------------------------------------------- 1 | --- 2 | id: triage-guide 3 | title: "Triage Guide" 4 | sidebar_label: "Triage Guide" 5 | keywords: 6 | - "triage guide" 7 | - "Issue triage best practices" 8 | - "GitHub triage process" 9 | - "Pull request triage steps" 10 | - "Triage workflow tutorial" 11 | - "Effective issue management" 12 | - "Open source contribution triage" 13 | - "Triage for project maintainers" 14 | - "Streamlining triage efforts" 15 | - "Collaborative issue handling" 16 | - "Contributor triage assistance" 17 | --- 18 | 19 | ## Triage Process 20 | 21 | When a new issue or pull request (PR) is opened, the issue will be labeled with `needs triage`. At OpenSauced, our team functions as the triage team. Once a teammate is available, they can help ensure all the required information is provided. 22 | 23 | ### Adding Issue and PR Labels 24 | 25 | Depending on the issue or PR, there are several labels the triage team can add for further classification, as follows: 26 | 27 | - `needs triage`: This can be kept if the triager is unsure which next steps to take. 28 | - `awaiting more info`: If more information has been requested from the author, apply this label. 29 | - `question`: User questions that do not appear to be bugs or enhancements. 30 | - `discuss`: Topics for discussion. It might end in an `enhancement` or `question` label. 31 | - `bug`: Issues that present reasonable conviction there is a reproducible bug. 32 | - `enhancement`: Issues that are found to be a reasonable candidate feature additions. 33 | - `style`: Minor CSS or visual changes. 34 | 35 | In all cases, maintainers may close issues if they don't receive a timely response when further information is sought or when additional questions are asked. 36 | 37 | ### Labeling `good first issue` 38 | 39 | Issues labeled as `good first issue` represent a curated list of easy contributions for new contributors. These issues are meant to help folks make their first contribution to open source and should not require excessive research or triaging on the contributor's part. 40 | 41 | All `good first issue` should include one or more of the following: 42 | 43 | - A solution. 44 | - A suggestion for a solution. 45 | - Links to components or in which issue occurs. 46 | 47 | Please be noted: 48 | 49 | - Issues that `needs triage` cannot be labeled as `good first issues`. 50 | - It is better to have no `good first issue` labeled issues than to have a `good first issue` confusing enough to deter a contributor from contributing. 51 | 52 | ## Approaches and Best Practices for Getting Into Triage Contributions 53 | 54 | - Review the project's Contribution Guidelines if they are present. In a nutshell, commit to the community's standards and values. 55 | 56 | - Review the documentation; for most projects, it is just the `README.md`. Ensure you understand the key APIs, semantics, configurations, and use cases. 57 | 58 | - Writing your own test apps to reaffirm your understanding of the key functions might be helpful. This may identify some gaps in documentation; record those as they might be good PRs to open. 59 | 60 | - Skim through the issues backlog; identify low-hanging and mostly new issues. From those, attempt to recreate issues based on the OP (Original Poster) description and ask questions if required. No question is a bad question! 61 | 62 | ## Removal of Triage Role 63 | 64 | There are a few cases where members can be removed from the triage role: 65 | 66 | - Breaking the [Code of Conduct](./code-of-conduct.md) or [project contributor guidelines](./introduction-to-contributing.md). 67 | - Abuse or misuse of the role as deemed by the Triage Team. 68 | - Lack of participation for more than six months. 69 | 70 | If any of these happen, we will discuss them as a part of the triage portion of the regular Triage Team meetings. If you have questions, feel free to contact any Triage Team members. 71 | 72 | ## Helpful Hints 73 | 74 | - When reviewing the list of open issues, there are some common types and suggested actions: 75 | - **New/unattended issues or simple questions**: A good place to start. 76 | - **Hard bugs & ongoing discussions**: Feel free to chime in and help. 77 | - **Issues that imply gaps in the documentation**: Open PRs with changes or help the user to do so. 78 | - For recurring issues, it is helpful to create functional examples to demonstrate (publish as gists or a repo). 79 | - Review and identify the maintainers. If necessary, mention one or more of them with `@` if you are unsure what to do. 80 | - Ensure all your interactions are professional, welcoming, and respectful to the parties involved. 81 | -------------------------------------------------------------------------------- /docs/features/contributor-insights.md: -------------------------------------------------------------------------------- 1 | --- 2 | id: contributor-insights 3 | title: "Organize and Monitor Your Contributors" 4 | sidebar_label: "Contributor Insights" 5 | keywords: 6 | - "contributor insights" 7 | - "contributors" 8 | - "open source contributor rating" 9 | - "contributor impact" 10 | - "value of open source contributions" 11 | - "open source sponsorship" 12 | - "Monitor Contributors" 13 | - "Organize Contributors" 14 | - "Contributor Contributor Insights Management" 15 | --- 16 | 17 | The Contributor Insights feature enables you to categorize, monitor, and analyze different groups of contributors within open source projects. With the Contributor Insights feature, gain granular insights into each contributor's activity and contributions. 18 | 19 | Monitor individual commit histories, track who is actively engaged, identify alumni or new contributors, and even compare the performance of contributors against each other. This encompasses a wide range of metrics such as code commits, created and reviewed pull requests (PRs), as well as issue creation and commenting. 20 | 21 | ![Contributor Insights Page](../../static/img/lists-page.png) 22 | 23 | ## How to Create a Contributor Insight Page 24 | 25 | After logging in, navigate to "Insights" in the sidebar. Click the "+" next to it to be presented with options, and select "New Contributor Insight." 26 | 27 | There are three ways to add a list: 28 | 29 | 1. **Explore Contributors**: Use our explore tool to find contributors and create your list. 30 | 2. **Sync your GitHub Team**: Connect to your GitHub to create a Contributor Insight Page from a team in your organization. 31 | 3. **Import your GitHub Following**: Connect to your GitHub to create a Contributor Insight Page with all the contributors you follow. 32 | 33 | Once your Contributor Insight Page is created, you'll be able to see an overview of all the contributors in your list, a graph of their activity, and a detailed breakdown of the contributors. 34 | 35 | :::tip 36 | 37 | If you're having trouble syncing your Organization or Team, check out the "[Sync Your GitHub Team](../welcome/faqs.md#sync-your-github-team)" section in our FAQs. 38 | 39 | ::: 40 | 41 | By default, your Contributor Insight Page is public. If your Contributor Insight Page is private (a PRO plan feature), only those with access to your Workspace will be able to view it. 42 | 43 | ## Open Source Contributor Rating (OSCR) 44 | 45 | On your Contributor Insight Page, you'll see that each contributor is assigned an [OSCR](../welcome/glossary.md#oscr). The OSCR is a metric to evaluate the engagement and impact of contributors across the entire open source ecosystem. This score aims to give insight into a contributor's involvement and the value they bring to open source communities as a whole. 46 | 47 | The OSCR takes into account various factors related to all of the contributor's activity and the quality of their contributions in open source. 48 | 49 | :::info 50 | OSCRs are calculated on a rolling 90-day basis across all of a contributor's activity and are out of 300 total points. This means the score reflects recent activity and engagement, providing a current snapshot of a contributor's open source involvement rather than a lifetime aggregate. 51 | ::: 52 | 53 | ### Insights into OSCR 54 | 55 | Here are some of the ways, the OSCR can be used: 56 | 57 | - Identifying currently active key contributors in a project 58 | - Evaluating the current health of an open source community 59 | - Finding potential collaborators based on recent activity 60 | - Recognizing and rewarding impactful contributors 61 | - Tracking contributor growth over time 62 | - Encouraging sustained participation in open source 63 | 64 | OSCRs are designed to be a helpful tool in understanding current open source dynamics, but should be considered alongside other factors when evaluating contributors or projects. -------------------------------------------------------------------------------- /docs/features/dev-card.md: -------------------------------------------------------------------------------- 1 | --- 2 | id: dev-card 3 | title: "Showcase Your Open Source Stats with Your Dev Card" 4 | sidebar_label: "Dev Card" 5 | keywords: 6 | - "dev card" 7 | - "DevCard" 8 | - "OpenSource" 9 | - "Open Source DevCard" 10 | - "Showcase DevCard" 11 | - "Showcase Your Open Source Stats" 12 | - "Open Source Stats DevCard" 13 | --- 14 | 15 | The Dev Card feature is what we like to call your "open source business card." 16 | 17 | On the front of your card, you see your profile picture, username, and your [OSCR](https://opensauced.pizza/docs/welcome/glossary/#oscr) score. Your OSCR score is a metric that measures your open source contributions and engagement. 18 | 19 | You'll see the back side of your card when you click it. It shows more information, including your profile headline, the number of pull requests you have created, the date of your first contribution on GitHub, activity rate, [PR velocity](https://opensauced.pizza/docs/welcome/glossary/#pr-velocity) rate, and a `View Profile` button that takes you to your dashboard. 20 | 21 | ![front and back sides of a dev card](../../static/img/DevCard.png) 22 | 23 | Your Dev Card is a snapshot of your contributions, skills, and engagement in the open source community. You can share it on social media, use it to monitor your progress, or show it off to potential employers. 24 | 25 | Eager to get your Dev Card? Here's how you can get yours today: 26 | 27 | 1. Log in to your OpenSauced account. 28 | 2. Navigate to your [profile](https://app.opensauced.pizza/user/{username}). 29 | 3. Click the Dev Card icon on your profile image. 30 | 31 | ![dev card icon on user profile](../../static/img/get-dev-card.png) 32 | -------------------------------------------------------------------------------- /docs/features/highlights.md: -------------------------------------------------------------------------------- 1 | --- 2 | id: highlights 3 | title: "Highlight Your Open Source Contributions" 4 | sidebar_label: "Highlights" 5 | keywords: 6 | - "Highlights" 7 | - "Open Source Highlights" 8 | - "Contribution Highlights" 9 | - "Highlight your open source contributiions" 10 | - "Open Source Contribution Highlights" 11 | --- 12 | 13 | The Highlights feature is the place you can display your favorite open source contributions, share the story, and inspire others to join you in your open source journey. For maintainers, it's a great way to showcase your project and the issues that need support and attract new contributors. 14 | 15 | There are currently three types of highlights you can add to your profile: 16 | 17 | - Blog posts 18 | - Pull request 19 | - Issue 20 | 21 | ## How to Add a Highlight 22 | 23 | First, go to [OpenSauced's Highlights feed](https://app.opensauced.pizza/feed), then click the "Post a highlight to show your work!" input. 24 | 25 | There are two ways to adding highlights: 26 | 27 | ### 1. Using Highlight Suggestions 28 | 29 | - Search the pull request or issue that you want to add in the "Highlight suggestions" section. 30 | - Click the "Fill content" button to paste the suggested link or the "Add and Summarize" button to paste the link and auto-summarize the content. 31 | 32 | ![highlights demo](../../static/gif/highlight.gif) 33 | 34 | :::note 35 | 36 | The "Highlight suggestions" are only suggesting issues and pull requests that you created. For blog posts, you need to add them manually. 37 | 38 | ::: 39 | 40 | ### 2. Adding a Link Manually 41 | 42 | - Paste the URL to your blog post, pull request, or issue in the bottom input. 43 | - Either use our Auto-Summarize feature or write your own summary. 44 | 45 | --- 46 | 47 | For more examples of highlights, go to the [OpenSauced Highlights feed](https://app.opensauced.pizza/feed). 48 | 49 | Eager to get started? Check out the [Effectively Highlight Your Contribution](https://opensauced.pizza/learn/intro-to-oss/the-secret-sauce#effectively-highlight-your-contributions) section in our free "Intro to Open Source" course to learn more. 50 | -------------------------------------------------------------------------------- /docs/features/repo-insights.md: -------------------------------------------------------------------------------- 1 | --- 2 | id: repo-insights 3 | title: "Insights into Open Source Repositories" 4 | sidebar_label: "Repository Insights" 5 | keywords: 6 | - "Repository Insights" 7 | - "open source" 8 | - "projects" 9 | - "Open Source Repository Insights" 10 | - "Project Repository Insights" 11 | - "Repository Insights into Open Source Projects" 12 | - "Open Source Project Repository Insights" 13 | --- 14 | 15 | The Repository Insights feature is your one-stop solution for understanding the pulse of your open source projects and contributions. This feature is designed to provide a comprehensive view of open source project's health and contributions. From contribution trends to community health, OpenSauced Repository Insights helps you make data-driven decisions that align with your goals. It's not just about numbers; it's about providing data to help you make decisions that can define your approach to open source and tell the story of your project or contribution journey. 16 | 17 | ![insight-pages-demo](../../static/gif/insight-page-demo.gif) 18 | 19 | ## How to Use Repository Insights 20 | 21 | ### Contributors 22 | 23 | - To track projects you're working on. 24 | - To identify potential projects to contribute to. 25 | - To discover other contributors to collaborate with. 26 | - To track the activity of a topic you're interested in. 27 | - To track the activity of your favorite programming languages. 28 | - To aid in the job search process. 29 | 30 | :::tip 31 | 32 | Check out our [Contributors Guide to OpenSauced](../contributors/contributors-guide.md#repository-insights-connecting-your-repositories) to learn more about how to create and use Repository Insights as a contributor. 33 | 34 | ::: 35 | 36 | ### Maintainers 37 | 38 | - To track the health of your project. 39 | - To identify contributors who are making an impact. 40 | - To find new contributors to support your project. 41 | 42 | :::tip 43 | 44 | Check out our [Maintainers Guide to OpenSauced](../maintainers/maintainers-guide.md) and our [Understanding Repository Insights Data](../maintainers/understanding-repo-insights.md) pages to learn more about how to create and use Repository Insights as a maintainer. 45 | 46 | ::: 47 | 48 | ## Sharing Your Repository Insights Page with Your Team 49 | 50 | After you've created your Repository Insights Page, share it with your team. 51 | 52 | Sharing this page with your team ensures that everyone is well-informed about the project's status and can collaborate more effectively. It fosters a collaborative environment where team members can align their efforts, make informed decisions, and collectively work toward the organization's success. 53 | 54 | ### How to Share Repository Insights Page 55 | 56 | This method gives view-only access to your Repository Insights Page. 57 | 58 | 1. Navigate to your sidebar. 59 | 2. Click the Repository Insight Page that you want to share. 60 | 3. On the top right, click the "Share" button to copy the Repository Insight Page URL to the clipboard. 61 | 4. Share the URL with your team members. 62 | 63 | By default, your Repository Insights are public. If you want to make your Repository Insights private, you can change it in the settings. -------------------------------------------------------------------------------- /docs/features/star-search.md: -------------------------------------------------------------------------------- 1 | --- 2 | id: star-search 3 | title: "Your Copilot for Git History" 4 | sidebar_label: "StarSearch" 5 | keywords: 6 | - "contributors" 7 | - "Monitor Contributors" 8 | - "git history" 9 | - "copilot for git history" 10 | - "open source companies" 11 | - "open source contributors" 12 | - "open source maintainers" 13 | - "AI" 14 | --- 15 | 16 | **StarSearch** is our AI-powered feature that provides in-depth insights into contributor history and activities, enabling users to query GitHub activities and analytics through natural language. This tool is designed to provide you with insights into GitHub projects and contributions without requiring any coding or complex queries, bringing transparency and a new depth of knowledge about open source projects. It's your copilot for git history. 17 | 18 | ## Key Features 19 | 20 | - **Real-Time Insights**: Access up-to-date information about GitHub contributions, issues, and projects. 21 | - **Conversational Queries**: Use natural language to explore GitHub data. 22 | - **Cross-Project Analysis**: Identify connections between different projects and technologies. 23 | - **Contributor Discovery**: Pinpoint key contributors and the work they've done. 24 | 25 | ### What Can You Discover with StarSearch? 26 | 27 | - **Contributor Activities**: Learn the details of contributions and contributors. 28 | - **Key Contributors**: Identify the key contributors to projects and ecosystems and their impact on the projects. 29 | - **Work-Based Connections**: Find potential collaborators based on their contributions to specific projects. 30 | - **Hidden Experts**: Discover untapped talent in the ecosystem. 31 | 32 | ![StarSearch](../../static/img/star-search.png) 33 | 34 | ## Getting Started with StarSearch 35 | 36 | 1. Log in to [Your OpenSauced Account](https://app.opensauced.pizza/) 37 | 2. Navigate to [https://app.opensauced.pizza/star-search](https://app.opensauced.pizza/star-search) or click the StarSearch tab in the sidebar or navigation bar. 38 | 39 | ### User Guide 40 | 41 | #### Basic Queries 42 | 43 | - What type of pull requests has \{username} worked on? 44 | - Who are the best developers that know \{technology} and are interested in \{technology}? 45 | - Who are the most prevalent contributors to the \{technology} ecosystem? 46 | - Show me the [lottery factor](https://opensauced.pizza/docs/welcome/glossary/#lottery-factor) for contributors in the \{repository} project? 47 | 48 | ### FAQs 49 | 50 | - **Can I continue conversations with StarSearch?** 51 | - Not yet, but stay tuned! 52 | - **Can I access my search history?** 53 | - This feature is currently not available, but we plan to include it in future updates. 54 | - **What time range does StarSearch cover?** 55 | - StarSearch is most accurate from March 1, 2024. 56 | - **Is StarSearch always right?** 57 | - StarSearch is an AI tool and may not always be accurate. We recommend verifying the information. 58 | 59 | ## Feedback 60 | 61 | Your feedback helps us improve StarSearch. If you have any suggestions or questions, please create a [discussion post](https://github.com/orgs/open-sauced/discussions/categories/general-feedback-or-bugs) or open an [issue](https://github.com/open-sauced/app/issues). You can also use the thumbs-up or thumbs-down buttons on the StarSearch page to let us know if the information was helpful. -------------------------------------------------------------------------------- /docs/introduction.md: -------------------------------------------------------------------------------- 1 | --- 2 | slug: "/" 3 | title: "Introduction to OpenSauced 🍕" 4 | sidebar_label: "Introduction to OpenSauced 🍕" 5 | keywords: 6 | - "introduction" 7 | - "introduction to opensauced" 8 | - "opensauced introduction" 9 | - "get to know opensauced" 10 | --- 11 | 12 | ![Example banner](../static/img/what-is-opensauced.png) 13 | 14 | :::info 15 | 16 | You can watch "[What is OpenSauced?](https://www.youtube.com/watch?v=JCNjj19iDa4)" on YouTube. 17 | 18 | ::: 19 | 20 | OpenSauced is a platform dedicated to empowering maintainers and teams and redefining the meaning of open source contributions. We believe that every contribution, big or small, is valuable and deserves to be recognized. Our platform provides a way to track contributions through a GitHub-powered dashboard, allowing users to showcase their contributions and gain insights into their open source projects. 21 | 22 | Our mission is to: 23 | 24 | - [**Empower maintainers and teams**](../docs/maintainers/maintainers-guide.md): Track and showcase your contributions and projects, connect with contributors, collaborate with your team, and gain insights into your open source projects. 25 | - [**Support contributors**](../docs/contributors/contributors-guide.md): Showcase your contributions, tell your story, connect with new projects and other contributors, and gain insights into your open source journey. 26 | - [**Highlight success**](../docs/features/highlights.md): Showcase your contributions with our shareable Highlights, inspiring others to embark on their open source journey. 27 | - [**Unlock Insights**](./features/repo-insights.md): Understand the health of your project, track contributions, and make data-driven decisions with OpenSauced Insights. 28 | -------------------------------------------------------------------------------- /docs/maintainers/understanding-contrib-insights.md: -------------------------------------------------------------------------------- 1 | --- 2 | id: understanding-contribs-insights 3 | title: "Understanding Contributor Insights Data" 4 | sidebar_label: "Understanding Contributor Insights Data" 5 | keywords: 6 | - "maintainers" 7 | - "guides" 8 | - "Contributor Insights Analysis" 9 | - "List Data Exploration" 10 | - "Data Organization" 11 | - "Data Insight from Contributor Insights" 12 | - "List Visualization" 13 | - "Data Representation in Contributor Insights" 14 | - "List Data Interpretation" 15 | - "Organizing Data in Contributor Insights" 16 | --- 17 | 18 | Once you've created your Contributor Insight Page, it's time to understand the data provided. Understanding this data is key to effectively managing your projects and contributors. 19 | 20 | ## Understanding Contributor Insights Data 21 | 22 | ### Interpreting Total Commits in the Last 30 Days 23 | 24 | Understanding the commits over the last 30 days helps in gauging the overall activity and productivity of the group. 25 | 26 | High commit volume might indicate a highly active and engaged team. A sudden drop could signal potential issues or a need for additional support or motivation. 27 | 28 | ### Monitoring Active Contributors 29 | 30 | Identifying active contributors helps in recognizing reliable team members and planning future tasks. 31 | 32 | Trends in active contributor numbers can indicate the health of the project community and the effectiveness of engagement strategies. Notice the ebbs and flows in individual contributors’ activity. 33 | 34 | A decline in a normally active contributor’s engagement could indicate burnout or dissatisfaction, while a surge in activity might be tied to recent changes or enhancements in the project. Tracking activity levels can help you manage team burnout, understand resource needs, and spot potential issues before they escalate. 35 | 36 | Each contributor has an OSCR score that reflects their recent activity and engagement. This score can help you identify key contributors, their recent activity and effectiveness, and recognize impactful contributors. 37 | 38 | ### Understanding Types of Contributors 39 | 40 | #### New Contributors 41 | 42 | Tracking new contributors is key to understanding the growth and influx of new talent. 43 | 44 | An influx of new contributors might be a positive sign of project popularity, successful outreach efforts, or the community health of your project. However, it could also indicate a need for more support and guidance for new contributors. 45 | 46 | #### Alumni Contributors 47 | 48 | Alumni contributors are contributors who haven't been active in the last 30 days. Identifying contributors who have stopped contributing helps in assessing potential issues or dissatisfaction. 49 | 50 | High churn rates could signal deeper problems within the project environment or community management. 51 | 52 | #### Most Active Contributors 53 | 54 | Identifying key contributors and potential leaders is important for project health and growth. It can help with delegation of responsibilities and recognition of top performers. It can also identify potential mentors for new contributors and help in planning for succession. 55 | 56 | If you see that a few active contributors are doing most of the work, it might be a sign that the project needs more support or that the workload needs to be better distributed. 57 | 58 | ### Activity Across Other Repositories 59 | 60 | Understanding the range of repositories to which contributors in a list have recently contributed shows the broader interests and skills of the community. It reveals contributors' engagement levels and potential specializations, which allows for effective task allocation and identifying mentorship or leadership candidates. 61 | 62 | Additionally, it opens paths for potential cross-project collaborations and strategic project planning, aligning the project’s goals with trends and interests in the open source ecosystem. 63 | 64 | Understanding the recent history of each contributor's engagement assists in tracking individual contribution patterns and identifying potentially cooling interests. 65 | -------------------------------------------------------------------------------- /docs/maintainers/understanding-repo-insights.md: -------------------------------------------------------------------------------- 1 | --- 2 | id: understanding-repo-insights 3 | title: "Understanding Repo Insights Data" 4 | sidebar_label: "Understanding Repo Insights Data" 5 | keywords: 6 | - "maintainers" 7 | - "guides" 8 | - "Insights Interpretation" 9 | - "Analytical Understanding" 10 | - "Insights Overview" 11 | - "Maintainer Insights" 12 | - "Guide to Data Understanding" 13 | - "Data Interpretation Methods" 14 | - "Insightful Data Examination" 15 | - "Guide to Understanding Data" 16 | --- 17 | 18 | Once your repositories are connected, it's time to understand the data provided on your page. Understanding this data is key to effectively managing your projects and contributors. 19 | 20 | ## Understanding Repository Insights Data 21 | 22 | ### Analyzing Contribution Trends 23 | 24 | Discover patterns in contributions over time. Look for spikes or drops in activity and correlate these with specific events or milestones. This can help you understand what drives engagement in your projects. 25 | 26 | ### Monitoring PR Activity 27 | 28 | Knowing the status of PRs (open, closed, draft, merged) helps in understanding the workflow efficiency and backlog. High volumes of open or draft PRs might indicate a need for more resources or a revision of your review process. Conversely, a steady flow of merged PRs can indicate a healthy, active development process. 29 | 30 | ### Measuring and Improving PR Velocity 31 | 32 | Track how quickly PRs are being merged. The average time taken for PRs to merge is a critical metric for understanding the efficiency of the code review and deployment process. Longer PR merge times might signal issues in the review process or resource allocation or could indicate complex code changes that require more thorough checks. Use this data to set benchmarks and identify opportunities for streamlining your review and integration processes. 33 | 34 | ## Understanding Repository Insights Contributor Data 35 | 36 | ### Identifying and Engaging with Key Contributors 37 | 38 | Recognizing key contributors helps in understanding the project's most active and influential members. Consider reaching out to them for deeper collaboration or acknowledging their efforts to keep them motivated and engaged. 39 | 40 | ### Tracking and Responding to Contributor Activity Levels 41 | 42 | Tracking how active contributors are and the trends in their activity levels is crucial for project health. Understanding the activity patterns of contributors helps in assessing their engagement and reliability. Regular contributors are often more familiar with the project and can be more dependable for critical tasks. 43 | 44 | Notice the ebbs and flows in individual contributor's activity. A decline in a normally active contributor’s engagement could indicate burnout or dissatisfaction, while a surge in activity might be tied to recent changes or enhancements in the project. Tracking activity levels can help you manage team burnout, understand resource needs, and spot potential issues before they escalate. 45 | 46 | ### Activity Levels Across Repositories 47 | 48 | This indicates the breadth of a contributor's involvement in open source projects. A contributor active across multiple repositories might bring diverse experiences and ideas but may also have divided attention. Alternatively, a contributor active in a single repository might be more focused and familiar with the project. 49 | 50 | ### Understanding Activity Levels Over Time 51 | 52 | Past activity levels can be a predictor of future contributions. Regular past contributions might suggest continued involvement. However, a contributor who has been inactive for a while might be less likely to contribute in the future. 53 | 54 | Trends in activity levels and contributions can be indicators of the overall health of the project community. A decline in activity might signal issues that need addressing to keep the community vibrant and engaged. 55 | 56 | ### Using Programming Language Data 57 | 58 | Awareness of the programming languages a contributor is comfortable with enables maintainers to assign tasks more effectively, ensuring that contributors work in areas where they are most skilled and interested. This can help in identifying contributors for specific tasks or projects. 59 | 60 | ### Creating Opportunities 61 | 62 | Understanding who contributes to what open source projects and when they do can help maintainers manage team dynamics. With this information, maintainers can make decisions to ensure workloads are balanced and contributors are working in areas that match their skills and interests. Identifying less experienced contributors who are active and showing potential can lead to mentorship opportunities, helping to grow the project’s contributor base. 63 | -------------------------------------------------------------------------------- /docs/opensauced-guides/job-seekers-guide/introduction.md: -------------------------------------------------------------------------------- 1 | --- 2 | id: job-seekers-guide-introduction 3 | title: "Learn How to Land a Tech Job Using OpenSauced" 4 | sidebar_label: "Introduction" 5 | keywords: 6 | - "open source tech job guide" 7 | - "open sauced tech job tips" 8 | - "open source career development" 9 | - "open source projects for tech resume" 10 | - "open source skills for tech employers" 11 | - "land your dream tech job" 12 | --- 13 | 14 | When you are looking for a tech job, it is important to stand out amongst the sea of candidates. One great way to stand out and showcase your skills is through open source contributions. 15 | 16 | Open source provides you the opportunity to showcase your code, documentation, communication, and collaboration skills to potential employers. You also have the ability to grow your professional network and build real connections within the tech industry through open source. 17 | 18 | OpenSauced can help you craft an open source profile that is attractive to hiring managers and recruiters and help you land that next role. 19 | 20 | In this guide, you will learn how to use OpenSauced features like your personal [Dev Card](../../features/dev-card.md), [Highlights](../../features/highlights.md), [Contributor Insights](../../features/contributor-insights.md), and [Repository Insights](../../features/repo-insights.md) to showcase your open source work and build connections to help you land a job. 21 | -------------------------------------------------------------------------------- /docs/opensauced-packages/check-engines.md: -------------------------------------------------------------------------------- 1 | --- 2 | id: check-engines 3 | title: "@open-sauced/check-engines" 4 | sidebar_label: "@open-sauced/check-engines" 5 | keywords: 6 | - "check engines" 7 | --- 8 | 9 | ## Description 10 | 11 | The `npm` package `@open-sauced/check-engines` is designed to help contributors install dependencies conforming to the `engines` property in `package.json`. 12 | 13 | ## Dependencies 14 | 15 | This package uses the following modules: 16 | 17 | - [npm-install-checks](https://github.com/npm/npm-install-checks) 18 | 19 | ## Installation 20 | 21 | ```shell 22 | npm install --save-dev @open-sauced/check-engines 23 | ``` 24 | 25 | Add the verification scripts to your `scripts` section in the `package.json` file: 26 | 27 | ```json 28 | { 29 | "scripts": { 30 | "preinstall": "npx @open-sauced/check-engines" 31 | } 32 | } 33 | ``` 34 | 35 | The reason why we provide `npx` in the `scripts` section is for the people using this as a development enhancement, interactive configurations or trimmed dependency trees, where using `npx` is preferred over installing all the dependencies at once. 36 | 37 | ## Usage 38 | 39 | Use your favorite package manager to install dependencies in your project or, if you set it as a global verification system: 40 | 41 | ```json 42 | { 43 | "scripts": { 44 | "check-engines": "npx @open-sauced/check-engines" 45 | "preinstall": "npm run check-engines", 46 | "prestart": "npm run check-engines" 47 | } 48 | } 49 | ``` 50 | 51 | ## Advanced Usage 52 | 53 | If you have an API or any other non-library type of application, you can decouple this package from any install scripts and just use it as a verification: 54 | 55 | ```json 56 | { 57 | "scripts": { 58 | "check-engines": "npx @open-sauced/check-engines" 59 | "prestart": "npm run check-engines" 60 | } 61 | } 62 | ``` 63 | 64 | A more traditional approach not using `pre` or `post` scripts, this example enables the check only for local machine development: 65 | 66 | ```json 67 | { 68 | "scripts": { 69 | "check-engines": "npx @open-sauced/check-engines" 70 | "start": "...", 71 | "dev": "npm run check-engines && npm start -- --watch" 72 | } 73 | } 74 | ``` 75 | 76 | ## FAQs 77 | 78 | ### Usage on an Older `node` and `npm` Versions 79 | 80 | Older `node` and `npm` versions won't be able to run this package; depending on the versions, the scripts section could be ignored completely. 81 | 82 | If you have that use case, this package is only worth enabling for progressive contributors frequently missing the legacy support of the respective module and forcefully upgrading dependencies - them running newer versions will force the error message and explicitly disable. 83 | 84 | ### Why Not Use `check-engines` or `engine-strict`? 85 | 86 | As described in the `npm@6` [engine-strict docs](https://docs.npmjs.com/cli/v6/configuring-npm/package-json#enginestrict): 87 | 88 | > Prior to npm 3.0.0, this feature was used to treat this package as if the user had set `engine-strict`. It is no longer used. 89 | 90 | In `npm@6` and later, this was re-introduced as a [config flag](https://docs.npmjs.com/cli/v7/using-npm/config#engine-strict). 91 | 92 | This package is designed with multiple legacy use cases in mind. 93 | 94 | ### Library Usage 95 | 96 | If you use this module in a library package, be advised that any `*install` script will run in the parent module when installed. 97 | 98 | For example, given a module `@demo-org/demo-package` with a `preinstall: "npx @open-sauced/check-engines"` script, running `npm install @demo-org/demo-package` will require your locally installed `node` and `npm` versions to match the `engines` section of your `package.json`. If that is not set, nothing should happen, and this package is a stray dependency in either `@demo-org/demo-package` or the module you are running this command in. 99 | 100 | ## Contributing 101 | 102 | We're always happy to onboard people into open source! 103 | 104 | Check out the repository at [@open-sauced/check-engines](https://github.com/open-sauced/check-engines). ❤️ 105 | -------------------------------------------------------------------------------- /docs/opensauced-packages/conventional-commit.md: -------------------------------------------------------------------------------- 1 | --- 2 | id: conventional-commit 3 | title: "@open-sauced/conventional-commit" 4 | sidebar_label: "@open-sauced/conventional-commit" 5 | keywords: 6 | - "commitizen conventional commit" 7 | - "open source commit standards" 8 | - "how to use @open-sauced/conventional-commit" 9 | - "npm package for conventional commit" 10 | - "open sauced commit guide" 11 | - "conventional commit best practices" 12 | - "Commit Message Standards" 13 | - "Semantic Versioning" 14 | - "Git Commit Conventions" 15 | - "Standardized Commit Messages" 16 | - "Version Control Best Practices" 17 | --- 18 | 19 | ## Description 20 | 21 | The `npm` package `@open-sauced/conventional-commit` is designed to help users `git commit` using [commitizen](https://github.com/commitizen/cz-cli) and [conventional commits](https://www.conventionalcommits.org/en/v1.0.0/). 22 | 23 | ## Dependencies 24 | 25 | This package uses the following modules: 26 | 27 | - [cz-cli](https://github.com/commitizen/cz-cli) 28 | - [cz-conventional-changelog](https://github.com/commitizen/cz-conventional-changelog) 29 | 30 | ## Installation 31 | 32 | ```shell 33 | npm install --save-dev @open-sauced/conventional-commit 34 | ``` 35 | 36 | Add the verification scripts to your `scripts` section in the `package.json` file: 37 | 38 | ```json 39 | { 40 | "scripts" { 41 | "push" "npx @open-sauced/conventional-commit" 42 | } 43 | } 44 | ``` 45 | 46 | The reason why we provide `npx` in the `scripts` section is for the people using this as a development enhancement, interactive configurations, or trimmed dependency trees, where using `npx` is preferred over installing all the dependencies at once. 47 | 48 | ## Usage 49 | 50 | All you have to do is run the script next to your `package.json`: 51 | 52 | ```shell 53 | npx @open-sauced/conventional-commit 54 | # or 55 | npx conventional-commit 56 | ``` 57 | 58 | ## Advanced Usage 59 | 60 | The most common use case for this package is to run it instead of the `git commit` command inside your `npm` scripts: 61 | 62 | ```json 63 | { 64 | "scripts" { 65 | "push" "npx @open-sauced/conventional-commit" 66 | } 67 | } 68 | ``` 69 | 70 | or 71 | 72 | ```json 73 | { 74 | "scripts" { 75 | "push" "npx conventional-commit" 76 | } 77 | } 78 | ``` 79 | 80 | If you want to ensure local-only usage: 81 | 82 | ```json 83 | { 84 | "scripts" { 85 | "push" "conventional-commit" 86 | } 87 | } 88 | ``` 89 | 90 | ## FAQs 91 | 92 | ## Contributing 93 | 94 | We're always happy to onboard people into open source! 95 | 96 | Check out the repository at [@open-sauced/conventional-commit](https://github.com/open-sauced/conventional-commit). ❤️ 97 | -------------------------------------------------------------------------------- /docs/tools/chrome-extension/highlights.md: -------------------------------------------------------------------------------- 1 | --- 2 | id: highlights 3 | title: "Highlight" 4 | sidebar_label: "Highlight" 5 | keywords: 6 | - "highlights" 7 | - "posting" 8 | - "Content Highlights" 9 | - "Featured Content" 10 | - "Noteworthy Points" 11 | - "Key Takeaways" 12 | - "Highlighted Information" 13 | - "Standout Features" 14 | - "Important Details" 15 | - "Highlighted Sections" 16 | - "Posting Highlights" 17 | - "Notable Content" 18 | - "Highlighted Insights" 19 | --- 20 | 21 | If you're in GitHub, you can use the OpenSauced Chrome Extension to post a [highlight](highlights.md) of your pull requests to the OpenSauced website. 22 | 23 | You can access the post to highlight it from the popup window in the extension. When you click it, it will automatically, populate the PR title and you can provide the summary. 24 | 25 | If your Highlight is successfully posted, you will get a message with an option to see the Highlight on the OpenSauced website. 26 | 27 | ![Successful message example](https://github.com/open-sauced/docs.opensauced.pizza/assets/18273833/723ac624-e996-45f8-acdf-0d3ff08af90b) 28 | -------------------------------------------------------------------------------- /docs/tools/chrome-extension/introduction-to-the-chrome-extension.md: -------------------------------------------------------------------------------- 1 | --- 2 | id: introduction-to-the-chrome-extension 3 | title: "Introduction to the Chrome Extension" 4 | sidebar_label: "Introduction to the Chrome Extension" 5 | keywords: 6 | - "introduction to the chrome extension" 7 | - "Chrome Extension Overview" 8 | - "Browser Extension Introduction" 9 | - "Chrome Add-On Introduction" 10 | - "Extension Development Basics" 11 | - "Getting Started with Chrome Extension" 12 | - "Browser Plugin Introduction" 13 | - "Chrome Web Store Add-On" 14 | - "Extension Development Guide" 15 | - "Chrome Extension Features" 16 | - "Introduction to Browser Extensions" 17 | - "Chrome Extension Fundamentals" 18 | - "Web Browser Plugin Basics" 19 | --- 20 | 21 | ## The OpenSauced Chrome Extension 22 | 23 | The OpenSauced Chrome extension seamlessly integrates GitHub with the OpenSauced platform. With this extension, you can easily view and discover open-source projects looking for contributions directly from GitHub, making collaboration and contribution easier than ever. 24 | 25 | ## Installing the Chrome Extension 26 | 27 | To install the OpenSauced Chrome extension, navigate to the [OpenSauced.ai extension on Chrome Web Store](https://chrome.google.com/webstore/detail/opensauced/aebjdjjodmkdnmejakflnfpkadblfmdh) and click the "Add to Chrome" button. 28 | -------------------------------------------------------------------------------- /docs/tools/chrome-extension/viewing-insights-and-invitations.md: -------------------------------------------------------------------------------- 1 | --- 2 | id: viewing-insights-and-invitations 3 | title: "Viewing Insights and Invitations" 4 | sidebar_label: "Insights and Invitations" 5 | keywords: 6 | - "github" 7 | - "insights and invitations" 8 | - "github insights and invitations" 9 | - "how to view insights and invitations on github" 10 | - "github insights dashboard" 11 | - "github invitations management" 12 | - "github insights and invitations tutorial" 13 | - "github insights and invitations best practices" 14 | - "github insights and invitations examples" 15 | --- 16 | 17 | View stats about open issues, PRs made, average PRs velocity, and contributed repos that are in the OpenSauced database. This page can be found by clicking the profile picture at the top left of the extension. 18 | 19 | ![GitHub Profile Insights](../../../static/img/extension-popup.png) 20 | 21 | ## Invite GitHub Users to Join OpenSauced With a Single Click 22 | 23 | Invite other users to create an OpenSauced account to keep track of open source contributions when visiting their GitHub profile. 24 | 25 | ![Invite GitHub Users](../../../static/img/extension-invite.png) 26 | 27 | ## View GitHub Users' OpenSauced Profiles and Connect With Them 28 | 29 | View a user’s OpenSauced profile when on their GitHub profile page. 30 | 31 | ![View OpenSauced Profiles](../../../static/img/extension-view.png) 32 | -------------------------------------------------------------------------------- /docs/tools/hot-opensauced.md: -------------------------------------------------------------------------------- 1 | --- 2 | id: hot-opensauced 3 | title: "Hot OpenSauced Project" 4 | sidebar_label: "Hot OpenSauced Project" 5 | keywords: 6 | - "hot opensauced project" 7 | - "Open Source Projects" 8 | - "Trending OpenSauced Projects" 9 | - "Featured Open Source Repositories" 10 | - "Active GitHub Projects" 11 | - "Noteworthy Open Source Initiatives" 12 | - "Popular GitHub Repositories" 13 | --- 14 | 15 | :::danger 16 | 17 | This tool is deprecated. To discover open source projects to contribute to, check out the [OpenSauced Explore Page](https://app.opensauced.pizza/explore/topic/javascript). 18 | 19 | ::: 20 | 21 | [Hot OpenSauced](https://hot.opensauced.pizza/) is a site that helps you discover the hottest open source projects to contribute to. You also have the ability to vote for your favorite open source projects. 22 | 23 | ## How to Find Hot Open Source Projects to Contribute to? 24 | 25 | When you visit the [Hot OpenSauced](https://hot.opensauced.pizza/) site, you will see a list of open source projects that are currently trending on GitHub. You can sign in with your GitHub account and search for the most upvoted, recent, and popular projects. 26 | 27 | ![hot opensauced upvoted repos](../../static/img/upvoted-repos-hot-opensauced.png) 28 | 29 | ## How to Vote for Your Favorite Open Source Projects? 30 | 31 | You can vote for your favorite open source project by clicking on the upvote button. You can view all of your upvoted projects under the My Votes tab. 32 | 33 | ![hot opensauced popular repos](../../static/img/popular-repos-hot-opensauced.png) 34 | -------------------------------------------------------------------------------- /docs/tools/pizza-cli/pizza-action.md: -------------------------------------------------------------------------------- 1 | --- 2 | id: pizza-action 3 | title: "Pizza CLI Action" 4 | sidebar_label: "Pizza Action" 5 | keywords: 6 | - "codeowners" 7 | - "codeowners automation" 8 | - "CLI codeowners" 9 | - "GitHub Actions" 10 | - "Codeowners GitHub Action" 11 | --- 12 | 13 | To automatically update your CODEOWNERS file every week, you can use the OpenSauced Pizza GitHub Action. This action runs the Pizza CLI in a GitHub Actions workflow. 14 | 15 | To set up the action: 16 | 17 | 1. Create a new file in your repository at `.github/workflows/pizza-action.yml` 18 | 2. Add the following content to the file: 19 | 20 | ```yaml 21 | name: OpenSauced Pizza Action 22 | 23 | on: 24 | schedule: 25 | # Run once a week on Sunday at 00:00 UTC 26 | - cron: "0 0 * * 0" 27 | workflow_dispatch: # Allow manual triggering 28 | 29 | jobs: 30 | pizza-action: 31 | runs-on: ubuntu-latest 32 | steps: 33 | - name: Pizza Action 34 | uses: open-sauced/pizza-action@v2.3.0 35 | with: 36 | # optional and false by default 37 | commit-and-pr: "true" 38 | 39 | ``` 40 | 41 | This workflow will run the Pizza CLI's `generate codeowners ./` command once a week, ensuring your CODEOWNERS file stays up-to-date. 42 | 43 | :::info 44 | 45 | - The action uses `fetch-depth: 0` to ensure all historical commits are available for analysis. 46 | - The `commit-and-pr` input determines whether to commit changes and create a pull request (default is `false`). 47 | - You can customize the `pizza-args` input to pass different arguments to the Pizza CLI (default is `generate codeowners ./`). 48 | 49 | ::: 50 | 51 | For more information about the Pizza Action, visit the [open-sauced/pizza-action repository](https://github.com/open-sauced/pizza-action). 52 | 53 | ### Troubleshooting 54 | 55 | If you encounter the error "pull request create failed: GraphQL: GitHub Actions is not permitted to create or approve pull requests (createPullRequest)", go to your repository settings under the Actions section and check "Allow GitHub Actions to create and approve pull requests". -------------------------------------------------------------------------------- /docs/tools/pizza-cli/pizza-cli.md: -------------------------------------------------------------------------------- 1 | --- 2 | id: pizza-cli 3 | title: "Introduction to the Pizza CLI" 4 | sidebar_label: "Pizza CLI" 5 | keywords: 6 | - "introduction to the pizza cli" 7 | - "Pizza CLI Overview" 8 | - "Command Line Interface Introduction" 9 | - "CLI Basics for GitHub Insights" 10 | - "CLI Usage Guide" 11 | - "Pizza CLI Commands" 12 | - "Introduction to Command-Line Interfaces" 13 | - "Command Line Tool Features" 14 | - "Getting Started with the CLI for GitHub Insights" 15 | --- 16 | 17 | The OpenSauced Pizza CLI is a command-line utility designed specifically for OpenSauced. It provides a comprehensive set of functionalities that make it easier for users to gain insights and metrics and manage various tasks related to open source projects through OpenSauced. 18 | 19 | Beyond just code commits, the pizza CLI reports on different ways individuals contribute to the open source ecosystem through community engagement, issue reporting, blog post writings, or pull request creations. 20 | 21 | :::info 22 | 23 | To access the CLI repo, visit the [pizza/cli GitHub repository](https://github.com/open-sauced/pizza-cli). 24 | 25 | ::: 26 | 27 | ## Key Features 28 | 29 | - **Bake**: Seamlessly source git commits into OpenSauced with the metaphorical 'oven' of technology. 30 | - **Insights**: Dive deep into data about git contributors, repositories, users, and pull requests. 31 | - **Repo-query**: Get your questions about any GitHub repository answered. 32 | - **Show**: Visualize the metrics of a repository, providing a holistic view of its health and activity. 33 | - **Login**: Securely log into the application via GitHub, ensuring a streamlined and safe experience. 34 | - **Codeowners**: Generate and manage CODEOWNERS files for your repositories. 35 | 36 | :::tip 37 | 38 | For more on the Codeowners command, visit the [Codeowners page](codeowners.md) 39 | 40 | ::: 41 | 42 | ## Installation and Instructions 43 | 44 | ### 📦 Download and Install 45 | 46 | The pizza CLI provides multiple installation methods to cater to the varied preferences of its users: 47 | 48 | - **Homebrew**: For macOS users who prefer the Homebrew package manager. 49 | 50 | ```bash 51 | brew install open-sauced/tap/pizza 52 | ``` 53 | 54 | - **NPM**: For those who are fond of the Node Package Manager. 55 | 56 | ```bash 57 | npm i -g pizza 58 | ``` 59 | 60 | - **Direct script**: A quick way to get started by directly fetching the installation script from GitHub. 61 | 62 | ```bash 63 | curl -fsSL https://raw.githubusercontent.com/open-sauced/pizza-cli/main/install.sh 64 | ``` 65 | :::danger 66 | 67 | Piping scripts directly from the web to your shell can be risky. Always ensure you trust the source. 68 | 69 | ::: 70 | 71 | For a safer approach, download, inspect, and then execute the following commands: 72 | 73 | ```bash 74 | curl -fsSL https://raw.githubusercontent.com/open-sauced/pizza-cli/main/install.sh > install.sh 75 | vim install.sh 76 | ./install.sh 77 | ``` 78 | - **Manual build and install**: For those who like a hands-on approach. 79 | 80 | ```bash 81 | make install 82 | ``` 83 | 84 | Ensure `/usr/local/bin/` is in your path with: 85 | 86 | ```bash 87 | export PATH="$PATH:/usr/local/bin" 88 | ``` 89 | 90 | Alternatively, after building with `make build`, move the binary to your desired location: 91 | 92 | ```bash 93 | mv build/pizza 94 | ``` 95 | 96 | ### 🖥️ Local Development Setup 97 | 98 | To contribute to or modify the pizza CLI, you need a specific set of tools: 99 | 100 | - [**Go Toolchain**](https://go.dev/doc/install): The foundational tool for building and managing Go applications. 101 | - [**Docker**](https://docs.docker.com/engine/install/): Required for linting and other auxiliary tooling. 102 | - **Make**: A build automation tool. 103 | 104 | Development commands: 105 | 106 | - **Linting**: Ensure code quality with `make lint`. 107 | - **Testing**: Verify functionality with `make test`. 108 | - **Building**: Create the executable with `make build`. 109 | -------------------------------------------------------------------------------- /docs/welcome/faqs.md: -------------------------------------------------------------------------------- 1 | --- 2 | id: faqs 3 | title: "Frequently Asked Questions" 4 | sidebar_label: "FAQs" 5 | keywords: 6 | - "faqs" 7 | - "Frequently asked questions" 8 | - "Popular FAQs guide" 9 | - "most asked questions" 10 | --- 11 | 12 | ## Contributions 13 | 14 | ### 1. How do I find good first issues? 15 | 16 | We believe that [good first issues don't exist](https://opensauced.pizza/blog/good-first-issues-dont-exist), and the best way to find an issue to work on is to create the issue yourself. 17 | 18 | However, sites like [Good First Issues](https://goodfirstissues.com/) and [First Timers Only](https://www.firsttimersonly.com/) can lead you to projects and issues worth working on. You can also use the `good first issue` label in the project search engine you want to contribute to. Check out [this guide](https://www.freecodecamp.org/news/how-to-find-good-first-issues-on-github/) to learn more about finding a `good first issue` on GitHub. 19 | 20 | #### Additional Resources: 21 | 22 | - ["Who's looking for open source contributors?" series on Dev.to](https://dev.to/bekahhw/series/23323) 23 | - [Intro to Open Source Course with OpenSauced](https://opensauced.pizza/learn/) 24 | 25 | ### 2. My contribution does not show up on my OpenSauced profile. How do I fix it? 26 | 27 | Create a [Repository Insights Page](https://app.opensauced.pizza/hub/insights) or add your merged pull request to a [Highlight](https://app.opensauced.pizza/feed). 28 | 29 | ### 3. Why does OpenSauced display contributors comments? 30 | 31 | On every OpenSauced user profile, in the contributions tab, we display the Pull Requests and Issues that the user has commented on. This is to give a more comprehensive view of the user's contributions to the open-source community. It also provides insight into the contributor's depth of knowledge, collaboration and communication skills, and provides an additional data point for understanding the user's open-source contributions. 32 | 33 | ### 4. I want to provide feedback on OpenSauced. 34 | 35 | We love feedback. Post your suggestion in our [feedback repository](https://github.com/orgs/open-sauced/discussions). 36 | 37 | ### 5. How is the OSCR calculated? 38 | 39 | The OpenSauced Contributor Rating (OSCR) is calculated using a combination of factors that reflect a contributor's overall impact in open source. The OSCR considers contribution quality and consistency, community engagement, project impact, collaboration skills, ecosystem involvement, and reputation. These categories are evaluated over recent activity periods (90 days) to produce a comprehensive score that represents a contributor's value (out of 300 total points) to the open source community. 40 | 41 | ## Sync Your GitHub Team 42 | 43 | ### 1. I don't see my organization on "Sync your GitHub Team." 44 | 45 | You may not see your organization if you are not a "public" member. You can update this by going to the organization on GitHub and selecting the "People" tab. Next, search for your name. You can then change "private" to "public." For complete instructions, see [this guide](https://docs.github.com/en/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-membership-in-organizations/publicizing-or-hiding-organization-membership). 46 | 47 | ### 2. I get an error when I try to select my team in "Sync your GitHub Team." 48 | 49 | If you see your organization but get an error when selecting a team, your organization likely has restricted third-party applications. You can check this if you are an owner by going to "Your organizations" on GitHub, selecting "Settings", and then "Third-party Access." 50 | 51 | If you're an **owner** of the repository, you can select "Allow select third-party access" or specifically approve OpenSauced by following the directions in [this guide](https://docs.github.com/en/organizations/managing-oauth-access-to-your-organizations-data/approving-oauth-apps-for-your-organization). 52 | 53 | If you are not an owner of the organization, you will need to check with your organization's owner and request access. For complete instructions, see [this guide](https://docs.github.com/en/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-membership-in-organizations/requesting-organization-approval-for-oauth-apps). 54 | 55 | ### 3. Do I need to grant authorization to connect GitHub to OpenSauced? 56 | 57 | Yes, auth access through GitHub OAuth is required to link your profile to a workspace/team. As an early stage startup, we chose this method for its simplicity. We also request read-only access to your GitHub organizations to gather Contributor Insights based on public GitHub Teams data. We ensure all data used is public and read-only. 58 | -------------------------------------------------------------------------------- /docs/welcome/glossary.md: -------------------------------------------------------------------------------- 1 | --- 2 | id: glossary 3 | title: "OpenSauced Glossary" 4 | sidebar_label: "OpenSauced Glossary" 5 | keywords: 6 | - "glossary" 7 | - "openSauced" 8 | - "OpenSauced Glossary" 9 | - "Tech Glossary" 10 | - "OpenSauced Glossary Guide" 11 | - "Open Source Project Glossary" 12 | --- 13 | 14 | Welcome to the glossary, where we define concepts used on our platform to help you get the most out of OpenSauced. 15 | 16 | ## Active Contributors 17 | 18 | A contributor who has been active in the last 30 days. 19 | 20 | ## Activity 21 | 22 | Activity tracks Pull Requests (PRs) over the last 30 days: 23 | 24 | - **High**: More than 80 PRs. 25 | - **Medium**: Between 5 and 80 PRs. 26 | - **Low**: Below 5 PRs. 27 | 28 | ## Activity Ratio 29 | 30 | The activity ratio in Workspaces is based on pull request commits, issues comments, and the number of unique contributors. 31 | 32 | ## Alumni Contributors 33 | 34 | A contributor who has not been active on a project in the last 30 days. 35 | 36 | ## Contributor Confidence 37 | 38 | Contributor Confidence is a metric that estimates the likelihood of users who star or fork a repository returning to make contributions within a specified time range. It is calculated by analyzing the contribution patterns of these users, considering both their activity in other repositories and their direct contributions to the repository in question. Forks are weighted more heavily than stars, and users who do return to contribute significantly influence the confidence score. This metric helps contributors gauge the activity level of a repository and assists maintainers in understanding user engagement, thereby providing insights into the overall health and vibrancy of the project. 39 | 40 | ## Contributor Insights 41 | 42 | The Contributor Insights feature enables you to categorize, monitor, and analyze different groups of contributors within open source projects. With the Contributor Insights feature, gain granular insights into each contributor's activity and contributions. 43 | 44 | ## Lottery Factor 45 | 46 | The Lottery Factor is a metric that identifies how at risk a project is if a key contributor leaves. It is calculated by the percentage of pull request (PR) contributions made by the top contributors. If 50% of the PR contributions come from two or fewer contributors, the lottery factor is high. 47 | 48 | The name "Lottery Factor" comes from the idea that if a key contributor wins the lottery and leaves, the project is at risk. This is sometimes known as the [bus factor](https://en.wikipedia.org/wiki/Bus_factor). 49 | 50 | ## New Contributors 51 | 52 | A contributor who has recently made their first contribution to a project. 53 | 54 | ## OSCR 55 | 56 | OSCR, or Open Source Contributor Rating, is a metric that evaluates the engagement and impact of contributors in open source projects. The OSCR is calculated on a rolling 90-day basis out of 300 points total and looks at all of a contributors open source contributions. To create the score, we look at the quality of contributions, their [contributor confidence](#contributor-confidence), and their sway - the ability to drive conversation in the open source ecosystem. The score reflects recent activity and engagement, providing a current snapshot of a contributor's involvement rather than a lifetime aggregate. 57 | 58 | ## OSSF Scorecard 59 | 60 | The Open Source Security Foundation (OSSF) Scorecard is a standardized metric developed by the Open Source Security Foundation to evaluate the security practices of open source projects based on a set of security criteria. These criteria cover various aspects of project maintenance and security practices. The resulting score provides a quick overview of the project's adherence to security best practices. 61 | 62 | ## PR Overview 63 | 64 | PR Overview tells the story of the Pull Requests (PRs) submitted in the last 30 days: 65 | 66 | - **Green line**: Open PRs. 67 | - **Red line**: Closed PRs. 68 | - **Purple line**: Merged PRs. 69 | - **Grey line**: Draft PRs. 70 | 71 | ## PR Velocity 72 | 73 | PR Velocity tracks how quickly Pull Requests (PRs) are being merged in by identifying the average time to completion from the request submission. 74 | 75 | ## Repository Insights 76 | 77 | The Repository Insights feature is a one-stop solution for understanding the pulse of your open source projects and contributions. This feature is designed to provide a comprehensive view of your project's health and your individual contributions. 78 | 79 | ## YOLO Coders 80 | 81 | A “YOLO coder” is an individual owner, contributor, or maintainer who pushes changes directly to the default branch of a repository without creating a pull request or seeking any community feedback. This risky practice bypasses essential review and collaboration processes. -------------------------------------------------------------------------------- /docs/welcome/opensauced-intro.md: -------------------------------------------------------------------------------- 1 | --- 2 | id: opensauced-intro 3 | title: "What is OpenSauced?" 4 | sidebar_label: "What is OpenSauced?" 5 | keywords: 6 | - "opensauced" 7 | - "what is opensauced" 8 | - "get to know opensauced" 9 | --- 10 | 11 | ## OpenSauced: Your Open Source Partner 12 | 13 | OpenSauced is a platform dedicated to nurturing and expanding your open source community while recognizing every contributor's impact. 14 | 15 | **Our OpenSauced dashboard allows you to:** 16 | 17 | - **Understand open source projects:** Get a comprehensive view of open source contributors and their engagement. 18 | - **Discover valuable insights:** Identify key contributors, emerging trends, and valuable project insights. 19 | - **Engage effectively:** Reach out to community members to foster involvement and collaboration. 20 | - **Generate reports:** Create insightful reports to visualize and communicate the influence of your community. 21 | - **Collaborate with your team:** Work together with your team or other contributors for a holistic approach to open source. 22 | - **See beyond the green squares:** Connect with various aspects of open source contribution and community activities. 23 | 24 | ## Who is OpenSauced for? 25 | 26 | OpenSauced is for maintainers, Open Source Program Offices (OSPOs), contributors, companies, community managers, and anyone interested in what's happening in the open source ecosystem. 27 | 28 | Embarking on an OpenSauced journey enhances your growth and community engagement. Let's launch your open source success story! 🚀 29 | -------------------------------------------------------------------------------- /netlify.toml: -------------------------------------------------------------------------------- 1 | [build] 2 | base = "/" 3 | publish = "build" # Make sure this points to the correct output directory 4 | command = "npm run build" # The command to build your site 5 | -------------------------------------------------------------------------------- /package.json: -------------------------------------------------------------------------------- 1 | { 2 | "name": "@open-sauced/docs.opensauced.pizza", 3 | "version": "1.75.4", 4 | "private": true, 5 | "engines": { 6 | "node": "^18.17.0 || >=20.5.0", 7 | "npm": ">= 9.6.0" 8 | }, 9 | "scripts": { 10 | "preinstall": "npx @open-sauced/check-engines", 11 | "prestart": "npx @open-sauced/check-engines", 12 | "push": "npx @open-sauced/conventional-commit", 13 | "docusaurus": "npx docusaurus", 14 | "start": "npm run docusaurus -- start", 15 | "build": "npm run docusaurus -- build", 16 | "swizzle": "npm run docusaurus -- swizzle", 17 | "deploy": "npm run docusaurus -- deploy", 18 | "clear": "npm run docusaurus -- clear", 19 | "serve": "npm run docusaurus -- serve", 20 | "write-translations": "npm run docusaurus -- write-translations", 21 | "write-heading-ids": "npm run docusaurus -- write-heading-ids", 22 | "pdf": "npx docusaurus-prince-pdf -u http://127.0.0.1:8080 -d ./build -o ./build/open-sauced-docs.pdf -f ./open-sauced-docs.txt --include-index" 23 | }, 24 | "dependencies": { 25 | "@docusaurus/core": "^3.5.2", 26 | "@docusaurus/plugin-pwa": "^3.5.2", 27 | "@docusaurus/preset-classic": "^3.5.2", 28 | "@docusaurus/theme-search-algolia": "^3.5.2", 29 | "@mdx-js/react": "^3.0.0", 30 | "axios": "^1.7.2", 31 | "fs": "^0.0.1-security", 32 | "posthog-docusaurus": "^2.0.1", 33 | "prism-react-renderer": "^2.1.0", 34 | "react": "^18.2.0", 35 | "react-dom": "^18.2.0" 36 | }, 37 | "devDependencies": { 38 | "@open-sauced/check-engines": "^1.2.0", 39 | "@open-sauced/conventional-commit": "^1.0.1", 40 | "@svgr/webpack": "^5.5.0", 41 | "clsx": "^1.2.1", 42 | "docusaurus-prince-pdf": "^1.1.1", 43 | "file-loader": "^6.2.0", 44 | "url-loader": "^4.1.1" 45 | }, 46 | "browserslist": { 47 | "production": [ 48 | ">0.5%", 49 | "not dead", 50 | "not op_mini all" 51 | ], 52 | "development": [ 53 | "last 1 chrome version", 54 | "last 1 firefox version", 55 | "last 1 safari version" 56 | ] 57 | } 58 | } 59 | -------------------------------------------------------------------------------- /src/css/custom.css: -------------------------------------------------------------------------------- 1 | /* stylelint-disable docusaurus/copyright-header */ 2 | /** 3 | * Any CSS included here will be global. The classic template 4 | * bundles Infima by default. Infima is a CSS framework designed to 5 | * work well for content-centric websites. 6 | */ 7 | 8 | /* You can override the default Infima variables here. */ 9 | :root { 10 | --ifm-color-primary: #2e8555; 11 | --ifm-color-primary-dark: #29784c; 12 | --ifm-color-primary-darker: #277148; 13 | --ifm-color-primary-darkest: #205d3b; 14 | --ifm-color-primary-light: #33925d; 15 | --ifm-color-primary-lighter: #359962; 16 | --ifm-color-primary-lightest: #3cad6e; 17 | } 18 | html[data-theme='dark'] { 19 | --ifm-color-primary: #25c2a0; 20 | --ifm-color-primary-dark: #21af90; 21 | --ifm-color-primary-darker: #1fa588; 22 | --ifm-color-primary-darkest: #1a8870; 23 | --ifm-color-primary-light: #29d5b0; 24 | --ifm-color-primary-lighter: #32d8b4; 25 | --ifm-color-primary-lightest: #4fddbf; 26 | } 27 | 28 | .docusaurus-highlight-code-line { 29 | background-color: rgba(0, 0, 0, 0.1); 30 | display: block; 31 | margin: 0 calc(-1 * var(--ifm-pre-padding)); 32 | padding: 0 var(--ifm-pre-padding); 33 | } 34 | 35 | html[data-theme='dark'] .docusaurus-highlight-code-line { 36 | background-color: rgba(0, 0, 0, 0.3); 37 | } 38 | 39 | .footer__title { 40 | position: relative; 41 | } 42 | 43 | .footer__col > .footer__title::after { 44 | content: ''; 45 | display: inline-block; 46 | width: 28px; 47 | height: 23px; 48 | background-position: center; 49 | background-size: contain; 50 | position: absolute; 51 | background-repeat: no-repeat; 52 | } 53 | -------------------------------------------------------------------------------- /static/android-chrome-192x192.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/open-sauced/docs/81b05471f63b289ecc61fb116c68682d1199c78c/static/android-chrome-192x192.png -------------------------------------------------------------------------------- /static/android-chrome-512x512.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/open-sauced/docs/81b05471f63b289ecc61fb116c68682d1199c78c/static/android-chrome-512x512.png -------------------------------------------------------------------------------- /static/apple-touch-icon.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/open-sauced/docs/81b05471f63b289ecc61fb116c68682d1199c78c/static/apple-touch-icon.png -------------------------------------------------------------------------------- /static/favicon-16x16.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/open-sauced/docs/81b05471f63b289ecc61fb116c68682d1199c78c/static/favicon-16x16.png -------------------------------------------------------------------------------- /static/favicon-32x32.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/open-sauced/docs/81b05471f63b289ecc61fb116c68682d1199c78c/static/favicon-32x32.png -------------------------------------------------------------------------------- /static/favicon.ico: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/open-sauced/docs/81b05471f63b289ecc61fb116c68682d1199c78c/static/favicon.ico -------------------------------------------------------------------------------- /static/gif/connections.gif: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/open-sauced/docs/81b05471f63b289ecc61fb116c68682d1199c78c/static/gif/connections.gif -------------------------------------------------------------------------------- /static/gif/contributors-sync-list.gif: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/open-sauced/docs/81b05471f63b289ecc61fb116c68682d1199c78c/static/gif/contributors-sync-list.gif -------------------------------------------------------------------------------- /static/gif/highlight.gif: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/open-sauced/docs/81b05471f63b289ecc61fb116c68682d1199c78c/static/gif/highlight.gif -------------------------------------------------------------------------------- /static/gif/insight-page-demo.gif: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/open-sauced/docs/81b05471f63b289ecc61fb116c68682d1199c78c/static/gif/insight-page-demo.gif -------------------------------------------------------------------------------- /static/gif/pr-code-explain.gif: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/open-sauced/docs/81b05471f63b289ecc61fb116c68682d1199c78c/static/gif/pr-code-explain.gif -------------------------------------------------------------------------------- /static/gif/pr-code-refactor.gif: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/open-sauced/docs/81b05471f63b289ecc61fb116c68682d1199c78c/static/gif/pr-code-refactor.gif -------------------------------------------------------------------------------- /static/gif/pr-code-test.gif: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/open-sauced/docs/81b05471f63b289ecc61fb116c68682d1199c78c/static/gif/pr-code-test.gif -------------------------------------------------------------------------------- /static/gif/pr-description.gif: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/open-sauced/docs/81b05471f63b289ecc61fb116c68682d1199c78c/static/gif/pr-description.gif -------------------------------------------------------------------------------- /static/gif/team-sync-insights.gif: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/open-sauced/docs/81b05471f63b289ecc61fb116c68682d1199c78c/static/gif/team-sync-insights.gif -------------------------------------------------------------------------------- /static/gif/team-sync.gif: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/open-sauced/docs/81b05471f63b289ecc61fb116c68682d1199c78c/static/gif/team-sync.gif -------------------------------------------------------------------------------- /static/icon-144x144.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/open-sauced/docs/81b05471f63b289ecc61fb116c68682d1199c78c/static/icon-144x144.png -------------------------------------------------------------------------------- /static/icon-192x192.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/open-sauced/docs/81b05471f63b289ecc61fb116c68682d1199c78c/static/icon-192x192.png -------------------------------------------------------------------------------- /static/icon-72x72.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/open-sauced/docs/81b05471f63b289ecc61fb116c68682d1199c78c/static/icon-72x72.png -------------------------------------------------------------------------------- /static/icon-96x96.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/open-sauced/docs/81b05471f63b289ecc61fb116c68682d1199c78c/static/icon-96x96.png -------------------------------------------------------------------------------- /static/img/DevCard.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/open-sauced/docs/81b05471f63b289ecc61fb116c68682d1199c78c/static/img/DevCard.png -------------------------------------------------------------------------------- /static/img/a-dev-card.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/open-sauced/docs/81b05471f63b289ecc61fb116c68682d1199c78c/static/img/a-dev-card.png -------------------------------------------------------------------------------- /static/img/access-workspace.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/open-sauced/docs/81b05471f63b289ecc61fb116c68682d1199c78c/static/img/access-workspace.png -------------------------------------------------------------------------------- /static/img/activity-repos-insights.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/open-sauced/docs/81b05471f63b289ecc61fb116c68682d1199c78c/static/img/activity-repos-insights.png -------------------------------------------------------------------------------- /static/img/add-to-workspace.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/open-sauced/docs/81b05471f63b289ecc61fb116c68682d1199c78c/static/img/add-to-workspace.png -------------------------------------------------------------------------------- /static/img/contrib-insight-new.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/open-sauced/docs/81b05471f63b289ecc61fb116c68682d1199c78c/static/img/contrib-insight-new.png -------------------------------------------------------------------------------- /static/img/contributing-avatar-top-right.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/open-sauced/docs/81b05471f63b289ecc61fb116c68682d1199c78c/static/img/contributing-avatar-top-right.png -------------------------------------------------------------------------------- /static/img/contributing-copy-auth-token.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/open-sauced/docs/81b05471f63b289ecc61fb116c68682d1199c78c/static/img/contributing-copy-auth-token.png -------------------------------------------------------------------------------- /static/img/contributing-maintainers-create-repository.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/open-sauced/docs/81b05471f63b289ecc61fb116c68682d1199c78c/static/img/contributing-maintainers-create-repository.png -------------------------------------------------------------------------------- /static/img/contributing-maintainers-env.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/open-sauced/docs/81b05471f63b289ecc61fb116c68682d1199c78c/static/img/contributing-maintainers-env.png -------------------------------------------------------------------------------- /static/img/contributing-maintainers-merge-protections.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/open-sauced/docs/81b05471f63b289ecc61fb116c68682d1199c78c/static/img/contributing-maintainers-merge-protections.png -------------------------------------------------------------------------------- /static/img/contributing-maintainers-merge-settings.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/open-sauced/docs/81b05471f63b289ecc61fb116c68682d1199c78c/static/img/contributing-maintainers-merge-settings.png -------------------------------------------------------------------------------- /static/img/contributing-resolve-merge-conflicts-commit-message.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/open-sauced/docs/81b05471f63b289ecc61fb116c68682d1199c78c/static/img/contributing-resolve-merge-conflicts-commit-message.png -------------------------------------------------------------------------------- /static/img/contributing-resolve-merge-conflicts-dont-do.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/open-sauced/docs/81b05471f63b289ecc61fb116c68682d1199c78c/static/img/contributing-resolve-merge-conflicts-dont-do.png -------------------------------------------------------------------------------- /static/img/contributing-resolve-merge-conflicts-merge-conflicts.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/open-sauced/docs/81b05471f63b289ecc61fb116c68682d1199c78c/static/img/contributing-resolve-merge-conflicts-merge-conflicts.png -------------------------------------------------------------------------------- /static/img/contributing-resolve-merge-conflicts-merge-success.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/open-sauced/docs/81b05471f63b289ecc61fb116c68682d1199c78c/static/img/contributing-resolve-merge-conflicts-merge-success.png -------------------------------------------------------------------------------- /static/img/contributing-resolve-merge-conflicts-ready-to-merge.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/open-sauced/docs/81b05471f63b289ecc61fb116c68682d1199c78c/static/img/contributing-resolve-merge-conflicts-ready-to-merge.png -------------------------------------------------------------------------------- /static/img/contributing-resolve-merge-conflicts-review-conflicts.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/open-sauced/docs/81b05471f63b289ecc61fb116c68682d1199c78c/static/img/contributing-resolve-merge-conflicts-review-conflicts.png -------------------------------------------------------------------------------- /static/img/contributing-resolve-merge-conflicts-view-merge-commit.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/open-sauced/docs/81b05471f63b289ecc61fb116c68682d1199c78c/static/img/contributing-resolve-merge-conflicts-view-merge-commit.png -------------------------------------------------------------------------------- /static/img/contributing-token-printed-to-console.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/open-sauced/docs/81b05471f63b289ecc61fb116c68682d1199c78c/static/img/contributing-token-printed-to-console.png -------------------------------------------------------------------------------- /static/img/contributors-insights.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/open-sauced/docs/81b05471f63b289ecc61fb116c68682d1199c78c/static/img/contributors-insights.png -------------------------------------------------------------------------------- /static/img/crossplane-scorecard.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/open-sauced/docs/81b05471f63b289ecc61fb116c68682d1199c78c/static/img/crossplane-scorecard.png -------------------------------------------------------------------------------- /static/img/extension-invite.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/open-sauced/docs/81b05471f63b289ecc61fb116c68682d1199c78c/static/img/extension-invite.png -------------------------------------------------------------------------------- /static/img/extension-links.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/open-sauced/docs/81b05471f63b289ecc61fb116c68682d1199c78c/static/img/extension-links.png -------------------------------------------------------------------------------- /static/img/extension-popup.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/open-sauced/docs/81b05471f63b289ecc61fb116c68682d1199c78c/static/img/extension-popup.png -------------------------------------------------------------------------------- /static/img/extension-view.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/open-sauced/docs/81b05471f63b289ecc61fb116c68682d1199c78c/static/img/extension-view.png -------------------------------------------------------------------------------- /static/img/favicon.ico: -------------------------------------------------------------------------------- 1 | 2 | 3 | 4 | -------------------------------------------------------------------------------- /static/img/files-changed-tab.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/open-sauced/docs/81b05471f63b289ecc61fb116c68682d1199c78c/static/img/files-changed-tab.png -------------------------------------------------------------------------------- /static/img/future-scorecard-workspaces.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/open-sauced/docs/81b05471f63b289ecc61fb116c68682d1199c78c/static/img/future-scorecard-workspaces.png -------------------------------------------------------------------------------- /static/img/future-scorecard.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/open-sauced/docs/81b05471f63b289ecc61fb116c68682d1199c78c/static/img/future-scorecard.png -------------------------------------------------------------------------------- /static/img/get-dev-card.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/open-sauced/docs/81b05471f63b289ecc61fb116c68682d1199c78c/static/img/get-dev-card.png -------------------------------------------------------------------------------- /static/img/highlights.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/open-sauced/docs/81b05471f63b289ecc61fb116c68682d1199c78c/static/img/highlights.png -------------------------------------------------------------------------------- /static/img/kubernetes-scorecard.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/open-sauced/docs/81b05471f63b289ecc61fb116c68682d1199c78c/static/img/kubernetes-scorecard.png -------------------------------------------------------------------------------- /static/img/list-graph.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/open-sauced/docs/81b05471f63b289ecc61fb116c68682d1199c78c/static/img/list-graph.png -------------------------------------------------------------------------------- /static/img/lists-page.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/open-sauced/docs/81b05471f63b289ecc61fb116c68682d1199c78c/static/img/lists-page.png -------------------------------------------------------------------------------- /static/img/logo.svg: -------------------------------------------------------------------------------- 1 | 2 | 3 | 4 | -------------------------------------------------------------------------------- /static/img/logo_darkmode.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/open-sauced/docs/81b05471f63b289ecc61fb116c68682d1199c78c/static/img/logo_darkmode.png -------------------------------------------------------------------------------- /static/img/logo_lightmode.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/open-sauced/docs/81b05471f63b289ecc61fb116c68682d1199c78c/static/img/logo_lightmode.png -------------------------------------------------------------------------------- /static/img/ml-explore-page.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/open-sauced/docs/81b05471f63b289ecc61fb116c68682d1199c78c/static/img/ml-explore-page.png -------------------------------------------------------------------------------- /static/img/openSauced-icon.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/open-sauced/docs/81b05471f63b289ecc61fb116c68682d1199c78c/static/img/openSauced-icon.png -------------------------------------------------------------------------------- /static/img/popular-repos-hot-opensauced.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/open-sauced/docs/81b05471f63b289ecc61fb116c68682d1199c78c/static/img/popular-repos-hot-opensauced.png -------------------------------------------------------------------------------- /static/img/pr-velocity-example.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/open-sauced/docs/81b05471f63b289ecc61fb116c68682d1199c78c/static/img/pr-velocity-example.png -------------------------------------------------------------------------------- /static/img/profile.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/open-sauced/docs/81b05471f63b289ecc61fb116c68682d1199c78c/static/img/profile.png -------------------------------------------------------------------------------- /static/img/repos-insights.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/open-sauced/docs/81b05471f63b289ecc61fb116c68682d1199c78c/static/img/repos-insights.png -------------------------------------------------------------------------------- /static/img/settings.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/open-sauced/docs/81b05471f63b289ecc61fb116c68682d1199c78c/static/img/settings.png -------------------------------------------------------------------------------- /static/img/star-search.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/open-sauced/docs/81b05471f63b289ecc61fb116c68682d1199c78c/static/img/star-search.png -------------------------------------------------------------------------------- /static/img/sync-branch-GH.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/open-sauced/docs/81b05471f63b289ecc61fb116c68682d1199c78c/static/img/sync-branch-GH.png -------------------------------------------------------------------------------- /static/img/upvoted-repos-hot-opensauced.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/open-sauced/docs/81b05471f63b289ecc61fb116c68682d1199c78c/static/img/upvoted-repos-hot-opensauced.png -------------------------------------------------------------------------------- /static/img/what-is-opensauced.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/open-sauced/docs/81b05471f63b289ecc61fb116c68682d1199c78c/static/img/what-is-opensauced.jpg -------------------------------------------------------------------------------- /static/img/what-is-opensauced.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/open-sauced/docs/81b05471f63b289ecc61fb116c68682d1199c78c/static/img/what-is-opensauced.png -------------------------------------------------------------------------------- /static/img/workspace-access.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/open-sauced/docs/81b05471f63b289ecc61fb116c68682d1199c78c/static/img/workspace-access.png -------------------------------------------------------------------------------- /static/img/workspace-sidebar.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/open-sauced/docs/81b05471f63b289ecc61fb116c68682d1199c78c/static/img/workspace-sidebar.png -------------------------------------------------------------------------------- /static/img/workspace-switcher.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/open-sauced/docs/81b05471f63b289ecc61fb116c68682d1199c78c/static/img/workspace-switcher.png -------------------------------------------------------------------------------- /static/img/workspace.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/open-sauced/docs/81b05471f63b289ecc61fb116c68682d1199c78c/static/img/workspace.png -------------------------------------------------------------------------------- /static/manifest.json: -------------------------------------------------------------------------------- 1 | { 2 | "short_name": "OpenSauced Docs", 3 | "name": "OpenSauced Docs", 4 | "start_url": "/?source=pwa", 5 | "background_color": "#ffffff", 6 | "display": "standalone", 7 | "scope": "/", 8 | "theme_color": "#313d3e", 9 | "icons": [ 10 | { 11 | "src": "\/icon-72x72.png", 12 | "sizes": "72x72", 13 | "type": "image\/png", 14 | "density": "1.5" 15 | }, 16 | { 17 | "src": "\/icon-96x96.png", 18 | "sizes": "96x96", 19 | "type": "image\/png", 20 | "density": "2.0" 21 | }, 22 | { 23 | "src": "\/icon-144x144.png", 24 | "sizes": "144x144", 25 | "type": "image\/png", 26 | "density": "3.0" 27 | }, 28 | { 29 | "src": "\/icon-192x192.png", 30 | "sizes": "192x192", 31 | "type": "image\/png", 32 | "density": "4.0" 33 | } 34 | ] 35 | } 36 | -------------------------------------------------------------------------------- /static/robots.txt: -------------------------------------------------------------------------------- 1 | # Allow all crawlers 2 | User-agent: * 3 | Allow: / --------------------------------------------------------------------------------