2016年8月9日 星期二

3 different types of participation - TW Mozillians in HKOSCon from 2014-2016

Last month in 6/24-26, several MozTW community members flied to Hong Kong visited HKOSCon, Hong Kong Open Source Conference. This is our 3rd time joining the event, and we had tried 3 different forms of participation, here I would like to share a bit about it.

HKOSCon

Hong Kong Open Source Conference is annual open source conference in Hong Kong, co-hosted by 3 communities, HKCOTA, HKLUG and Open Source Hong Kong.

One of the event's characteristic is that HKOSCon is formed by volunteers and students, not by for-profit company (which is pretty similar to COSCUP, another open source conference in Taiwan).

Actually, according to one of the funder (and Mozilla Rep) Sammy Fung said, we can think it as a smaller (around 500 ppls) and more internationalized (English-based) version of COSCUP, which have around 2k participants and use Chinese as main language.

According to my observation, participants in HKOSCon is a combination of local (Hong Kong) enginners and students, speakers and students from Taiwan, and foreign speakers.

2014 - Chinese Mozillians Unite

Booth and Forum Session

2014 (March 29) is our first time to participating in HKOSCon. We tried to gather 8 Reps from Hong Kong (2), Taiwan (3) and China (3) together in the conference. We host a typical Mozilla community booth, a forum (“Mozilla communities in Chinese-speaking regions”) and a private meetup to discuss various topics about building Mozilla communities in the region.

Hong Kong is a special place that is 1) accessable by people from both Taiwan and China, without many political problems and limitations, 2) use both Chinese / English as primary language, and 3) close to all major east-Asian cities, so it's pretty pratical to be choosen as the place that we all gathered. I also experience that Wikimania 2013 (took place in Hong Kong Polytechnic University) also take the advantage to gathered many China / Taiwan contributors. Singapore has similar advantages but it just 4 times far away for us.

What worked and what didn't?

The idea of unite the Mozillians from different places really works, and I believed that we need to do it more (re-engage MozCamp perhaps?) But next time if we want to take HKOSCon as a chance, we may need to plan a whole dedicated day for Mozillian meetup, to work longer besides participating inside confernece, to get into more detailed discussion. (which may look similar to Leadership Summit and MozCamp beta in India?)

Here is my debrief about our participation in HKOSCon 2014,

2015 - Involved more Taiwanese Mozillians

Booth and Workshop

In 2015 (June 26-27), we take a different approach that bring more Taiwanese Mozillian to get involved to HKOSCon. Total 7 Mozillians (5 Reps) joined. This year we also focus our most effort on the booth, and I personally host a Webmaker workshop.

The theme of the booth is FoxYeah campaign, we asked people to take selfie photos with 5 FoxYeah banners and received stickers. Most participants already know Firefox and was our user, so we would like to recall their attention back to the core value of Firefox.

For the Webmaker workshop, due to the design of the room and session length, it's not really work out well. Also I feel that Webmaker is not really suitable for this developer-focus conference participants that it just too simple.

What worked and what didn't?

Designing a more interactive booth event worked really good, we had interacting with many graceful people at the booth, and got more then 40 “FoxYeah photos”.

Webmaker workshop which focus on education and entering level of contributors not work. The main participants of HKOSCon are more engineer based (far more then COSCUP) and we need our workshop to be more technical for them.

Here is my debrief about our participation in HKOSCon 2015, you can also find the link of articles from other participants inside.

2016 - Just focus on session

This year, due to overwhelmed workload after London Allhands, I didn't pay as much planning effot as previous 2 years that can involved many participants together. Instead, I try just to focus on session, and keep it simple that only 3 TW Mozillians joined and gave 2 sessions, debrief my journey of contributing in Mozilla and yajs.vim, JavaScript syntax highlight for VIM by Othree, another speaker from TW community*.

Besides sessions from the community volunteer, there are another 2 from Mozilla paid-staff - Mozilla Eir, connecting device topic by Kevin Hu and Fuzzing testing by Gary Kwong.

What worked and what didn't?

Because that we didn't set a booth, it's hard to evaluate how many attendees is interesting in participating Mozilla this time (compare to the previous 2 years that we had contributing forms at our booth).

But the Fuzzing and Othree's HTML5-related sessions, as well as my session did attach many people and I can feel overall better response then last year's workshop. Another reason of the better atmosphere at sessions may due to several OSS participating-related sessions had been organized next each other in schedule, and thus attached the right audiences.

And suggestion for the future...

