WEBVTT

00:00.000 --> 00:15.000
Okay. Hello everybody. Next up we've got in on Taiwan's shared OSS community and event infrastructure.

00:15.000 --> 00:18.000
And your time starts.

00:18.000 --> 00:20.000
Now.

00:20.000 --> 00:25.000
Okay. Hello everyone. I'm from Taiwan and I'm going to tell you that I'm going to throw

00:25.000 --> 00:29.000
the Taiwan's shared over the open source community and event infrastructure.

00:29.000 --> 00:33.000
And that's two projects. One is the OSB pass.

00:33.000 --> 00:37.000
One is the old pass app and the OSB pass.

00:37.000 --> 00:40.000
And I'm in Yan and Kotkap on here.

00:40.000 --> 00:44.000
And I'm in this second time.

00:44.000 --> 00:49.000
I come to first the first time I stay on stage.

00:49.000 --> 00:52.000
I always remember this time I see this on the stage.

00:52.000 --> 00:56.000
It's the stage. It's the same to each other. I read that first.

00:56.000 --> 00:58.000
And then I have online.

00:58.000 --> 01:01.000
Today's I'm going to talk about the Kotkap.

01:01.000 --> 01:04.000
This is the Taiwan's shared conference.

01:04.000 --> 01:06.000
It's really inspired by first.

01:06.000 --> 01:09.000
And the second part I'm going to talk about those two.

01:09.000 --> 01:11.000
One is the old pass.

01:11.000 --> 01:13.000
This is the open source event.

01:13.000 --> 01:15.000
It's press management.

01:15.000 --> 01:22.000
It will include clarification on the packaging and the old.

01:22.000 --> 01:30.400
And also the OSB pass is the open source

01:30.400 --> 01:35.000
the IP pass is unified by the applications controlled.

01:35.000 --> 01:37.960
Actually, let's hope that we will get involved in future

01:37.960 --> 01:40.640
technician, let's check out our

01:40.640 --> 01:44.560
or how I'll spend our profession or some refining.

01:44.560 --> 01:48.640
So first, introduce lab co-scab and open source

01:48.640 --> 01:49.760
in Taiwan.

01:49.760 --> 01:51.880
Actually, the co-scab is the one-all-logist

01:51.880 --> 01:54.440
largest open source community conference

01:54.440 --> 01:55.720
that's in Taiwan.

01:55.720 --> 01:58.160
They organized by a lot of volunteers

01:58.160 --> 02:03.280
by each open source community since 2006.

02:03.280 --> 02:06.120
So this year is our 20th anniversary.

02:06.120 --> 02:08.160
So this is then we have grown

02:08.160 --> 02:11.720
from the gathering about 200 people, people.

02:11.720 --> 02:14.960
And now we have over 3,000 participants.

02:14.960 --> 02:18.000
And really inspired by Boston or

02:18.000 --> 02:20.800
a customer, which I found a free entry

02:20.800 --> 02:24.400
and now residential model and making really high

02:24.400 --> 02:26.560
assessment now.

02:26.560 --> 02:31.560
But why, or past, we have this app originally,

02:32.120 --> 02:35.520
because before co-scab, we started

02:35.520 --> 02:38.920
to have, we start already the legend.

02:38.920 --> 02:40.960
You have to do that, you have to do that,

02:40.960 --> 02:42.920
you have to do that to our conference,

02:42.920 --> 02:46.160
seeing about, before we, we should,

02:46.160 --> 02:49.120
you should have a, you should have a ticket,

02:49.120 --> 02:50.360
you have to buy a ticket, buy a ticket, buy a thing,

02:50.360 --> 02:52.640
buy a thing, three, you have to buy a ticket, you have three.

02:52.640 --> 02:55.600
And we will have a long residential line

02:55.600 --> 02:57.800
in front of our doors.

02:57.800 --> 02:59.840
And everybody will be very,

02:59.840 --> 03:03.640
feel very bad experience for entertainities.

03:03.640 --> 03:06.800
So we try to have these app,

03:06.800 --> 03:09.880
this app that we can support for the,

03:09.880 --> 03:11.080
you can support now,

03:11.080 --> 03:14.960
they can, and entities can just use the unique token

03:14.960 --> 03:18.040
by the mail or spell sorting, access the event.

03:18.040 --> 03:21.360
Then they can have to self, self,

03:21.360 --> 03:25.120
they can have a self, self-checking with the,

03:25.120 --> 03:29.320
with, with, with, with this opass.

03:29.320 --> 03:32.560
And this high-�, the kind of customization

03:32.560 --> 03:35.360
in that organizer can, you just figure out,

03:35.360 --> 03:39.080
figure it using a JSON, and integrate it with our,

03:39.080 --> 03:40.600
obviously turn.

03:40.600 --> 03:44.360
And actually, as this, as this project,

03:44.360 --> 03:46.120
I am, and it's local.

03:46.120 --> 03:50.120
And in, and in, and it's local desire.

03:50.120 --> 03:52.120
And far, I used the web app,

03:52.120 --> 03:55.400
because I think this, this, this app,

