We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
目前的話,readme.md 皆是以歷史背景出發點再說的。 開發者對於如何參與這個專案是一頭霧水的。
目前我個人看法是應該直接把 milestone 擺在顯眼的地方,並且每個 isssue 都應該要確實的 assign 給某個要接的人。 避免出現明明這個 issue 有人再做卻要看討論才知道。
然後應該要把時程表放在顯眼的地方,哪邊做了哪邊沒做,方便開發者知道目前進度。
無,討論到大家滿意為止
README.md
The text was updated successfully, but these errors were encountered:
時程表的部分應該會放在 FOR_DEVELOPER.md 上面,因為開發者和實際上執行使用的人是兩種使用者
Sorry, something went wrong.
Merge pull request #172 from y2468101216/feature/#151-readme_refactor
db01e3a
增加給貢獻者相關訊息
Merge pull request #200 from y2468101216/feature/#151-readme_refactor
9013518
根據 whitefloor 調整了既有的說明文檔
Successfully merging a pull request may close this issue.
實作細節 / Details of Implement
目前的話,readme.md 皆是以歷史背景出發點再說的。
開發者對於如何參與這個專案是一頭霧水的。
目前我個人看法是應該直接把 milestone 擺在顯眼的地方,並且每個 isssue 都應該要確實的 assign 給某個要接的人。
避免出現明明這個 issue 有人再做卻要看討論才知道。
然後應該要把時程表放在顯眼的地方,哪邊做了哪邊沒做,方便開發者知道目前進度。
期程 / Schedule
無,討論到大家滿意為止
相關文件 / Documents
README.md
The text was updated successfully, but these errors were encountered: