Long-time Slashdot reader renuk007 is a retired Unix/Linux systems programmer with the ultimate question: After retiring I started a second career as a teacher -- and I'm loving it. My problem: I designed a (I feel) wonderful new language compiler, but implementing it will take me another ten years if I have to do it part-time.

Linus Torvalds was able to leverage the enthusiasm of the Internet to make Linux exist, but 1990 was a more innocent time. How does it work today? Any thoughts?
Or, to put it another way, how can you build a community to bring your ideas to light? Leave your best thoughts and suggestions in the comments. How can you make your own vaporware real?

The newly-relaunched Linux Journal just interviewed the Open Source Initiative's president, Simon Phipps. An anonymous reader summarizes the highlights: Phipps collects no salary -- unlike the executive director of the Linux Foundation, who reportedly received over $300,000 in 2010. "We're a very small organization actually", Phipps said. "We have a board of directors of 11 people and we have one paid employee..." But he explains their importance by citing the controversy over Facebook's original licensing for React. "I think prior to that, people felt it was okay for there just to be a license and then for there to be arbitrary additional terms applied. I think that the consensus of the community has moved on from that."

Phipps is proud of the OSI's independence from corporate sponsors. "If you want to join a trade association, that's what the Linux Foundation is there for. You can go pay your membership fees and buy a vote there, but OSI is a 501(c)(3). That's means it's a charity that's serving the public's interest and the public benefit. It would be wrong for us to allow OSI to be captured by corporate interests." The article notes that most issues are resolved publicly, adding that one big concern is "freeware" -- proprietary software offered at no cost but erroenously marketed as open source. "In those cases, OSI definitely will reach out and contact the offending companies, and as Phipps says, 'We do that quite often, and we have a good track record of helping people understand why it's to their business disadvantage to behave in that way.'"

And he's also seeking warmer relations with the Free Software community. "As I've been giving keynotes about the first 20 years and the next ten years of open source, I've wanted to make very clear to people that open source is a progression of the pre-existing idea of free software, that there is no conflict between the idea of free software and the way it can be adopted for commercial or for more structured use under the term open source."
He cites the OSI's collaboration with the Free Software Foundation Europe on amicus briefs in important lawsuits, which he says address "significant issues, including privacy and including software patents...

"I hope in the future that we'll be able to continue cooperating and collaborating."

An anonymous reader quotes a report from XDA Developers: You've probably seen mentions of the Fuchsia operating system here and there since it has been in development for almost 2 years. It's Google's not-so-secretive operating system which many speculate will eventually replace Android. We've seen it grow from a barely functional mock-up UI in an app form to a version that actually boots on existing hardware. We've seen how much importance Google places on the project as veteran Android project managers are starting to work on it. But after all of this time, we've never once had either an official announcement from Google about the project or any documentation about it -- all of the information thus far has come as a result of people digging into the source code.

Now, that appears to be changing as Google has published a documentation page called "The Book." The page aims to explain what Fuchsia, the "modular, capability-based operating system" is and is not. The most prominent text on that page is a large section explaining that Fuchsia is NOT Linux, in case that wasn't clear already. Above that are several readme pages explaining Fuchsia's file systems, boot sequence, core libraries, sandboxing, and more. The rest of the page has sections explaining what the Zircon micro-kernel is and how the framework, storage, networking, graphics, media, user interface, and more are implemented.

An anonymous reader shares a report: Linux computer manufacturer System76 made its mark in part because of its commitment to open source principles and doing what it believes is right. Last year it released its homegrown Linux, Pop!_OS. In early March, System76 founder Carl Richell tweeted about the company's plans to locate its computer manufacturing factory in Denver, Colorado. By moving its manufacturing from China to the United States, System76 is offering more proof that it's not afraid to buck prevailing tech norms to do things "the System76 way." Carl Richell, founder and CEO of System76, says in a Twitter exchange that they anticipate shipping products from the factory by the end of the year.