03:55.400 --> 03:58.200
we, we want, we want it to run into a,

03:58.200 --> 04:00.120
over through a lot of different components.

04:00.120 --> 04:02.440
So it got a rainbow outside.

04:02.440 --> 04:04.800
And I make it do like the opass,

04:04.800 --> 04:09.000
so we, we like, like, you can smile like this.

04:09.000 --> 04:12.560
And also this is a final logo that we use that,

04:12.560 --> 04:14.880
as a logo.

04:14.880 --> 04:19.880
And actually, we, we just send a link to our website,

04:19.880 --> 04:24.320
or to, to, to, to, to, to mail, to ask everybody

04:24.320 --> 04:27.040
to just install this app.

04:27.040 --> 04:30.760
And, after it's done it app, you, inside you have some

04:30.760 --> 04:33.120
feature about a schedule announcement,

04:33.120 --> 04:36.000
and then you can have a value defining where you are.

04:36.000 --> 04:38.960
Also, we just, in high-�, we usually use the telegram.

04:38.960 --> 04:43.960
So it has a sync lock with telegram and IRC lock.

04:43.960 --> 04:46.560
And also inside, we have the boost renewal,

04:46.560 --> 04:49.760
the telemetry activity, and you can just,

04:49.760 --> 04:52.320
we can, because in high-�, we didn't realize

04:52.320 --> 04:53.320
what we talked about.

04:53.320 --> 04:56.120
So it's with the boost renewal activity,

04:56.120 --> 04:58.480
the people will live to talk with each other.

04:58.480 --> 05:01.640
And after you talk, you'll get a rewards point.

05:01.640 --> 05:03.880
And also, we have a volunteer quest.

05:03.880 --> 05:06.120
It's just, you know, like, it's just like,

05:06.120 --> 05:08.960
like, the first thing you have about here.

05:08.960 --> 05:11.520
If ever you have about here, you'll get a point

05:11.520 --> 05:14.520
with the, with the rewards activity.

05:14.520 --> 05:17.240
Once of the activity in the points, it can become,

05:17.240 --> 05:20.760
it can become a point that you can buy some

05:20.760 --> 05:23.920
souvenirs in our conference.

05:23.920 --> 05:28.920
And also, now this, previously, it's only for Coast Card.

05:28.920 --> 05:32.800
And, but now today, it's built by community.

05:32.800 --> 05:35.040
We now is open for all the community.

05:35.040 --> 05:37.600
Coast Card has developed this tool for a lot of youth

05:37.600 --> 05:39.640
and you can just see in the left side.

05:39.640 --> 05:41.400
You have a kick-kong and high-kong-type one.

05:41.400 --> 05:45.960
Also, your stick-kong-type is the high-one student,

05:45.960 --> 05:49.440
high-one student conference.

05:49.440 --> 05:52.320
Now, this project is initialized before Earth,

05:52.320 --> 05:57.520
but now you can just really, even not use

05:57.520 --> 06:00.720
any high-one artists, even internationally.

06:00.720 --> 06:04.320
And also, in this, these are the close platform

06:04.320 --> 06:07.880
to all for every, for the checking engagement.

06:07.880 --> 06:11.680
Also, we have a web one, an iOS one, an Android one.

06:11.680 --> 06:14.040
And we have a tendency to check in and visit

06:14.040 --> 06:15.800
a real-time notification.

06:15.800 --> 06:19.520
Also, we have built a event scheduling issue.

06:19.520 --> 06:23.640
And as I say, we got a game, we have a game feature inside,

06:23.640 --> 06:26.080
so a lot of the tendency to interact with the rules

06:26.080 --> 06:30.680
and underprens and returns the rewards.

06:30.680 --> 06:35.160
And first, actually, first, as the adoption

06:35.160 --> 06:37.520
I showed in first-in-charge, as a close card,

06:37.520 --> 06:40.600
now, and that in the HIKANG and the high-kong-type one

06:40.600 --> 06:43.000
and other open-source conference in Taiwan.

06:43.000 --> 06:46.360
And it's the GitHub host project.

06:46.360 --> 06:51.280
You just have to give us a much, much request,

06:51.280 --> 06:54.000
and with the suggestion, you can just add

06:54.000 --> 06:55.920
on your event inside.

06:55.920 --> 07:00.640
And now, it's available on the web led.

07:00.640 --> 07:03.320
We really invite in global contributors

07:03.320 --> 07:07.720
to help us to localize our translation.

07:07.720 --> 07:11.760
OK, then the second part is about the RNCB pass

07:11.760 --> 07:14.840
open-source conference VIP pass.

07:14.840 --> 07:17.400
It is a vacation system for open-source

07:17.400 --> 07:22.600
contributeers, open-end spatial creates in the event.

07:22.600 --> 07:27.400
And the project is divided by open-source foundation

07:27.400 --> 07:30.480
and the community to unify the contributors

07:30.480 --> 07:32.920
to the organizations.

07:32.920 --> 07:35.160
And also, it approved the contributors

07:35.160 --> 07:38.440
to receive a candidate for the entire years

