my name is Mata Hirono Datetoday, what I'd like to talk about is a historya history of enterprises with the NUXNUX IDEA你们が本質技術の方法を見てみましたthat started as a hobbybut now he's being used in many products私は主人公の仕事についてお話しします。今日、私は私の歴史についてお話しします。ここはディスクレーマーです。そしてここは私の経験です。でも、私はあなたにとっても重要ではありません。今日のテーマは、私の話をお話しします。あなたが彼のヘノメナムのスプレットの開発のソフトウェアを説明しています。私はここに2本の説明を説明します。1本はオープニロベーションです。2本はオジノミックスです。1980年に、スペリアのオープニロベーションとインベンテーションが、ヘノメナムのエンバルメントをクリエイティティとして、クリエイティのレーシング stable をし、フランのクリエイティのレーシング stableをスペリアのレーシングしています。2本の説明を説明しています。これは、、フランのエンバルメントをクリエイティティにして、オープニロベーションについても、とても素晴らしい例。エルクラサイペディアスは非常に便利です。家族や家族が使われています。でも、毎日ウィキペディアを使うことができます。ウィキペディアは10,000人の人たちの世界を作っています。ウィキペディアの文化を使っています。この文化があると、タプスコットについてウィキペディアの文化はオープニエス、キャリン、シェリン、アクティング、グローバーを使っています。ウィキペディアの文化はギナックスコミュニティを使っています。この文化はギナックスコミュニティを使っています。しかし、ギナックスコミュニティを使っています。新たなデブログメンバーやゴールドマイニンスサーチを紹介します。オープンマスコロボレーションを新たなデブログメンバーを作っています。ギナックスコミュニティを使っています。ギナックスコミュニティを使っています。ミニックスワーキンググループやギナックスコミュニティを使っています。25年4月1991年その時にタネンバーを使っています。ミニックスは一つの方法でオブレディンシステムを使っています。しかし、オープンマスコロボレーションを使っています。その時、オープンマスコロボレーションを使っています。数週間、デブログメンバーやギナックスコミュニティを使っています。1994年にインターネットが推薦されています。しかし、オープンマスコロボレーションを使っています。インターネットに関してアプローチを行っています。2つのイベントを追加しています。ステップンストーンです。ルイスラスナーがIBMの CEOです。IBMの外側から初めてのイベントを行っています。初めてのイベントを行っています。イベントがIBMの外側からインターネットやオープンスターを使っています。プロプライアティのロクゼンストラテジーを使っています。2000年にアナウンスターを行っています。IBMのコンパニーは1ビリオンで1ビリオンで1ビリオンで訪れるのが今寄り添えます。これがこのメッセージを言います。今の通りIBMは新たにヤシ料理してDNXを作業します。DNXのロクゼンストラテジーはIBMの中央を訪れることができます。Software Business Unit is one of the most important and valuable business units that generate about 30% of net income and provide the foundation of their service business.I remember I spent PC server business and some servers like A400 or OS2 were eroded by windows. Besides windows eroded, they are middleware.When windows was introduced, customer chose SQL server instead of DB2 for DBMS and they adopted IIS instead of WebSphere for application server.So, IBM specific strategy is they put LAN relux on their all servers including mainframe and on top of them they install their middleware with relux.So, that IBM has established FSD Free Standard Group to create the standardized Linux API.LSB defined standardized API and it's complied with by learning certification kit.LSB defined standard API for Linux. I was amazed at seeing the success of LSB. At that time there was a rumor like community believed innovation was more important than compatibility.But, let heart to them and even not the community supported LSB.Then, IBM started Cheap Hopper Program. Cheap Hopping means software applications that compliant LSB. They ensured to run it on every IBM server with relux.And, IBM started enhancement of Linux in order for Linux to achieve the requirement for the high end server.So, that they created data center Linux working group at OSDR.One of the pioneer company in terms of promotion Linux is Intel.When Intel visited telecom companies in Europe to promote their PC server, namely Windows server,then they are told like we are happy with Park Slice.Pc server is good enough in terms of performance but Windows is not good enough in terms of functionality for us.Linux is much closer to the goal but still some features are missing.Then, Intel thought if such features were update, they adopt Intel server.So, they started carrier grade relux working group at OSDR.Oracle impacted some server vendors regarding Linux.In 1996,Oracle decided like from now on, we only support 5 platforms.5 platforms are Spark Service,HPX, IBM AX,Windows,Deck Clinics.So, other vendors like Japanese vendors,Pyramid,DG,they had to decide to withdraw their own units.Because customer didn't buy on which they couldn't run Oracle products.Linux became the only OS that they can deliver and develop the functions that customer requested.Oracle itself started investment for Linux.The step stone was the TBCC benchmark.There is benchmarks in a TBCC that compete for transaction processing performance per cost.At that time,Oracle couldn't win against SQL server with Windows.So,Larielison,CO of Oracle,asked engineering department.Isn'tOracle the best DBMS in the world?Is it?Engineering department did right.Microsoft use the compiler that had a special optimization function for SQL server.And they use authorization path.Authorization path are specific dedicated faster path just for OS.And it is on set.So,you are saying that if don't have OS,we cannot win the benchmark.Is that so?Engineering department said.Let's tune up Linux in order for Oracle to achieve higher performance.Then,they started invention.So,they changed difference platform from Spark service to Red Hat Enterprise Redux.And in 2007,they produced Oracle Enterprise Redux from Red Hat Enterprise Redux.Then,they companies started young development.Developers and their managers were confused because there are differences in terms of development methodwithin the companies and in the community.CGL asked community to develop the requirement from the district app from the telecom market.But,communities replied like,you are not.Ah,sorry.We are not your slaves.If you want something in Linux,use to develop them by yourselves.And you can continue to use Spark service.After that,CGL dropped some functions and provided source code for their remain functions.And community replied.If you want some function in Linux,you have to discuss with maintenance at a community.And work together,develop further in a community according to the community way.And they received some critical comment like,you are proposed real time scheduler is too strict.So that it has a strong side effects.So,it's not so appropriate for general purpose.They are requirement and accepted almost at all.Eventually,called Montabista,invested by Intel,started to develop CGL functions in Linux.That was focused from upstream.So,Montabista shipped,delivered carrier-grade Linux,apart from upstream.I mean,started porting Linux on their old servers,including mainframe according to their strategy.But,at that time,mainframe,the modern 10-much processors,and last enhancement.Enhancement teachers,Lux is still in adequate for mainframe.So,I will recommend it,running Linux on VM,virtual machine,GVM.And they started enhancement for multi-processor or hardware loss.In order to learn,application was software effectively on a multi-processor.We need a lightweight process,thread.That can share memory in a process.But,there is a problem.Because,other threads may rewrite the contents of memory,without permission.Especially like,library,that written just for the conventional process.So,in order for libraries to be made thread-self,we have to provide mutex control functions for libraries.It took a long time to be discussed,and to be considered between IBM engineers and committee engineers.Because,there are two ways,IBM implementation and committee implementation.Finally,community implementation was accepted.During hardware loss enhancement,we need a layer that separates logical one and physical one.Like,virtual memory and real memory.Or,logical volume manager and physical volume.To enhance loss feature for disks,we have to provide logical volume manager.Like,read implementation.You know,read guy.Slowly,IBM discussed,developed such function internally at IBM.And,they provided large source code to community.But,community first refused it,because it's too ready to be reviewed or to be discussed.IBM banned internal communication.So,engineer had to have a communication just with the community.And,they restarted from a small chunk of source code.And,goodly,increasing.Finally,community adopted,logical volume manager.Like,yeah,developed,and their manager had a lot of problems.Again,because of the difference between their deployment method and community one.And,they adopted it.What are four models?Functional specifications are defined.And,according to them,test plan was compared.And,test result report is compared.And,quality is evaluated.Then,development complete.It's like defined in ISO 9000,internal standard.But,we have no choice but to adopt the community way at community.So,even I had a severe problems.Like,first people,my boss,asked me,like,show me the roadmap of Linux.Show me the functions,specifications that are promised to deliver to the application development team.Again,if we want to have some functions in Linux,we have no choice but to work with them together.So,often,we couldn't persuade community way to the upper manager or sales people.Then,many focused version were created,especially in an embedded day.So,important thing is,community members are not made up of only particular company's employee.Therefore,their manager cannot manage their development without having a win-and-win relationship.And,to collaborate with them.We cannot go forward,right?So,to do so,I'd like to introduce two examples that I explained.We created do-and-don't list with IBM engineers.Like,start to contribute with small patches,other than big chunk of source code.And,like,don't demand patch adoption by saying,it is already in Solaris,and other major vendors also.That's a really,prohibited,hopeful influence,in a community.She's here,became a Linux distribution.But,without eyes,we support.Because,they couldn't catch up with the upstream.And,even now,it caused some incompatibility with upstream.Let's start through the continue,or continue to develop under or based on upstream first policy.I'd like to introduce some activity in Japan.As you can see,there is a huge Pacific Ocean between United States and Japan.So,there are many barriers,like distance,time difference,and languages.So,engineers' complains or dissatisfactions were piled up.Like,we couldn't have any responses.No matter how many emails I sent to Khan and Merlin list.So,we set up the meeting between Japanese vendors.And,next,main maintenance,to discuss a couple of issues,like,drivers' issues,dissource managers,and last features.When,we discuss the topics in Japan,like,something like this.If,they provide driver's API,like,DDI driver,device driver,interface driver.For Solaris,or VKI for Windows.We don't need to provide source code.In Japan,Dinox is still minor orders.But,they request it.You have to read source code,you develop drivers,and you have to provide source code.But,we are porting drivers from the Solaris or Windows.If,they continue such an absurd request,Dinox never becomes major orders in Japan.Please tell them to provide drivers'compatible API with Solaris.Of course,I couldn't say that so directly.If,you provide driver's API.According to them,we can develop drivers,and we don't need to provide source code.Before,the presentation was over.Mr.GreatKH interrupted.Or,if,you don't want to provide source code.You can learn your driver in user.If,it's coming.We share one source code within the community.So,that,we can develop together,mainterance together,collaborate with each other.It's a basic principle as a relaxed kind of community.Major drivers are doing.So,if,it's coming.If,you encounter the problem.Everyone can support you,help you,collaborate with you.It's in cloud source.We can't investigate anything.Or,it's not so difficult to develop drivers in Dinox.Haven't you read my white paper,that describe how to write drivers in Dinox?Have you?Or,you haven't read it.I already messed up this period,disappointing.And I thought,I couldn't have such meeting anymore.But,at the end of meeting,Mr.Andryumoto,gave a hand to rescue me.Like,sortently,there are some excellent engineers in Japan.And we know,often,they lack communication with us.So,let us go to Japan a few times a year.So,started Japan Dinox,simple.It's a very successful effective event.At that time,the head of OSDR,Mr.Kunai,he did excellent job.He requested that every communication should be done in English.Even between Japanese.And he said,after long breaks between sessions,we call it coffee breaks or coffee times.And at the end of the meeting,there was a party with simple catering food and drinks.Japanese engineers took advantage of that opportunity.They talked with maintainers.Maintenors were willing to talk with them.Soon,we experienced a lot of positive things.In 2006,Mr.Boto from Fujitsu,he attended the Karnel Summit as the first Japanese from Japan.And participants from Korea and China increased.In 2009,Karnel Summit was held in Japan.It's the only Karnel Summit that was held outside of North America and Europe.Still,then,Dizephan from Fujitsu Nanjin attended as the first Chinese from mainland of China.Actually,reaction symposium Japan or Japan reaction symposium provided a lot of opportunity to improve communication and educate engineers.Finally,the contribution from Japan increased up to about 10% of Karnel patches.And long breaks have been taken over by the Relax Foundation.relax foundation played key role to improve communication in a relax ecosystem.They started collaboration summit or end user meeting.So,probably in a 2.6.10 to 2.6.20,some major functions were installed,like native projects,like library,asynchronous IU,64-bit addressing,and so on.Then,it's a time for crossing cards,customers,adopted,DINUX server,other Linux alternative.Now,as you know,DINUX is everywhere,other standard OS,in a mobile phone,super computer,and more than 85% ofDINUX developers are employees of enterprises or companies,and they developed DINUX during their working time.Actually,reaction to the technical issues,we encountered a lot of bigger issues,but today I will skip them because of time constraint.So,let me enter today's main subject.As I said,Oconsocio is eating the world.And,in the future,even in the future,like AIG,fabji,everywhere,that's used in a TV,cameras,rice cooking machine,wash machine,you'll name it.But,even like,you have to deal with OSS.You don't have enough time and resources to run from mistakes,figures that have been done byserver vendors,including me,in 2008.So,here,very nice document fromDINUX foundation.Oconsocio guides for the enterprise.There are some document here.What kind of organization?You should have,in a company.Or,what tools there are to deal with open source?Or,how to evaluate open source success?This one is very good.How to join the committee?Or,how to attend committee?It shows from small chunk of source code,or long breaks at events,already as I mentioned.There are many best practices.Story,I recommend you to read this,if you want to join committee.I didn't explain the problem of legal issues.But,today,open source is used in parts,like navigator,or in vehicle camera,in cars.So,now,it's very important to manage the OSS governance in an entire supply chain,including part.Please imagine this.Your friend decided not to use all the code and gave it to you at $200.Without user guide,without user guide.Also,you wanted new one and gave it to another friend.Then,stranger visit you,like you violated GPR.Therefore,you are banned from using GPR.Because,user guide contains the location of relanx.Please come call the eGrip with relanx.And,describe the fact that it's delivered under GPR license.Without both information,GPR prohibited,displeasure of license software.Well,you will be upset,right?What does it mean by burning from using GPR?I cannot use the internet.I cannot get on a train or a car.If you gave me $200,I will tell nobody.But,it happened in Europe.Someone called license law and a few million dollars by this way in Europe.So,again.OSS is everywhere.So,you have to manage OSS governance through entire supply chain.Ok,that's it for today.I wanted you to know the information activity when you deal with OSS from my experience,my mistakes,my failures.Thank you for your listening and watching.Thank you.