disfactory

Month: 2020-09

2020-09-01

LisbethW1130 19:51:15
這週大忙(公司伺服器有點狀況),應該只能星期三去開會的時候改完了Q
X Lin 22:23:06
大家晚安
明天又得pass
案子拖了還沒結Q_Q

2020-09-02

Oriyar 11:49:36
嗨嗨,今晚八點連線喲!
Image from iOS
2
tobyliu 17:19:12
公司大爆炸我今天也 pass
2
Aaron 18:05:18
我應該也不行~
1
LittleWhiteYA 18:09:27
我今天會線上
大概 8 點多到家
大家都4線上 因為地公北辦今天全體在阿里山上~~
LittleWhiteYA 2020-09-02 19:55:00
喔喔喔喔 差點XD
deeper 19:35:43
今日小聚連結:https://meet.google.com/egx-zvjk-ouv
小聚紀錄:https://g0v.hackmd.io/@yukaii/Disfactory/%2FU_G8jIAOTWOEryhc0rd1Ng

meet.google.com

Meet

Real-time meetings by Google. Using your browser, share your video, desktop, and presentations with teammates and customers.

IU 19:58:20
啊啊啊
IU 19:58:31
我現在才發現是線上 XD
@oriyaroriyar 以後改線上是不是該 tag 所有通常會來的人?
我剛剛才問了deeper如何tag整個channel....
下週的演講我會tag channel 和常來的人
😆 1
IU 19:59:51
其實我都走到門口了 (🤣
😓 3
ael 20:16:32
這週末在松菸有社會設計展,很推薦大家去看https://www.accupass.com/event/2006200701541169176714

accupass.com

【Design can help, Design is helping】4th Design For Taiwan社會設計展|Accupass 活動通

『Design can help/Design is helping』第四屆Design For Taiwan社會設計展,一群來自全台不同領域的熱血青年,歷經一年的冒險,想用設計思考來解決周遭的問題。雖然第二階段的課程大都在線上完成,但各組每個月依舊不段的迭代,希望用自己小小的力量,也能改變社會,展覽期間每天會有不同的社會創新講堂,歡迎每位關心台灣的朋友們,一起來看展覽,聽講座,讓我們更美好!

github 20:38:35

#10 Review App

☐ netifly? ☐ staging server CORS domain whitelist

ael 21:56:41
今天 To Do 小結:
1. 9/9 小聚取消!!!!
2. 請 @cstsai @sandrahtlin 要督促 @aelcenganda 整理專案資料,不要讓 @aelcenganda 變成 bottleneck
3. User need research: @cstsai @jennie97111 會先整理出研究目標和可能要訪談的 TA persona,9/16 @sandrahtlin 會加入討論,@jnleyan 有時間的話可以上線加入。 @sandrahtlin 有空的話請提供 user research guideline 和 template。
4. 前端的部分,要跟 @yoyo930021 確認前端 CI 沒問題,還有 @yukai 提議可以加入前端 review app,讓 @cstsai 方便 review Frontend 2.0。 Frontend 2.0 目標是 9/30 可以完成,但是一切還是以可維護性為優先。
5. 後端的部分,需要 @cph 開 server 權限給大家還有 CD 的部分,避免 deploy 卡在你身上,你 9/16 有辦法參加小聚嗎?@f46284628 create document 的 action 再麻煩你了。 @swind 感謝你看了 many to many 欄位要怎麼做和呈現,再研究一下吧!@jsaon92 9/30 等你的 `display_status` XD 然後 @cstsai 有欄位問題想要找 @tobyliu
剛剛有人提醒我,最好還是跟大家講一下我最近狀態很差,需要有人主動戳我。大家應該有發現我至少一個月沒有力氣在小聚前先 PO 會議待討論事項。所以這段時間還請大家多多幫忙了 ><
我這週末會處理 review app
還會寫一些前端 我終於週末有空了 QQ
@yoyo930021 sorry 讓你昨天白跑一趟,下週沒有小聚噢
不會啦 我自己沒看到
LisbethW1130 2020-09-09 14:34:06
感謝,剛剛想說臨時起意過來看看,還好有看到
OK 9/16 會到現場
3 1 🤩 1 1
ael 22:08:57
剛剛有人提醒我,最好還是跟大家講一下我最近狀態很差,需要有人主動戳我。大家應該有發現我至少一個月沒有力氣在小聚前先 PO 會議待討論事項。所以這段時間還請大家多多幫忙了 ><
SL 22:09:44
👹 User need research 的一些下一步 👹


1️⃣ *定義出「地公想緊緊抓牢的人」*
可透過現有的群眾去做劃分

2️⃣ *理解他們* 
透過質性訪談去了解(我猜測我們的樣本數會偏小,所以與其廣發問券不如直接去問)

3️⃣ *發想相對應可做的事情*
看我們訪談整理的怎麼樣,針對我們的發現做發想囉


所以定義得出*「地公想緊緊抓牢的人」*會滿重要的(會讓之後的事情變輕鬆很~多)

-------------例子分隔線--------------------

【現在有什麼樣的人在舉報呢? 】

種類A:
行為特徵|一個人短期舉報很多工廠、會來關切有沒有舉報成功、blah blah
地公愛他們指數|4/5,因為這些人可以成為推廣小天使

種類B:
行為特徵|會上傳沒有用的照片、看起來有點搞不清楚狀況、blah blah
地公愛他們指數|1/5,因為就是不需要更多沒用的資訊

種類C:
行為特徵|認識的人、舉報不多但全都是可用的資訊
地公愛他們指數|3/5,因為有可靠的基本盤就是安心  

-------------例子分隔線--------------------

上面是例子啦,但我相信光是看舉報的資料,應該可以歸納出滿多種不同的人,然後我們就可以從中挑選



以上,以同步 @cstsai@jennie97111 ,但也在這邊跟大家說一聲~~~
🤩 2 1 👍 1
ael 23:33:24
我放棄修改我四月寫的產品經理心得,直接 publish 了。現在回頭看會覺得裡面有些地方寫的有些可笑,但我沒力氣改了 XD

https://medium.com/@aelcenganda/open-source-civic-tech-product-manager-in-disfactory-with-ngo-f40d050f886b

Medium

在 g0v 專案當 PM — 開源社群與 NGO 的混亂有序開放協作|Disfactory 農地違章工廠回報系統

這是寫於 2020 年 4 月初的文章。三月的某個星期三晚上十二點,還有六七個人在辦公室瘋狂解程式的 bug 和準備隔天的記者會,再三確認產品介紹網頁和 demo…

等 g0v 年會結束後,再寫一篇吧
2

2020-09-03

2020-09-07

github 21:12:52

#13 測試 Netlify Deploy Previews #2

:white_check_mark: All checks have passed

github 21:16:42

#13 測試 Netlify Deploy Previews #2

@yoyo930021 所以我可以理解成,是正在做 reviewing app,但是還有些問題所以 repoen 嗎?
其實沒問題了
只是因為關閉 PR 就看不到了
所以打開給大家看看
其實沒問題了
只是因為關閉 PR 就看不到了
所以打開給大家看看
@yoyo930021 所以現在有連結可以給 @cstsai review 已經做好的部分嗎?上次是用 yukai 自己的 host

2020-09-08

Oriyar 10:15:07
*明晚(9/8)現場小聚暫停,大家來聽講座吧!*

嗨嗨大家 <!channel> ,明晚我們和獨立媒體報導者舉辦談日本處理遷廠的政策講座。報名連結在此(線上和現場都必須報名呦)。所以明天地公北辦不會開放,大家可以現場聚或線上見囉。

_____分格線______

農地違章工廠在台灣農村屢見不鮮,數量龐大且具污染的農地違章工廠,是台灣的難解問題,然而台灣並非是亞洲唯一出現違章工廠的地方,在日本,也出現住工混合的違章工廠污染問題,由於日本公害頻傳,如駭人聽聞的水俁病,促使日本痛定思痛,花了50年要解決住工混合造成的公害問題。而日本究竟如何解決違章工廠問題,地球公民基金會至日本取經,借鏡日本的解決策略。該場將透過報導者記者林慧貞與孔德廉對台灣農地違章工廠的現況與遷廠觀察切入,再藉由地球公民基金會研究員深入日本的參訪與研究,反省台灣的可能遷廠措施。
▌時間:2020/9/9 19:00-21:00
▌地點:派大星 Event Space(台北市松山區八德路三段12巷16弄3號地下室)
▌主講人:陳威志、李翰林、吳其融/地球公民基金會專員
▌與談人:林慧貞、孔德廉/報導者記者
▌主持人:吳沅諭/地球公民基金會專員
▌主辦單位:地球公民基金會、報導者
報名連結:https://bit.ly/3jb8GjZ
提醒您,需連進網址點「線上報名」才表示報名成功喔!報名分為「現場參加」與「線上參與」兩種方式。
延伸閱讀:因公害中覺醒的日本,如何解決違章工廠問題?
1.日本如何因公害覺醒,解決「違章工廠」問題 https://bit.ly/34H4g0w
2.2兆日圓帶動20兆公害防治投資 https://bit.ly/32wGZeR
3.日本中小企業廠商如何協力和政府打交道 https://bit.ly/3lnRppL
118095633_3278739275520629_1364738305441614725_o (1).jpg
<!channel>
@cstsai 已知用火!感謝~
我線上也不會出現喔
1 2 2
deeper 10:29:18
<!channel>

2020-09-09

ael 12:03:59
我線上也不會出現喔
Oriyar 16:08:42
<!channel> 再提醒大家一次,今晚沒有線上線下小聚,不過有線上講座可以參加!


【線上+現場講座】看看日本70年代如何解決「違章工廠」|報名講座👉 https://bit.ly/2DnNJ6e

---
農地工廠在1960年代也曾經是日本的問題,但卻與台灣走向完全不一樣的結果,地球公民研究員組成訪問團前往日本,實際走訪工業區並訪問多位教授,帶回珍貴日本經驗。本次與報導者共同舉辦講座,看看日本70年代經驗,一起思考台灣面對違章工廠議題的更多可能性,除了報名現場之外也歡迎大家線上參與噢!
▌時間:2020/9/9 19:00-21:00
▌地點:派大星 Event Space(台北市松山區八德路三段12巷16弄3號地下室)
▌主講人:陳威志、李翰林、吳其融/地球公民基金會研究員
▌與談人:林慧貞、孔德廉/報導者記者
▌主持人:吳沅諭/地球公民基金會專員
▌主辦單位:地球公民基金會、報導者
報名講座👉 https://bit.ly/2DnNJ6e

地球公民基金會

9/9 【線上+現場】看看日本70年代如何解決「違章工廠」 | 地球公民基金會

農地違章工廠在台灣農村數量龐大且具污染的農地違章工廠,是台灣的難解問題,在日本,也出現住工混合的違章工廠污染問題,由於日本公害頻傳,如駭人聽聞的水俁病,促使日本痛定思痛,花了50年要解決住工混合造成的公害問題。而日本究竟如何解決違章工廠問題,地球公民基金會至日本取經,借鏡日本的解決策略。該場將透過報導者記者林慧貞與孔德廉對台灣農地違章工廠的現況與遷廠觀察切入,再藉由地球公民基金會研究員深入日本的參訪與研究,反省台灣的可能千廠措施。

Sonia 16:18:54
Hi @cstsai 好久不見XDDD 因為我自己這幾個月有事要忙,所以可能暫時這1-3個月沒有心力把時間撥到專案上,標籤跟郵局文件剩下調整格式但我一直沒空處理,真的覺得非常抱歉🧎‍,不知道你這邊覺得怎麼做比較好,是願意等我有時間弄嗎?進度可能會極度緩慢,還是想要讓其他人接手,我會好好把 code 整理好交接?
咦咦其實我測試staging那邊的功能,現在格式是對的欸! @swind 也說可以接手,所以不用太擔心喔 尼已經幫了大忙
@sonia8715 可以幫忙把已經做到的進度更新在這裡嗎?

https://github.com/Disfactory/Disfactory/issues/321
👍 1 👌 1
kiang 16:21:17
也許可以參考透明足跡的作法,透過群眾募資方式取得資金,正式僱用工程師協助加速開發工作 😉

https://npost.tw/archives/42630

NPOst 公益交流站

綠盟曾虹文:「群眾募資不只為了籌錢,還為經營受眾與倡議」/NPO 群募百樂餐 - NPOst 公益交流站

給支持者一個期待,然後對他們負責。

2020-09-10

deeper 10:35:41
@jennie97111 初步討論的user need research plan
https://g0v.hackmd.io/@yukaii/Disfactory/%2F5_JZQYLeRuO8VBJvK7vPbg
大家有任何想問使用者的問題都歡迎進去補充喔~
@sandrahtlin @jnleyan @xinrooforwork 可以在訊息海中先看這裡
好的!感謝
1
ael 10:44:32
@yoyo930021 所以我可以理解成,是正在做 reviewing app,但是還有些問題所以 repoen 嗎?
IU 10:51:46
其實沒問題了
只是因為關閉 PR 就看不到了
所以打開給大家看看
ael 11:31:33
@jnleyan 想請你幫忙看一下這些 `design` 相關的 issue 有沒有哪些可以關一關,尤其是路人來提供建議的部分,我想很多你的新版 UI 都有處理到,可以回應一下然後關掉。 https://github.com/Disfactory/Disfactory/issues?q=is%3Aissue+is%3Aopen+label%3Adesign

2020-09-11

github 16:22:10

#6 Bump http-proxy from 1.18.0 to 1.18.1

Bumps <https://github.com/http-party/node-http-proxy|http-proxy> from 1.18.0 to 1.18.1. Changelog _Sourced from <https://github.com/http-party/node-http-proxy/blob/master/CHANGELOG.md|http-proxy's changelog>._ &gt; *<https://github.com/http-party/node-http-proxy/compare/1.18.0...v1.18.1|v1.18.1> - 2020-05-17* &gt; *Merged* &gt; &gt; • Skip sending the proxyReq event when the expect header is present <https://github-redirect.dependabot.com/http-party/node-http-proxy/pull/1447|`[#1447](https://github.com/http-party/node-http-proxy/issues/1447)`> &gt; • Remove node6 support, add node12 to build <https://github-redirect.dependabot.com/http-party/node-http-proxy/pull/1397|`[#1397](https://github.com/http-party/node-http-proxy/issues/1397)`> Commits • <https://github.com/http-party/node-http-proxy/commit/9b96cd725127a024dabebec6c7ea8c807272223d|`9b96cd7`> 1.18.1 • <https://github.com/http-party/node-http-proxy/commit/335aeeba2f0c286dc89c402eeb76af47834c89a3|`335aeeb`> Skip sending the proxyReq event when the expect header is present (<https://github-redirect.dependabot.com/http-party/node-http-proxy/issues/1447|#1447>) • <https://github.com/http-party/node-http-proxy/commit/dba39668ba4c9ad461316e834b2d64b77e1ca88e|`dba3966`> Remove node6 support, add node12 to build (<https://github-redirect.dependabot.com/http-party/node-http-proxy/issues/1397|#1397>) • See full diff in <https://github.com/http-party/node-http-proxy/compare/1.18.0...1.18.1|compare view> <https://docs.github.com/en/github/managing-security-vulnerabilities/configuring-github-dependabot-security-updates|Dependabot compatibility score> Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. * * * Dependabot commands and options You can trigger Dependabot actions by commenting on this PR: • `@dependabot rebase` will rebase this PR • `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it • `@dependabot merge` will merge this PR after your CI passes on it • `@dependabot squash and merge` will squash and merge this PR after your CI passes on it • `@dependabot cancel merge` will cancel a previously requested merge and block automerging • `@dependabot reopen` will reopen this PR if it is closed • `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually • `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) • `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) • `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) • `@dependabot use these labels` will set the current labels as the default for future PRs for this repo and language • `@dependabot use these reviewers` will set the current reviewers as the default for future PRs for this repo and language • `@dependabot use these assignees` will set the current assignees as the default for future PRs for this repo and language • `@dependabot use this milestone` will set the current milestone as the default for future PRs for this repo and language You can disable automated security fix PRs for this repo from the <https://github.com/Disfactory/about.disfactory.tw/network/alerts|Security Alerts page>.

github 17:24:08

#392 有資訊但沒照片的新增點位

*Describe the bug* 出現了只有資訊但沒有照片的新增點位 *To Reproduce* <https://disfactory.tw/#map=17.00/120.6809347/24.272856620000013|https://disfactory.tw/#map=17.00/120.6809347/24.272856620000013> *Expected behavior* 我只是想知道為什麼會有這個情況:sweat_smile: 照理說照片應是必填資訊? *screenshot* <https://user-images.githubusercontent.com/60970217/92905190-0a931e80-f456-11ea-97a3-78eb28ed7051.png|截圖 2020-09-11 下午5 26 40> <https://user-images.githubusercontent.com/60970217/92905212-0ebf3c00-f456-11ea-9de9-9d788f4968c2.png|截圖 2020-09-11 下午5 26 47> <https://user-images.githubusercontent.com/60970217/92905215-0f57d280-f456-11ea-91e0-a749d76fa84c.png|截圖 2020-09-11 下午5 26 55>

因為我要幫這個點位檢舉,所以現在就會幫它上傳一下google街景截圖了
github 20:44:39

#7 chore(deps): bump http-proxy from 1.18.0 to 1.18.1

Bumps <https://github.com/http-party/node-http-proxy|http-proxy> from 1.18.0 to 1.18.1. Changelog _Sourced from <https://github.com/http-party/node-http-proxy/blob/master/CHANGELOG.md|http-proxy's changelog>._ &gt; *<https://github.com/http-party/node-http-proxy/compare/1.18.0...v1.18.1|v1.18.1> - 2020-05-17* &gt; *Merged* &gt; &gt; • Skip sending the proxyReq event when the expect header is present <https://github-redirect.dependabot.com/http-party/node-http-proxy/pull/1447|`[#1447](https://github.com/http-party/node-http-proxy/issues/1447)`> &gt; • Remove node6 support, add node12 to build <https://github-redirect.dependabot.com/http-party/node-http-proxy/pull/1397|`[#1397](https://github.com/http-party/node-http-proxy/issues/1397)`> Commits • <https://github.com/http-party/node-http-proxy/commit/9b96cd725127a024dabebec6c7ea8c807272223d|`9b96cd7`> 1.18.1 • <https://github.com/http-party/node-http-proxy/commit/335aeeba2f0c286dc89c402eeb76af47834c89a3|`335aeeb`> Skip sending the proxyReq event when the expect header is present (<https://github-redirect.dependabot.com/http-party/node-http-proxy/issues/1447|#1447>) • <https://github.com/http-party/node-http-proxy/commit/dba39668ba4c9ad461316e834b2d64b77e1ca88e|`dba3966`> Remove node6 support, add node12 to build (<https://github-redirect.dependabot.com/http-party/node-http-proxy/issues/1397|#1397>) • See full diff in <https://github.com/http-party/node-http-proxy/compare/1.18.0...1.18.1|compare view> <https://docs.github.com/en/github/managing-security-vulnerabilities/configuring-github-dependabot-security-updates|Dependabot compatibility score> Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. * * * Dependabot commands and options You can trigger Dependabot actions by commenting on this PR: • `@dependabot rebase` will rebase this PR • `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it • `@dependabot merge` will merge this PR after your CI passes on it • `@dependabot squash and merge` will squash and merge this PR after your CI passes on it • `@dependabot cancel merge` will cancel a previously requested merge and block automerging • `@dependabot reopen` will reopen this PR if it is closed • `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually • `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) • `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) • `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) • `@dependabot use these labels` will set the current labels as the default for future PRs for this repo and language • `@dependabot use these reviewers` will set the current reviewers as the default for future PRs for this repo and language • `@dependabot use these assignees` will set the current assignees as the default for future PRs for this repo and language • `@dependabot use this milestone` will set the current milestone as the default for future PRs for this repo and language You can disable automated security fix PRs for this repo from the <https://github.com/Disfactory/license.disfactory.tw/network/alerts|Security Alerts page>.

2020-09-12

github 13:30:30

*<https://github.com/Disfactory/Disfactory/compare/a276cca5d78b...c46e17760694|2 new commits> pushed to <https://github.com/Disfactory/Disfactory/tree/master|`master`>* <https://github.com/Disfactory/Disfactory/commit/b130a5adcee59864ec7180ebde0bae609aa50c77|`b130a5ad`> - add batch size to bulk_update to avoid large query overhead <https://github.com/Disfactory/Disfactory/commit/c46e17760694e536763b7a383e268103667ef432|`c46e1776`> - Merge pull request #390 from Disfactory/optimize-0023-migration-speed

github 16:55:50

*<https://github.com/Disfactory/Disfactory/compare/c46e17760694...0a0d59dc9061|2 new commits> pushed to <https://github.com/Disfactory/Disfactory/tree/master|`master`>* <https://github.com/Disfactory/Disfactory/commit/fa2b02ceca6fb4ba9614c970fdd8bfa7632a1e9e|`fa2b02ce`> - Add GovAgency migration with initial data <https://github.com/Disfactory/Disfactory/commit/0a0d59dc9061771f6b068af7e09e23c09c0c1c31|`0a0d59dc`> - Merge pull request #361 from Disfactory/backend-add-gov-agency-table

github 17:01:00

#393 add display_number in FactorySerializer

resolved <https://github.com/Disfactory/Disfactory/issues/224|#224> , now the API returns factory with display_number

:white_check_mark: All checks have passed

github 17:48:43

#394 Workaround python-docx bug https://github.com/python-openxml/python-docx/issues/187

Thanks <https://github.com/stegben|@stegben> <https://github.com/Disfactory/Disfactory/issues/323#issuecomment-691423661|#323 (comment)> Accroding to <https://github.com/python-openxml/python-docx/issues/187|python-openxml/python-docx#187> python-docx can't parse some jpeg files correctly, so we use PIL to format all jpeg files to workaround this issue when generating docx file.

:white_check_mark: All checks have passed

github 19:29:41

*<https://github.com/Disfactory/Disfactory/compare/0a0d59dc9061...afe2f6580372|2 new commits> pushed to <https://github.com/Disfactory/Disfactory/tree/master|`master`>* <https://github.com/Disfactory/Disfactory/commit/c6aff3a9b727232f4b030b44cc77ddde41022eae|`c6aff3a9`> - Accroding to <https://github.com/python-openxml/python-docx/issues/187> <https://github.com/Disfactory/Disfactory/commit/afe2f658037276c7462622643d5adbec76d858d6|`afe2f658`> - Merge pull request #394 from Disfactory/workaround_python_docx_jpeg_bug

2020-09-13

github 03:48:13

#2 Bump node-fetch from 2.6.0 to 2.6.1

Bumps <https://github.com/bitinn/node-fetch|node-fetch> from 2.6.0 to 2.6.1. Release notes _Sourced from <https://github.com/bitinn/node-fetch/releases|node-fetch's releases>._ &gt; *v2.6.1* &gt; &gt; *This is an important security release. It is strongly recommended to update as soon as possible.* &gt; &gt; See <https://github.com/node-fetch/node-fetch/blob/master/docs/CHANGELOG.md#v261|CHANGELOG> for details. Changelog _Sourced from <https://github.com/node-fetch/node-fetch/blob/master/docs/CHANGELOG.md|node-fetch's changelog>._ &gt; *v2.6.1* &gt; &gt; *This is an important security release. It is strongly recommended to update as soon as possible.* &gt; &gt; • Fix: honor the `size` option after following a redirect. Commits • <https://github.com/node-fetch/node-fetch/commit/b5e2e41b2b50bf2997720d6125accaf0dd68c0ab|`b5e2e41`> update version number • <https://github.com/node-fetch/node-fetch/commit/2358a6c2563d1730a0cdaccc197c611949f6a334|`2358a6c`> Honor the `size` option after following a redirect and revert data uri support • <https://github.com/node-fetch/node-fetch/commit/8c197f8982a238b3c345c64b17bfa92e16b4f7c4|`8c197f8`> docs: Fix typos and grammatical errors in README.md (<https://github-redirect.dependabot.com/bitinn/node-fetch/issues/686|#686>) • <https://github.com/node-fetch/node-fetch/commit/1e99050f944ac435fce26a9549eadcc2419a968a|`1e99050`> fix: Change error message thrown with redirect mode set to error (<https://github-redirect.dependabot.com/bitinn/node-fetch/issues/653|#653>) • <https://github.com/node-fetch/node-fetch/commit/244e6f63d42025465796e3ca4ce813bf2c31fc5b|`244e6f6`> docs: Show backers in README • <https://github.com/node-fetch/node-fetch/commit/6a5d192034a0f438551dffb6d2d8df2c00921d16|`6a5d192`> fix: Properly parse meta tag when parameters are reversed (<https://github-redirect.dependabot.com/bitinn/node-fetch/issues/682|#682>) • <https://github.com/node-fetch/node-fetch/commit/47a24a03eb49a49d81b768892aee10074ed54a91|`47a24a0`> chore: Add opencollective badge • <https://github.com/node-fetch/node-fetch/commit/7b136627c537cb24430b0310638c9177a85acee1|`7b13662`> chore: Add funding link • <https://github.com/node-fetch/node-fetch/commit/5535c2ed478d418969ecfd60c16453462de2a53f|`5535c2e`> fix: Check for global.fetch before binding it (<https://github-redirect.dependabot.com/bitinn/node-fetch/issues/674|#674>) • <https://github.com/node-fetch/node-fetch/commit/1d5778ad0d910dbd1584fb407a186f5a0bc1ea22|`1d5778a`> docs: Add Discord badge • Additional commits viewable in <https://github.com/bitinn/node-fetch/compare/v2.6.0...v2.6.1|compare view> Maintainer changes This version was pushed to npm by <https://www.npmjs.com/~akepinski|akepinski>, a new releaser for node-fetch since your current version. <https://docs.github.com/en/github/managing-security-vulnerabilities/configuring-github-dependabot-security-updates|Dependabot compatibility score> Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. * * * Dependabot commands and options You can trigger Dependabot actions by commenting on this PR: • `@dependabot rebase` will rebase this PR • `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it • `@dependabot merge` will merge this PR after your CI passes on it • `@dependabot squash and merge` will squash and merge this PR after your CI passes on it • `@dependabot cancel merge` will cancel a previously requested merge and block automerging • `@dependabot reopen` will reopen this PR if it is closed • `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually • `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) • `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) • `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) • `@dependabot use these labels` will set the current labels as the default for future PRs for this repo and language • `@dependabot use these reviewers` will set the current reviewers as the default for future PRs for this repo and language • `@dependabot use these assignees` will set the current assignees as the default for future PRs for this repo and language • `@dependabot use this milestone` will set the current milestone as the default for future PRs for this repo and language You can disable automated security fix PRs for this repo from the <https://github.com/Disfactory/TaiwanLegislatorData/network/alerts|Security Alerts page>.

2020-09-14

github 22:17:00

*<https://github.com/Disfactory/Disfactory/compare/afe2f6580372...737546a48a12|2 new commits> pushed to <https://github.com/Disfactory/Disfactory/tree/master|`master`>* <https://github.com/Disfactory/Disfactory/commit/9e9144a52743d693fcc9eb8df7bd48f2f2a0aefe|`9e9144a5`> - add display_number in FactorySerializer <https://github.com/Disfactory/Disfactory/commit/737546a48a12126b0808cb9fb3d038e9155db96a|`737546a4`> - Merge pull request #393 from Disfactory/expose-display-number

2020-09-15

LittleWhiteYA 00:17:47
問ㄍ問題
我現在 local 跑 migration 會噴出這個 error
``` File "/usr/local/lib/python3.7/site-packages/django/db/backends/utils.py", line 84, in _execute
return self.cursor.execute(sql, params)
django.db.utils.ProgrammingError: column "agency_name" of relation "api_govagency" does not exist
LINE 1: INSERT INTO "api_govagency" ("agency_name", "zip_code", "add...```
查了一下是因為這個 PR https://github.com/Disfactory/Disfactory/pull/376
感覺是因為改到舊的 migrations 但是已經在 local 跑新的 migration 了?

#376 在 admin page 上新增 輸出成 docx 檔 的 action

<https://user-images.githubusercontent.com/126123/89883513-d0d2bc00-dbfa-11ea-9408-d1863d1edfe8.png|image> 延續 <https://github.com/darrenjhsu|@darrenjhsu> `export_doc branch` 的實做。 使用 python-docx 開啟在 `doc_resources` 內的 template, 之後將選中的 factory 的資訊,以及 image 下載放入 docx 檔案中(所以 export 所需要的時間,跟圖片多寡有很大的關係 ) 並且在 admin 中增加了針對 action 的測試 產生出來的文件使用 google doc 開啟的結果如下 <https://user-images.githubusercontent.com/126123/89884182-c2d16b00-dbfb-11ea-9de3-712476a3be9b.png|image>

改到舊的 migrations 但是已經在 local 跑新的 migration 了?

Orz 抱歉,想確認一下。
LittleWhiteYA 2020-09-15 19:56:02
我的情形應該是我已經 migrate 到 24 還 25
但是我是跑舊的 17
所以導致說我跑到最新的那個 migration 的時候,裡面會用到的欄位我沒有
deeper 14:23:52
我們上週辦的【污染不停止,以後吃什麼】座談:看看日本70年代如何解決「違章工廠」,講座紀錄和錄影已經上網嚕~~~ 有興趣的大家有空可以聽聽

地球公民基金會

9/9 【講座紀錄】看看日本70年代如何解決「違章工廠」 | 地球公民基金會

農地違章工廠在台灣農村數量龐大且具污染的農地違章工廠,是台灣的難解問題,在日本,也出現住工混合的違章工廠污染問題,由於日本公害頻傳,如駭人聽聞的水俁病,促使日本痛定思痛,花了50年要解決住工混合造成的公害問題。而日本究竟如何解決違章工廠問題,地球公民基金會至日本取經,借鏡日本的解決策略。該場將透過報導者記者林慧貞與孔德廉對台灣農地違章工廠的現況與遷廠觀察切入,再藉由地球公民基金會研究員深入日本的參訪與研究,反省台灣的可能千廠措施。

1 1
Oriyar 19:22:56
*明天記得要小聚* and *COMBO記者會成果*

雖然 @cstsai 早我一步分享上週講座的紀錄(10月還有呦),但我有這兩週連開記者會的成果哼哼。

【0831記者會】
• 各縣市增加違章工廠稽查人手、增列拆除經費,尤其是新增數量快的彰化縣、桃園市。
• 各縣市應依《工輔法》更新地方裁量基準,立即執法
• 經濟部中部辦公室應公開未登記工廠名單、位置與查處情形
• 經濟部中部辦公室應依法邀請民間團體參與工廠管理輔導會報
• 經濟部應修改《未登記工廠停止供水供電作業程序》,具體化代行斷水斷電的實施方式,讓各縣市有所依循。
_媒體露出_ 
1.20200831中央社--農地違章工廠查處落後 環團籲地方加強人力 
2.20200831自由--違章工廠新增不斷 環團點名彰化縣居全台之冠 
3.20200901自由--工輔法3月實施 新增違章工廠居冠 環團批彰縣零拆除 (彰縣府說已斷水斷電12家) 
4.20200831自由--鄭文燦駁斥違章工廠全國第一說法 強調拆除量才是第一 
5.20200831新頭殼--新增違章工廠竟只有一間自行拆除? 環團批縣市首長擺爛 
6.20200831環資--新工輔法上路五個月 檢舉150家農地工廠僅拆1家 環團怒:即報即拆淪口號 
7.20200831公視--新工廠輔導法上路近半年 檢舉逾150件僅1件拆除 
8.20200831客家電視--新版工輔法上路 違章工廠亂象未改 
9.20200831華視--317間只拆1家 環團直擊彰化違章工廠 
10.20200903公庫--新版工輔法上路成效不彰 環團點名人力、經費、法規有缺失

【0908記者會】
• 經濟部應公開中高污染農地違章工廠名單(包含1,153家中高污染未登記工廠與314家中高污染臨時登記工廠)名稱、所在位置與產業類型。
• 各地方政府應統一格式公開未登記工廠清查報告,並公布中高污染廠商的名稱、位置與產業別。
• 政府應跨部會(農業、環保、經發等)共同規劃中高污農地違章工廠遷廠;成立專責機構、輔導廠商聯合貸款與遷廠,且要有工業用地媒合。
_媒體露出_
1.20200908中央社--石蚵疑染重金屬 環團籲公開農地工廠名單 
2.Sina新浪網(中央社)--石蚵疑染重金屬 環團籲公開農地工廠名單 
3.20200908經濟日報(中央社)--中高污染未登記工廠 經部要求明年3/19前申請改善 
4.20200908上下游--中高污染違章工廠毒害魚米之鄉,經濟部清查卻不公開名單,環團批《工輔法》虛有其表 
5.20200908聯合UDN--石蚵疑受重金屬汙染變綠色 環團籲公開農地工廠名單 
6.20200908環資--中高污染工廠遷廠原則公布 環團批虛有其表 籲經濟部公開名單 
7.20200908 Hinet生活誌(環資)--中高污染工廠遷廠原則公布 環團批虛有其表 籲經濟部公開名單 
8.20200908* *ET today*-*-花7千萬納稅錢清查農地工廠!環團怒政府資料不公開「虛有其表」 
9.20200908 Yahoo新聞--石蚵疑遭重金屬汙染 環團籲公開農地工廠名單 
10.20200908公視--高污染違章工廠 環團籲經部公開名單 
11.20200908苦勞網--【記者會】清查資訊不公開,幽靈農地工廠抓不到--工輔子法虛有其表,中高污染遷廠須有配套 
12.20200908工商時報--經濟部公布非低污染未登記工廠處理原則 輔導期最長可達6年(經濟部回應記者會發稿,完全沒看我們新聞稿)
1 😆 1 1
github 21:27:49

#14 Mobile share button

:white_check_mark: All checks have passed

2020-09-16

ael 11:47:57
設計的部份,今天 @sandrahtlin 會來跟 @cstsai@jennie97111 討論使用者需求訪談,看 @jnleyan@xinrooforwork 要不要加入
我今天可以! 但身體不太舒服,線上加入 !
X Lin 11:48:52
我今天可以! 但身體不太舒服,線上加入 !
ael 16:48:58
今天 @cph 會來, @swind @jsaon92 @f46284628
我一樣大約 8:30 分會到
cph 剛剛說他來不及
會喔
我忘了 yah @tobyliu
LittleWhiteYA 2020-09-16 18:43:43
公司東西壞掉ㄌ ...
會晚點
我無法去我工作爆炸QQ
我這邊還沒有進度,明天會上一波
LittleWhiteYA 2020-09-16 20:50:51
要過去ㄌ
ael 17:42:27
█ g0v Summit 2020 12/3-6 盲鳥票/辦桌票開賣 █

「在這個世界裏,尋找著你的門票
你問我門票在哪裏?
我正在賣 我正在賣」

如果等待議程公布前的片刻不足以填補你靈魂的乾涸,
那就和盲鳥一起展翅吧!
划算的價格、與府城限定的秘密小食,將是對汝等勇氣的嘉賞。

議程盲鳥票這裡去:https://g0v-summit-2020.kktix.cc/events/c0nf
辦桌食飯票看這裡: https://g0v-summit-2020.kktix.cc/events/eat-table

#g0vSummit2020

█ g0v Summit 2020 Ticket Now Available! █

“Looking for admission in the wide, wide world
Where have the tickets gone, you asked
It is I who is selling them.”

Fly with us as a “blind” early bird,
if the wait before schedule announcement doesn’t soothe your inner crave.
Ticket discounts and secret local treats are the prize reserved for the brave.

Early conference registration: https://g0v-summit-2020.kktix.cc/events/c0nf
Reserve a seat in our after-party: https://g0v-summit-2020.kktix.cc/events/eat-table

#2020SummitWinWin


text by RSChiang, bess; image by chihao
g0v Summit 2020

g0v-summit-2020.kktix.cc

g0v Summit 2020 台灣零時政府雙年會

g0v Summit 兩年舉辦一次,關注開放政府、開源協作、公民參與等議題,是國際開放政府社群的焦點活動。2020 雙年會移師台南,在市區的 5 個會場聯合在地社群,推出連續 3 天的活動。

g0v-summit-2020.kktix.cc

g0v Summit 2020 辦桌特別場

辦桌特別場,除了有吃有喝以外,每桌將有不只一個 g0v Summit 2020 的議程講者坐鎮。台南道地美食,加上無法估量的腦袋交流,滿足肚皮滿足心。

@channel 想去 12 月 g0v 年會的朋友可以買票了唷~~ 這次 Disfactory 相關的分享會有三場議程唷!!

1. Disfactory 專案開發歷程介紹: 從 NGO 和從開源社群的角度
2. 有組織與無組織之間:不同組織與開源社群的合作經驗對談
3. 牧貓人:在 g0v 專案中做專案管理
已報名
LisbethW1130 19:29:29
今天在公司處理事情,不會去地公
👌 2
deeper 19:35:55
今日小聚連結:https://meet.google.com/egx-zvjk-ouv
小聚紀錄:https://g0v.hackmd.io/@yukaii/Disfactory/%2FWCYD9b--RC-lUfjIgp_CXA

meet.google.com

Meet

Real-time meetings by Google. Using your browser, share your video, desktop, and presentations with teammates and customers.

github 19:49:45

#395 後端建立工廠 API 應檢查圖片應為必填欄位

*Is your feature request related to a problem? Please describe.* A clear and concise description of what the problem is. Ex. I'm always frustrated when [...] *Describe the solution you'd like* A clear and concise description of what you want to happen. *Describe alternatives you've considered* A clear and concise description of any alternative solutions or features you've considered. *Additional context* Add any other context or screenshots about the feature request here. related to <https://github.com/Disfactory/Disfactory/issues/392|#392>

ael 19:51:52
@yukai `display_number` 應該已經合上去了,幫我看 API 能不能拿了。有問題找 @f46284628
ael