the-turing-way/the-turing-way

[Discussion] What are our norms as a community around development on branches vs forks?

Open

#3,871 建立於 2024年10月28日

在 GitHub 查看
 (13 留言) (1 反應) (2 負責人)TeX (2,144 star) (747 fork)batch import
book-dash-nov24community-handbookdocumentationhelp wantedproject governance

描述

Summary

This question came up at the Book Dash Intro to GitHub session on 28 October 2024: should we be asking people to make their own forks of the project and make edits there OR develop on branches within the turing-way/turing-way repo.

Both have pros and cons, including reflecting other open source norms (forks) to managing build previews with our current infrastructure (branches?)

I'd like to have a discussion on what the community (and in particular maintainers) views are on this and whether we want to establish community practices around the decision.

What needs to be done?

  • Discuss what maintainers would like the community norms to be
  • Make an initial agreement on community norms
  • Update documentation and materials to reflect the decision
  • Teach new members the preferred approach going forward

Who can help?

  • Maintainers and community members, please weigh in with your thoughts!

Updates

Lorem ipsum dolor sit amet, consectetur adipiscing.

貢獻者指南

技術棧
無
領域
developer experiencedocumentation
議題類型
research
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
2
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
1-2 days
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
active
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
clear
前置要求
無
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
80
研究方向
This is a discussion issue requiring input from maintainers and community members. Read through the 13 existing comments to gauge opinions. The goal is to reach an agreement on whether to recommend forks or branches, and then update the contributing documentation accordingly. No code changes are needed.
[Discussion] What are our norms as a community around development on branches vs forks? · the-turing-way/the-turing-way#3871 | Good First Issue