From our previous experiences, here I come up with some suggestions for next year,

  1. Bring in more foreign technical speakers

    There are more developers in HKOSCon that is interesting in technical topics, engineering speaker can have better interaction in HKOSCon, things like “how we use Rust” or “How do we do Firefox release engineering” should do well there.

  2. Booth is necessery

    With only session, it's hard for us to interaction with all partcipants, booth does that well. Besides giving out stickers and demonstrating hardware / flyers, plan a simple event such as FoxYeah photo campaign in 2015 will please everyone.

  3. 7~10 Mozillians is good numbers for participation

    We had around 10 Mozillians (excludes local HK Mozillians which are all dedicated to run HKOSCon) in both 2014 and 2015 HKOSCon, 5~7 of them are volunteers. It's enough to both manage a booth and give 3 to 5 sessions with this numbers, and the rate of Mozillians to all participants would be around 2%.

2016年6月17日 星期五

The different kinds of (Mozilla) community spaces and it’s pathway

This is part of the result we found from the “How might we (re)invent existing and future MozSpace to run innivation experiments”, which we address different kinds of community space at the community space session on Mozilla AllHands 2016 in London.

(see original draft poster from our discussion)

The characteristic

There are different types of spaces with various characteristic, eg.

  • # of core contributors
  • scale of community
  • # of non-Mozilla communities involved
  • meeting / event frequency
  • density of the region / distence of the contributors (transit difficulties)
  • resource invest from Mozilla and community

Different type of spaces

Following is the space various in different type that we found in our expereinces and in different region, it may be a of community space (and probably also same for the community meeting).

Temporary (in time & venue) spaces

  • Online space (forum / IM / IRC channels)
  • Kitchen (or school) table
  • Meet in coffee house
  • Hackathon & sprint in private apartment / meeting venue
  • Partnership with co-working space (eg., The Hub)
  • Cooperating / supporting existing hackerspace / makerspace

Physically communtiy space

  • Mozilla Community Spaces, eg., Taipei, Manila & Jakarta
  • Space inside Mozilla office

Online space (forum / IM / IRC channels)

It was begin when some people who is interesting in promoting Mozilla and it’s various products gathering and meet online.

  • # of core contributors - 2~20
  • scale of community - 5~150
  • there will be much harder more then this numbers
  • # of non-Mozilla communities involved - 0
  • meeting / event frequency - variously
  • distence of the contributors - withing country / same languages area
  • resource invest from Mozilla and community - minimin

Kitchen (or school) Table

Some people may want to meet face-by-face hacking / discussing frequenly

  • # of core contributors - 2~3
  • scale of community - 2~5
  • # of non-Mozilla communities involved - 0
  • meeting / event frequency - various from weekly to monthly
  • distence of the contributors - closly, within city
  • resource invest from Mozilla and community - minimum

Meet in coffee house

If there are more contributors within in the city, they may able to meet weekly / bi-weekly / monthly and maybe more leisure with loose agenda ccording to the meeting frequency

  • # of core contributors - 5~10
  • scale of community - 5~30
  • # of non-Mozilla communities involved - some randemly
  • meeting / event frequency - weekly to monthly
  • density of the region / distence of the contributors - within city
  • resource invest from Mozilla and community - small, mainly a cup of coffee

Private apartment / meeting venue

When more contributors focus on some contirbuting regions, they will run some hackathon / design sprint periodically

  • # of core contributors - 5~15
  • scale of community - 10~100
  • # of non-Mozilla communities involved - 0
  • meeting / event frequency - quatyly / 6 months / yearly
  • density of the region / distence of the contributors - within country
  • resource invest from Mozilla and community - medium each time

Partnership with co-working space (eg., The Hub)

If there are some contributors or remoties work more frequenly and host more events, they may want to find a permanently / half-permanently space. We find that sometimes there are good cooperating and supporting from local co-working space.

  • # of core contributors - 3~10
  • scale of community - 20~
  • # of non-Mozilla communities involved - some
  • meeting / event frequency - daily, bi-daily, weekly
  • density of the region / distence of the contributors - within city
  • resource invest from Mozilla and community - small/medium monthly

Cooperating with existing hackerspace / makerspace

Similar to the above co-working space, there may be some hackerspace / makerspace already exist and in good align with Mozilla’s mission, the community may like to join or get involved the venue.

We should have some application procedure at this stage, for communities who is interesting in get into next stage of pathway.

  • # of core contributors - 3~10
  • scale of community - 20~
  • # of non-Mozilla communities involved - more then 2
  • meeting / event frequency - daily, bi-daily, weekly
  • density of the region / distence of the contributors - within city
  • resource invest from Mozilla and community - small/medium monthly

Physical Community Space

