Hacktoberfest 2026:維護者為十月標記出來的 issue,仍然開放、適合新手。 瀏覽 Hacktoberfest issue

Pattern Idea: Scripts To Rule Them All

未關閉
#180 2 則留言 0 個 reaction 已指派 0 人 在 GitHub 檢視

還沒有人認領這個 Issue。

評估

難度
5/5
預估耗時
一週以上
新手友好度
25/100
Issue 類型
文件
描述清晰度
需要釐清
活躍度
停滯
領域
documentation

研究方向

先從連結的 GitHub 文章和 github/scripts-to-rule-them-all 儲存庫開始,了解所提議的模式。訪談一位熟悉此方法的人,然後記錄它如何支援多語言專案的啟動;完成的標準是形成一個基於這些輸入的完整、可供審查的模式。

由索引模型根據 Issue 內容生成。

描述

:book: Type - Content Work :bulb: Early Idea

Pattern idea: Enable contributions in polyglot environments with "Scripts To Rule Them All"

Many companies have a polyglot environment, using multiple different programming languages for the software that they build. The different programming ecosystems come with various ways of bootstrapping the project locally. That means that getting from git clone to an up-and-running project in a development environment works very differently, depending on the programming ecosystem.

Hypothesis

Making it easy to bootstrap a project will encourage contributions from a wider range of contributors, even if they don't know the specific programming language that well.

Examples in the wild

The GitHub team has written about this idea here:
https://github.blog/2015-06-30-scripts-to-rule-them-all/
https://github.com/github/scripts-to-rule-them-all

How to write the pattern

One approach for writing this pattern could be to find somebody that works at GitHub and is familiar with the Scripts To Rule Them All approach. Interview them and write a pattern about this approach together with them.

Other references

Also see this discussion in the InnerSource Commons Slack about the "impact of choice of programming language for the success of an InnerSource project":
https://innersourcecommons.slack.com/archives/C04PXKRN4/p1589456355371100

(link doesn't work anymore because we cannot go that far back in the Slack history)

主要語言
HTML
星號
853
分支
206
平均合併
1 天 23 小時
30 天內合併 PR
2

貢獻指南

開啟貢獻指南

從這裡開始

  1. 先讀完整個 Issue,再讀專案的貢獻指南。
  2. 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
  3. Fork 儲存庫,在一個分支上完成修改。
  4. 送出 Pull Request,並在描述裡引用這個 Issue 編號。

InnerSourceCommons/InnerSourcePatterns 的其他 Issue

查看 InnerSourceCommons/InnerSourcePatterns 的全部 Issue

相似的 Issue

更多 Documentation Issue

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。