Welcome to Anthon Open Source Community! We are a group of free and open technology enthusiasts working hard for improvements.

Most good programmers do programming not because they expect to get paid or get adulation by the public, but because it is fun to program. – Linus Torvalds


  • New Mirror at CQU-Lanunion!MARCH 18, 2019

    Our community repository has received yet another mirror, hosted by CQU-Lanunion at Chongqing University!

    Go check out their mirror homepage!

  • Repository MigrationDECEMBER 25, 2018

    On December 29th (UTC +8), our Community Repository server will migrate to a new server in the United States with a 1Gbps bandwidth. As users of AOSC OS, no manual intervention would be needed. However, if you are any of our mirror maintainers, please take note of the following:

    • Check if you are using any of [,,] as rsync domain.
      • If so, no intervention is needed. We will change the DNS record on Dec 30, 2018.
      • If not, please replace any non-domain reference (i.e., IP addresses) with Under no circumstances should you use the IP address directly in the future.
    • Check if the syncing completes successfully on Dec 31, 2018.
      • If not, please contact Xiaoxing Ye, our Repository maintainer at

    The server is kindly sponsored by For more information, please refer to our Migration Guide.

  • Re-Cap: AOSCC 2018AUGUST 13, 2018

    Even though we didn’t have the fortune to meet each other in person like we did last year, AOSCC 2018 has been productive and a whole heap of fun. While there’s obviously no picture of the event this time, we do have a full log of the sessions over the two weeks for your reference.

    This year’s conference was constituted by a series of topic, with 14 topics discussed across 16 sessions over the span of two weekends. The purpose of this news post is to provide a summary of decisions made and changes planned for the coming year - so you’ll know what to expect. There are lots of things to talk about so… Let’s dive in.

    Codename and Wallpaper

    Friends of our community never disappoints in terms of creativity and sense of humour… And this year is no exception. Out of 40 nominated codenames, the community voted “Fsck” to be the codename of AOSC OS Core 6. Fsck, file system consistency check, or an elegant rendition of a widely used profanity - like how Fsck was originally called…

    *Dennis Ritchie: “So fsck was originally called something else”*
    *Question: “What was it called?”*
    *Dennis Ritchie: "Well, the second letter was different"*

    This year’s default wallpaper was made by Tianhao Chai with Blender - titled “Campanula”.


    “Campanula” also comes in two variants, one with an alternative layout, and another rendered in a “neon light” style. All these wallpapers could be downloaded here.

    We have also received 39 wallpaper submissions from our community members, currently available for download here

    AOSC OS Core 6

    AOSC OS will continue to evolve around a Core, and with Core 6, we expect to make some major changes in terms of version updates and build configurations.

    • Version updates, for example, GCC 8.2, and GNU C Library 2.28, etc.
    • GCC will (finally) update to the new stdc++ ABI, no longer using the aging GCC 4 compatibility ABI.
    • For AMD64, the default -mtune= parametre will now point to sandybridge instead of core2, which should marginally improve binary performance on newer AMD64 devices.

    AOSC OS Core 6 will come as a part of the next wave of major updates, expected in December.

    Changes to AOSC OS Updates and Branches

    Two of the most notable changes planned are the switch to a seasonal update model, and the introduction of a third system update branch/channel. Allow me to break it down a little bit…

    Seasonal Update Model

    This change originated largely originated from the time and scheduling trouble we have had since the last summer’s switch to monthly update cycles - as there’s simply too little time for us to make it happen (and too little of us, mind you), and we did not have a concrete policy on feature planning and freezing periods.

    With this new update model, the change is not limited to (obviously) switching to a seasonal schedule to provide stable updates. With this new model, extensive changes are made to how AOSC OS is maintained and updated - known patch releases (typically, z in a x.y.z version format) will be provided for “stable” channel users, a month-long freezing period will be set in place for the “testing” channel, a strategy to align update cycles with upstream LTS branch updates is also introduced.

    The “stable” channel will also become our focus of maintenance, which we find a bit “left behind” and starved of updates. While this tend not to break things - since security updates were practically the only updates pushed to this channel - the channel also suffered from lack of backported bugfix due to the aforementioned time and scheduling issues. A good example of this issue is best demonstrated in this severely delayed update cycle, where on the “stable” channel a graphical bug that prevented transparency to be displayed on Plasma panels on deviced with Intel GMA/Core Graphics - while this was addressed when libGLVND was introduced in the “testing” channel, though for the extensive changes required to introduce this library and the fact that we did not have enough time to investigate for a more minimalistic approach to fix this issue, this “fix” was then never backported to the “stable” channel.

    Users of the “testing” channel can also expect more stability in the future, as updates will go through a process of automatic testing and auditing before landing in this channel. This will be discussed in the section below.

    Introducing… The “Explosive” Channel

    This update channel is intended as a “No Man’s Land”, where immediate version updates are uploaded, and tested automatically, before landing in the “testing” channel.

    The “explosive” channel is also introduced to aid in feature freezing and release scheduling, as freezing for users of both channels will no longer hinder package updates - to reduce time waste, which could in turn hinder updates for the next cycle.

    The branch is also limited to the amd64 port of AOSC OS - due to computational limitations, we chose not to build any “explosive” updates on the other ports, they will in turn receive updates merged from the “explosive” branch, while build fixes for these ports will be merged back to “explosive”.

    Again, this channel is not intended to be used by anyone - not even the developers themselves. If you feel obliged to update with this channel, you are on your own.

    Security Updates

    On the question of security updates, we are looking to expand user notifications beyond GitHub issues and our mailing list. In the future, security advisories will be posted as a brief list here on the Portal.

    We are also seeking help on security vulnerable discovery, reporting, fixing, and testing - please do contact us at #aosc or at our Telegram group if you are interested.

    Implementing AOSC OS Optimisation Overlays

    This change was first discussed at AOSCC 2017 but was unfortunately never materialised, though overlay support has already been implemented in Autobuild3 and apt-gen-list.

    We will implement two overlays in the coming year - in the form of an extra repository:

    • AMD64 AVX2+ Overlay, for AVX2-enabled (Advanced Vector Extensions 2) devices, where most devices with Intel Haswell (4th Generation Core) processors or newer, and all AMD Ryzen are supported.
    • PowerPC 32-bit Big Endian G4+ Overlay, intended for PowerPC-based Apple Macintosh computers with a G4 processor or newer - where AltiVec is available.

    Both overlays aimed to produce higher performance binaries with optimisations for these newer, vector-based instruction sets (or SIMD) - this can provide performance uplift in certain applications, as benchmarked by Phoronix in the case of AVX2 in 2013.

    However, these optimisations may come with a price of higher power consumption and heat output - as briefly described in this Super User Post. In our current plan, users will be made aware if an overlay repository is available for their device(s), though it will not be enabled by default automatically. We plan to conduct more up-to-date performance, power consumption, and thermal testings in the future.

    LiveKit, RescueKit, and System Releases

    One of the longest running discussion among the AOSC OS users and developers has been the introduction of Live media and a system installer. For system installation and configuration, LiveKit will be similar to GParted Live - a lightweight toolkit environment.

    An installation program is also planned, inspired by the Which Wich order form - a single-page installation configurator. More details will come once the implementation process begins.

    RescueKit takes on roughly the same idea, though it is assembled as a RAM disk image that is bootable right from the GRUB menu - where users could boot into to repair their AOSC OS installation. Additionally, users will be able to package a backup of their current system as a system tarball, which could be in turn installed by the system installer, as discussed above.

    In the question of system releases, we plan on maintaining a seasonal update cycle, much like the aforementioned seasonal update model - with additional system releases made available in case of major security vulnerabilities.

    AOSC Bazaar

    In the coming months, a community-wide platform for goods and devices exchange will be implemented to provide friends in and around the community with community goods such as the legendary (?) AOSCC sticker packs and other souvenirs.

    Community developers could also request for compiling/testing/… devices on this platform, which will be provided by community members or other developers as a donation.

    What’s More?

    This has already been quite a long news post, so it might not be in the interest of information and transparency to keep extending this post. Here is a brief (and incomplete) list of things we’ve discussed and decided upon, in no particular order…

    • AOSC OS packaging repository (aosc-os-abbs and aosc-os-core) will begin to enforce source checksum, link accessibility, secure connections (HTTPS replacing HTTP and FTP, as much as possible).
    • Old forks found in our GitHub organisation will be cleaned up and archived.
    • AOSC OS’s KDE/Plasma variant will switch to the Arc KDE theme and a suitable icon theme.
    • Introduction of package variants for different system configurations.
    • Packages for legacy ports (specified as ARMv7, armel; and PowerPC 32-bit Big Endian, powerpc) will have minimalised configurations to remove features unsuitable or unapplicable to their performance and platform support.

    AOSCC 2019?

    With the lessons learned from AOSCC 2018, we will no longer hold community-wide poll on next year’s meeting location unless anyone could secure a venue before hand. Therefore, next year’s meeting location is not yet known, and hopefully we will get some choices in the near future.


    And with such, the re-cap of AOSCC 2018 is now complete, AOSCC 2018 had been quite a productive conference and will surely point a clearer direction for our community projects in the coming year. Look forward to see you again in AOSCC 2019!

    — Mingcong Bai

  • AOSCC 2018JULY 17, 2018

    It’s been nearly three months without any posting on the Portal - these have certainly been three busy months for us. Our community is still alive - just check out our GitHub Organisation… A more detailed “what’s-up” post will be made on a later date.

    But anyways, let’s get to the subject.

    AOSCC 2018, An Online Gathering

    Unfortunately, AOSCC 2018 will not be held in Wuhan as promised from our last AOSCC Re-cap due to some reasons out of our hands - and for this particular reason, we were unable to obtain any viable venues for our annual gathering/conference. Therefore, we will be doing this online instead - (hopefully) same discussions, same community-wide polls, and same fun.

    AOSCC 2018 will take place on an open Telegram Group, which is synchronised with an IRC channel (which we will have to make another post about, since we are not yet ready with that). While another Telegram Group will be made available to attendees to cast their votes.

    As most participants and contributors to AOSC projects are Chinese speakers, we will limit our discussion languages to Chinese Simplified and Chinese Traditional - while English could certainly be viable, it may still hinder your ability to participate in our discussions, as we would have to switch back and forth between languages.

    The 2018 online gathering and conferences will take place across two weekends, the weekend of July 21st, and the weekend of July 28th. A detailed schedule could be found on the event read-me file linked below - though be advised that all discussion sessions are organised according to the China Standard Time (UTC+8) considering the geographic distribution of community members, so do convert and plan ahead of time if you do not reside in this particular timezone.

    For more details about the organisation, scheduling, and rules of the gathering and conferences, please take a read at our AOSCC 2018 README. We look forward to see you this weekend!

    AOSC OS Core 6 Codename, and 2018 - 2019 Wallpapers

    As per tradition, we will be voting community-wide on a (meme-worthy) codename for the next AOSC OS Core release series, and also for a default wallpaper for the AOSC OS releases of the coming year. Here’s how you could participate…


    This year’s AOSC OS Core codename will be named after a word or two-word phrase headed by the letter “F” (as natural succession to Core 3’s “Cyanflame”, Core 4’s “Duang-Duang”, and the current Core 5’s “eMMC”). With additonal constraints…

    • Do not include any politically-charged keyword(s), topic(s), or opinion(s).
    • Do not include any profanity.
    • Do not nominate “F”, a single letter.
    • Do not include words or phrases that are copyrighted and disallowed to be used even on a non-commercial basis.

    While we do not necessarily block nominations, any codename submitted that violates any of the four rules above will be invalidated - and of course, you will be notified. You are free to nominate more than one codename.

    Otherwise, please submit your codename nomination by July 21st (UTC) at


    Next year’s (from this July to the next) AOSC OS system releases/distributions will apply a new set of wallpapers, and one that will be used as the default for all releases. If you would like to submit and compete for the “default” status…

    • Your submission must be your original creation and licensed accordingly to allow for redistribution with the system releases.
    • Your submission must be in nature of computer-aided design but not of original and non-stylised photography.
    • Your submission must not include any reference to politically-charged keyword(s), icons(s), or opinion(s).
    • You must not submit more than one design - though it could be a collection of variants of the same design, which will be treated as a collection.

    If you would like to submit your work to be a part of the default wallpapers collection…

    • Your submission(s) must be your original creation and licensed accordingly to allow for redistribution with the system releases.
    • Your submission(s) must not include any reference to politically-charged keyword(s), icons(s), or opinion(s).

    Any submission that violates any of the rules above will be invalidated, and you will be notified of this incident, along with our evaluation.

    Otherwise, please submit your wallpaper(s) by July 28th (UTC) at


    If you have any questions or concerns, please file an issue at our AOSCC GitHub repository.

    — Mingcong Bai

  • AOSC OS Spring Wave of Updates!APRIL 27, 2018

    I know… We are supposed to push out waves of updates every month, however, with a new constraint added to our already high workload-per-capita, a monthly wave was simply too difficult for our development capacity. However, there are certainly enough changes made to AOSC OS for you to be excited about.

    New Packages, and Dropped Packages

    Several quick statistics on package addition and removal…

    • 63 new packages were added.
    • 9 packages were dropped (removed from repository).

    Most of the new packages were not, unfortunately, added from user requests, but to serve new features added to AOSC OS - some of which new functions, some of which dependencies. I will get into more details… Now.

    Enhancements and Changes

    Most of the package changes made in this Wave are to catch up with upstream versions, and to ensure all architectures could enjoy as much of the new updates as possible. However, changes are also made to the desktop experience and system base in general.

    Major Component Updates

    • Linux Kernel is updated to the 4.15 branch, while the LTS (Long-Term Support) branch has switched from 4.9 to the 4.14 branch.
    • GNOME Desktop and applications have been updated to 3.28.
    • KDE Frameworks have been updated to 5.44.0, Plasma Desktop has been updated to 5.12.4, and KDE Applications to 17.12.3.
    • MATE Desktop has been updated to 1.20.
    • AOSC OS Core has been updated to 5.3.1, with component updates and added RISC-V architecture support.

    Desktop-Specific Changes

    Various MATE components have been updated and ported from Ubuntu MATE to further enhance desktop functionalities and user experience. Most notably of which was the introduction of MATE Tweak, which allows for easy management of desktop layouts, window manager alternatives, and individual enhancements like the MATE HUD (a keyboard-driven menu browsing system) and global application menu (as found with macOS and Unity 7).


    MATE Tweak, showing possible customisations with desktop layouts and extra panel features.

    Core Component Enhancements

    Package for GNU C Library (Glibc, glibc) now generates all locales at compile-time. Users should experience significantly faster update times, especially on performance constrained devices like older PowerPC hardware, ARM-based devices, etc. as the package will no longer generate locales as a post-installation configuration procedure - saving up to an hour.

    Performance Enhancements

    With Fontconfig updated to 2.13.0 and Michal Srb’s performance tweaks ( rebased to our Fontconfig package, applications like LibreOffice should see visible improvement to UI responsiveness. The new update also significantly improved efficiency of font cache generation (fc-cache), especially with larger font packages installed (Noto CJK Fonts, for instance), generation time reduced from several minutes to seconds - also avoiding freezing issues with GNOME when updating the Fontconfig package.

    We have also removed an old patch for Pixman which introduces gamma correction, as it caused larger LibreOffice Calc to become unresponsive when scrolling through larger spreadsheets.

    Architectural Ports

    As mentioned in our last Wave’s announcement in January, we were working on re-synchronising package updates between our various architectural ports. We are happy to report that this wave of updates are now available for all of our currently active ports:

    • AMD64, or x86_64 (amd64).
    • ARMv7 (armel) and AArch64 (arm64).
    • PowerPC 32/64-bit, Big Endian (powerpc and ppc64, respectively).


    Apple iBook G4, freshly updated to the Spring Wave.

    And so says “active”, as in this news, we regret to announce an indefinite freeze to our MIPS/Loongson ports due to lack of developer commitment and the software repositories for both 32 and 64 bit ports are now off-line. We will report back if we gain any more development support for these two ports.

    Oops, almost forgot, we have now started an experimental port to the RISC-V 64-bit architecture (specifically, rv64gc). We have now compiled all packages contained in a “Container” distribution variant - that is, a “Base” variant minus bootloader and Linux Kernel. Due to the lack of hardware available to our developers, we currently have no plan to expand this particular repository. Also, due to the experimental nature of this port, we have not yet differentiated stable and testing repositories for this port. The packaging architecture is denoted as riscv64.

    New Tarballs?

    We are looking to release new tarballs for all architectures in the coming month, along with updated ARM device images.


    A sneak-peek at our new project device, Nokia N900, running on mainline Linux Kernel.

    Next Wave, When?

    Assuming that the current development workload continues, you should expect the next wave of update before July - though still in debate, our update cycle may lengthen to a season (that is, normally, three months) instead of a monthly update.

    In the coming cycle, we will return our focus on user requests and further enhancement of user experience (or usability in general) on non-AMD64 ports, especially for users of ARM-based devices.

    Thanks for your continued support for AOSC OS, and we wish you productivity and enjoyment with AOSC OS.

    — Mingcong Bai

  • An Important (and Unfortunate) Project Update

  • New Tarball Releases!

  • Progress Report: AOSC OS, "Meltdown" and "Spectre"

  •



  • AOSC OS Packages

    A catalog of packages available for AOSC OS.

  • Community Repository

    Our community repository server, where AOSC OS installation medias, tarballs, packages, project documentation, etc. are stored.

  • Mirror Status

    Take a look at current mirror synchronization and availability information.

  • Mailing Lists

    Community mailing lists for discussions, advisories, and announcements.

  • IRC Channel

    Get in touch with the community.

  • Google+

    Learn about newest news and happenings in and around AOSC.

  • Hermes WebMail

    Our WebMail service for AOSC developers and contributors.

  • Public Clipboard

    Our public clipboard service (or pastebin) that you can use for all your clippy needs.