# foss Published articles for foss. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Omarchy gains $18.5M in backing, fresh converts - and fierce critics DevFeed: [Omarchy gains $18.5M in backing, fresh converts - and fierce critics]() Original publisher: [Read original article]() Author: Liam Proven Published: 2026-09-17T10:44:00Z Content type: news Language: en Sources: [www.theregister.com - Articles]() Topics: [Linux](), [foss](), [releases](), [version](), [Quickshell](), [Ruby](), [Ruby on Rails]() Tags: [anthropic](), [apple-silicon](), [digitalocean](), [foss](), [linux](), [meta](), [open-source](), [openai](), [releases](), [software](), [version]() ### AI overview The Register reports that Omarchy, an Arch-based Linux distribution led by David Heinemeier Hansson, has grown from $8 million to approximately $18.5 million in pledges and donations. The project has released version 4.0.3, announced support plans for Apple Silicon Macs, hired technical staff, and attracted both supporters and criticism in the FOSS community. ### Source excerpt DHH's Arch-based desktop becomes the latest front in FOSS's culture wars ## Forge-X on the Adventurer 5M: how to ditch FlashMaker and run Klipper anyway DevFeed: [Forge-X on the Adventurer 5M: how to ditch FlashMaker and run Klipper anyway]() Original publisher: [Read original article]() Author: Shed Stack Published: 2026-09-16T19:00:00Z Content type: tutorial Language: en Sources: [Shed Stack]() Topics: [Embedded Software Dev](), [foss](), [Software](), [USB](), [GitHub](), [Network](), [screen]() Tags: [firmware](), [flashing](), [foss](), [github](), [how-to](), [network](), [screen](), [usb]() ### AI overview A tutorial for installing Forge-X, an open firmware mod that runs Klipper on the Flashforge Adventurer 5M and 5M Pro. It covers the risks, required firmware and USB drive, flashing process, networking, updates, recalibration, and OrcaSlicer setup. ### Source excerpt Forge-X is an open firmware mod that runs real Klipper on the Flashforge Adventurer 5M and 5M Pro to free you from FlashMaker. The whole install, the recalibration, and the OrcaSlicer setup. ## Shopify extends lifeline to Tailwind as vibe coding erodes web dev platform's bottom line DevFeed: [Shopify extends lifeline to Tailwind as vibe coding erodes web dev platform's bottom line]() Original publisher: [Read original article]() Author: Brandon Vigliarolo Published: 2026-09-10T19:43:55Z Content type: news Language: en Sources: [www.theregister.com - Articles]() Topics: [Web Development](), [modern web development]() Tags: [acquisition](), [acquisitions](), [ai-and-ml](), [css](), [devops](), [foss](), [framework](), [open-source](), [shopify](), [tailwind](), [vibe-coding](), [web](), [web-developers]() ### AI overview Shopify's acquisition gives the open-source CSS framework Tailwind a stable long-term home amid pressure on web development platforms from vibe coding. ### Source excerpt Acquisition gives open source CSS framework 'a stable long-term home' ## Ethereum Protocol Studies 2026 DevFeed: [Ethereum Protocol Studies 2026]() Original publisher: [Read original article]() Author: Josh Davis; Mario Havel Published: 2026-02-17T00:00:00Z Content type: release Language: en Sources: [Ethereum Foundation Blog]() Topics: [Ethereum](), [Cryptography](), [Learning](), [Zero-knowledge proof](), [Post-Quantum](), [foss](), [Discord](), [Wiki]() Tags: [2026](), [cryptography](), [discord](), [ethereum](), [foss](), [learning](), [math](), [platform](), [post-quantum](), [q-a](), [real-time](), [research-development](), [video](), [zero-knowledge]() ### AI overview Ethereum Protocol Studies returns in 2026 with new cryptography and consensus content tracks, including material on zkEVMs, plus a self-paced learning platform built on Moodle. The program begins February 23. ### Source excerpt tl;dr: Ethereum Protocol Studies returns for 2026 with new content tracks in cryptography, lean consensus and zkEVM, plus a new self-paced learning platform. The program kicks off February 23rd. Visit epf.wiki to get started. Ethereum Protocol Studies (EPS) is back. Since launching as a 10-week study group ahead of... ## A critique of FUTO's open-source claims, grant program, and affiliations DevFeed: [A critique of FUTO's open-source claims, grant program, and affiliations]() Original publisher: [Read original article]() Author: October Published: 2025-10-22T00:00:00Z Content type: opinion Language: en Sources: [Drew DeVault]() Topics: [Open Source](), [foss](), [Cloudflare]() Tags: [cloudflare](), [foss](), [open-source](), [open-source-software]() ### AI overview The article criticizes FUTO's use of the term "open source," arguing that the organization applies it to commercial source-available software. It also questions FUTO's grant program, its use of project logos and names, and its collaborations and promotions. ### Source excerpt Some time ago, I noticed some new organization called FUTO popping up here and there. I'm always interested in seeing new organizations that fund open source popping up, and seeing as they claim several notable projects on their roster, I explored their website with interest and gratitude. I was first confused, and then annoyed by what I found. Confused, because their website is littered with bizzare manifestos,1 and ultimately annoyed because they were playing fast and loose with the term "open source", using it to describe commercial source-available software. FUTO eventually clarified their stance on "open source", first through satire and then somewhat more soberly, perpetuating the self-serving myth that "open source" software can privilege one party over anyone else and still be called open source. I mentally categorized them as problematic but hoped that their donations or grants for genuinely open source projects would do more good than the harm done by this nonsense. By now I've learned better. tl;dr: FUTO is not being honest about their "grant program", they don't have permission to pass off these logos or project names as endorsements, and they collaborate with and promote mask-off, self-proclaimed fascists. An early sign that something is off with FUTO is in that "sober" explanation of their "disdain for OSI approved licenses", where they make a point of criticizing the Open Source Initiative for banning Eric S. Raymond (aka ESR) from their mailing lists, citing right-wing reactionary conspiracy theorist Bryan Lunduke's blog post on the incident. Raymond is, as you may know, one of the founders of OSI and a bigoted asshole. He was banned from the mailing lists, not because he's a bigoted asshole, but because he was being a toxic jerk on the mailing list in question. Healthy institutions outgrow their founders. That said, FUTO's citation and perspective on the ESR incident could be generously explained as a simple mistake, and we should probably match gen ## Cloudflare's sponsorship of Ladybird and Omarchy draws criticism DevFeed: [Cloudflare's sponsorship of Ladybird and Omarchy draws criticism]() Original publisher: [Read original article]() Author: September Published: 2025-09-24T00:00:00Z Content type: opinion Language: en Sources: [Drew DeVault]() Topics: [Cloudflare](), [foss](), [Web]() Tags: [blog](), [cloudflare](), [foss]() ### AI overview The opinion article criticizes Cloudflare's decision to sponsor the Ladybird and Omarchy projects, arguing that the projects' association with fascist politics makes the funding choice unusual. It also discusses the broader political climate and the presence of fascism in the FOSS community. ### Source excerpt US politics has been pretty fascist lately. The state is filling up concentration camps, engaging in mass state violence against people on the basis of racialized traits, deporting them to random countries without any respect for habeas corpus, exerting state pressure on the free press to censor speech critical of the current administration, and Trump is openly floating the idea of an unconstitutional third term. Fascism is clearly on the rise, and they're winning more and more power. None of this is far removed from us in the FOSS community - there are a number of fascists working in FOSS, same as the rest of society. I don't call them fascists baselessly - someone who speaks out in support of and expresses solidarity with fascists, or who uses fascists dog-whistles or promotes fascist ideology and talking points, or boosts fascist conspiracy theories - well, they're a fascist. If one consistently speaks in support of a certain political position and against the opponents of that position then it is correct to identify them with this political position. Facts, as it were, don't care about feelings, namely the feelings that get hurt when someone is called a fascist. Fascists naturally do not want to be identified as such and will reject the label, but we shouldn't take their word for it. People should be much more afraid of being called out as fascist than they are afraid of calling someone a fascist. If someone doesn't want to be called a fascist, they shouldn't act like one. It's in this disturbing political context that I saw an odd post from the Cloudflare blog pop up in my circles this week: Supporting the future of the open web: Cloudflare is sponsoring Ladybird and Omarchy. Based on Ladybird's sponsorship terms we can assume that these projects received on the order of $100,000 USD from Cloudflare. I find this odd for a few reasons, in particular because one thing that I know these two projects have in common is that they are both run by fascists. Even at fac ## No billionaires at FOSDEM DevFeed: [No billionaires at FOSDEM]() Original publisher: [Read original article]() Author: January Published: 2025-01-16T00:00:00Z Content type: opinion Language: en Sources: [Drew DeVault]() Topics: [FOSDEM](), [foss](), [Open Source](), [Blockchain](), [Fediverse](), [X (Twitter)]() Tags: [blockchain](), [ceo](), [elon-musk](), [event](), [fosdem](), [foss](), [keynote](), [open-source](), [twitter]() ### AI overview This opinion article argues that FOSDEM should not give its keynote platform to Jack Dorsey. It connects the criticism to Dorsey's former role at Twitter, the impact of Twitter's sale on the fediverse and free software communities, and Block's sponsorship of FOSDEM. The article also notes that Dorsey's talk was later cancelled. ### Source excerpt Update: Dorsey's talk was cancelled! See the update here. Jack Dorsey, former CEO of Twitter, ousted board member of BlueSky, and grifter extraordinaire to the tune of a $5.6B net worth, is giving a keynote at FOSDEM. The FOSDEM keynote stage is one of the biggest platforms in the free software community. Janson is the biggest venue in the event - its huge auditorium can accommodate over 1,500 of FOSDEM's 8,000 odd attendees, and it is live streamed to a worldwide audience as the face of one of the free and open source software community's biggest events of the year. We've platformed Red Hat, the NLNet Foundation, NASA, numerous illustrious community leaders, and many smaller projects that embody our values and spirit at this location to talk about their work or important challenges our community faces. Some of these challenges, as a matter of fact, are Jack Dorsey's fault. In 2023 this stage hosted Hachyderm's Kris Nóva to discuss an exodus of Twitter refugees to the fediverse. After Dorsey sold Twitter to Elon Musk, selling the platform out to the far right for a crisp billion-with-a-"B" dollar payout, the FOSS community shouldered the burden - both with our labor and our wallets - of a massive exodus onto our volunteer-operated servers, especially from victims fleeing the hate speech and harassment left in the wake of the sale. Two years later one of the principal architects of, and beneficiaries of, that disaster will step onto the same stage. Even if our community hadn't been directly harmed by Dorsey's actions, I don't think that we owe this honor to someone who took a billion dollars to ruin their project, ostracize their users, and destroy the livelihoods of almost everyone who worked on it. Dorsey is presumably being platformed in Janson because his blockchain bullshit company is a main sponsor of FOSDEM this year. Dorsey and his colleagues want to get us up to speed on what Block is working on these days. Allow me to give you a preview: in addition to post ## Why competition conflicts with the collaborative economics of open source software DevFeed: [Why competition conflicts with the collaborative economics of open source software]() Original publisher: [Read original article]() Author: July Published: 2024-07-16T00:00:00Z Content type: opinion Language: en Sources: [Drew DeVault]() Topics: [Open Source](), [foss](), [Software](), [Development]() Tags: [development](), [foss](), [open-source](), [software]() ### AI overview The article argues that open source software succeeds through collaboration, shared research and development costs, and cross-company talent. It contends that business models centered on competing with or replacing open source conflict with the collaborative economics that make FOSS effective. ### Source excerpt We are living through an interesting moment in source-available software.1 The open source movement has always had, and continues to have, a solid grounding in grassroots programmers building tools for themselves and forming communities around them. Some looming giants brought on large sums of money - Linux, Mozilla, Apache, and so on - and other giants made do without, like GNU, but for the most part if anyone thought about open source 15 years ago they were mostly thinking about grassroots communities who built software together for fun. With the rise of GitHub and in particular the explosion of web development as an open platform, commercial stakeholders in software caught on to the compelling economics of open source. The open source boom that followed caused open source software to have an enormous impact on everyone working in the software industry, and, in one way or another, on everyone living on planet Earth. Over the past decade or so, a lot of businesses, particularly startups, saw these economics unfolding in front of them and wanted to get in on this boom. A lot of talented developers started working on open source software with an explicit aim towards capitalizing on it, founding businesses and securing capital investments to build their product - an open source product. A few years following the onset of these startups, the catch started to become apparent. While open source was proven to be incredibly profitable and profoundly useful for the software industry as a whole, the economics of making open source work for one business are much different. It comes down to the fact that the free and open source software movements are built on collaboration, and all of our success is attributable to this foundation. The economics that drew commercial interest into the movement work specifically because of this collaboration - because the FOSS model allows businesses to share R&D costs and bring together talent across corporate borders into a great melting pot ## Ethereum Protocol Fellowship Cohort 4 Recap DevFeed: [Ethereum Protocol Fellowship Cohort 4 Recap]() Original publisher: [Read original article]() Author: EF Protocol Support Published: 2024-04-22T00:00:00Z Content type: article Language: en Sources: [Ethereum Foundation Blog]() Topics: [Ethereum](), [Development](), [Programming](), [Wiki](), [Protocol (disambiguation)](), [foss]() Tags: [contributions](), [devconnect](), [developers](), [development](), [ethereum](), [foss](), [knowledge-base](), [learning](), [open](), [programming](), [projects](), [recap](), [research-development](), [updates]() ### AI overview The Ethereum Protocol Fellowship completed its fourth cohort, with 35 stipend-supported participants and five retroactive stipends. Fellows worked with 27 core developer mentors, reported nearly 600 weekly updates, and proposed or contributed to 35 projects. The program also launched a 10-week study group and the EPF.wiki knowledge base to help aspiring core developers learn Ethereum protocol development. ### Source excerpt TL;DR: The EPF concluded the fourth cohort and is preparing for a fifth cohort. Applications will be open soon. In the meantime, explore the new EPF.wiki and sign up to get notified when they open. The Ethereum Protocol Fellowship recently completed its fourth successful cohort, culminating with EPF Day... ## Mobian's 2023 progress DevFeed: [Mobian's 2023 progress]() Original publisher: [Read original article]() Author: Mobian team Published: 2024-01-14T00:00:00Z Content type: opinion Language: en Sources: [Mobian's Blog]() Topics: [Debian](), [Mobile](), [Flatpak](), [foss](), [FOSDEM]() Tags: [debian](), [distribution](), [fosdem](), [foss](), [mobile]() ### AI overview A retrospective on Mobian's 2023 development, covering the Bookworm stable release, growth in mobile-friendly applications, efforts to reduce Mobian-specific packages and align more closely with Debian, and participation in FOSDEM and distro collaborations. ### Source excerpt Time flies when you are having fun. 2023 was no exception, and we find ourselves in 2024 already! Time to take stock what happened last year (and perhaps also what we attempt to achieve this year). Bookworm release It is safe to say that the bookworm release was a major milestone for Mobian. For the first time, we have a stable release that we find to actually be useful on a mobile screen and phone. Putting out stable images was quite some work but we are proud of it. We had decided to move on and focus on the next development cycle rather than starting to backporting features and releases. So bookworm continues to receive security updates, but no new features. Still, it might be a useful stable base for people who do not like to break their phone that often. By using flatpak and other means, one can even use actual releases of apps and not miss out on the latest hotness. App ecosystem The ecosystem of applications suitable for mobile screen continued to grow in 2023, filling many important functionality gaps. That includes core GNOME apps included in the distribution that became ported to work better on small screens, to an external ecosystem of applications that can be installed via flatpak or other means. Whether you want to track your jogging tracks, travel via public transportation, or toot on social media, many puzzle pieces start to fall into place. https://linuxphoneapps.org/ gives you a great overview of what exists within and outside of distributions. (and yes, there is active Debianization of some apps going on, such as the "railway" application which went into Debian just now. Shrinking Mobian Despite all that growth we managed to shrink the packages that are in the mobian repository even more over time. As you know, Mobian is nothing but a thin overlay over stock Debian (the regular Debian repository with its updates is a core pillar of Mobian), and it is declared goal of Mobian to abolish itself by upstreaming all deviations and changes to Debian prope ## Announcing a Chainguard Image for OpenTF DevFeed: [Announcing a Chainguard Image for OpenTF]() Original publisher: [Read original article]() Published: 2023-09-06T00:00:00Z Content type: release Language: en Sources: [Chainguard: Unchained]() Topics: [chainguard images](), [Open Source](), [Containers](), [foss](), [Terraform](), [Security]() Tags: [chainguard](), [chainguard-images](), [container](), [foss](), [linux](), [oci-registry](), [open-source](), [opentf](), [scanners](), [security](), [state](), [terraform]() ### AI overview Chainguard announces a Chainguard Image for OpenTF, the open-source fork of Terraform created after HashiCorp's license changes. The image is available through Wolfi and Chainguard Images for Linux amd64 and arm64, with a 65 MB size and zero known CVEs according to supported scanners. The article also discusses planned state encryption and OCI registry support, plus future testing and Terraform plugin availability for OpenTF. ### Source excerpt Discover how Chainguard for OpenTF bridges the open-source community, ensuring secure and efficient container ecosystem transitions. ## OSS Security: Chainguard Spring 2023 update DevFeed: [OSS Security: Chainguard Spring 2023 update]() Original publisher: [Read original article]() Published: 2023-03-22T00:00:00Z Content type: release Language: en Sources: [Chainguard: Unchained]() Topics: [chainguard](), [open-source-security](), [supply-chain-security](), [Open Source](), [Security](), [software bill of materials]() Tags: [chainguard](), [cloud-native](), [cloud-native-security-con](), [fosdem](), [foss](), [gitops](), [kubecon-eu](), [kubernetes](), [open-source-software](), [open-source-software-security](), [openssf](), [oss](), [sigstore](), [software-bill-of-materials](), [software-supply-chain](), [supply-chain-security]() ### AI overview Chainguard's Spring 2023 update describes its involvement in open-source software security during the first part of 2023. It covers community leadership, conference talks and workshops, software freedom advocacy, and efforts to make software bills of materials useful and widely adopted for supply-chain security. ### Source excerpt Chainguard believes open source is important and we mean it. Check out how we've been involved in OSS Security in the first part of 2023. ## These months in Mobian: February/March 2023 DevFeed: [These months in Mobian: February/March 2023]() Original publisher: [Read original article]() Author: Mobian team Published: 2023-03-10T00:00:00Z Content type: article Language: en Sources: [Mobian's Blog]() Topics: [FOSDEM](), [Mobile](), [Linux](), [Debian](), [Website](), [foss](), [JavaScript](), [CSS](), [HTML](), [Kernel]() Tags: [collaboration](), [conference](), [css](), [debian](), [fosdem](), [foss](), [html](), [javascript](), [kernel](), [linux](), [mobile](), [website]() ### AI overview A February-March 2023 roundup from Mobian covers the physical FOSDEM mobile Linux devroom, related talks and community collaboration, a JavaScript-free website redesign that retains its animation, and Debian Bookworm's transition toward a freeze. ### Source excerpt March isn't even over yet and we are already summing up what has happened in both February and March. Dang, are we fast... FOSDEM February 2023 began with a bang: finally a physical FOSDEM conference in Brussels, and a few (or rather, plenty of) mobile Linux people organized a physical devroom on "FOSS on mobile Linux". Many submissions on various topics, from many distros and projects, of which 10 were selected. (Photo by spaetz under CC-0) Directly relevant were talks on "What's new in the world of phosh?" and "Mobian: to stable... and beyond!". But also others, such as the talk on ondev2, a new cross-distro installer, which Mobian will potentially use. Many other interesting talks on convergence, so if you have not already, check out the whole track. Another highlight was the cross-distro stand with an unusual high density of Linux phones being put on a single table, and a dense crowd of people being interested in Mobile on Linux. Some were well-know names and faces, that are already familiar with the state of things, while others were surprised that Linux on Mobile "is a thing". Most importantly though, it was one of those rare moments in life to physically meet your collaborators. And while we did not manage to do a live-podcast as the postmarketOS contributors did, we did have beer, dinner, talks, and fun together. Sometimes, these are the most important times in a collaboration! And yes, we will try to have Mobian stickers next time around! :-) Website Our Website does not contain a lot of content, but previously it still used some Javascript in order to provide a flying-in animation (and possibly other things). Thanks to community member Sven J. Grewe, we have now done away with the Javascript entirely (still keeping the animation) and our root page now consists of 1 html, 1 css and 7 icons/images, loading pretty fast. Thank you Sven, contributions are always welcome! Debian Bookworm Debian has started its soft freeze towards the Bookworm release. This implies: ## An opinionated guide to consolidating our data DevFeed: [An opinionated guide to consolidating our data]() Original publisher: [Read original article]() Author: Abhi Vaidyanatha Published: 2022-05-24T00:00:00Z Content type: article Language: en Sources: [Trino Blog]() Topics: [data-engineering](), [data](), [foss](), [Open Source]() Tags: [article](), [blog-post](), [community](), [data-engineering](), [foss](), [open-source](), [partnership]() ### AI overview An opinionated guide to consolidating data in a central location with minimal architectural choices. It recommends Airbyte as a straightforward open-source ELT tool that can be deployed with three terminal commands, managed through a UI, and used for incremental data synchronization. Meltano and KETL are discussed as alternatives, but the article recommends Airbyte for this use case. ### Source excerpt Maximizing your experience with zero choices. I'm publishing this blog post in partnership with the Trino community to go along a lightning talk I'm giving for their event, Cinco de Trino. This article was originally published on Abhi's Medium site "My data is all over the place and attempting to analyze or query it is not only time consuming and expensive, but also emotionally taxing." ## October Update Follow-up DevFeed: [October Update Follow-up]() Original publisher: [Read original article]() Published: 2021-10-29T00:00:00Z Content type: article Language: en Sources: [Community blog on PINE64]() Topics: [Pinephone-Pro](), [Soquartz](), [Discord](), [Raspberry Pi](), [foss](), [Matrix](), [IRC]() Tags: [announcement](), [community-update](), [discord](), [foss](), [irc](), [matrix](), [pinedio](), [pinephone](), [pinephone-pro](), [quartz64](), [soquartz](), [telegram](), [update]() ### AI overview Pine64's October community update follow-up covers discussion of the PinePhone Pro, delivery delays affecting China and the USA, community chat activity across Discord and bridged platforms, and the planned Pine Store availability of the SOQuartz module. SOQuartz is described as pin-compatible with the Raspberry Pi Compute Module 4 and suitable for existing CM4 baseboards and planned hostboards. ### Source excerpt Happy Halloween! As promised earlier this month, here is the follow-up to the October community update. Some of the topics I'll touch upon will be covered in more detail in November. I'll keep this one brief. Housekeeping PineTalk discussed the PinePhone Pro in last week's episode. At the time of writing, it is the most listened-to episode of our community-run podcast, and there is a reason for it - it is a very good episode. I encourage you to have a listen. Earlier this week we had a guest post about the creation of the Meet the PinePhone Pro announcement trailer. If you're interested in learning how the trailer was made, and which software was used during its production, then I invite you to have a read. Logistics issues in China and the USA have caused a significant increase in parcel delivery times. The USA is particularly affected by the situation. There is nothing we can do about it, but the reason I am bringing it up is due to the increase in support tickets requesting help in tracking down packages (and sporadic claims of packages being lost). All I can do is ask you for patience - it may take a long time, but in 99.9% of cases the parcel will eventually arrive at your doorstep. Lastly, our Discord is about to reach (or already reached) 9000 members, making it the biggest chat platform out of all protocols used by our community. I think this is quite the milestone and I am very happy to see many new faces actively engaging in discussions. I know Discord is frowned upon by some in the FOSS community, so before anyone complains - there are corresponding and bridged channels in Telegram, IRC, and Matrix available for those who wish to use a different platform. Full chat list here. SOQuartz The SOquartz module will be available for purchase in the Pine Store next week. I already covered the SOQuartz in-depth in the June update, so I encourage you to read that blog entry for more information. For those who do not know, the SOQuartz is a module that is pin-compat ## Pine Store Community Pricing & Online Retail Stores DevFeed: [Pine Store Community Pricing & Online Retail Stores]() Original publisher: [Read original article]() Published: 2020-12-02T00:00:00Z Content type: opinion Language: en Sources: [Community blog on PINE64]() Topics: [foss](), [Linux](), [Hardware](), [Support](), [Wiki]() Tags: [community](), [developers](), [foss](), [hardware](), [linux](), [pine-store](), [pine64](), [pinebook](), [product](), [retail](), [software](), [store](), [support]() ### AI overview PINE64 explains that new online retail stores planned for 2021 will operate alongside the existing Pine Store, whose community-oriented pricing and device sales will remain unchanged. The strategy is intended to serve general consumers while preserving the existing community-focused model and reducing pressure on support staff from software troubleshooting requests. ### Source excerpt In 2021 you'll see online retail Pine stores open in Europe, North America and possibly also worldwide at a later stage. Let me start by making one thing clear - the current Pine Store isn't going away and the pricing in the Pine Store will remain unchanged. You'll always be able to buy and pre-order your devices from pine64.com at a community-oriented price point. The retail stores will function alongside the Pine Store, not replace it, and offer a different customer experience. In this blog I'll explain the rationale behind this strategy. PINE64 is not a business First things first - PINE64 is a community, not a business, and the Pine Store's sole purpose is to serve this community by providing FOSS development-friendly hardware. Sales numbers and revenue are not, and never were, a driving force behind this project; making the next fun and often experimental device was and still is. Some devices, such as the original Pinebook, were even sold at a loss at times - simply because we knew people wanted one. Seriously. Victims of our own success Our strategy was always clear - work with developers to design a product, have partner projects and community developers work on the software and sell the device at a community-oriented price point. This approach has proven to be a great way forward for us, and one that, dare I say it, ultimately distinguished us from the other FOSS-vendors and manufacturers. That said, we're slowly falling victim to our own success. News of our devices have reached people outside of our target audience, and enthusiast-grade products now frequently end up in the hands of non-technical customers. I have just been looking at the incoming support tickets these past weeks, and the majority of incoming queries are by people who are not comfortable troubleshooting software problems, have little Linux experience, and do not understand the nature of our devices. In a nutshell, they are general tech-consumers unfamiliar with the intricacies of Linux, FO ## Journey with Airflow as an Outreachy Intern DevFeed: [Journey with Airflow as an Outreachy Intern]() Original publisher: [Read original article]() Author: Apache Airflow Published: 2020-08-30T00:00:00Z Content type: opinion Language: en Sources: [Apache Airflow Blog]() Topics: [airflow](), [REST API](), [foss](), [Development](), [Pull Request]() Tags: [airflow](), [apache-airflow](), [community](), [contributions](), [foss](), [intern](), [outreachy](), [rest-api]() ### AI overview The article recounts an Outreachy intern's experience contributing to Apache Airflow, including choosing a REST API project, setting up the development environment, submitting and reviewing pull requests, learning from feedback, and understanding Airflow concepts such as pools, tasks, DAGs, and DAG runs. ### Source excerpt Outreachy is a program which organises three months paid internships with FOSS projects for people who are typically underrepresented in those projects. Contribution Period The first thing I had to do was choose a project under an organisation. After going through all the projects I chose "Extending the REST API of Apache Airflow", because I had a good idea of what REST API(s) are, so I thought it would be easier to get started with the contributions. The next step was to set up Airflow's dev environment which thanks to Breeze, was a breeze. Since I had never contributed to FOSS before so this part was overwhelming but there were plenty of issues labelled "good first issues" with detailed descriptions and some even had code snippets so luckily that nudged me in the right direction. These things about Airflow and the positive vibes from the community were the reasons why I chose to stick with Airflow as my Outreachy project. Internship Period My first PR was followed by many new experiences one of them being that I introduced a bug in it;). But nonetheless it made me familiar with the feedback loop and the feedback on my subsequent PRs was the focal point of the overall learning experience I went through, which boosted my confidence to contribute more and move out of my comfort zone. I wanted to learn more about the things that happen under the Airflow's hood so I started filtering out recent PRs dealing with different components and I would go through the code changes along with discussion that would help me get a better understanding of the whole workflow. Airflow's mailing list was also a great source of knowledge. The API related PRs that I worked on helped me with some of the important concepts like: Pool CRUD endpoints where pools limit the execution parallelism. Tasks determine the actual work that has to be carried out. DAG which represents the structure for a collection of tasks. It keeps track of tasks, their dependencies and the sequence in which they have ## March Update: Manjaro on Pinebook Pro & PinePhone Software DevFeed: [March Update: Manjaro on Pinebook Pro & PinePhone Software]() Original publisher: [Read original article]() Published: 2020-03-15T00:00:00Z Content type: news Language: en Sources: [Community blog on PINE64]() Topics: [Pinephone](), [Operating system](), [Development](), [Kernel](), [IRC](), [Matrix](), [foss](), [communications]() Tags: [community-update](), [foss](), [irc](), [kernel](), [manjaro](), [matrix](), [os](), [pinebook-pro](), [pinephone](), [pinetime](), [software]() ### AI overview PINE64's March community update reports that Pinebook Pro production is resuming with Manjaro KDE as the default operating system, with pre-orders planned for March 18 and shipping planned for early May. It also covers PinePhone development, PineTime software, spare parts and cases, hardware production, and migration of IRC and Matrix services to a PINE64 cluster. ### Source excerpt COVID-19 recovery in China is underway and factory work is slowly returning back to normal. This is good news, and we hope to have a constant stream of updates for you in the coming weeks. That said, we're taking it one step at a time, since factories are still at 20% of the normal manufacturing capacity and it's hard to predict the recovery pace. So rather than offering you my guesstimates for particular device availability, we will make announcements once all stages of production are secured for each device. Frankly speaking, this also means that announcements will likely drop suddenly; so If you haven't done so yet, this is probably the time to subscribe to this blog and be notified when it happens. The big news of this community update is that Pinebook Pros are about to re-enter production and will be shipping with Manjaro KDE as the default operating system! Pre-orders for the new production run starts on Wednesday (March 18th) and shipping is planned for early May. TL;DR for this month Moving PINE64 services to the PINE64 cluster Spare parts for the PinePhone and Pinebook Pro OG Pinebook entering production for charity; closing the digital gap PINE A64-LTS will be produced until 2025 Pinebook Pro pre-orders start March 18th; expected shipping date early May Manjaro KDE is the new default OS for the Pinebook Pro! mainline kernel 5.7 mainline Pinebook Pro support Minor Pinebook Pro refinements and tweaks PinePhone development is steaming ahead; new OSes and features PinePhone soft and hard protective cases available soon PineTime OSes start coming together; first glimpse at a fully fledged FOSS OS Housekeeping We're getting ready to move PINE64 community services to our ROCKpro64 cluster. The IRC and Matrix are the first services on our list, which means disruptions to all chats are expected at some point this month. We obviously hope that the downtime will be minimal, but given the complexity of our communications setup - which spans across multiple chat protoc ## Setting the Record Straight: PinePhone Misconceptions DevFeed: [Setting the Record Straight: PinePhone Misconceptions]() Original publisher: [Read original article]() Published: 2020-01-24T00:00:00Z Content type: opinion Language: en Sources: [Community blog on PINE64]() Topics: [Pinephone](), [allwinner](), [foss](), [Open Source](), [SOC](), [Linux](), [GPU](), [Kernel]() Tags: [bluetooth](), [boot](), [foss](), [gpu](), [kernel](), [linux](), [misconceptions](), [open-source](), [pinephone]() ### AI overview The article addresses misconceptions that the PinePhone is closed-source. It explains that the Allwinner A64 SoC uses mainline Linux, mainline ATF and u-boot, with open-source drivers for its main components. It also identifies non-FOSS parts, including WiFi and Bluetooth firmware, optional camera autofocus firmware, and the Quectel EG25-G modem's closed-source operating system. ### Source excerpt I take no pleasure in writing this blog post. In fact, even as I am writing these words I am internally torn on whether this is the right approach to addressing the problem on hand. Whether I've chosen the right approach remains to be seen, but regardless, I now feel it's time to confront misconceptions about the PinePhone. What's the misconception? The misconception concerns the openness of the PinePhone. On numerous occasions I've seen the PinePhone being refereed to as closed-source on one level or another. I don't know the origin of this misconception nor do I understand the reason why it has become propagated throughout the internet. What I do know, however, is that it has been repeatedly quoted in online articles covering the PinePhone or other Linux devices for over a year now. So let's set the record straight: the PinePhone is not 'full of closed-source firmware' and, moreover, is one of the most open devices out there. Here's what's open Let's start with the Allwinner A64 SoC, which is the brains of the PinePhone; it runs mainline Linux, uses mainline ATF and u-boot and there are open source drivers for all main SoC components. This openness extends to the Lima GPU driver introduced in kernel 5.2. Linux 5.6 will contain drivers for all major components of the SoC. The parts which still need to be upstreamed to mainline are HDMI audio and msgbox - both drivers are in the works. For more information on mainlining efforts, please refer to the A64 column at https://linux-sunxi.org/Linux_mainlining_effort#Status_Matrix It's worth mentioning that LPDDR3 initialization is done by u-boot SPL, which is also open source. There are no blobs in there either. Needless to say, the PinePhone itself is an open platform for any OS to run on. The grand majority of the OSes developed for the PinePhone are, in and of themselves, completely open too. So, where are the blobs? The non-FOSS parts of the phone are as follows: WiFi and Bluetooth firmware must be uploaded to the Real ## December Update: Thank You For 2019! DevFeed: [December Update: Thank You For 2019!]() Original publisher: [Read original article]() Published: 2019-12-05T00:00:00Z Content type: news Language: en Sources: [Community blog on PINE64]() Topics: [foss](), [Hardware](), [Pinephone](), [.NET Conf]() Tags: [communities](), [community](), [community-update](), [contributors](), [developers](), [firmware-update](), [fosdem](), [foss](), [hardware](), [pine64](), [pinebook-pro](), [pinephone](), [pinephone-keyboard](), [pinetab](), [pinetime](), [users]() ### AI overview PINE64's December 2019 community update thanks contributors and users, reviews progress across PineTime, PineTab, PinePhone, keyboards, firmware, and other hardware, and previews January updates and FOSDEM 2020 announcements. ### Source excerpt Welcome to the last community update of the year. I think that 2019 will be remembered as the year PINE64 transitioned from being a relatively niche FOSS hardware project to a mainstream one. This transition is an exciting prospect for all of us involved with PINE64, and we cannot wait to see how the project develops over the next 12 months. Let me take this opportunity to thank those of you whom have been with us thus far: the partner-project developers, community contributors, mods and admins, shipping and assembly teams, and - above all else - the end-users who make this project possible. Thank you for actively shaping PINE64 and making it one of the most vibrant and welcoming communities in the FOSS space. The amount of progress we've made in just one year is incredible and the success is truly collectively ours. Thank you! Here's the TL;DR: Next Community Update January 12th ; Give us some feedback The PineTime is now in the PINE Store ; Great development PineTab early adopter pre-orders likely in January ; New keyboard ; LTE/ SSD adapter Brave Heart PinePhones worked on ; shipping early January ; PinePhone cases ; First phone call ; PinePhone keyboard Continual good reception ; Keyboard / TP firmware update available ; A lot of OSs coming ; regional keyboards ; OG Pinebook upgrade kit likely in January 2020. New announcements at FOSDEM 2020 ; teaser of what's to come next year Happy New Year! Housekeeping I'll try to keep this section short. It's unlikely that I'll be able to publish the next Community Update on 05/01/2020 seeing as I'll be traveling during the Holiday and New Year's period. In other words, I won't have an opportunity to sit down and write the blog until I am back home on January 7th. I feel like the earliest date I can commit to for an update blog entry is 12/01/2020. In the meantime, if some noteworthy or urgent information surface then I'll post ad-hoc updates in the forum news section. Make sure to check it once in a while during the holid ## Why Financial Support Is Important for Sustainable Open-Source Software DevFeed: [Why Financial Support Is Important for Sustainable Open-Source Software]() Original publisher: [Read original article]() Published: 2019-08-19T00:00:00Z Content type: opinion Language: en Sources: [Community blog on PINE64]() Topics: [Open Source](), [foss](), [Maintainers](), [Linux]() Tags: [community](), [contribute](), [digital-gap](), [financial](), [foss](), [giving](), [linux](), [maintainers](), [open-source-software](), [sustainable-foss]() ### AI overview PINE64 discusses why open-source software projects need financial support to sustain development and keep free software accessible. The article encourages users and organizations to contribute to the projects they rely on. ### Source excerpt PINE64's commitment to giving back to the community, partner projects and the society has been outlined by TL Lim during our community meetup in Hyde Park, London on 18 August, 2018. No one has ever become poor by giving ~ Anne Frank Free as in a bird, not as a beer. Libre and not gratis. We all understand this concept while simultaneously appreciating that open source software is, for the most part, also free of charge to regular end-users. By relying on donations and sponsorships to make revenue and keep the light on, most projects maintain a low barrier to entry for new and prospectus users. Anyone with a computer and an internet connection can readily use just about any Linux or *BSD operating system, as well as any open software these OS' run. Not to mention that anyone is welcome to study, contribute to and alter the said software. I know that I am preaching to the choir but FOSS is amazing. That said, these are hardly the only reasons for using open source software. For a sizable number of people, the payment-free model also means access to good and viable alternatives to proprietary software, which may be financially out of reach. I myself, as an undergrad student in the early 2000's, resorted to using OpenOffice - not for ideological reasons, but rather because I couldn't afford the MS Office Suite. That said, projects need money to sustain the development process and, ultimately, the software they deliver free of charge to end-users. Much has already been written on the subject of sustainability of FOSS projects by people more knowledgeable than myself, so if you're interested in the subject matter then search for FOSS financial sustainability. In a nutshell, keeping a FOSS project financially sustainable is very difficult; In the words of Andre Staltz, data shows "(...) that open source creators and maintainers are receiving low income" and "[t]his is not the first time [in history] hard-working honest people are giving their all, for unfair compensation". ## Volumio Motivo: a FOSS Audiophile Experience DevFeed: [Volumio Motivo: a FOSS Audiophile Experience]() Original publisher: [Read original article]() Published: 2019-06-10T00:00:00Z Content type: article Language: en Sources: [Community blog on PINE64]() Topics: [fpga](), [SOC](), [foss](), [Linux](), [interface](), [Software](), [IO](), [USB]() Tags: [audio](), [audioplayer](), [foss](), [fpga](), [interface](), [io](), [linux](), [motivo](), [soc](), [software](), [specifications](), [usability](), [usb](), [volumio]() ### AI overview This article presents the Volumio Motivo, a higher-end audio device powered by the Volumio Linux distribution. It describes Yottamusic's Metaclock design, which uses an A64 SoC, SDIO data transfer, a dedicated FPGA, memory buffering, and DAC communication, and lists reported audio measurements and hardware specifications. ### Source excerpt The higher end alternative to the PRIMO, the MOTIVO, will catch your eye and ear. It is powered by the FOSS audiophile Linux distribution - Volumio - that is aviable for many Single Board computers, including the PINE A64-LTS and the ROCK64. From our point of view, the technology inside the MOTIVO is what makes it stand out, although, we can't argue with its great looks. Powered by a SOPine module, the Volumio Motivo is a true fusion of form and fucntion, and a brainchild of a Joint Venture between world-class industrial design firm Design Narratives and R&D and audio design Company Yottamusic. Yottamusic has been working for 10 years on their the core-technology which is now in the Motivo: METACLOCK. This Technology has 3 core principles: Do not use a generic SOC (which handles communication with the DAC) Use an interface that, other than USB and I2S allows faster data transfer Use a dedicated FPGA to handle communication with the DAC. Therefore emancipating the Audio Quality outcome from the OSCPU combination. It works this way: The audio stream is sent from the A64 SOC via a high-speed BUS (SDIO) to a dedicated FPGA Here the stream is reclocked via a double buffer and stored on a high-speed memory It's then sent, at the right moment to the DAC The results that it brings: 104dB THD+N 110dB SNR Jitter: 200ps Maximum Network data correction This means that with Metaclock technology, Volumio Motivo is able to achieve outstanding sound quality performances without the need of esoteric (and expensive) designs, following Volumio's core principle: the best possible sound quality with an unbeatable priceperformance ratio. Integrating Metaclock technology is being probably the biggest challenge Volumio Team has faced so far: since this technology has never been done before, in this way, there is no standard to follow nor any HOWTO nor literature. Work is currently being done to implement the very complex software integration to take the most out of this technology, without ## Keeping Track of Open Source Software Licenses DevFeed: [Keeping Track of Open Source Software Licenses]() Original publisher: [Read original article]() Author: taylor@goteleport.com (Taylor Wakefield) Published: 2016-10-18T00:00:00Z Content type: tutorial Language: en Sources: [Teleport]() Topics: [Open Source](), [foss](), [Software](), [open-source-security]() Tags: [acquisition](), [advice](), [customer](), [foss](), [intellectual-property](), [open-source](), [open-source-software](), [saas](), [signing](), [startup]() ### AI overview This article explains why startups and enterprise software teams should track open-source software licenses early. It describes the legal and business risks that can arise during acquisitions or major customer deals, recommends reviewing licenses and watching for copyleft terms, and suggests scanning code with a script and consulting a lawyer. ### Source excerpt It might be mundane and boring but keeping track of your FOSS license usage can save you from a big headache at the least opportune time. ## Understanding WebDriver, Selenium, Marionette, and Browser Automation DevFeed: [Understanding WebDriver, Selenium, Marionette, and Browser Automation]() Original publisher: [Read original article]() Author: Maja Frydrychowicz Published: 2016-07-12T04:00:00Z Content type: article Language: en Sources: [Mozilla Automation]() Topics: [webDriver](), [Browser Automation](), [Selenium](), [Testing](), [Firefox](), [HTTP](), [JSON](), [Mozilla](), [JavaScript](), [Open Source]() Tags: [automation](), [browser](), [browser-ui](), [browsers](), [client-driver](), [firefox](), [foss](), [geckodriver](), [harness](), [http](), [javascript](), [json](), [marionette](), [mozilla](), [open-source](), [payload](), [request](), [responses](), [selenium](), [w3c](), [web](), [webdriver]() ### AI overview An explanatory article untangles the terminology around Marionette, Selenium, WebDriver, FirefoxDriver, and geckodriver. It explains the W3C WebDriver Specification and how its browser-agnostic protocol uses JSON over HTTP to send commands and receive responses for browser automation and testing. ### Source excerpt I define WebDriver, W3C WebDriver, Selenium, geckodriver, FirefoxDriver, Marionette harness/runner/client/driver and more. [Next page]()