Mozilla has announced the release of an open source tool meant to help scientists and engineers write and share interactive documents on the web.
Mozilla released Iodide, an “experimental tool” make it easier for engineers and scientists to create, view, and replicate data visualizations on the web.
The tool is currently in alpha, and available from GitHub in open source under Mozilla Public License 2.0.
Iodide source code on GitHub: github.com/iodide-project/iodide, Also available on alpha.iodide.io
Microsoft has announced that the Windows Calculator app is being open sourced on GitHub. The GitHub project hosts the source code, build system, unit tests, and the product roadmap, which should give developers an idea about how the app works.
Microsoft said on a blog post that the Windows Calculator app will be available for open source community under the MIT License.
The Windows Calculator is written in C++ and offers standard, scientific, programmer, and converter functionality. To run and test the code, Developers need Windows 10 version 1803 or later, any SKU of the latest version of Visual Studio, UWP development workload, C++ UWP tools, Windows 10 SDK, and the XAML Styler extension for Visual Studio.
The windows Calculator app code on GitHub: github.com/Microsoft/calculator
Sony Pictures Imageworks has announced making the code of its color management tool OpenColorIO available to the open source community. The tool is widely used by the company to make animation movies like Spider-Man: Into the Spider-Verse and Hotel Transylvania 3.
Sony Pictures Imageworks has passed the code of OpenColorIO to the Academy Software Foundation, a Linux Foundation-backed project devoted to increasing the use of open source software in the movie industry. The color management tool has been shared under a BSD-like license.
By handing the code to the Academy Software Foundation, the studio said "hopes that it is the community who will help see this advanced tool used to its fullest potential". According to Sony executive Michael Ford, "developers and companies that use it every day will guide the project roadmap".
The source code of OpenColorIO available on GitHub: github.com/imageworks/OpenColorIO and Imageworks website: opensource.imageworks.com/?p=opencolorio
Redis Labs is dropping its Commons Clause license in favor of its new "available-source" license: Redis Source Available License (RSAL). This is not an open-source license.
Redis Labs had used Commons Clause on top of the open-source Apache License to protect its rights to modules added to its 3-Clause-BSD-licensed Redis, the popular open-source in-memory data structure store. But, as Manish Gupta, Redis Labs' CMO, explained, "It didn't work. Confusion reigned over whether or not the modules were open source. They're not open-source."
So, although it hadn't wanted to create a new license, that's what Redis Labs ended up doing.
RSAL covers some Redis Modules, which run on top of open-source Redis. The current modules covered by RSAL are: RedisSearch, RedisGraph, RedisJSON, RedisML, and RedisBloom. Redis remains under the BSD license.
The RSAL grants, Gupta said, equivalent rights to permissive open-source licenses for the vast majority of users. With the RSAL, developers can: Use the software; modify the source code; integrate it with an application; and use, distribute, support, or sell their application.
But -- and this is big -- the RSAL forbids you from using any application built with these modules in a database, a caching engine, a stream processing engine, a search engine, an indexing engine, or a machine learning/artificial intelligence serving engine. In short, all the ways that Redis Labs makes money from Redis. Gupta wants to make it perfectly clear: "We're not calling it open source. It's not."
At the same time, Redis Labs wants everyone to understand the new RSAL will have:
Zero effect on the Redis core license, which is and will always be licensed under the 3-Clause-BSD. Unlike many other open source database companies, we have built a dedicated team (led by Salvatore Sanfilippo, the creator of Redis), who manages the Redis core in a completely independent manner. Additionally, we have chosen not to limit the functionality of open source Redis by moving core components to closed source. Consequently, open source Redis includes all the ingredients needed to run a distributed database system -- replication, auto-failover, data-persistence and clustering.
Besides, Redis argues the RSAL doesn't target developers. Instead, as Redis Labs CEO, Ofer Bengal, recently put it, "Cloud companies [which] use their monopoly power to adopt any successful open-source project without contributing anything to it."
Redis added in their announcement, "other respected open source companies, like MongoDB and Confluent, created their own proposals for modern variants to open-source licensing. Each company took a different approach, but all shared the same goal — stopping cloud providers from taking successful open source projects that were developed by others, packaging them into proprietary services, and using their monopoly power to generate significant revenue streams."
Others don't buy this argument. Matt Asay, head of Adobe developer ecosystem, said:
It has become fashionable to call out the cloud vendors, and particularly AWS, as parasitic destroyers of open source value. What real-world contributor data actually tells us, however, is that this view of the clouds is completely wrong, at least at the macro level. Google and Microsoft are orders of magnitude bigger contributors to open source communities than any other company. Even AWS, which has perhaps correctly been criticized as not 'doing more', is one of the world's top-10 largest contributors, and has scaled up its contributions considerably in the last year. It would seem that more cloud tends to equate with more open source. Perhaps, then, the clouds are not the enemies of open source, but the best allies.
Gordon Haff, a Red Hat technology evangelist, pointed out recently that Redis' argument isn't new. In 2008, not long after Amazon Web Services (AWS) was founded, he saw the fear "companies will wholesale strip-mine Open Source projects." Despite Redis' arguments to the contrary, Haff doesn't believe that's the case. Instead, companies, including cloud businesses, are embracing open source not so much because of it lets you "view source code," but because of "its collaborative development model."
Haff went on: "A lot of the heat around licenses like the Commons Clause comes about because the companies involved seem to be, on the one hand, trying to gain the perceived value of a proprietary license while also getting credit for still being open source. 'Open core' arguably plays the same parlor trick."
Now that Redis has made it black and white that its new RSAL is not open source, while the Reddis code itself remains open source, perhaps the arguments will die down. In effect, what Redis is doing is putting its own license around the old open core business model.
What the effect of that on future of the Open Source Software?!
The Linux Foundation launched the Enabling Linux in Safety Applications (ELISA) open source project to create a shared set of tools and processes to help companies build and certify Linux-based safety-critical applications and systems whose failure could result in loss of human life, significant property damage or environmental damage.
ELISA will make it easier for companies to build safety-critical systems such as robotic devices, medical devices, smart factories, transportation systems and autonomous driving using Linux.
Additional project goals include:
Develop reference documentation and use cases.
Educate the open source community on safety engineering best practices and educate the safety community on open source concepts.
Enable continuous feedback with the open source community to improve processes, and to automate quality assessment and assurance.
Support members with incident and hazard monitoring of critical components relevant to their systems and establish best practices for member response teams.
Founding members of ELISA include big companies like Arm, BMW Car IT GmbH, KUKA, Linutronix, and Toyota.
ELISA project can be found on: elisa.tech and on GitHub: github.com/elisa-tech
Offensive Security has announced the release of Kali Linux 2019.1. This is the first release of the Linux based distro in 2019, bringing the kernel to version 4.19.13. This release also fixes many bugs and includes several updated packages.
Kali Linux, is an open source distribution based on Linux, for Advanced Penetration Testing, Ethical Hacking and network security assessments.
The release announcement notes that "the big marquee update of this release is the update of Metasploit to version 5.0, which is their first major release since version 4.0 came out in 2011."
Users can download Kali Linux from: kali.org/downloads
Google Chrome is a web browser developed and maintained by tech giant Google. Chrome uses the open source web browser Chromium’s source code and adds a bunch of features developed by Google and some non free components. Otherwise, Chromium is totally an open-source web browser developed and maintained by The Chromium Project and many contributors from the community of open source developers.
Users can differentiate Chrome and Chromium browser by looking at their logo. Google Chrome is colorful, and Chromium is blue. However, that’s not the only difference between Chrome and Chromium.
Other differences between Chrome and Chromium:
1- Automatic Updates
Chrome uses Google Update on Windows (GoogleSoftwareUpdateAgent and GoogleSoftwareUpdateDaemon on Mac) to automatically update to the latest version. It is not available for Chromium. On some Linux distributions, updates are made available via package repositories. Google Update is also used for other applications like Google Earth. Don’t forget to read the difference between Google Earth and Google Maps.
2- Usage tracking and crash reporting
Unlike Chromium, Google has added the crash reporting and send usage statistics options. Chrome sends data to Google servers. It includes general data like information about your device and OS, Chrome settings, visited websites having malware, search queries, etc. This allows Google to throw suggestions, results, and ads that are relevant to you.
Crash reporting and usage tracking can be disabled from Chrome’s settings.
3- Chrome Web Store
On Google Chrome, the functionality to add extensions outside the Chrome Web Store is disabled on all Windows and Mac Channels. However, the extensions can be added via developer mode.
4- Media Codec support
Chromium’s HTML5 audio/video codec support is limited to what is available as non-proprietary codecs like Theora, Vorbis, WebM, VP9, etc. In the case of Chrome, it adds support for some non-free stuff like AAC, MP3, and H.264 (now free).
5- Non-optional tracking
Google Chrome installer includes a randomly generated token. The token is sent to Google after the installation completes in order to measure the success rate.
Google also uses the RLZ identifier to track a user on Google Search and while using the address bar. The RLZ identifier stores information – in the form of encoded strings – like the source of chrome download and installation week. It doesn’t include any personal information, and it’s used to measure the effectiveness of a promotional campaign. Chrome downloaded from Google’s website doesn’t have the RLZ identifier. The source code to decode the strings is made open by Google.
Both Chrome and Chromium browser have Sandbox support. It is always enabled in the case of Google Chrome. For Chromium, some Linux distributions may disable the Sandbox feature.
NVIDIA has open-sourced a hyper-realistic face generator called "StyleGAN", which can use many human photos to generate high quality realistic faces for people doesn't exist.
StyleGAN is a TensorFLOW implementation for A Style-Based Generator Architecture for Generative Adversarial Networks.
The Flickr-Faces-HQ (FFHQ) dataset used for training in the StyleGAN paper contains 70,000 high-quality PNG images of human faces at 1024×1024 resolution (aligned and cropped).
Users can either train their own model or use the pre-trained model to build their face generators. Linux and Windows are supported, with specific system requirements as follows:
Both Linux and Windows are supported, but we strongly recommend Linux for performance and compatibility reasons.
64-bit Python 3.6 installation. We recommend Anaconda3 with numpy 1.14.3 or newer.
TensorFlow 1.10.0 or newer with GPU support.
One or more high-end NVIDIA GPUs with at least 11GB of DRAM. We recommend NVIDIA DGX-1 with 8 Tesla V100 GPUs.
NVIDIA driver 391.35 or newer, CUDA toolkit 9.0 or newer, cuDNN 7.3.1 or newer.
StyleGAN source Code Available on: github.com/NVlabs/stylegan
Flickr-Faces-HQ Dataset (FFHQ) available on: github.com/NVlabs/ffhq-dataset
share your Opinion: How you can use this generator?!
Here!, You'll find a content specially developed for Serving Free and Open Source Software community in Egypt. Please, Register or Log in to join our community and to enjoy using our services or to do the following: