Slack archive

g0v-github

Month: 2020-01

2020-01-18

ronnywang 15:06:26
@ronnywang has joined the channel
pm5 15:07:49
@pm5 has joined the channel
s72503013 15:08:06
@s72503013 has joined the channel
meisheep 15:08:09
@meisheep has joined the channel
yutin 15:08:24
@yutin has joined the channel
ronnywang 15:08:45
上面是 g0v domain 的機制
yutin 15:09:31
PR/ISSUE 樣板: https://help.github.com/en/github/building-a-strong-community/about-issue-and-pull-request-templates
貢獻者線上簽署工具: https://github.com/cla-assistant/cla-assistant

help.github.com

About issue and pull request templates - GitHub Help

With issue and pull request templates, you can customize and standardize the information you'd like contributors to include when they open issues and pull requests in your repository.

GitHub

cla-assistant/cla-assistant

Contributor License Agreement assistant (CLA assistant) - cla-assistant/cla-assistant

Scott 15:09:55
@mmm90415 has joined the channel
ronnywang 15:12:49
我把 domain 規範先 copy 過來成為 github 規範，我們先用這個來作修改
dean 15:18:33
@chusian4work has joined the channel
robinsonweng 15:22:25
@robinsonweng100 has joined the channel
ael 22:00:39
@aelcenganda has joined the channel

2020-01-19

lanf0n 01:39:43
@lanf0n has joined the channel

2020-01-20

wildjcrt 10:29:13
@wildjcrt has joined the channel
wildjcrt 10:32:38
team 是不是該整理成權限控管來用？
因為我看不太懂 member 的權限到哪裡
ronnywang 10:36:59
基礎松當天實驗結果是，member 可以 commit 所有 g0v 下面未保護的 repository ，可以自由新增 repository ，但是不能刪除 repository ，也不能使用所有的 repository settings 功能
ronnywang 10:37:58
但是當天沒有實驗很完整，也歡迎如果有任何功能權限疑惑都可以提出來，也可以做實驗和記錄
wildjcrt 10:44:53
PR 呢
ronnywang 10:45:28
PR 是連非 member 都可以做
ronnywang 10:45:45
不過 member 好像也可以 confirm PR
wildjcrt 10:46:02
不應該用實驗，是在這邊設定
https://github.com/organizations/g0v/settings/member_privileges

GitHub

GitHub is where people build software. More than 40 million people use GitHub to discover, fork, and contribute to over 100 million projects.

ronnywang 10:47:05
喔喔，那看來可能也要討論看看這邊權限有沒有要改成非預設的？
wildjcrt 10:47:26
是的。
但我要下班後才會有空仔細看 XD
ronnywang 10:48:22
admin 要求開兩步驗證應該不算太嚴苛的要求吧？
不會用 2CA 請他會用再來申請 admin？
wildjcrt 10:48:55
我覺得主要方向有兩種啦
1. 寬鬆的允許加入 member，但只有很 basic 權限
2. 相較嚴格的確認加入 member，但設計給予的權限比較多
wildjcrt 10:49:13
不會用 2CA 請他會用再來申請 admin？
ronnywang 10:49:33
另外基礎松也有討論到要求新加入 member 必須要用 pull request 送自我介紹，這樣會不會有點嚴苛，當時覺得應該還好，就順便加上讓新參者都學會 pull request
wildjcrt 10:49:56
這回歸到，加入 member 要幹嘛
ronnywang 10:50:18
admin 可能就不走自行申請成為 admin 的模式，而是像 domain policy 或是 g0v-talks policy 採現有成員兩人同意申請制吧
➕ 2
ronnywang 10:50:28
成為 member 可以讓自己專案的程式碼可以被放在 github.com/g0v 下
ronnywang 10:51:28
其實這也是另一個可以深入討論的議題
github.com/g0v 下面該放什麼？
選項A: 只放基礎建設，社群相關的東西。各別專案建議自己開 organization
選項B: 有g0v精神的專案都可以放進來
老實說，這我沒啥意見 XD 都行
wildjcrt 10:51:41
g0v 下的 repo，裡面的 repo member 有一定要是 g0v member 嗎？
我自己覺得如果我們把 member 加入機制變得很簡單沒門檻（以目前草案只要到 github.com/g0v/nobody 內 PR 自我介紹就好），那強制 repo member 一定要是 g0v member 應該不過份
先承認你就是沒有人
ronnywang 10:53:10
前者的好處是可以有比較嚴格的限制比較安全，而且也更去中心化。
後者的好處則是新參者想要找g0v相關的程式碼會比較容易（還有一點是現在 g0v organiazation 是地球上前三大的 civic tech github organization，可以維持這個虛榮 XD）
chewei 10:56:29
@chewei has joined the channel
wildjcrt 11:00:40
老實說，這我沒啥意見 XD 都行
caasi 14:04:36
@caasi has joined the channel
ronnywang 21:39:48
@ronnywang has renamed the channel from "github" to "g0v-github"
ronnywang 21:40:31
頻道決定改名叫 g0v-github ，跟 g0v-domain 類似，這樣比較有社群基礎建設討論的統一性 (感謝 @wildjcrt 建議)
✌️ 3 👍 5 🖖 1 1

2020-01-21

sean 15:28:31
@sean has joined the channel

2020-01-22

constmoon 22:34:08
@jiiw.kang has joined the channel