Language Selection

English French German Italian Portuguese Spanish

GNOME Project Welcomes Canonical and Ubuntu to GNOME Foundation Advisory Board

Filed under
GNOME
Ubuntu

With the release of the Ubuntu 17.10 (Artful Aardvark) operating system, Canonical replaced their Unity user interface with the GNOME desktop environment, and now they're looking to sponsor the project by becoming a member of the Advisory Board.

Among some powerful members of GNOME Foundation's Advisory Board, we can mention Google, FSF (Free Software Foundation), and Linux Foundation. And now, Canonical will also support the GNOME Project by providing funding and expert consultation.

Read more

Also: Ubuntu Linux-maker Canonical joins GNOME Foundation advisory board

More on "Canonical Joins The GNOME Advisory Board"

  • Canonical Joins The GNOME Advisory Board
  • Canonical Has Joined the GNOME Foundation Advisory Board

    It’s a timely and logical appointment what with the recent Ubuntu 17.10 release being the first version of Ubuntu to ship with the GNOME Shell desktop environment by default.

    But what is the GNOME Advisory Board?

    Well, GNOME explain it as “…a body of stakeholder organizations and companies who support the GNOME Project by providing funding and expert consultation.”

    Other members of the board include Google, The Document Foundation, Red Hat and SUSE.

Original

  • Canonical joins GNOME Foundation Advisory Board

    As you’re no doubt aware, the default Ubuntu desktop is now running GNOME Shell following the 17.10 release and so we naturally have a great deal of interest in the plans and direction of the GNOME project. The best way for us to get more involved in the future of GNOME is to become a member of the Advisory Board, and so, I’m happy to announce that we are now fully signed up members.

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

More in Tux Machines

GitLab Web IDE

  • GitLab Web IDE Goes GA and Open-Source in GitLab 10.7
    GitLab Web IDE, aimed to simplify the workflow of accepting merge requests, is generally available in GitLab 10.7, along with other features aimed to improve C++ and Go code security and improve Kubernets integration. The GitLab Web IDE was initially released as a beta in GitLab 10.4 Ultimate with the goal of streamlining the workflow to contribute small fixes and to resolve merge requests without requiring the developer to stash their changes and switch to a new branch locally, then back. This could be of particular interest to developers who have a significant number of PRs to review, as well as to developers starting their journey with Git.
  • GitLab open sources its Web IDE
    GitLab has announced its Web IDE is now generally available and open sourced as part of the GitLab 10.7 release. The Web IDE was first introduced in GitLab Ultimate 10.4. It is designed to enable developers to change multiple files, preview Markdown, review changes and commit directly within a browser. “At GitLab, we want everyone to be able to contribute, whether you are working on your first commit and getting familiar with git, or an experienced developer reviewing a stack of changes. Setting up a local development environment, or needing to stash changes and switch branches locally, can add friction to the development process,” Joshua Lambert, senior product manager of monitoring and distribution at GitLab, wrote in a post.

Record Terminal Activity For Ubuntu 16.04 LTS Server

At times system administrators and developers need to use many, complex and lengthy commands in order to perform a critical task. Most of the users will copy those commands and output generated by those respective commands in a text file for review or future reference. Of course, “history” feature of the shell will help you in getting the list of commands used in the past but it won’t help in getting the output generated for those commands. Read
more

Linux Kernel Maintainer Statistics

As part of preparing my last two talks at LCA on the kernel community, “Burning Down the Castle” and “Maintainers Don’t Scale”, I have looked into how the Kernel’s maintainer structure can be measured. One very interesting approach is looking at the pull request flows, for example done in the LWN article “How 4.4’s patches got to the mainline”. Note that in the linux kernel process, pull requests are only used to submit development from entire subsystems, not individual contributions. What I’m trying to work out here isn’t so much the overall patch flow, but focusing on how maintainers work, and how that’s different in different subsystems. Read more

Security: Updates, Trustjacking, Breach Detection

  • Security updates for Monday
  • iOS Trustjacking – A Dangerous New iOS Vulnerability
    An iPhone user's worst nightmare is to have someone gain persistent control over his/her device, including the ability to record and control all activity without even needing to be in the same room. In this blog post, we present a new vulnerability called “Trustjacking”, which allows an attacker to do exactly that. This vulnerability exploits an iOS feature called iTunes Wi-Fi sync, which allows a user to manage their iOS device without physically connecting it to their computer. A single tap by the iOS device owner when the two are connected to the same network allows an attacker to gain permanent control over the device. In addition, we will walk through past related vulnerabilities and show the changes that Apple has made in order to mitigate them, and why these are not enough to prevent similar attacks.
  • What Is ‘Trustjacking’? How This New iOS Vulnerability Allows Remote Hacking?
    This new vulnerability called trustjacking exploits a convenient WiFi feature, which allows iOS device owners to manage their devices and access data, even when they are not in the same location anymore.
  • Breach detection with Linux filesystem forensics
    Forensic analysis of a Linux disk image is often part of incident response to determine if a breach has occurred. Linux forensics is a different and fascinating world compared to Microsoft Windows forensics. In this article, I will analyze a disk image from a potentially compromised Linux system in order to determine the who, what, when, where, why, and how of the incident and create event and filesystem timelines. Finally, I will extract artifacts of interest from the disk image. In this tutorial, we will use some new tools and some old tools in creative, new ways to perform a forensic analysis of a disk image.