An anonymous reader quotes a report from The Verge: Microsoft is releasing the source code for its original Windows File Manager from nearly 28 years ago. Originally released for Windows 3.0, the File Manager was a replacement for managing files through MS-DOS, and allowed Windows users to copy, move, delete, and search for files. While it's a relic from the past, you can still compile the source code Microsoft has released and run the app on Windows 10 today. The source code is available on GitHub, and is maintained by Microsoft veteran Craig Wittenberg under the MIT license. Wittenberg copied the File Manager code from Windows NT 4 back in 2007, and has been maintaining it before open sourcing it recently. It's a testament to the backward compatibility of Windows itself, especially that this was originally included in Windows more than 20 years ago.

TechRadar marked the 25th anniversary of the Ruby programming language by writing "there are still questions over whether it can survive another 25 years." The popularity of the Ruby language has been bolstered for many years by the success of the Ruby on Rails (RoR) web application framework which dominated the web scene, particularly among startups who wanted something that deal with much of the heavy lifting... But RoR, although popular, isn't the superstar that it was and It has faced fierce competition as issues such as scaling have become a greater concern for web companies. The JavaScript framework Node.js, for instance, has become popular as it requires less memory to deal with numerous connections because of its callback functions...

To improve performance further Ruby is introducing JIT (Just-In-Time) technology, which is already used by JVM and other languages. "We've created a prototype of this JIT compiler so that this year, probably on Christmas Day, Ruby 2.6 will be released," Matz confirmed. You can try the initial implementation of the MJIT compiler in the 2.6 preview1... Probably the clearest overview explanation of how MJIT works is supplied by Shannon Skipper: "With MJIT, certain Ruby YARV instructions are converted to C code and put into a .c file, which is compiled by GCC or Clang into a .so dynamic library file. The RubyVM can then use that cached, precompiled native code from the dynamic library the next time the RubyVM sees that same YARV instruction.
Ruby creator Yukihiro Matsumoto says Ruby 3.0 "has a goal of being three times faster than Ruby 2.0," and TechRadar reports that it's obvious that Matsumoto "will do anything he can to enable Ruby to survive and thrive..."

And in addition, "he's thoroughly enjoying himself doing what he does... and his outlook is quite simple: Programming is fun, he's had fun for the last 25 years making Ruby, and at the age of 52 now, he hopes that he'll get to spend the next 25 years having as much fun working on the language he dreamt up and wrote down in -- a now lost -- notebook, at the age of 17."

"We want Ruby to be the language that is around for a long time and people still use," Matsumoto tells another interviewer, "not the one people used to use."

"The folks at Nightdive Studios this week released the source code for a Mac version of Looking Glass Studios' 1994 classic System Shock," reports Gamasutra. Friday the game's new owners unveiled on GitHub "the original, unaltered source code that was discovered by OtherSide Entertainment and graciously shared with us a few months ago... We have been hard at work updating this code and plan to release a new version of System Shock: Enhanced Edition as well as the code in the near future." We've gone back to the original vision we shared with you at the start of our Kickstarter campaign -- this time with more reliable performance and higher fidelity visuals thanks to the Unreal Engine... We have been able to re-use the majority of work we've done over the past year and we're making significant progress in a very short amount of time. With that said we'll be inviting our highest tier backers to privately test the game beginning in September at which point we estimate that the game will be fully playable, from start to finish. The majority of the art won't be finished, but we'll be ready to start high-level testing.
Going forward there's even a Twitch component. "In an effort to remain transparent throughout development we're going to begin streaming on a regular basis and inviting the backers to join us." And the audio department has also revealed some of the music from the medical deck.

After their Kickstarter was funded, Nightdive had explored making a "bigger, better game" after receiving a verbal commitment from a game publisher, but then "were left high and dry after making crucial, consequential changes in staff and scope... We still have the funds necessary to complete the game, but the timeline will inevitably move back with our shift in direction..."

"This will be closer to a 1:1 remake with updates to the weapon/character designs but without altering the core gameplay of the original."

