Скачать с ютуб What does the buyout of @arduino mean for в хорошем качестве

What does the buyout of @arduino mean for

Kathy Giori http://lca2018.linux.org.au/schedule/... @KathyReid tweeted the title of this talk on July 29, 2017, a day after the Arduino buyout was announced. She was suggesting that the topic be submitted to #LCA2018. Having heard from a college friend that LCA is probably the best open source conference on the planet, I thought, why not provide my take? I will share stories of Arduino (and Wiring Project) history, including the open licensing decisions that enabled its phenomenal organic growth, worldwide. Inhibitors to continued innovation occurred whenever key Arduino personnel attempted to restrict ecosystem participation (such as limiting microcontroller partners), or limit visibility of Arduino-compatible technology. Internal personnel feuds didn’t help either. It led to two years of lawsuits among co-founders, during which two different “Arduino” companies were vying for the trademark, to capture customer loyalty. Even after a “settlement” was announced, with smiles and public handshakes shared on social media, the merged structure began with just a 3-person trademark holding company licensing the brand to the two feuding entities that continued to operate independently. They sold different boards, keeping their own profits, and keeping future projects and plans secret. Silicon vendors were confused, still dealing with two entities. To keep new products hidden, software wasn’t developed openly until the product was announced, vastly limiting expert review and collaboration that would have improved the quality, and reduced redundancy of new libraries, drivers, and core features. Similarly, an open and collaborative review of hardware designs, and cross-industry discussions for defining smaller “standard” form factors, was limited. The buyout eliminates the “two Arduino” problem. But will the remaining Arduino team learn from the past and be more accepting of Arduino-compatible alternatives around them? Will the development process become more community-driven, allowing companies like TI to participate instead of feeling obligated to fork the IDE and roll their own? Will Arduino embrace and promote the great diversity of open source software options for programming the Wiring/Arduino framework, such as Snap! (Snap4Arduino), PlatformIO, embedXcode, and others? Will Arduino and compatible board designs remain open? I discovered my passion for the open hardware community while working at Qualcomm Atheros, and was already engaged in pushing upstream Linux development of the Atheros Wi-Fi drivers. I met one of the newcomers to Arduino hardware at CES, and supported him with the integration of the AR9331 into the Arduino Yun, the first board to bridge a microprocessor running embedded Linux (OpenWrt) with a microcontroller running the Wiring/Arduino framework. This led to me joining the Arduino.org team, where I forged strategic relationships with additional chip vendors, board manufacturers, and did outreach in education and professional IoT. Due to management issues, I had resigned just before the buyout announcement. But there are reasons to stay involved in the community. Take for example RISC-V -- with an open architecture processor, we’re on the verge of open software, open hardware, and open silicon. Come listen to my take on Arduino history and where I think #openhardware can go in the future. This talk was given at Linux.conf.au 2018 (LCA2018) which was held on 22-26 January 2018 in Sydney Australia. linux.conf.au is a conference about the Linux operating system, and all aspects of the thriving ecosystem of Free and Open Source Software that has grown up around it. Run since 1999, in a different Australian or New Zealand city each year, by a team of local volunteers, LCA invites more than 500 people to learn from the people who shape the future of Open Source. For more information on the conference see https://linux.conf.au/ #linux.conf.au #linux #foss #opensource