After all this stage, the community now has more people and frequenly events and many meetups, they may want to get their own community spaces in order to better hosting and contributing.

The most important thing in this stage is that besides benefit Mozilla community, we want to also help / support other communities within the region, in order to better using the resource, and they most probably also under their early stage of this pathway.

# of core contributors - 10~20 scale of community - 50~ # of non-Mozilla communities involved - 10 and more meeting / event frequency - daily, bi-daily density of the region / distence of the contributors - within city resource invest from Mozilla and community - large monthly

Space inside Mozilla office

If we have more and more remoties working at Mozilla during the growth of the Mozilla community, eventually we will set up a Mozilla office inside the area. It will be similar to the community spaces and have good community-staff relationship if we follow and grow alone the path.

  • # of core contributors - 20~35
  • scale of community - 100~
  • # of non-Mozilla communities involved - 10 and more
  • meeting / event frequency - daily, bi-daily
  • density of the region / distence of the contributors - within city / country
  • resource invest from Mozilla and community - large monthly

The pathway (aka. A River of Spaces)

Above different kinds of space is a typical pathway we found in different communities and in our community's 10+ years experience. We had pass all of those stage (besides the office one), and some other communities may currently in one of the earlier stage.


A River of Spaces

It’s like the flow of the river from upper reach to the ocean, we can imaging the flow as the size of the community / the resource / the reach and the impact. Different communities are not necessery follow the same pathway but it should be somehow similer.

Thanks all of the Mozilla Community Space stewards in the session, especially Henrik, Gaspar, Nikos, Yofie who is in this discussion.

2016年1月10日 星期日

Mozilla, we had a little transparency problem

We put too less attention to  "Community driven development" and "Transparent" part of our core culture recent years.

Why is Focus stay so secret before Mozlando, even we NDA covered Mozillians know nothing about it before it on stage? How can "we" say something like "we will take Firefox OS ..." or "we will go..."  without we even knowing it before the news and before someone on stage make the notice? Why is there more and more secret and non-public future feature of Firefox that we cannot find plan anywhere (eg., that "stream" things), And why could we took down all l10n-ed part of Webmaker (and even change it's name to Mozilla Learning without we had any discussion, and so far we still don't know anything about it's future's l10n strategy?)

we, we, we, we, we. How can Mozilla talk about “we” when “we” don’t even know what’s going on? - Elio 
I'm pretty agree the echo from BobChao's comment to Elio's blog post. We had a serious problem here and we need a little more TRANSPARENT PROCEDURE to fix it, just as our manifesto indicated. "Transparent community-based processes promote participation, accountability and trust." And we does need some more participation now!

2015年7月20日 星期一

TW Mozillians @ 香港開源年會 HKOSCon 2015

In the end of June, totally 7 Taiwan Mozillians (5 reps, 2 core contributors) flew to Hong Kong to host a Mozilla booth at HKOSCon 2015 (Hong Kong Open Source Conference). The following are 2 blog posts from Yao Wei and Ernest.

Mozilla Links 正體中文版: Showing off Firefox in HKOSCon 2015
Participating HKOSC 2015 — Medium

日前, ErnestBobChaoOrinRJ魏藥Peter 等共七位 MozTW 成員,一同前往香港開源年會,並擺設 Mozilla 攤位。關於活動的情形,歡迎閱讀以上魏藥及 Ernest 的直擊文章。

Here I will add some of my own experience & observation.
以下紀錄一些我個人的經驗與觀察。

Booth 攤位

MozTW Mozillians #FoxYeah @ HKOSCon2015
(TW Mozillians with Sammy Fung, Bob & Ernest is not in this photo)
(台灣成員與香港的 Sammy,Bob 與 Ernest 不在這張照片中)

Create big banners from FoxYeah stickers to demostrate, is indeed good try on our booth. We can take chance to sharing ideas with people on those topics of banner (security, customize...), and ask people to choose their favorite one to take photo, has really positive feedback.

將 FoxYeah 標語製作成大扛棒在攤位上展示,並讓人拿著最喜歡的標語拍照,是一個準備簡單,卻非常有笑點的小活動。不但容易吸引目光,也成為與參觀者的交流話題。