An anonymous reader quotes Phoronix: The kernel lockdown feature further restricts access to the kernel by user-space with what can be accessed or modified... Pairing that with UEFI SecureBoot unconditionally is meeting some resistance by Linus Torvalds. The goal of kernel lockdown, which Linus Torvalds doesn't have a problem with at all, comes down to "prevent both direct and indirect access to a running kernel image, attempting to protect against unauthorised modification of the kernel image and to prevent access to security and cryptographic data located in kernel memory, whilst still permitting driver modules to be loaded." But what has the Linux kernel creator upset with are developers trying to pair this unconditionally with UEFI SecureBoot. Linus describes Secure Boot as being "pushed in your face by people with an agenda." But his real problem is that Secure Boot would then imply Kernel Lockdown mode... "Tying these things magically together IS A BAD IDEA."

Long-time Slashdot reader Billly Gates writes: Debian is now available in the Windows app store. It joins Ubuntu, Suse Leap, SuSe enterprise, and Kali Linux for those who cannot or do not want to bother with a virtual machine or a full install of the OS. However, it included stable 9.3. 9.4 is available from the repository if you run apt-get update and apt-get upgrade.
"Fedora is not yet available, although Microsoft has stated openly that it is working to make it so," reports Computer Weekly. And there's more: Microsoft has also provided an open source tool called Microsoft WSL/DistroLauncher for users who want to build their own Linux package where a particular distribution is either a) not available yet or b) is available, but the user wants to apply a greater degree of customisation to it than comes as standard.

Slashdot reader silverdirk writes: Compiled languages have long provided access to the OpenGL API, and even most scripting languages have had OpenGL bindings for a decade or more. But, one significant language missing from the list is our old friend/nemesis Bash. But worry no longer! Now you can create your dazzling 3D visuals right from the comfort of your command line!
"You'll need a system with both Bash and OpenGL support to experience it firsthand," explains software engineer Michael Conrad, who created the first version 13 years ago as "the sixth in a series of 'Abuse of Technology' projects," after "having my technical sensibilities offended that someone had written a real-time video game in Perl.

"Back then, my primary language was C++, and I was studying OpenGL for video game purposes. I declared to my friends that the only thing worse would be if it had been 3D and written in Bash. Having said the idea out loud, it kept prodding me, and I eventually decided to give it a try to one-up the 'awfulness'..."

Thousands of Google employees, including dozens of senior engineers, have signed a letter protesting the company's involvement in a Pentagon program that uses artificial intelligence to interpret video imagery and could be used to improve the targeting of drone strikes (Editor's note: the link may be paywalled; alternative source). From a report: The letter, which is circulating inside Google and has garnered more than 3,100 signatures, reflects a culture clash between Silicon Valley and the federal government that is likely to intensify as cutting-edge artificial intelligence is increasingly employed for military purposes. "We believe that Google should not be in the business of war," says the letter, addressed to Sundar Pichai, the company's chief executive. It asks that Google pull out of Project Maven, a Pentagon pilot program, and announce a policy that it will not "ever build warfare technology."

That kind of idealistic stance, while certainly not shared by all Google employees, comes naturally to a company whose motto is "Don't be evil," a phrase invoked in the protest letter. But it is distinctly foreign to Washington's massive defense industry and certainly to the Pentagon, where the defense secretary, Jim Mattis, has often said a central goal is to increase the "lethality" of the United States military.

The Tor Project has announced that it's winding down its privacy-focused Tor Messenger chat program, nearly three years after its beta debut. From a report: Tor, an acronym of "The Onion Router," is better known for its privacy-focused browser that directs traffic through a volunteer-run network of relays to prevent any untoward eavesdropping on users' online activity. Indeed, the Tor Browser is often used by activists, whistleblowers, and anyone wishing to remain anonymous, and major companies -- such as Facebook -- have embraced Tor over the years.

