Welcome to This Week in Solus, Installation #7. As you may (or may not) have noticed, this blog post is in a different location. As of this blog post, these installations are official. If you want to see previous installs, you can read them by going here.
Core Team Roles
We have some project announcements to make this week. Roles and titles have been provided to core team members.
These roles will accompany the coding and package development that is existing currently.
Some formal rules and guidelines have been set within the Solus Project. We have also posted the guidelines of the team so the community can understand what our process is for enforcing guidelines.
You may view these community guidelines by going to this page.
As Budgie 2.0 is in development, the status of Budgie will remain a talking point of these weekly updates. As of this week, Budgie is currently pending some cleanup and merging of the codebase. There has been some issues discovered in the current system, such as notification applet crashes, and as a result those issues will need to be addressed as well.
As we work on moving to the GNOME 3.18 stack, there has been a multitude of issues that have been addressed. Currently we are working on addressing an issue where keyboard layouts in Mutter do not function as intended.
There currently is no news to report on Steam and multilib (32-bit libraries). Currently other aspects of the Solus operating system are being addressed, which you can read about in the Current Work section of this blog post.
We are currently in the process of creating debug information (-dbginfo) packages for software in the Solus operating system. These debug information packages will enable us to debug software under Solus and we plan to have a system to automatically generate stack traces for coredumps uploaded to our system. This will enable us to track and address software issues more easily. In the event they are found to not be Solus-specific, such issues will be reported to upstream package providers for fixing.
Currently, the driver management graphical tool, referred to as DoFlicky, is taking priority. We have recently enabled the NVIDIA 304xx legacy driver, with 340xx and AMD planned as well. We will have full automatic driver detection and installation.
The following package updates are broken down based on contributor and within each contributor section, a “new package” and “updated package” sections (where it applies). Not everything that landed is included, just some major items.