Kuansim Meeting Minutes - 2013/10/05
編輯歷史
| 時間 | 作者 | 版本 |
|---|---|---|
| 2013-12-07 17:18 | r1896 | |
顯示 diff（42 行未修改）
|
||
| 2013-11-03 15:07 – 15:07 | r1887 – r1895 | |
顯示 diff（37 行未修改）
待辦事項(Actions)
- *hychen : add github id of Berkeley to gv .
- *hychen: 術語定義, 像是什麼是爭議, 什麼是事件, 什麼是問題
+ *hychen : add github id of Berkeley to gv . done.
+ *hychen: 術語定義, 像是什麼是爭議, 什麼是事件, 什麼是問題 done.
*Glossary definition , such as "what is the meaning of an issue/event/problem?"
|
||
| 2013-10-21 20:52 – 20:52 | r1885 – r1886 | |
顯示 diff- Kuasnim Meeting Minutes - 2013/1
+ Kuansim Meeting Minutes - 2013/1
/05
（39 行未修改）
|
||
| 2013-10-06 17:38 – 18:53 | r1833 – r1884 | |
顯示 diff- Kuasnim Meeting Minuts - 2013/1
+ Kuasnim Meeting Minutes - 2013/1
/05
（1 行未修改）
*澄清這個專案在這個週期要做什麼, 不做什麼
- *To discuss what this project will be implemented
+ *To discuss what will be implemented in this project.
*討論專案採取什麼方式實作
- *To discuss the way how g0v developers and Berkly student cooperate.
+ *To discuss how g0v developers and Berkeley students will cooperate together
參與者(Attendees)
（11 行未修改）
*Berkeley 團隊主要實做列在 kuansim flow chart (English version) 的 "high priority" 的頁面除了公眾人物時間軸部份。
- *Berkeley team will focus on implementing the "top priority" pages excluding the public figure timeline in kuansim flow chart (English version).
+ *Berkeley team will focus on implementing the "top priority" pages excluding the public figure timeline in the kuansim flow chart (English version).
*Berkeley 團隊會用 Ruby on Rails 實作上面提到的 "top priroty" 頁面的後端, 同時 g0v kuansim 團隊會用 node.js 繼續實作其他功能。換句話說, 不同的後端實作各自負責的功能並且提供 Restful API。
- *Berkeley team will implement the backend of above functionalities in Ruby on rails and g0v kuansim team will implement the rest parts of kuansim in node.js in parallel. *dIn another words, dfferent backend/db takes care about different parts of the functionality and provide consist restful API.
+ *Berkeley team will implement the backend of above functionalities in Ruby on Rails and g0v kuansim team will implement the rest of kuansim in node.js in parallel. *dIn other words, dfferent backend/db takescare aofdifferent parts of the functionality and provide a consistent RESTful API.
*g0v kuansim 團隊跟 Berkely 團隊使用共同的前端程式碼
*g0v kuansim team and Berkeley team will use the same front-end code base.
（13 行未修改）
|
||
| 2013-10-05 13:02 – 13:02 | r1826 – r1832 | |
顯示 diff（38 行未修改）
*hychen : add github id of Berkeley to gv .
- *hychen: 術語定義, 像是什麼是爭議, 什麼是事件.
+ *hychen: 術語定義, 像是什麼是爭議, 什麼是事件, 什麼是問題
*Glossary definition , such as "what is the meaning of an issue/event/problem?"
|
||
| 2013-10-05 11:40 – 11:40 | r1824 – r1825 | |
顯示 diff（37 行未修改）
待辦事項(Actions)
- *hychen : add github id of Berkely to gv .
+ *hychen : add github id of Berkeley to gv .
*hychen: 術語定義, 像是什麼是爭議, 什麼是事件.
*Glossary definition , such as "what is the meaning of an issue/event/problem?"
|
||
| 2013-10-05 09:21 – 09:21 | r1820 – r1823 | |
顯示 diff（39 行未修改）
*hychen : add github id of Berkely to gv .
*hychen: 術語定義, 像是什麼是爭議, 什麼是事件.
- *Glossary difnition , such as "what is the meaning of an issue/event/problem?"
+ *Glossary definition , such as "what is the meaning of an issue/event/problem?"
|
||
| 2013-10-05 08:57 – 09:05 | r1752 – r1819 | |
顯示 diff（28 行未修改）
*g0v kuansim team and Berkeley team will use the same front-end code base.
*Any UI/UX/technical suggestion is welcomed
- *coding convention will follow each languages'/tools' offcial coding style.
+ *coding convention will follow each languages'/tools' offcial convention. e.g. we will follow jade's official coding style when writing jade.
尚待討論的問題(Open Questions)
（9 行未修改）
|
||
| 2013-10-05 08:57 – 08:57 | r1750 – r1751 | |
顯示 diff（6 行未修改）
*To discuss what this project will be implemented
*討論專案採取什麼方式實作
- *To discuss the way how g0v developers and Berkly student coperate
+ *To discuss the way how g0v developers and Berkly student cooperate.
參與者(Attendees)
（31 行未修改）
|
||
| 2013-10-05 08:57 – 08:57 | r1740 – r1749 | |
顯示 diff（28 行未修改）
*g0v kuansim team and Berkeley team will use the same front-end code base.
*Any UI/UX/technical suggestion is welcomed
- *coding convention will follow the language's offcial coding style. i.e.,
+ *coding convention will follow each languages'/tools' offcial coding style.
尚待討論的問題(Open Questions)
（9 行未修改）
|
||
| 2013-10-05 08:57 – 08:57 | r1738 – r1739 | |
顯示 diff（6 行未修改）
*To discuss what this project will be implemented
*討論專案採取什麼方式實作
- *To discuss the way how g0v developers and Berkly student
+ *To discuss the way how g0v developers and Berkly student coperate
參與者(Attendees)
（31 行未修改）
|
||
| 2013-10-05 08:56 – 08:56 | r1688 – r1737 | |
顯示 diff（28 行未修改）
*g0v kuansim team and Berkeley team will use the same front-end code base.
*Any UI/UX/technical suggestion is welcomed
+ *coding convention will follow the language's offcial coding style. i.e.,
尚待討論的問題(Open Questions)
（9 行未修改）
|
||
| 2013-10-05 08:46 – 08:56 | r1408 – r1687 | |
顯示 diff（12 行未修改）
*hychen (g0v kuansim coordinator & backend engineer)
*kcliu (g0v kuansim frontend engineer)
- *brecht (g0v kuansim frontend engineer)
*raejin
*mmmmmhuang
（14 行未修改）
尚待討論的問題(Open Questions)
+
+ *API
+ *實作方式
+
+ 待辦事項(Actions)
+
+ *hychen : add github id of Berkely to gv .
+ *hychen: 術語定義, 像是什麼是爭議, 什麼是事件.
+ *Glossary difnition , such as "what is the meaning of an issue/event/problem?"
|
||
| 2013-10-05 08:46 | r1407 | |
顯示 diff（28 行未修改）
*g0v kuansim 團隊跟 Berkely 團隊使用共同的前端程式碼
*g0v kuansim team and Berkeley team will use the same front-end code base.
- *Any UI/UX/technical suggestions is welcomed
+ *Any UI/UX/technical suggestion is welcomed
尚待討論的問題(Open Questions)
|
||
| 2013-10-05 08:45 – 08:46 | r1398 – r1406 | |
顯示 diff（28 行未修改）
*g0v kuansim 團隊跟 Berkely 團隊使用共同的前端程式碼
*g0v kuansim team and Berkeley team will use the same front-end code base.
- *g0v kuansim team is ok to use grunt to leaverage the less and sass.
*Any UI/UX/technical suggestions is welcomed
（1 行未修改）
|
||
| 2013-10-05 08:45 – 08:45 | r1390 – r1397 | |
顯示 diff（29 行未修改）
*g0v kuansim team and Berkeley team will use the same front-end code base.
*g0v kuansim team is ok to use grunt to leaverage the less and sass.
- *Any UI/UX/coding convetion suggestions is welcomed
+ *Any UI/UX/technical suggestions is welcomed
尚待討論的問題(Open Questions)
|
||
| 2013-10-05 08:42 – 08:45 | r1296 – r1389 | |
顯示 diff（22 行未修改）
達成的共識(Agreement)
- *Berkeley 團隊主要實做列在 kuansim flow chart (English version) 的 "high priority" 的頁面除了公眾人物時間軸部份
+ *Berkeley 團隊主要實做列在 kuansim flow chart (English version) 的 "high priority" 的頁面除了公眾人物時間軸部份。
*Berkeley team will focus on implementing the "top priority" pages excluding the public figure timeline in kuansim flow chart (English version).
- *Berkeley 團隊會用 Ruby on Rails 實作上面 "top priroty 界面, g0v kuansim 團隊
- *Berkeley team will implement the backend of above functionalities in Ruby on rails and g0v kuansim team will implement the rest parts of kuansim in node.js in parallel.
- *g0v kuansim 團隊 Berkeley 團隊*dIn another words, dfferent backend/db takes care about different parts of the functionality and provide consist restful API.
- *
+ *Berkeley 團隊會用 Ruby on Rails 實作上面提到的 "top priroty" 頁面的後端, 同時 g0v kuansim 團隊會用 node.js 繼續實作其他功能。換句話說, 不同的後端實作各自負責的功能並且提供 Restful API。
+ *Berkeley team will implement the backend of above functionalities in Ruby on rails and g0v kuansim team will implement the rest parts of kuansim in node.js in parallel. *dIn another words, dfferent backend/db takes care about different parts of the functionality and provide consist restful API.
+ *g0v kuansim 團隊跟 Berkely 團隊使用共同的前端程式碼
*g0v kuansim team and Berkeley team will use the same front-end code base.
*g0v kuansim team is ok to use grunt to leaverage the less and sass.
（3 行未修改）
|
||
| 2013-10-05 08:42 – 08:42 | r1294 – r1295 | |
顯示 diff（25 行未修改）
*Berkeley team will focus on implementing the "top priority" pages excluding the public figure timeline in kuansim flow chart (English version).
*Berkeley 團隊會用 Ruby on Rails 實作上面 "top priroty 界面, g0v kuansim 團隊
- *Berkeley team will implement the backend of above functionalities in Ruby on rails and g0v kuansim team will implement rest parts of kuansim in node.js in parallel.
+ *Berkeley team will implement the backend of above functionalities in Ruby on rails and g0v kuansim team will implement the rest parts of kuansim in node.js in parallel.
*g0v kuansim 團隊 Berkeley 團隊*dIn another words, dfferent backend/db takes care about different parts of the functionality and provide consist restful API.
*
（5 行未修改）
|
||
| 2013-10-05 08:42 – 08:42 | r1291 – r1293 | |
顯示 diff（24 行未修改）
*Berkeley 團隊主要實做列在 kuansim flow chart (English version) 的 "high priority" 的頁面除了公眾人物時間軸部份
*Berkeley team will focus on implementing the "top priority" pages excluding the public figure timeline in kuansim flow chart (English version).
- *Berkeley 團隊會用 Ruby on Rails 實作上面 "top priroty 界面
+ *Berkeley 團隊會用 Ruby on Rails 實作上面 "top priroty 界面, g0v kuansim 團隊
*Berkeley team will implement the backend of above functionalities in Ruby on rails and g0v kuansim team will implement rest parts of kuansim in node.js in parallel.
*g0v kuansim 團隊 Berkeley 團隊*dIn another words, dfferent backend/db takes care about different parts of the functionality and provide consist restful API.
（6 行未修改）
|
||
| 2013-10-05 08:42 – 08:42 | r1288 – r1290 | |
顯示 diff（25 行未修改）
*Berkeley team will focus on implementing the "top priority" pages excluding the public figure timeline in kuansim flow chart (English version).
*Berkeley 團隊會用 Ruby on Rails 實作上面 "top priroty 界面
- *Berkeley team will implement the backend of above functionality in Ruby on rails and g0v kuansim team will implement rest parts of kuansim in node.js in parallel.
+ *Berkeley team will implement the backend of above functionalities in Ruby on rails and g0v kuansim team will implement rest parts of kuansim in node.js in parallel.
*g0v kuansim 團隊 Berkeley 團隊*dIn another words, dfferent backend/db takes care about different parts of the functionality and provide consist restful API.
*
（5 行未修改）
|
||
| 2013-10-05 08:41 – 08:42 | r1278 – r1287 | |
顯示 diff（24 行未修改）
*Berkeley 團隊主要實做列在 kuansim flow chart (English version) 的 "high priority" 的頁面除了公眾人物時間軸部份
*Berkeley team will focus on implementing the "top priority" pages excluding the public figure timeline in kuansim flow chart (English version).
- *Berkeley 會用 Ruby on Rails 實作上面 "top priroty 界面
+ *Berkeley 團隊會用 Ruby on Rails 實作上面 "top priroty 界面
*Berkeley team will implement the backend of above functionality in Ruby on rails and g0v kuansim team will implement rest parts of kuansim in node.js in parallel.
- **dIn another words, dfferent backend/db takes care about different parts of the functionality and provide consist restful API.
+ *g0v kuansim 團隊 Berkeley 團隊*dIn another words, dfferent backend/db takes care about different parts of the functionality and provide consist restful API.
*
*g0v kuansim team and Berkeley team will use the same front-end code base.
（4 行未修改）
|
||
| 2013-10-05 08:41 – 08:41 | r1276 – r1277 | |
顯示 diff（23 行未修改）
*Berkeley 團隊主要實做列在 kuansim flow chart (English version) 的 "high priority" 的頁面除了公眾人物時間軸部份
- *Berkeley team will focus on implementing the "high priority" pages excluding the public figure timeline in kuansim flow chart (English version).
+ *Berkeley team will focus on implementing the "top priority" pages excluding the public figure timeline in kuansim flow chart (English version).
*Berkeley 會用 Ruby on Rails 實作上面 "top priroty 界面
*Berkeley team will implement the backend of above functionality in Ruby on rails and g0v kuansim team will implement rest parts of kuansim in node.js in parallel.
（7 行未修改）
|
||
| 2013-10-05 08:41 – 08:41 | r1271 – r1275 | |
顯示 diff（24 行未修改）
*Berkeley 團隊主要實做列在 kuansim flow chart (English version) 的 "high priority" 的頁面除了公眾人物時間軸部份
*Berkeley team will focus on implementing the "high priority" pages excluding the public figure timeline in kuansim flow chart (English version).
- *Berkeley 會用 Ruby on Rails 實作上面 "high priroty 界面
- *Berkeley team will implement the backend of above functionality in Ruby on rails and g0v kuansim team will implement rest parts of kuansim in node.js in parallel. *dIn another words, dfferent backend/db takes care about different parts of the functionality and provide consist restful API.
+ *Berkeley 會用 Ruby on Rails 實作上面 "top priroty 界面
+ *Berkeley team will implement the backend of above functionality in Ruby on rails and g0v kuansim team will implement rest parts of kuansim in node.js in parallel.
+ **dIn another words, dfferent backend/db takes care about different parts of the functionality and provide consist restful API.
*
*g0v kuansim team and Berkeley team will use the same front-end code base.
（4 行未修改）
|
||
| 2013-10-05 08:40 – 08:40 | r1267 – r1270 | |
顯示 diff（22 行未修改）
達成的共識(Agreement)
- *Berkeley 團隊主要實做列在 kuansim flow/chart (English version) 的 "high priority" 的頁面除了公眾人物時間軸部份
- *Berkeley team will focus on implementing the "high priority" pages excluding the public figure timeline in kuansim flow/chart (English version).
+ *Berkeley 團隊主要實做列在 kuansim flow chart (English version) 的 "high priority" 的頁面除了公眾人物時間軸部份
+ *Berkeley team will focus on implementing the "high priority" pages excluding the public figure timeline in kuansim flow chart (English version).
*Berkeley 會用 Ruby on Rails 實作上面 "high priroty 界面
*Berkeley team will implement the backend of above functionality in Ruby on rails and g0v kuansim team will implement rest parts of kuansim in node.js in parallel. *dIn another words, dfferent backend/db takes care about different parts of the functionality and provide consist restful API.
（6 行未修改）
|
||
| 2013-10-05 08:37 – 08:40 | r1236 – r1266 | |
顯示 diff（22 行未修改）
達成的共識(Agreement)
- *Berkeley 團隊主要實做列在 kuansim flow/chart (English version) 的 "high pri" 的頁面除了公眾人物時間軸部份
+ *Berkeley 團隊主要實做列在 kuansim flow/chart (English version) 的 "high priority" 的頁面除了公眾人物時間軸部份
*Berkeley team will focus on implementing the "high priority" pages excluding the public figure timeline in kuansim flow/chart (English version).
- *
+ *Berkeley 會用 Ruby on Rails 實作上面 "high priroty 界面
*Berkeley team will implement the backend of above functionality in Ruby on rails and g0v kuansim team will implement rest parts of kuansim in node.js in parallel. *dIn another words, dfferent backend/db takes care about different parts of the functionality and provide consist restful API.
*
（5 行未修改）
|
||
| 2013-10-05 08:37 – 08:37 | r1229 – r1235 | |
顯示 diff（23 行未修改）
*Berkeley 團隊主要實做列在 kuansim flow/chart (English version) 的 "high pri" 的頁面除了公眾人物時間軸部份
- *Berkeley team implement the "high priority" pages excluding the public figure timeline in kuansim flow/chart (English version).
+ *Berkeley team will focus on implementing the "high priority" pages excluding the public figure timeline in kuansim flow/chart (English version).
*
*Berkeley team will implement the backend of above functionality in Ruby on rails and g0v kuansim team will implement rest parts of kuansim in node.js in parallel. *dIn another words, dfferent backend/db takes care about different parts of the functionality and provide consist restful API.
（6 行未修改）
|
||
| 2013-10-05 08:37 | r1228 | |
顯示 diff（22 行未修改）
達成的共識(Agreement)
- *Berkeley 團隊主要實做列在 kuansim flow/chart (English version) 的 "high " 的頁面除了公眾人物時間軸部份
+ *Berkeley 團隊主要實做列在 kuansim flow/chart (English version) 的 "high pri" 的頁面除了公眾人物時間軸部份
*Berkeley team implement the "high priority" pages excluding the public figure timeline in kuansim flow/chart (English version).
*
（7 行未修改）
|
||
| 2013-10-05 08:37 | r1227 | |
顯示 diff（23 行未修改）
*Berkeley 團隊主要實做列在 kuansim flow/chart (English version) 的 "high " 的頁面除了公眾人物時間軸部份
- *Berkeley team m implement the "high priority" pages excluding the public figure timeline in kuansim flow/chart (English version).
+ *Berkeley team implement the "high priority" pages excluding the public figure timeline in kuansim flow/chart (English version).
*
*Berkeley team will implement the backend of above functionality in Ruby on rails and g0v kuansim team will implement rest parts of kuansim in node.js in parallel. *dIn another words, dfferent backend/db takes care about different parts of the functionality and provide consist restful API.
（6 行未修改）
|
||
| 2013-10-05 08:37 | r1226 | |
顯示 diff（22 行未修改）
達成的共識(Agreement)
- *Berkeley 團隊主要實做列在 kuansim flow/chart (English version) 的 "h" 的頁面除了公眾人物時間軸部份
+ *Berkeley 團隊主要實做列在 kuansim flow/chart (English version) 的 "high " 的頁面除了公眾人物時間軸部份
*Berkeley team m implement the "high priority" pages excluding the public figure timeline in kuansim flow/chart (English version).
*
（7 行未修改）
|
||
| 2013-10-05 08:37 | r1225 | |
顯示 diff（23 行未修改）
*Berkeley 團隊主要實做列在 kuansim flow/chart (English version) 的 "h" 的頁面除了公眾人物時間軸部份
- *Berkeley team majo implement the "high priority" pages excluding the public figure timeline in kuansim flow/chart (English version).
+ *Berkeley team m implement the "high priority" pages excluding the public figure timeline in kuansim flow/chart (English version).
*
*Berkeley team will implement the backend of above functionality in Ruby on rails and g0v kuansim team will implement rest parts of kuansim in node.js in parallel. *dIn another words, dfferent backend/db takes care about different parts of the functionality and provide consist restful API.
（6 行未修改）
|
||
| 2013-10-05 08:37 | r1224 | |
顯示 diff（22 行未修改）
達成的共識(Agreement)
- *Berkeley 團隊主要實做列在 kuansim flow/chart (English version) 的 "" 的頁面除了公眾人物時間軸部份
+ *Berkeley 團隊主要實做列在 kuansim flow/chart (English version) 的 "h" 的頁面除了公眾人物時間軸部份
*Berkeley team majo implement the "high priority" pages excluding the public figure timeline in kuansim flow/chart (English version).
*
（7 行未修改）
|
||
| 2013-10-05 08:37 | r1223 | |
顯示 diff（23 行未修改）
*Berkeley 團隊主要實做列在 kuansim flow/chart (English version) 的 "" 的頁面除了公眾人物時間軸部份
- *Berkeley team major implement the "high priority" pages excluding the public figure timeline in kuansim flow/chart (English version).
+ *Berkeley team majo implement the "high priority" pages excluding the public figure timeline in kuansim flow/chart (English version).
*
*Berkeley team will implement the backend of above functionality in Ruby on rails and g0v kuansim team will implement rest parts of kuansim in node.js in parallel. *dIn another words, dfferent backend/db takes care about different parts of the functionality and provide consist restful API.
（6 行未修改）
|
||
| 2013-10-05 08:37 – 08:37 | r1201 – r1222 | |
顯示 diff（22 行未修改）
達成的共識(Agreement)
- *Berkeley 團隊主要實做 公眾人物ˇˇㄨㄛ
+ *Berkeley 團隊主要實做列在 kuansim flow/chart (English version) 的 "" 的頁面除了公眾人物時間軸部份
*Berkeley team major implement the "high priority" pages excluding the public figure timeline in kuansim flow/chart (English version).
*
（7 行未修改）
|
||
| 2013-10-05 08:36 – 08:36 | r1192 – r1200 | |
顯示 diff（29 行未修改）
*g0v kuansim team and Berkeley team will use the same front-end code base.
*g0v kuansim team is ok to use grunt to leaverage the less and sass.
- *Any UI/UX/coding convetion suggestions is welcomed hihihihihihihihihihihihihi
+ *Any UI/UX/coding convetion suggestions is welcomed
尚待討論的問題(Open Questions)
|
||
| 2013-10-05 08:36 | r1191 | |
顯示 diff（22 行未修改）
達成的共識(Agreement)
- *Berkeley 團隊主要實做 公眾人物ˇㄨㄛ
+ *Berkeley 團隊主要實做 公眾人物ˇˇㄨㄛ
*Berkeley team major implement the "high priority" pages excluding the public figure timeline in kuansim flow/chart (English version).
*
（7 行未修改）
|
||
| 2013-10-05 08:36 | r1190 | |
顯示 diff（29 行未修改）
*g0v kuansim team and Berkeley team will use the same front-end code base.
*g0v kuansim team is ok to use grunt to leaverage the less and sass.
- *Any UI/UX/coding convetion suggestions is welcomed hihihihihihihihihihih
+ *Any UI/UX/coding convetion suggestions is welcomed hihihihihihihihihihihihihi
尚待討論的問題(Open Questions)
|
||
| 2013-10-05 08:36 | r1189 | |
顯示 diff（22 行未修改）
達成的共識(Agreement)
- *Berkeley 團隊主要實做 公眾人物ㄨㄛ
+ *Berkeley 團隊主要實做 公眾人物ˇㄨㄛ
*Berkeley team major implement the "high priority" pages excluding the public figure timeline in kuansim flow/chart (English version).
*
（7 行未修改）
|
||
| 2013-10-05 08:36 | r1188 | |
顯示 diff（29 行未修改）
*g0v kuansim team and Berkeley team will use the same front-end code base.
*g0v kuansim team is ok to use grunt to leaverage the less and sass.
- *Any UI/UX/coding convetion suggestions is welcomed hihihihihihihih
+ *Any UI/UX/coding convetion suggestions is welcomed hihihihihihihihihihih
尚待討論的問題(Open Questions)
|
||
| 2013-10-05 08:36 | r1187 | |
顯示 diff（22 行未修改）
達成的共識(Agreement)
- *Berkeley 團隊主要實做 公眾人物
+ *Berkeley 團隊主要實做 公眾人物ㄨㄛ
*Berkeley team major implement the "high priority" pages excluding the public figure timeline in kuansim flow/chart (English version).
*
（7 行未修改）
|
||
| 2013-10-05 08:36 | r1186 | |
顯示 diff（29 行未修改）
*g0v kuansim team and Berkeley team will use the same front-end code base.
*g0v kuansim team is ok to use grunt to leaverage the less and sass.
- *Any UI/UX/coding convetion suggestions is welcomed hihihihih
+ *Any UI/UX/coding convetion suggestions is welcomed hihihihihihihih
尚待討論的問題(Open Questions)
|
||
| 2013-10-05 08:36 | r1185 | |
顯示 diff（22 行未修改）
達成的共識(Agreement)
- *Berkeley 團隊主要實做 公眾人物我五部
+ *Berkeley 團隊主要實做 公眾人物
*Berkeley team major implement the "high priority" pages excluding the public figure timeline in kuansim flow/chart (English version).
*
（7 行未修改）
|
||
| 2013-10-05 08:36 | r1184 | |
顯示 diff（29 行未修改）
*g0v kuansim team and Berkeley team will use the same front-end code base.
*g0v kuansim team is ok to use grunt to leaverage the less and sass.
- *Any UI/UX/coding convetion suggestions is welcomed hihi
+ *Any UI/UX/coding convetion suggestions is welcomed hihihihih
尚待討論的問題(Open Questions)
|
||
| 2013-10-05 08:36 | r1183 | |
顯示 diff（22 行未修改）
達成的共識(Agreement)
- *Berkeley 團隊主要實做 公眾人物我五部誤
+ *Berkeley 團隊主要實做 公眾人物我五部
*Berkeley team major implement the "high priority" pages excluding the public figure timeline in kuansim flow/chart (English version).
*
（7 行未修改）
|
||
| 2013-10-05 08:36 – 08:36 | r1181 – r1182 | |
顯示 diff（29 行未修改）
*g0v kuansim team and Berkeley team will use the same front-end code base.
*g0v kuansim team is ok to use grunt to leaverage the less and sass.
- *Any UI/UX/coding convetion suggestions is welcomed
+ *Any UI/UX/coding convetion suggestions is welcomed hihi
尚待討論的問題(Open Questions)
|
||
| 2013-10-05 08:36 – 08:36 | r1175 – r1180 | |
顯示 diff（22 行未修改）
達成的共識(Agreement)
- *Berkeley 團隊主要實做 ㄍㄨㄥ
+ *Berkeley 團隊主要實做 公眾人物我五部誤
*Berkeley team major implement the "high priority" pages excluding the public figure timeline in kuansim flow/chart (English version).
*
（7 行未修改）
|
||
| 2013-10-05 08:36 | r1174 | |
顯示 diff（29 行未修改）
*g0v kuansim team and Berkeley team will use the same front-end code base.
*g0v kuansim team is ok to use grunt to leaverage the less and sass.
- *Any UI/UX/coding conveti suggestions is welcomed
+ *Any UI/UX/coding convetion suggestions is welcomed
尚待討論的問題(Open Questions)
|
||
| 2013-10-05 08:36 | r1173 | |
顯示 diff（22 行未修改）
達成的共識(Agreement)
- *Berkeley 團隊主要實做 ㄍㄨㄥ
+ *Berkeley 團隊主要實做 ㄍㄨㄥ
*Berkeley team major implement the "high priority" pages excluding the public figure timeline in kuansim flow/chart (English version).
*
（7 行未修改）
|
||
| 2013-10-05 08:36 | r1172 | |
顯示 diff（29 行未修改）
*g0v kuansim team and Berkeley team will use the same front-end code base.
*g0v kuansim team is ok to use grunt to leaverage the less and sass.
- *Any UI/UX/coding conv suggestions is welcomed
+ *Any UI/UX/coding conveti suggestions is welcomed
尚待討論的問題(Open Questions)
|
||
| 2013-10-05 08:36 | r1171 | |
顯示 diff（22 行未修改）
達成的共識(Agreement)
- *Berkeley 團隊主要實做
+ *Berkeley 團隊主要實做 ㄍㄨㄥ
*Berkeley team major implement the "high priority" pages excluding the public figure timeline in kuansim flow/chart (English version).
*
（7 行未修改）
|
||
| 2013-10-05 08:36 – 08:36 | r1169 – r1170 | |
顯示 diff（29 行未修改）
*g0v kuansim team and Berkeley team will use the same front-end code base.
*g0v kuansim team is ok to use grunt to leaverage the less and sass.
- *Any UI/UX/codi suggestions is welcomed
+ *Any UI/UX/coding conv suggestions is welcomed
尚待討論的問題(Open Questions)
|
||
| 2013-10-05 08:36 | r1168 | |
顯示 diff（22 行未修改）
達成的共識(Agreement)
- *Berkeley 團隊主要實做 ej/
+ *Berkeley 團隊主要實做
*Berkeley team major implement the "high priority" pages excluding the public figure timeline in kuansim flow/chart (English version).
*
（7 行未修改）
|
||
| 2013-10-05 08:36 | r1167 | |
顯示 diff（29 行未修改）
*g0v kuansim team and Berkeley team will use the same front-end code base.
*g0v kuansim team is ok to use grunt to leaverage the less and sass.
- *Any UI/UX/c suggestions is welcomed
+ *Any UI/UX/codi suggestions is welcomed
尚待討論的問題(Open Questions)
|
||
| 2013-10-05 08:36 | r1166 | |
顯示 diff（22 行未修改）
達成的共識(Agreement)
- *Berkeley 團隊主要實做 ej
+ *Berkeley 團隊主要實做 ej/
*Berkeley team major implement the "high priority" pages excluding the public figure timeline in kuansim flow/chart (English version).
*
（7 行未修改）
|
||
| 2013-10-05 08:36 | r1165 | |
顯示 diff（29 行未修改）
*g0v kuansim team and Berkeley team will use the same front-end code base.
*g0v kuansim team is ok to use grunt to leaverage the less and sass.
- *Any UI/UX/ suggestions is welcomed
+ *Any UI/UX/c suggestions is welcomed
尚待討論的問題(Open Questions)
|
||
| 2013-10-05 08:36 – 08:36 | r1163 – r1164 | |
顯示 diff（22 行未修改）
達成的共識(Agreement)
- *Berkeley 團隊主要實做
+ *Berkeley 團隊主要實做 ej
*Berkeley team major implement the "high priority" pages excluding the public figure timeline in kuansim flow/chart (English version).
*
（7 行未修改）
|
||
| 2013-10-05 08:36 – 08:36 | r1160 – r1162 | |
顯示 diff（29 行未修改）
*g0v kuansim team and Berkeley team will use the same front-end code base.
*g0v kuansim team is ok to use grunt to leaverage the less and sass.
- *Any UI/UX suggestions ar welcomed
+ *Any UI/UX/ suggestions is welcomed
尚待討論的問題(Open Questions)
|
||
| 2013-10-05 08:36 | r1159 | |
顯示 diff（22 行未修改）
達成的共識(Agreement)
- *Berkeley 團隊主要實做
+ *Berkeley 團隊主要實做
*Berkeley team major implement the "high priority" pages excluding the public figure timeline in kuansim flow/chart (English version).
*
（7 行未修改）
|
||
| 2013-10-05 08:36 | r1158 | |
顯示 diff（29 行未修改）
*g0v kuansim team and Berkeley team will use the same front-end code base.
*g0v kuansim team is ok to use grunt to leaverage the less and sass.
- *Any UI/UX suggestions are welcomed
+ *Any UI/UX suggestions ar welcomed
尚待討論的問題(Open Questions)
|
||
| 2013-10-05 08:36 – 08:36 | r1152 – r1157 | |
顯示 diff（22 行未修改）
達成的共識(Agreement)
- *Berkeley 團隊主要實做 "高優ㄧㄢㄒ
+ *Berkeley 團隊主要實做
*Berkeley team major implement the "high priority" pages excluding the public figure timeline in kuansim flow/chart (English version).
*
（7 行未修改）
|
||
| 2013-10-05 08:36 | r1151 | |
顯示 diff（29 行未修改）
*g0v kuansim team and Berkeley team will use the same front-end code base.
*g0v kuansim team is ok to use grunt to leaverage the less and sass.
- *Any UI/UX suggestions welcomed
+ *Any UI/UX suggestions are welcomed
尚待討論的問題(Open Questions)
|
||
| 2013-10-05 08:36 | r1150 | |
顯示 diff（22 行未修改）
達成的共識(Agreement)
- *Berkeley 團隊主要實做 "高優ㄒ
+ *Berkeley 團隊主要實做 "高優ㄧㄢㄒ
*Berkeley team major implement the "high priority" pages excluding the public figure timeline in kuansim flow/chart (English version).
*
（7 行未修改）
|
||
| 2013-10-05 08:36 | r1149 | |
顯示 diff（29 行未修改）
*g0v kuansim team and Berkeley team will use the same front-end code base.
*g0v kuansim team is ok to use grunt to leaverage the less and sass.
- *Any UI/UX suggestions i welcomed
+ *Any UI/UX suggestions welcomed
尚待討論的問題(Open Questions)
|
||
| 2013-10-05 08:36 | r1148 | |
顯示 diff（22 行未修改）
達成的共識(Agreement)
- *Berkeley 團隊主要實做 "
+ *Berkeley 團隊主要實做 "高優ㄒ
*Berkeley team major implement the "high priority" pages excluding the public figure timeline in kuansim flow/chart (English version).
*
（7 行未修改）
|
||
| 2013-10-05 08:36 | r1147 | |
顯示 diff（29 行未修改）
*g0v kuansim team and Berkeley team will use the same front-end code base.
*g0v kuansim team is ok to use grunt to leaverage the less and sass.
- *Any UI/UX suggestions is welcomed
+ *Any UI/UX suggestions i welcomed
尚待討論的問題(Open Questions)
|
||
| 2013-10-05 08:36 | r1146 | |
顯示 diff（22 行未修改）
達成的共識(Agreement)
- *Berkeley 團隊主要實做 "ㄍ
+ *Berkeley 團隊主要實做 "
*Berkeley team major implement the "high priority" pages excluding the public figure timeline in kuansim flow/chart (English version).
*
（7 行未修改）
|
||
| 2013-10-05 08:36 | r1145 | |
顯示 diff（29 行未修改）
*g0v kuansim team and Berkeley team will use the same front-end code base.
*g0v kuansim team is ok to use grunt to leaverage the less and sass.
- *Any UI/UX suggestion is welcomed
+ *Any UI/UX suggestions is welcomed
尚待討論的問題(Open Questions)
|
||
| 2013-10-05 08:36 | r1144 | |
顯示 diff（22 行未修改）
達成的共識(Agreement)
- *Berkeley 團隊主要實做 " ㄍ
+ *Berkeley 團隊主要實做 "ㄍ
*Berkeley team major implement the "high priority" pages excluding the public figure timeline in kuansim flow/chart (English version).
*
（7 行未修改）
|
||
| 2013-10-05 08:36 | r1143 | |
顯示 diff（29 行未修改）
*g0v kuansim team and Berkeley team will use the same front-end code base.
*g0v kuansim team is ok to use grunt to leaverage the less and sass.
- *Any UI/UX suggesto is welcomed
+ *Any UI/UX suggestion is welcomed
尚待討論的問題(Open Questions)
|
||
| 2013-10-05 08:36 | r1142 | |
顯示 diff（22 行未修改）
達成的共識(Agreement)
- *Berkeley 團隊主要實做 "ㄍ
+ *Berkeley 團隊主要實做 " ㄍ
*Berkeley team major implement the "high priority" pages excluding the public figure timeline in kuansim flow/chart (English version).
*
（7 行未修改）
|
||
| 2013-10-05 08:36 | r1141 | |
顯示 diff（29 行未修改）
*g0v kuansim team and Berkeley team will use the same front-end code base.
*g0v kuansim team is ok to use grunt to leaverage the less and sass.
- *Any UI/UX suggest is welcomed
+ *Any UI/UX suggesto is welcomed
尚待討論的問題(Open Questions)
|
||
| 2013-10-05 08:36 | r1140 | |
顯示 diff（22 行未修改）
達成的共識(Agreement)
- *Berkeley 團隊主要實做 "
+ *Berkeley 團隊主要實做 "ㄍ
*Berkeley team major implement the "high priority" pages excluding the public figure timeline in kuansim flow/chart (English version).
*
（7 行未修改）
|
||
| 2013-10-05 08:36 | r1139 | |
顯示 diff（29 行未修改）
*g0v kuansim team and Berkeley team will use the same front-end code base.
*g0v kuansim team is ok to use grunt to leaverage the less and sass.
- *Any UI/UX sug is welcomed
+ *Any UI/UX suggest is welcomed
尚待討論的問題(Open Questions)
|
||
| 2013-10-05 08:36 | r1138 | |
顯示 diff（22 行未修改）
達成的共識(Agreement)
- *Berkeley 團隊主要實做
+ *Berkeley 團隊主要實做 "
*Berkeley team major implement the "high priority" pages excluding the public figure timeline in kuansim flow/chart (English version).
*
（7 行未修改）
|
||
| 2013-10-05 08:36 | r1137 | |
顯示 diff（29 行未修改）
*g0v kuansim team and Berkeley team will use the same front-end code base.
*g0v kuansim team is ok to use grunt to leaverage the less and sass.
- *Any UI/UX s is welcomed
+ *Any UI/UX sug is welcomed
尚待討論的問題(Open Questions)
|
||
| 2013-10-05 08:36 | r1136 | |
顯示 diff（22 行未修改）
達成的共識(Agreement)
- *Berkeley 團隊主要實做
+ *Berkeley 團隊主要實做
*Berkeley team major implement the "high priority" pages excluding the public figure timeline in kuansim flow/chart (English version).
*
（7 行未修改）
|
||
| 2013-10-05 08:36 – 08:36 | r1134 – r1135 | |
顯示 diff（29 行未修改）
*g0v kuansim team and Berkeley team will use the same front-end code base.
*g0v kuansim team is ok to use grunt to leaverage the less and sass.
- *Any UI/UX ide is welcomed
+ *Any UI/UX s is welcomed
尚待討論的問題(Open Questions)
|
||
| 2013-10-05 08:36 | r1133 | |
顯示 diff（22 行未修改）
達成的共識(Agreement)
- *Berkeley 團隊主要實
+ *Berkeley 團隊主要實做
*Berkeley team major implement the "high priority" pages excluding the public figure timeline in kuansim flow/chart (English version).
*
（7 行未修改）
|
||
| 2013-10-05 08:36 | r1132 | |
顯示 diff（29 行未修改）
*g0v kuansim team and Berkeley team will use the same front-end code base.
*g0v kuansim team is ok to use grunt to leaverage the less and sass.
- *Any UI/UX idea is welcomed
+ *Any UI/UX ide is welcomed
尚待討論的問題(Open Questions)
|
||
| 2013-10-05 08:36 – 08:36 | r1126 – r1131 | |
顯示 diff（22 行未修改）
達成的共識(Agreement)
- *Berkel
+ *Berkeley 團隊主要實
*Berkeley team major implement the "high priority" pages excluding the public figure timeline in kuansim flow/chart (English version).
*
（7 行未修改）
|
||
| 2013-10-05 08:36 | r1125 | |
顯示 diff（29 行未修改）
*g0v kuansim team and Berkeley team will use the same front-end code base.
*g0v kuansim team is ok to use grunt to leaverage the less and sass.
- *Any UI/UX idea is welcome
+ *Any UI/UX idea is welcomed
尚待討論的問題(Open Questions)
|
||
| 2013-10-05 08:36 | r1124 | |
顯示 diff（22 行未修改）
達成的共識(Agreement)
- *Berkl
+ *Berkel
*Berkeley team major implement the "high priority" pages excluding the public figure timeline in kuansim flow/chart (English version).
*
（7 行未修改）
|
||
| 2013-10-05 08:36 | r1123 | |
顯示 diff（29 行未修改）
*g0v kuansim team and Berkeley team will use the same front-end code base.
*g0v kuansim team is ok to use grunt to leaverage the less and sass.
- *Any UI/UX idea is wel
+ *Any UI/UX idea is welcome
尚待討論的問題(Open Questions)
|
||
| 2013-10-05 08:36 | r1122 | |
顯示 diff（22 行未修改）
達成的共識(Agreement)
- *Berk
+ *Berkl
*Berkeley team major implement the "high priority" pages excluding the public figure timeline in kuansim flow/chart (English version).
*
（7 行未修改）
|
||
| 2013-10-05 08:36 | r1121 | |
顯示 diff（29 行未修改）
*g0v kuansim team and Berkeley team will use the same front-end code base.
*g0v kuansim team is ok to use grunt to leaverage the less and sass.
- *Any UI/UX idea is well
+ *Any UI/UX idea is wel
尚待討論的問題(Open Questions)
|
||
| 2013-10-05 08:36 | r1120 | |
顯示 diff（22 行未修改）
達成的共識(Agreement)
- *Berkl
+ *Berk
*Berkeley team major implement the "high priority" pages excluding the public figure timeline in kuansim flow/chart (English version).
*
（7 行未修改）
|
||
| 2013-10-05 08:36 | r1119 | |
顯示 diff（29 行未修改）
*g0v kuansim team and Berkeley team will use the same front-end code base.
*g0v kuansim team is ok to use grunt to leaverage the less and sass.
- *Any UI/UX idea is
+ *Any UI/UX idea is well
尚待討論的問題(Open Questions)
|
||
| 2013-10-05 08:36 | r1118 | |
顯示 diff（22 行未修改）
達成的共識(Agreement)
- *Berkle
+ *Berkl
*Berkeley team major implement the "high priority" pages excluding the public figure timeline in kuansim flow/chart (English version).
*
（7 行未修改）
|
||
| 2013-10-05 08:35 – 08:35 | r1116 – r1117 | |
顯示 diff（29 行未修改）
*g0v kuansim team and Berkeley team will use the same front-end code base.
*g0v kuansim team is ok to use grunt to leaverage the less and sass.
- *Any UI/UX idea are
+ *Any UI/UX idea is
尚待討論的問題(Open Questions)
|
||
| 2013-10-05 08:35 | r1115 | |
顯示 diff（22 行未修改）
達成的共識(Agreement)
- *Ber
+ *Berkle
*Berkeley team major implement the "high priority" pages excluding the public figure timeline in kuansim flow/chart (English version).
*
（7 行未修改）
|
||
| 2013-10-05 08:35 | r1114 | |
顯示 diff（29 行未修改）
*g0v kuansim team and Berkeley team will use the same front-end code base.
*g0v kuansim team is ok to use grunt to leaverage the less and sass.
- *Any UI/UX idea are w
+ *Any UI/UX idea are
尚待討論的問題(Open Questions)
|
||
| 2013-10-05 08:35 | r1113 | |
顯示 diff（22 行未修改）
達成的共識(Agreement)
- *B
+ *Ber
*Berkeley team major implement the "high priority" pages excluding the public figure timeline in kuansim flow/chart (English version).
*
（7 行未修改）
|
||
| 2013-10-05 08:35 | r1112 | |
顯示 diff（29 行未修改）
*g0v kuansim team and Berkeley team will use the same front-end code base.
*g0v kuansim team is ok to use grunt to leaverage the less and sass.
- *Any UI/UX idea are
+ *Any UI/UX idea are w
尚待討論的問題(Open Questions)
|
||
| 2013-10-05 08:35 | r1111 | |
顯示 diff（22 行未修改）
達成的共識(Agreement)
- *
+ *B
*Berkeley team major implement the "high priority" pages excluding the public figure timeline in kuansim flow/chart (English version).
*
（7 行未修改）
|
||
| 2013-10-05 08:35 – 08:35 | r1105 – r1110 | |
顯示 diff（29 行未修改）
*g0v kuansim team and Berkeley team will use the same front-end code base.
*g0v kuansim team is ok to use grunt to leaverage the less and sass.
- *Any UI/UX i
+ *Any UI/UX idea are
尚待討論的問題(Open Questions)
|
||
| 2013-10-05 08:35 | r1104 | |
顯示 diff（34 行未修改）
|
||
| 2013-10-05 08:35 – 08:35 | r1096 – r1103 | |
顯示 diff（29 行未修改）
*g0v kuansim team and Berkeley team will use the same front-end code base.
*g0v kuansim team is ok to use grunt to leaverage the less and sass.
- *Any que
+ *Any UI/UX i
尚待討論的問題(Open Questions)
|
||
| 2013-10-05 08:35 | r1095 | |
顯示 diff（34 行未修改）
|
||
| 2013-10-05 08:35 – 08:35 | r1089 – r1094 | |
顯示 diff（29 行未修改）
*g0v kuansim team and Berkeley team will use the same front-end code base.
*g0v kuansim team is ok to use grunt to leaverage the less and sass.
- *any
+ *Any que
尚待討論的問題(Open Questions)
|
||
| 2013-10-05 08:35 | r1088 | |
顯示 diff（26 行未修改）
*
*Berkeley team will implement the backend of above functionality in Ruby on rails and g0v kuansim team will implement rest parts of kuansim in node.js in parallel. *dIn another words, dfferent backend/db takes care about different parts of the functionality and provide consist restful API.
+ *
*g0v kuansim team and Berkeley team will use the same front-end code base.
*g0v kuansim team is ok to use grunt to leaverage the less and sass.
（3 行未修改）
|
||
| 2013-10-05 08:35 – 08:35 | r1084 – r1087 | |
顯示 diff（28 行未修改）
*g0v kuansim team and Berkeley team will use the same front-end code base.
*g0v kuansim team is ok to use grunt to leaverage the less and sass.
+ *any
尚待討論的問題(Open Questions)
|
||
| 2013-10-05 07:42 – 08:35 | r1 – r1083 | |
顯示 diff- Untitled
+ Kuasnim Meeting Minuts - 2013/1
+ /05
- This pad text is synchronized as you type, so that everyone viewing this page sees the same text. This allows you to collaborate seamlessly on documents!
+ 會議目的(Goal of this meeting)
+
+ *澄清這個專案在這個週期要做什麼, 不做什麼
+ *To discuss what this project will be implemented
+ *討論專案採取什麼方式實作
+ *To discuss the way how g0v developers and Berkly student
+
+ 參與者(Attendees)
+
+ *hychen (g0v kuansim coordinator & backend engineer)
+ *kcliu (g0v kuansim frontend engineer)
+ *brecht (g0v kuansim frontend engineer)
+ *raejin
+ *mmmmmhuang
+ *jason
+ *dseeto
+ *jerchung
+ *ayc92
+
+ 達成的共識(Agreement)
+
+ *
+ *Berkeley team major implement the "high priority" pages excluding the public figure timeline in kuansim flow/chart (English version).
+ *
+ *Berkeley team will implement the backend of above functionality in Ruby on rails and g0v kuansim team will implement rest parts of kuansim in node.js in parallel. *dIn another words, dfferent backend/db takes care about different parts of the functionality and provide consist restful API.
+ *g0v kuansim team and Berkeley team will use the same front-end code base.
+ *g0v kuansim team is ok to use grunt to leaverage the less and sass.
+
+ 尚待討論的問題(Open Questions)
|
||
| 2013-10-05 07:42 | r0 | |
顯示 diff+ Untitled
+ This pad text is synchronized as you type, so that everyone viewing this page sees the same text. This allows you to collaborate seamlessly on documents!
|
||