The people behind the anonymity network started working on Tor Messenger in early 2014, launched it in alpha a year later, before rolling out the beta version in October 2015, where it has remained since -- though there have been more than 10 separate beta releases. [...] In terms of why Tor Messenger is being sunsetted, well, there are a number of reasons. Arguably the most important of the reasons is that uptake wasn't quite where Tor wanted it to be at to justify working on it, while it also realized that it wasn't the perfect private messaging client due to its metadata problem.

To mark Red Hat's 25th anniversary, TechCrunch spoke with the company's CEO Jim Whitehurst to talk about the past, present and future of the company, and open-source software in general. An excerpt: "Ten years ago, open source at the time was really focused on offering viable alternatives to traditional software," he told me. "We were selling layers of technology to replace existing technology. [...] At the time, it was open source showing that we can build open-source tech at lower cost. The value proposition was that it was cheaper." At the time, he argues, the market was about replacing Windows with Linux or IBM's WebSphere with JBoss. And that defined Red Hat's role in the ecosystem, too, which was less about technological information than about packaging. "For Red Hat, we started off taking these open-source projects and making them usable for traditional enterprises," said Whitehurst.

About five or six ago, something changed, though. Large corporations, including Google and Facebook, started open sourcing their own projects because they didn't look at some of the infrastructure technologies they opened up as competitive advantages. Instead, having them out in the open allowed them to profit from the ecosystems that formed around that. "The biggest part is it's not just Google and Facebook finding religion," said Whitehurst. "The social tech around open source made it easy to make projects happen. Companies got credit for that." He also noted that developers now look at their open-source contributions as part of their resume. With an increasingly mobile workforce that regularly moves between jobs, companies that want to compete for talent are almost forced to open source at least some of the technologies that don't give them a competitive advantage.
In October, Whitehurst also answered questions from Slashdot readers.

Christine Peterson is a long-time futurist who co-founded the nanotech advocacy group the Foresight Institute in 1986. One of her favorite tasks has been contacting the winners of the institute's annual Feynman Prize in Nanotechnology, but she also coined the term "Open Source software" for that famous promotion strategy meeting in 1998. Now Christine's agreed to answer questions from Slashdot readers. We'll pick the very best questions and forward them along for answers.

Interestingly, Christine was also on the Editorial Advisory Board of NASA's Nanotech Briefs, and on the state of California's nanotechnology task force. Her tech talks at conferences include "Life Extension for Geeks" at Gnomedex and "Preparing for Bizarreness: Open Source Physical Security" at the 2007 Singularity Summit. Another talk argues that the nanotech revolution will be like the information revolution, except that "Instead of with bits, we should do it with atoms," allowing molecule-sized machines that can kill cancer and repair DNA. Her most recent publication is "Cyber, Nano, and AGI RIsks: Decentralized Approaches to Reducing Risks." Christine graduated from MIT with a bachelors in chemistry.