07:38.440 --> 07:45.600
and get access to the multiple events.

07:45.600 --> 07:47.720
So why is the OC pass?

07:47.720 --> 07:51.760
Before in Taiwan, we lost all of the most of the event

07:51.760 --> 07:54.320
in Taiwan, you have to have together

07:54.320 --> 07:57.840
the suggestion to get inside to sign in.

07:57.840 --> 08:03.920
But each event has a lot of people

08:03.920 --> 08:05.280
want to have to go in.

08:05.280 --> 08:08.680
But Samsung, there will have a special,

08:08.680 --> 08:12.280
special entry, special ticket,

08:12.280 --> 08:15.000
that is a contributors ticket.

08:15.000 --> 08:17.200
So you will send the contributors.

08:17.200 --> 08:19.680
Everything will have to marry better

08:19.680 --> 08:22.400
by the contributors to lead to the inconsistency

08:22.400 --> 08:25.440
and the time-consuming processing.

08:25.440 --> 08:29.080
So every time, if in the areas of the contributors,

08:29.080 --> 08:31.680
you want to go into one event.

08:31.680 --> 08:38.680
They were sent the medication to lead to lead conference.

08:38.680 --> 08:41.840
And now they let OC pass podire standardized

08:41.840 --> 08:45.480
and sent a centralized review system

08:45.480 --> 08:49.520
like in our, like provide by OCF.

08:49.520 --> 08:53.320
Then provide us a bunch here inside

08:53.320 --> 08:56.520
and making the medication easier for the event.

08:56.520 --> 08:58.280
Now that they have it, because this project

08:58.280 --> 09:01.880
is the same as 2000 and 19,

09:01.880 --> 09:06.120
and it's open over 600 application contributors

09:06.120 --> 09:08.240
has had been processed.

09:09.560 --> 09:13.840
But actually, we just finalized and helped a lot

09:13.840 --> 09:16.760
of conference to deal with the,

09:16.760 --> 09:19.240
to verify their contributors,

09:19.240 --> 09:21.440
but we just finalized some problem.

09:21.440 --> 09:24.640
Actually, it's really, really easy in the beginning

09:24.640 --> 09:26.720
because everybody, every conference,

09:26.720 --> 09:29.480
they say, they can have the help to help others,

09:29.480 --> 09:30.800
help each others.

09:30.800 --> 09:34.320
And by the same, the 2000 and 2022,

09:34.320 --> 09:36.640
you have become the most of the entities

09:36.640 --> 09:39.320
to most of our contributors,

09:39.320 --> 09:43.200
come inside, but they get down just soon.

09:43.200 --> 09:47.480
And scaling the entry, which I'll find out the challenges

09:47.480 --> 09:49.680
that you're scaling the declaration

09:49.680 --> 09:54.440
to ensure the fairness while you deal with the administrative,

09:54.440 --> 09:56.080
it's really a workload.

09:56.080 --> 09:58.320
And it's forming the specialized publication

09:58.320 --> 10:02.280
to the different technical fields based on the feedback

10:02.280 --> 10:05.040
from other partners event.

10:05.040 --> 10:07.760
And we want to let we can expand

10:07.760 --> 10:10.760
the beyond open source comments to collaborate

10:10.760 --> 10:13.360
with the tech and the commercial event.

10:13.360 --> 10:15.880
This is what is our event now.

10:15.880 --> 10:21.880
And so in the last week, we are acting as anybody

10:21.880 --> 10:25.640
to get involved, you're invited to contribute

10:25.640 --> 10:29.240
to our project, or past, and the OECP has

10:29.240 --> 10:33.120
a big hit GitHub, the server, and the designer,

10:33.120 --> 10:34.920
and the translator, our well-come.

10:34.920 --> 10:37.400
And also, OPPAS now is our website.

10:37.400 --> 10:39.400
You can just give, you can get in.

10:39.400 --> 10:41.800
And also, you can maybe you can have test the tool

10:41.800 --> 10:44.240
and you're in the OECP and get in best,

10:44.240 --> 10:47.720
give us a lot of feedback to help to involve that.

10:47.720 --> 10:48.760
OK, thank you.

10:48.760 --> 10:49.760
Thank you, everybody.

10:49.760 --> 10:57.600
APPLAUSE

10:57.600 --> 10:58.600
Any questions?

11:07.200 --> 11:11.840
You said the first pass is used by the international conference

11:11.840 --> 11:19.120
and which means is there any conference outside of the Taiwan?

11:19.120 --> 11:28.560
Uh, actually, now we, no, actually, no.

11:28.560 --> 11:32.080
But in some international conference in Taiwan,

11:32.080 --> 11:33.760
you said that he can't?

11:33.760 --> 11:34.560
Yeah.

11:34.560 --> 11:35.080
I see.

11:35.080 --> 11:36.080
Thank you.

11:38.880 --> 11:39.680
Other questions?

11:41.840 --> 11:46.840
OK, thank you very much, please.

11:46.840 --> 11:47.840
OK.

11:47.840 --> 11:50.840
APPLAUSE