みなさんこんにちは、私はケイチョウミチですNECです。今日はチャレンジ、ペネフィッス、ファン、オープンソースのコントリビューションを紹介します。まず、NECでオープンソースのコントリビューションを紹介します。NECはオープンソースエコシステムをコントリビューしています。20年間、クーバーネティス、リナックス、ハイパーレッジャー、オープンスタック、 etc。例えば、この左側のコントリビューションは、クーバーネティス1.18のデベロクメントと、NEC-9のコントリビューションです。この右側のコントリビューションは、オープンスタックバージョン、ビクトリア、NEC-5のオープンソースのコントリビューションです。今日はオープンソースのコントリビューションを紹介します。今日はオープンソースのコントリビューションを紹介します。このコントリビューションは、NEC-1のオープンソースエコシステムのコントリビューションです。今日はNEC-1のパネルディスカッションパネルリースです。モトキさん、お会いしましょう。こんにちは。モトキさんです。オープンソースエコシステムのオープンソースタックバージョンは、10年から始まります。コーデベロッパーのコーデベロッパーのアクセルアプロジェクトが、ネットワークリングプロジェクトと、ライズンGiプロジェクトが、プロジェクトのテクニカルリードを、ライズンが、去年に行っています。A-1のオープンソースエコシステムは、NEC-1のオープンソースエコシステムで、全国的ではオープンソースエコシステムで、プロジェクトというクラウドアキテクトのアクセル説明を行います。この歴史を動かすコーデベロッパーたくさんのアクセルのコーデベロッパーです。ここでいらっしゃいます。ありがとうございます。モトキさん、お会いしましょう。みなさん、お会いしましょう。I work in OpenStack community for around six years in upstream and before upstream things like around one or two years on the support side.In OpenStack I'm a technical committee member since I think two years and I also served as a QAPTL for two years.Also a core member in NOAA, QA and various other projects.My main focus in OpenStack along with technical membership responsibility is quality assurance and the API stability.And having such a good community motivates me to contribute more and more in that.And thanks for having me here.Thank you, Ma-san.So next, Horiguchi-san, please.Yes, thank you for invitation.I'm now in Horiguchi, a senior software engineer working for NEC solution innovators.I'm living in Tokyo.I'm working for more than 10 years with OSS community.I'm joining two major OSS community.One is a Linux kernel community since 2009.And Hypervisor community since 2016.In Linux kernel community I have a role of kernel mentor.I'm one of the subsystem internal memory management system.My responsibility is to maintain memory error handling code.I'm usually writing patches and reviewing, testing, discussing of submitted patches.And sometimes I contribute to memory optimization features like huge page and memory compaction,meditable processing.In Hypervisor community I also download some.Patch contribution from Hypervisor Fabric related to tools.And I have a new contribution.I have a few contribution translating Fabric document to Japanese.My main focus on Hypervisor community is to develop and implement MIMBFT consensus algorithmwith Byzantine Fortress.This project is running as Hypervisor Lab project.That's an experimental small project and Hypervisor.Next meet you.Thank you.Next, Muto-san, please.Okay.Hi.I'm Shuu Muto.I'm working on platform solution division in NEC solution innovators.Since 2015, I have started to contribute to OpenStack Dashboard and several related projects.I had created some plug-in projects for Dashboard and maintained them.Then since 2018, I started to contribute to Kubernetes Dashboard and became one of container for it.Also, we run Kubernetes upstream training at some community events in Japan.Thank you.Thank you, Muto-san.Next, Mori-san, please.Hi.I'm Uiko Mori from NEC solution innovators.I'm working for Kubernetes for about one year.Previously, I was working for OpenStack for about three or four years.Sorry.Thank you.That's all.Thank you, Mori-san.Today, I'm run as a moderator.I'm Kenichi Omichi from NEC also.I'm developing Kubernetes and the development tool Kube Spray in the community.I worked for OpenStack also before.And maybe 10 or more years ago, I worked for Linux kernel, which is a crush dump tool.So, we will have some discussion in this member.Let's get started.So, first topic is first the most hard or difficult challenge of OpenStack or OpenSource contribution.First of all, I'd like to ask this question to Motoki-san.Do you have any idea related to most difficult thing for OpenSource contribution?Yeah.I see several challenging point in OpenSource contribution.First thing I see is OpenSource culture.The next one is communication in technically.But in my personal experience, I didn't have difficulty in these areas.Luckily, it is lucky enough.The other point I see is language and time zones.I'm not a native English speaker.I had no chance to use English regularly before joining the community.So, it is a big challenge to me.Another thing is time zone.I live in Japan, most communication happens in US or European time zone when I joined the community.I see these challenges.That's difficulty comes from OpenStack, right?Yeah.It's my experience from OpenStack.But I think it is common in many OpenSource projects.OK.So, I'd like to ask this question to Horiguchi-san.You have joined two communities.Do you face this kind of issue or difficulty?Yes.First difficulty is finding time.Before starting contributing to the community,I was a full-time contributor for the X-CANNEL.But I'm not now because I joined two communities.I have some roles in the hybridized community.That's an internal project.I'm just getting busier.I have to spend time and effort to complete some meaningful work.Sometimes, because it's a lack of time.So, I'm feeling that task management and information sharing is critical to work with.Another difficulty is complexity.X-CANNEL is also a very big and complicated project.Hyperagin is also rapidly growing and becoming complicated.My feeling is that the problem I try to solve is getting harder and harder.It used to be years ago.So, improving some tools and automated testing is very important.That seems like technical difficulty.Not cultural difficulty.You didn't face some communication issues.These two communities are very different cultures and using different tools.X-CANNEL is still using mailing lists to discuss.Hyperagin is using GitHub or CI or everything.Modern technologies for development.So, it's very difficult and different.Okay.X-CANNEL itself developed with old-fashioned way.With email.Thank you.Mori-san, do you face some difficulty to join Open Source community?What I feel difficult is basically Open Source developers are contributing as volunteers.Usually, there is a fixed schedule.We must finish one thing by fixed schedule.Other members in other companies doesn't have this schedule.We cannot finish our work until fixed schedule.A few years ago, I was working for OpenStack.I was developing one feature.It was a little bit important for our company.I promised with my boss I would implement this feature in this cycle.But we couldn't finish it until in the cycle.Then, I was a little bit...I got scolded by my boss so that what I learned from this isI cannot promise with my boss.Yeah, I can finish it until this schedule.Okay.We are working both things.One is Open Source community and another is a company.Those companies are so different.In our company, we have some concrete schedule for development.It is difficult to make consensus to make some specific schedule.Mori-san, you are running as a technical member in OpenStack.You have some idea or something to collaborate with many people from different companies.So, how to solve this kind of thing in the technical community?I think that's a very important point from Open Source point of view.Because in Open Source, any project, you don't have a defined number of contributors.Sometimes, you have a very large number of contributors in your project.Sometimes, you have very fewer contributors.Both have their own drawback.Because if you have a very large number of contributors, it's very difficult to get the consensus.It may take time to get the final decision on what the design or implementation should be.And if you have a fewer contributors, as Mori-san mentioned,you don't find enough developers to review your code or you don't find experts to review your code and merge.So, that's one of the big things in that you cannot promise or you cannot define the exact thing that lies to be merged in Open Source.One way to overcome is like in Open Source, it is like even take things.So, you review others' code, they review your code.So, you need to spend also like more times on getting other things, other code merged.Have the calibration with them, have a good relationship, building the trust there.So that whenever the features or code you are proposing, that can get the good review.And within that cycle time zone.From technical committee perspective, it is difficult to like force any technical decision on project side.Because all the technical debates, what feature has to be merged on what time is all project specific decisions.So, technical committee try to check the health check of each project in OpenStack.If there are very less contributor in any project, features are not getting merged.So, that time we try to help them.We try to publish that issue in the mailing list, newsletters so that other developers can come in and help there.So that way, some extent we can solve it.Okay, we are facing some less contributors.You are sending email to get more volunteer from different project or something.Yes, especially from the users.If any of the company has or using that project in their solution or in their product.So, they can at least check okay, there are some less contributor things happening in this project.There are no maintainer in this project.For example, last couple of cycle, we are getting one or two project having no maintainer.So, we publish it as a retirement of that project.So, that is a good indication or notification to the users.Okay, if you are like making money of this project using that project in your product.It's the time you have to come up and help in upstream contribution.I see.Thank you, Manzo.How about Muto san?Do you face any issue for joining open source community?English conversation is most difficult things for me.My TOIC score was around 400.So, it's very hard to communicate in English.And I tended to fear about foreigners who talks English fluently.But I found the most contributors volunteer at OSS community.So, I found they are very, very kind human.So, I don't need to fear about communicating with them.That difficulty is English conversation.But it's not so fearful of things.And at first,I found Asian contributors who use easier English like me.Chinese or Korean contributors.They look similar to Japanese.So, I don't have to be so nervous.I feel the same.It's not easy to overcome language difficulty directly.But I think it is important to be a barrier contributor in the communities.Once we are recognized, we can mitigate these gaps.We are software engineers.Once we honor each other, we hear or propose a video with respect.That's how I felt in the community.I see.So, one I face difficulty is how to make consensus in the community.So, sometimes in a relaxed community,as Horiguchi-san said,we are using e-mail for communication too.But on the open stack,we are using IRC chat or face-to-face discussion in some events.Technical thing for technical thing.And in Kubernetes,we are using a Slack.S Slack for daily communication.And we are using Zoom for weekly meeting.So, that kind of thing is always hard for ESL guy like us.So, actually,my interest is how to make a consensus.What is the most important communication way for each community?Horiguchi-san,FAT is the most important making fiction way in Linux and Hyper-leisure.In Linux,most technical decision is made by a manager.And some community-wide big decision are face-to-face conference.In conference.Maybe voting.And in Hyper-leisure community,they also use Slack,locate chat, IRC,mailing list,and there is a technical setting committee.So, maybe just have 15 members.They are discussing and making decision over community thing.Thank you.But at this time,we are facing COVID-19 issue.And it is difficult to make face-to-face conference at this time.So, how to make such decision in Linux community at this time?I don't know.Maybe email.Just email.And Hyper-leisure communityalso uses Zoom meeting by weekly basis.Nice.Thank you.So, how about in OpenStack community?How to make big decision?How to make a big decision?What is the most important communication tool for maker decision in OpenStack?Nan-san?So, in OpenStack,even with the COVID thing,we have the PTZ called Project Team Gathering,where we do the design discussion and all.So, it's happening virtually also.And it's not so much effective as it used to be physicallybecause you see the people and have the discussion.But at some extent,we are able to conduct virtual discussions.Like within one week,everyone gathers and we have the schedules for every project.And we discuss the design things for the next cycles.So, that is the one thing.And other thing we do with more excellent conus way.Like we have the specification model for each project.Where if you have any idea or if you have any new feature proposal.So, we discuss it like,okay, this is a good idea.And now let's go with the more design discussionand implementation detail.So, you can submit the spec.And on the spec which happens in the Garrett review tool.And there you can start discussing the designand implementation detail and the consensus.I see.Thank you, Man-san.So, the time comes for finishing this topic.So, the difficulty we are facing,we faced before is,one is the culture gap between company and community.It is hard to make a concrete schedule.So, we needed to discuss or make,get an understanding from our boss in my company,his company.And another thing is hard to communicate in Englishas the ESL guy.But the committee member is mostly a good guy.So, we don't need to feel fear here at all.And another thing is,sorry.So, we needed to make a suitable communication wayfor each committee.That is very important.So, that is great advice for us.So, let's go to the next topic.So, we are,actually we are company guys.We are working for community,but we are working for company also.So, how to open source contribution workfor company benefit?So, I'd like to ask this question forOriguchi-san first.Yes.I have some for company benefit.So, company sends engineers to OSS community.So, simply to get easy access to technical business community.So, I think that clear benefit is thatif you join OSS community,you can directly solve your problem on community.If you don't have any access to OSS community,you might have to wait someone to find and solve it.That's not realistic because it takes long.The fix submitted might not be what you want.What you really want.And another benefit is thatConnection to OSS committee helps your companyimprove quality of service and support.So, I think that company benefit.Yes, that's good point.Actually, maybe if we want to do something,we need to create something.Yes, that's right.Okay, do you have any idea for this topic,Muto-san?Yes.For example,I think experiences in the communitysuch as using new toolsor new methodologiesor new architecturesand knowing new point of view, etc.So,finally, we will be able to create a new idea.Actually, these experiences in OSS communityare always fresh for me.And this gives me a lot of good stimulatesand the stimulates motivate me for next walk.So, bringing something newor motivation back to companyis the value, I think.Thank you.Do you have any idea,Mori-san?I think there are two big benefits.One is cost feature.So, we can decrease development costby pushing a patch to upstreamnot having other private patch.And another big benefit for our companyis about security issue, right?So, we can...You know, when there is weakness in open source,for example, a few years ago,heart bleed occurred in open SSL project, right?So,when the security issue occurs in open source,if we have private patch in our company,then new version will be released for supporting weakness.It's difficult to version up to the latest one.That's all.Yeah, I see.That is very important point.So, actually, open source softwareis growing always,open source is developed always,and the code itself is always changing.So, if we have some private code,it is so hard to apply those private codeinto the greatest code of open source.That is very important point for company viewpoint.How about...Do you have any ideafor this topic,Mori-san?I think several topics are already covered.I see other two points.One is similar to what we discussed so far.It is to bridge upstream developer and real project.We upstream developer are familiar withwhat is happening in the upstream development.So, we can advise the real projectmaking the real direction.We can advise the direction to real project.We can also implement new feature and fix bugbased on real project needs.It will be our advantage when working with customers.The other point I see isto improve the corporate branding.Recently, our customers check our activitiesin open source communities.So, active involvement in the communitybrings good reputation andit leads to the best chances,I think.That's what I see.Okay.I see.How about Man-san?Do you have any idea?Do you want to add more things?So, along with what we discussed,it also helps avoiding the vendor lock insbecause in open source there is no vendorspecific things are there.So, you get the software where you can build the productand you can avoid the vendor lock in.In the current market,it's a timewhere people get more feasibilityor you can say more interoperability,not just the vendor specific thingsbecause sometimes they can move the hardware alsosometimes they can move the software also.So, having such a product which doesn't have any vendor lock inalways helps the company to sell their product.Second is the quality side alsobecause in open source community,it's not just the developersbut operators,provider,and users,they also participate.So, they lock the bug,they share their use case,they test the things and tell you likethis is not working as expected in this scenario or something.So, sharing these kind of knowledge in open sourcegives you the better quality product,qualitysoftware,which you can use in your company to make the product.So, that also very important point in that.And one of the also best thing isit's already discussed,it provided less development costbecause you don't need,it's not just developerbut tooling,development,tooling,infrastructurein open source,it's free,right?It doesn't need to spend much price salesor the money on the development tools or infrastructure.So, that is also one of the important part.Yeah, right.So, actually it is so hard to developopen stock or Kubernetes from scratch by our company.So, it is great to share our cost in the communityand it is better to implementour necessary features or quality in the community.Yeah, that is important thing.So, thank you.That time is coming for next topic.Next topic isFat is the most fan thing of open source contribution.I'd like to ask this question for Mori-san.Fat, please.I recommend other guysabout this first.Okay.So, Mori-san,please.Yeah, I think the fun part,one of the best thing personally I think isyou learn about the different culturesbecause in closed source wherever you workone country,one companyor it can involve more than one country developersbut in open source you see it's more than50-60 country's developers you can meetyou can talk to themyou can learn their cultureyou travel also in some of the physical eventsso that actually grow yourself alsonot just technical thingpersonality development also it really helpswhich is my personal experience alsoand technical term if you seeI think open source is one of the bestopportunity for any developersbecause you have very great skill developersacross the world and you get the chance to work with themso you can learn continuously learnunlimited thing from themand the best thing for any developer can happenwhich I thinkI see but that is interestingso one thing Motoki-san saidyou are working for both company internal projector company internal projectand open source projectso then you can get to knowthe requirement from actual projectto open source communityso that actuallythis kind of thing make you busybecause you are workingdifferent time zone in the communitybut maybe something you are motivatedsome fancy motivate you toattend community alwaysso what is your motivationyeahI thinkit isgood time to implementbased on the real needsbutwhat I feel in the communitymost iscollaboration is big thingeveryone has different skillsknowledge,experience,cultureand so onbut we work for the same goaland build software togetherwein addition,everyone has different needsso some companieslike to implement some featuresbutanother company has totally differentimplement totally different thingsthat's very interestingwe encourage each otherand it motivates me a lotI believeit is a communityand it is really nicethat's good pointI'm not surewhat is your motivationthank youone unique skill is likehe doesn't sleepwhether you are paying him,he replyso that's very goodpreviously it workedbutI'm no longer youngso I cannot do itnowhow about Horiguchi-sando you have any questionsyes I have a few ideasfrom a relaxed perspectivemy favorite thing is impact on the worldI am a memory managementsubstitutedthat's a core part of the kernelso if I contribute some codethat's used by millions of serversand devices all over the worldand that's exciting and encouraging for meand from a high-paragraph perspectiveit's just fun to me to get familiar withgrpcand security featureinter-cgxso these are very new to meso very excitingHoriguchi-sanyou are still working for the post-committeethe high-paragraph nature,right?yesby collaboratingboth committeestechnical thingsactually these two committees are very farso no overlap technologybut some development toolslike Git is used by both committeesand OSS committeehow OSS committee works is similarso I can use some knowledgefrom the relaxed kernel communityto high-paragraphnuto-sando you have any fancy in your experience?from meI already saidvarious experiences are valueand so it's alsofun thingsand as generallyin TV advertisingfrom construction industrythey told workthat remains on the mapsI think OSS contribution issuch kind of work for software developerand our childrenchildren would be able to find my workon the internetas a developerand as a fatherI proud such work a littleand this yearGid have had stored our contributionsat Arctic Islandat Arctic Islandandwe all may havearctic code or boldcontributor on Gid haveourcontribution is forever1000 years1000 yearsbeen a body proudokso I'm waiting for Moisaquick answermoisa pleasemy fun thingit's not majorlittle bit minor I thinkbut what I feel fun isopen source isnew conceptopen source business strategyis not clear and very difficult to decideit's a big challenge for usandwe can learn other big companies workholding the worldin our companywe develop ourselvescan discuss open source strategyand it's usuallywe cannot do it in usual projectit'sperhaps just in my caseyeah so mine is notmajor conceptat the end of this sessionmuto-san explainkubanex upstream training in Japanmuto-san please introduce itokwe have heard kubanex upstream trainingin Japan these yearsat cloud native days Tokyoor okinawa open daysand kubefest Tokyowe introduce how to startcontribute to kubanex communitysuch ashow to sign up c-areahow to create patcheshow to communicate with other developersetc.this year after covid-19we held them in virtualwe havepreseed the links in this sessiondescriptionalso we willannounce for new schedule hereplease check it, thank youthat's all todaythank you so much for watching this sessionand we hope you enjoy this session todaybyebye