So leave your best questions in the comments. (Ask as many questions as you'd like, but please, one per comment.) We'll pick the very best questions and forward them along for answers.

An anonymous reader writes: Google, Qualcomm, and Samsung "are among 80 tech companies joining forces to develop a new open-source chip design for new technologies like self-driving vehicles," writes Seeking Alpha, citing a (pay-walled) report on The Information. "Western Digital and Nvidia also plan to use the new chip design for some of their products," while Tesla "has joined the RISC-V Foundation and is considering using the tech in its new chip efforts."

MIT Technology Review adds that while Arm had hoped to bring their low-power/high performance processors to AI and self-driving cars, "The company that masterminded the processor inside your smartphone may find that a set of free-to-use alternative designs erode some of its future success."

Each year the Free Software award goes to someone making "a great contribution to the progress and development of free software, through activities that accord with the spirit of free software." This year's winner is a former executive of the GNOME Foundation, Karen Sandler. Jeremy Allison - Sam, Slashdot reader #8,157, brought this announcement. Richard Stallman, President of the FSF, presented Sandler with the award during a ceremony. Stallman highlighted Sandler's dedication to software freedom. Stallman told the crowd that Sandler's "vivid warning about backdoored nonfree software in implanted medical devices has brought the issue home to people who never wrote a line of code. Her efforts, usually not in the public eye, to provide pro bono legal advice to free software organizations and [with Software Freedom Conservancy] to organize infrastructure for free software projects and copyleft defense, have been equally helpful."

In her acceptance speech, Sandler spoke about her dedication to free software as a patient, advocate and professional. "Coming to terms with a dangerous heart condition should never have cost me fundamental control over the technology that my life relies on", said Sandler... "This issue is personal not just for me but for anyone who relies on software, and today that means every single person."

Artem Tashkinov writes: After three years in development the Alliance for Open Media is releasing the royalty-free AOMedia Video Codec 1.0 (AV1) specification. The AV1 codec promises an average of 30 percent greater compression over competing codecs according to independent member tests.
The release of AV1 includes:

• Bitstream specification to enable the next-generation of silicon
• Unoptimized, experimental software decoder and encoder to create and consume the bitstream
• Reference streams for product validation
• Binding specifications to allow content creation and streaming tools for user-generated and commercial video

dryriver writes: Before I ask my question, there already is free and open-source software (FOSS) for wind turbine design and simulation called QBlade. It lets you calculate turbine blade performance using nothing more than a computer and appears compatible with Xfoil as well. But consider this: the ultimate, most efficient and most real-world usable and widely deployable wind turbine rotor may not have traditional "blades" or "foils" at all, but may be a non-propeller-like, complex and possibly rather strange looking three-dimensional rotor of the sort that only a 3D printer could prototype easily. It may be on a vertical or horizontal axis. It may have air flowing through canals in its non-traditional structure, rather than just around it. Nobody really knows what this "ultimate wind turbine rotor" may look like.

The easiest way to find such a rotor might be through machine-learning. You get an algorithm to create complex non-traditional 3D rotor shapes, simulate their behavior in wind, and then mutate the design, simulate again, and get a machine learning algorithm to learn what sort of mutations lead to a better performing 3D rotor. In theory, enough iterations -- perhaps millions or more -- should eventually lead to the "ultimate rotor" or something closer to it than what is used in wind turbines today. Is this something FOSS developers could tackle, or is this task too complex for non-commercial software? The real world impact of such a FOSS project could be that far better wind turbines can be designed, manufactured and deployed than currently exist, and the fight against climate change becomes more effective; the better your wind turbines perform, and the more usable they are, the more of a fighting chance humanity has to do something against climate change. Could FOSS achieve this?

LG has released an open-sourced version of webOS that's freely available to anyone that wants to download and poke around the code. From a report: The release of webOS Open Source Edition is meant to act as a catalyst to drive further adoption of webOS beyond LG televisions, smart refrigerators, and the occasional never-to-be-released smartwatch. So, devices like webOS tablets and set-top boxes as pictured in the LG-supplied image above. This is the second time an open-source version of webOS has been released, the first coming under the failed tenure of HP back in 2011. LG's cross-town rival Samsung develops and uses the open-sourced Tizen operating system on a variety of devices including smartwatches, televisions, Blu-ray players, and robotic vacuums.

Microsoft is joining Red Hat, Facebook, Google and IBM in committing to extending right to "cure" open source licensing noncompliance before taking legal measures. From a report: On March 19, officials from Microsoft -- along with CA Technologies, Cisco, HPE, SAP and SUSE -- said they'd work with open together with the already-committed vendors to provide more "predictability" for users of open source software. "The large ecosystems of projects using the GPLv2 and LGPLv2.x licenses will benefit from adoption of this more balanced approach to termination derived from GPLv3," explained Red Hat in a press release announcing the new license-compliance partners. The companies which have agreed to adopt the "Common Cure Rights Commitment" said before they file or continue to prosecute those accused of violating covered licenses, they will allow for users to cure and reinstate their licenses.