KubeEdge Community, 30 Sep 2020

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: KubeEdge Community Meeting 20200930 (Europe Time)

Description

https://github.com/kubeedge

A

Okay, uh the recordings hello, everyone welcome to the cuvees community meeting today is september the 3rd. It's your friendly time. This.

B

A

Please everyone on the meeting. Add your name to the attendees section.

A

Let me also I'm sure.

C

Turn the link to the chat window.

C

A

D

First of all,.

A

Let's go through the, um let me go through the future.

E

Development status.

E

A

Support exec to the edge, so this one we already have the uh implementation for request and sims still.

C

A

C

B

F

Yeah, I think maybe we need to add some e3 tests in this.

E

B

A

All right, um the k get me get data.

E

A

G

F

D

F

A

All right, um this one is still on the intuition, probably one more week.

A

Still didn't see the proposal submitted so.

B

We probably need to do.

F

More work, otherwise.

C

A

C

Post about this.

H

Okay, release process.

A

Improvement, any updates on.

B

E

A

A

This one, I think so it's also okay. Next one uh support this watch from majorcore any.

C

A

D

E

H

A

A

All right, so this one is still 100 division, but at this moment we need to reveal comments as input to finalize the details of the implementation.

A

And next one clear mean reset page.

D

Actually, uh y'all review. Okay.

A

So this one I.

C

Think yeah, it's still under review. Probably we need more spend more time.

A

And next website website upgrade should have a demo demo website online.

A

But there are still some stunning things new to be.

B

A

Okay, so this is the new design about the our website.

A

So the most important thing is that we added the version section once we finished the moving the government to the website repo, we can enable users switching between different versions of cuba, release and that's much more friendly for checking the document content.

A

C

A

There are still some styling things.

A

Okay, so we will have case studies.

A

And updates about community events and also the patented section and also footer and for the community, we will have the dedicated partner page. So we will invite more uh member organizations.

C

A

The partner, but the styling is not yet finalized.

A

A

A

A

uh So the blogs, so the details page, are not yet updated.

A

Okay, uh that's brief about the uh website updates. uh We still need maybe one more week to finish the study and.

A

A

Okay, uh the data pipelines, one expanding motorbike mapper go implementation. Any updates on this.

A

Okay, it looks like uh tramway is not online.

A

A

A

Okay, this one, we need a review on the.

A

Proposal here, the main store this one is also under reveal.

A

It looks like this.

H

A

And maybe we we can have some breakout the review meeting on the uh in the community, so we can uh have our reviewers and the approvers spend some dedicated time on reviewing the uh request.

A

Okay test the test devices: this is a launch and fix download service file. This one I saw I could pull requests through it.

A

Any updates on.

D

A

Service, so this one is waiting for another one to accept it.

A

Okay, add the option package path. This one is a new one right.

H

C

A

Okay, next one option to the uh cleared me updates on this.

A

Oh, this one is uh okay. This one is waiting for dia, another pro requester to accept it um next, one device namespace support.

D

D

F

A

A

All right uh next, one update to 119 so looks like this one is still painting. I didn't see the poor request yet.

A

Okay, next one introduce kubernetes original end-to-end test.

A

This is a a new task started this week, so actually uh taisha have updated me that he has run uh first around and that they got some initial results and he's still under looking into the details.

A

We'll probably share the result. Next, the time.

A

So, okay, uh that's all about the uh release! Updates!

A

Let's go back to the agenda anything anymore. Would you like to discuss.

H

A

A

D

D

D

A

A

A

A

A

A

A

A

A

B

H

F

A

A

D

D

A

A

A

C

C

C

D

Congratulations.

A

B

F

You wouldn't mess.

D

D

A

G

A

H

A

A

A

A

E

A

B

A

A

A

A

A

All right, so we need.

G

We actually need to.

A

Open this open a discussion thread or start vote, prioritizing the roadmap and after the roadmap document for the items to do uh just to refresh.

A

uh For cleavage, currently, we think that we need improvement.

C

A

Networking capabilities, for example, provide the cross-subnet communication. This one is already in our release plan but started, and we need to uh verify the using my plugin implementations.

A

uh Integrations with two page, and probably we need some.

C

Fixes in the underlying implementation.

A

And also for the device we need, we already identified that other discussion in the community is that we need to refresh the mapper implementation, for example, motorbox, bluetooth.

A

Wifi, this one, these implementations will be located in a new repository instead of the memory, and we also need to.

A

Keep improving the device uh best management framework.

A

And also for the uh data pipeline integration on the edge, and we need to provide a member called skeleton which makes it easier for new developers to develop code, new mapper implementations for the mec. We actually do need a more discussion. Currently, apparently, the missing member did just recently have some new material to share.

A

I think we can invite them to the next time to share latest updates, and then we can identify what to do what to especially what to develop in the in the community and another one is ai on the age. So this one, the obvious things we can do is that we can verify mainstream ai frameworks running on the edge.

C

I think we can just say.

A

And also for the big data things we can verify spark flink running on age and also uh actually another thing uh already being under discussion that how to make the ai applications on the agenda in the cloud coordinated together.

A

For a security thing, we actually have a long-term thing on our roadmap, but now you started is that integrated with spiffy or spire to to achieve.

A

Kind of decentralized authorized, authentication and authorization so make the applications easy to to achieve security, especially when they are disconnected to the club.

A

And so wrestler 4 rested things are more relevant to the project healthy. We need to improve cold quality reflect also reflect some of the uh all the implementation and do some cleanup.

A

So this one uh there have been a lot of detailed discussion on different points for now. I think it's time to collect all the ideas together and set up plan what to do first, like that, and we can also invite more people joining this and another big thing we need to continue work on is that uh to improve the test coverage.

A

And for the data document improvement, we need to move content to the website report. This one is not yet done already on our plan and we need uh invite more people joining the internationalization for more language and also uh we need to improve, continue, improve the document. Content.

A

And for the contributor experience we, we just started trying to host the above configurations on the bot configurations on github.

A

We still need to do more work to also host like, for example, slack, configs, github, and also we need to enforce the uh automated uh config apply for for these things. Okay, that's a brief about the road map.

A

Any other things to.

A

A

H

A

All right, um if not maybe we can end the meeting a few minutes earlier today,.

A

So the next time would be.

A

Actually I have a question about the next meeting, so uh so the october 7th is on vacation in china, and many of our contributors are would be other four office right. So maybe we can skip the next meeting and make it next week I mean one week.

A

A

A

A

All right, uh if no other things to discuss well, I think we can end the meeting today.

A

Thank you all for joining the community meeting and hope you all enjoyed the vacation so see you until next time we we're going to skip the october 7th uh community meeting, so the next one will be october, the uh 14th it will be still uh europe-friendly time next. One, okay, thank.

H