Thomas #FoxYeah @ HKOSCon2015
(We even got a "Gandi love Firefox" big thumb up from Gandi.net's Asia COO Thomas)
(我們甚至獲得了 Gandi 的 Asia COO Thomas 的「Gandi Love Firefox」認證)

Hong Kong local mozillians were basically all workers for HKOSCon, so we had to self-help on organize booth. Carry those Firefox OS devices and Firefox souvenir were not easy - the stickers are so-heavy. We had to separate them to everyone to carry in luggage when flight. Printer big stickers and make slogan banner on sight is good idea.

香港當地的 Mozillians 都是 HKOSCon 的主辦成員,我們只好自力救濟。要把這麼多展示品(包含近十台 Firefox OS 裝置、與各類 Firefox 紀念品)從台灣帶到香港,的確是蠻麻煩的一件事,貼紙卡片又重又多,要讓大家平均分攤裝行李箱托運。印貼紙跟買瓦楞版當場製作,又快效果又好。

We also got 21 filled contribute forms at the booth. Hope that we can get some more contributors at Hong Kong. (BTW, on our contribute form, we had various contributed area for people to choose their prefer, and most of people select multiple area. We should improve our [online form](http://mozilla.org/contribute) to accepting multiple choices too.)

本次攤位上,我們亦收集到 21 名有意貢獻者的聯絡方式。希望未來在香港能有更多 Mozilla 貢獻者。

Webmaker Workshop 工作坊

Webmaker Workshop @HKOSCon2015

Host a Webmaker workshop is one of my main topic in HKOSCon. But the lecture room is under "speak" mode, and not too easy for workshop that it's hard to see how attendees' status. Fortunately that my content is half exercise and half lecture intro.

主講 Webmaker 工作坊,是這次參與 HKOSCon 的主要任務。可惜的是,雖然參加者大多都有攜帶電腦,但是演講形式的座位安排,不太好掌握台下參加者的參與狀況,還是不太適合工作坊。幸好我準備的內容是實作與演講兼具。

This is also my first time to connecting Keynote, iPad (remote control and viewing keynote speaker note), Firefox, iPhone (share internet to mac), Reflector 2 (receive Chrome Cast mirrow from Mi2S), and Mi2S Android phone all together on stage. Perhaps the environment is too complicated thus my Mac hang for twice and it tooks me 5 mins to reboot when in 2/3 of workshop. Too bad that it cost me too much time and I cannot play last video in slide. I'll need to simplified the environment next time.

這也是我第一次同時使用 Keynote、iPad(連動 Keynote 看講者備忘)、Firefox、iPhone(分享網路給 Mac,再作熱點給 iPad 與 Android 手機)、Reflector 2(用於接收 Chrome Cast Mirrow 展示 Android 手機的 Webmaker App)與一台小米 2S Android 手機等六項裝置與軟體,在進行到約 2/3 時,遭遇到電腦當機了兩次,浪費了約五分鐘,讓最後一片短片來不及播放。環境太複雜,下次最好還是精簡一點,避免再次發生。

Here is my workshop slide,
以下是這次的投影片:


Webmaker + Workshop @HKOSCon 2015

Accommodation 住宿

Our accommodation "Royal Park Hotel" is really really valuable! Locating in central Shatin, 10 mins walk from train station all inside mall (cool and easy for luggage!), half hour metro to downtown, 1 hour Airport bus directly to hotel door. The best is price, 4 star hotel with large room (twice as large as hotel room in Kowloon) equipment with bathtub, the price only about 130 USD per 4pax room per night. (Almost same price to 2pax room.)

這次我們的住宿「帝都酒店」真的非常超值!極力推薦給四人以上一起到香港的朋友。地點位於沙田市中心,沙田車站約只要走十分鐘,全程都是室內商場(又涼又好拉行李)。搭地鐵不用半小時就能進到九龍,且 A41 機場巴士一小時直達飯店門口。最棒的是,四星級飯店,兩間四人房共定七晚,稅前一晚不到一千港幣(跟兩人房價格差不多),而且房間是九龍飯店的兩倍大以上(甚至有浴缸!)

2014年12月22日 星期一

Uber 與技術變革時的產業管制

我從 Uber 自去年(2013/12)在台灣開台到現在,已經搭了一百五十次以上,包含四五次機場接送與百多次市區通勤、另外還有幾次國外的搭乘經驗,對於服務品質、安全性與價格只能說非常滿意。

可惜它們應付管制的方式、與公然挑戰公權力的作法,以這麼不和諧的文化,想要挑戰運輸這種在台灣還是高度管制的行業,恐怕在目前的政府執政之下是經營不下去的。

很久沒有寫文章,把 Facebook 的討論以及整理拿回來,整理成一篇,好好談談。

Uber 的安全性控管與品質

只要有用過 Uber(或 Airbnb 之類「共享經濟」的服務),都可以體會它們對於服務提供者的品質控管機制。

Uber 每趟搭完車後,都有讓乘客評分的機制;五顆星是滿分,四顆星以下就會提供問題反應的功能,填寫意見在一天內一定會有專人回覆,司機低於四分就會被關注,服務內不太有機會搭到三顆星的司機,因此相對於計程車而言,Uber 的司機整體水準平均許多,對於用戶而言也會感受到相對安全許多吧。

Uber 還有另一個非常大的優點是,駕駛途中都會紀錄 GPS 軌跡,也會即時回報到營運系統;雖然行駛距離可能沒有計程車跳表的精確,但是在路線上,帳單上都會顯示出路線,有憑有據的。搭車後,如果有發生司機路不熟、繞路等問題,都可以透過網站反應,而客服會直接根據行駛紀錄,刷退多餘的費用。

很多人會說現在也有 55688 等 App 叫車,但對於司機、車輛、路線的即時意見反應與控管,就算是兩大車隊的 App 上路這麼多年,還是沒有善用 App 的優點,去造就服務水準的正向循環。過去你搭計程車碰到問題,頂多打叫車電話回去罵罵客服,最後還是只能默默吞下去。

政府對於計程車司機的管制根本只是低標(不能有犯罪紀錄、駕駛行為用扣點去控管…等),Uber 的問題根本不是安全的問題!

Uber 的問題本質

Uber 現在在台灣的問題,其實單純就只是徵白牌車(無營業執照駕駛)跟逃稅的問題罷了。

逃稅的問題好解決,我相信國稅局沒有這麼弱到只能查小市民的避稅,沒法查 Uber 等大公司(與大財團)的逃稅;而牌照問題,如果想要正向的方法去解決,就是輔導所有白牌司機拿營業職照,同時搞清楚為什麼他們寧願招募白牌車去違法經營、為什麼這些有興趣參與的司機不去考照、以載客為閒暇副業的司機該如何納管等等,好好檢討不合時宜的營業車輛相關規定。

計程車的服務品質費率管制

除了營業執照外,很多人反對的其中一個理由是「Uber 的高費率」。姑且不論 Uber 是否太貴(事實上 Uber X 的價格以市內通勤其實很合理、以服務而言我覺得 Uber Black 的價格也可接受)。費率上實際的問題其實是,相對於現行的計程車而言,作一樣的受召載客的核心服務,Uber 司機收入就是比較高。

所以面對計程車業的抗議,作法不應該是把 Uber 之類的行業趕出去,而是放寬不合時宜的計程車費率管制,讓司機提供高品質時,也可以換得高報酬,培養出本地的高品質車隊,才能牽制外來服務,同時解決納稅跟控管問題。

就像衛星車隊的出現,革新原本品質一律很糟的計程車產業。過去計程車需要費率跟牌照管制,因為乘客只能在路上攔車,天知道攔到什麼爛車坐地起價、或碰到哪種司機殺人越貨,所以要加重管制。

在衛星與網路車隊,諸如台灣大車隊、大都會車隊出現後,有了車隊篩選機制,叫到的車大部分都能有一定水準,但司機不論是加入此類車隊,或是以傳統的方式在路上巡迴載客,單趟收益都是一樣,頂多因為車隊的調度,能有較多車趟。

計程車業最不合理的現象

正是費率管制,讓那些願意提升能力,學外語、幫忙殘障客等,服務這麼好的司機,也賺不到更高的收入,只能跟其他沒有服務的司機一般跳表收費,這才是整個費率管制上最不合理的情形。

現在的技術演進,已經可以做到,透過 App 讓乘客在叫車時,先選好價格跟品質、確認司機評價,因此早已可以鬆綁過去那種強加控管費率的作法。 如果用制度上的設計,讓司機能在提供優質服務的同時,得到更好的報酬,自然就能讓整體品質提升。

如果制度上無法解決怎麼擺爛都是一樣收益的狀態,最後就是計程車業現在這樣,大家都爛到一個以台灣大車隊等車隊為高標、以無車隊的車子為低標的固定均勻的品質。

最好的時機

如果計程車業與司機,把矛頭放在明確指出核心問題、提出解決方案的 Uber 身上,方向就大錯特錯了。現在有 Uber 出現並挑戰法令(出來當標靶),正是整個產業最好的時機點,讓產業內的司機可以藉此爭取修改相關法規,建立對乘客、司機與經營者都更好、更有利的制度。

如果只是想把 Uber 等新競爭對手趕出去,那最終還是會持續過去數十年這樣的,產業成本持續上升、司機收入停滯不動、乘客乘車品質不穩的狀態,也就浪費了這個最好的時機點了。

任何的產業,面對新科技所帶來的變革,總該要支持政府隨著技術演進、有效開放管制的立場,才能持續向上提升,否則只會很殘酷的被時代淘汰罷了。