mirror of
https://github.com/LCTT/TranslateProject.git
synced 2025-02-28 01:01:09 +08:00
删除旧闻
This commit is contained in:
Xingyu Wang
parent
ea7713f8af
commit
86a92f297e
@ -1,109 +0,0 @@
|
||||
[#]: subject: "GNOME 43 Plans to Introduce Redesigned Quick Settings"
|
||||
[#]: via: "https://www.debugpoint.com/gnome-43-quick-settings/"
|
||||
[#]: author: "Arindam https://www.debugpoint.com/author/admin1/"
|
||||
[#]: collector: "lkxed"
|
||||
[#]: translator: " "
|
||||
[#]: reviewer: " "
|
||||
[#]: publisher: " "
|
||||
[#]: url: " "
|
||||
|
||||
GNOME 43 Plans to Introduce Redesigned Quick Settings
|
||||
======
|
||||
The upcoming GNOME 43 release changes the system tray menu completely. Here’s how it looks.
|
||||
|
||||
![][0]
|
||||
|
||||
Among all the attractive changes coming to GNOME 43, the redesigned quick settings menu is the most visible revamp. The quick settings or system tray menu remained the same for a long time. There were minor tweaks, such as earlier consolidation of menu items. But we never got to experience a complete overhaul before.
|
||||
|
||||
![Complex Quick Settings View – GNOME 43][1]
|
||||
|
||||
### GNOME 43 Quick Settings
|
||||
|
||||
So, GNOME 43 quick settings look, menu items are changing to look below.
|
||||
|
||||
![GNOME 43 quick settings – side-by-side basic view][2]
|
||||
|
||||
Firstly, the individual menu items are now more visible with “pill-shaped” buttons. These buttons perform dual functions when applied. You click on them to enable/disable the function (i.e. quick toggles). Also, if you click on the small arrow, you get additional options.
|
||||
|
||||
Secondly, the ‘pill-buttons’ appearance indicates whether the option is enabled or disabled by changing its colour.
|
||||
|
||||
The submenu, which opens up after you bring up more settings for a function, can draw itself on top of the earlier menu items. This eliminates another additional click.
|
||||
|
||||
Another interesting change which I feel is super helpful is the active indicator of privacy-related functions. For example, if an app currently uses your mic or you are having a screen-sharing session with your colleagues/friends, the quick settings give you additional colour identification to appraise you.
|
||||
|
||||
In addition, the batter indicator is also coming up as more descriptive inside the quick settings menu with an icon and the available power capacity.
|
||||
|
||||
### When the quick settings would be available?
|
||||
|
||||
The merge request is currently open ([MR 2392][3]) as of publishing this page.
|
||||
|
||||
What does that mean?
|
||||
|
||||
It means that GNOME devs and contributors will test and review the changes in design and functionality. So, I guess in a few weeks, it might get merged.
|
||||
|
||||
GNOME 43 release candidate and hard code freeze due a month from now, i.e. September 3rd, 2022. If all goes well, it should be available for you to test via GNOME nightly OS.
|
||||
|
||||
Here are the mock-up images and sample videos (credit to the GNOME team) to treat your eyes which I organized in a single place.
|
||||
|
||||
A caution note is that all these are still subject to change in the final release.
|
||||
|
||||
* ![Quick toggles -2][3a]
|
||||
* ![Quick toggles -1][3b]
|
||||
* ![Complex Quick Settings View - GNOME 43][3c]
|
||||
* ![GNOME 43 quick settings - side-by-side view][3d]
|
||||
|
||||
![quick-toggles-4][4]
|
||||
|
||||
![Quick toggles -2][5]
|
||||
|
||||
![Quick toggles -1][6]
|
||||
|
||||
![Complex Quick Settings View - GNOME 43][7]
|
||||
|
||||
![GNOME 43 quick settings - side-by-side view][8]
|
||||
|
||||
![][9]
|
||||
|
||||
### Does it resemble anything?
|
||||
|
||||
Do you remember when I [reviewed dahliaOS earlier][10] based on Google’s Fuchsia operating system? When I first saw these mock-ups, I remember they looked somewhat similar to dahliaOS’s tray menu. See below. Although it’s at the bottom and looks a little wider – you can see the resemblance.
|
||||
|
||||
![System Tray of dahliaOS][11]
|
||||
|
||||
Anywho.
|
||||
|
||||
### Thoughts?
|
||||
|
||||
If you ask me, I guess it’s refreshing and probably a long due. An overall nice and intuitive design requires no additional learning from the new users. Finally, GNOME 43 is shaping to be a powerful release after all.
|
||||
|
||||
**Now you**: What do you think about this design change that impacts all the users? Let’s discuss in the comment box.
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: https://www.debugpoint.com/gnome-43-quick-settings/
|
||||
|
||||
作者：[Arindam][a]
|
||||
选题：[lkxed][b]
|
||||
译者：[译者ID](https://github.com/译者ID)
|
||||
校对：[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出
|
||||
|
||||
[a]: https://www.debugpoint.com/author/admin1/
|
||||
[b]: https://github.com/lkxed
|
||||
[0]: https://www.debugpoint.com/wp-content/uploads/2022/08/gnome43-head-q.jpg
|
||||
[1]: https://www.debugpoint.com/wp-content/uploads/2022/08/Complex-Quick-Settings-View-GNOME-43.jpg
|
||||
[2]: https://www.debugpoint.com/wp-content/uploads/2022/08/GNOME-43-quick-settings-side-by-side-view.jpg
|
||||
[3]: https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/2392
|
||||
[3a]: https://www.debugpoint.com/wp-content/uploads/2022/08/Quick-toggles-2-1600x950.jpg
|
||||
[3b]: https://www.debugpoint.com/wp-content/uploads/2022/08/Quick-toggles-1-1600x877.jpg
|
||||
[3c]: https://www.debugpoint.com/wp-content/uploads/2022/08/Complex-Quick-Settings-View-GNOME-43.jpg
|
||||
[3d]: https://www.debugpoint.com/wp-content/uploads/2022/08/GNOME-43-quick-settings-side-by-side-view-545x320.jpg
|
||||
[4]: https://www.debugpoint.com/wp-content/uploads/2022/08/quick-toggles-4-1024x1024.png
|
||||
[5]: https://www.debugpoint.com/wp-content/uploads/2022/08/Quick-toggles-2-1024x608.jpg
|
||||
[6]: https://www.debugpoint.com/wp-content/uploads/2022/08/Quick-toggles-1-1024x561.jpg
|
||||
[7]: https://www.debugpoint.com/wp-content/uploads/2022/08/Complex-Quick-Settings-View-GNOME-43-1024x576.jpg
|
||||
[8]: https://www.debugpoint.com/wp-content/uploads/2022/08/GNOME-43-quick-settings-side-by-side-view.jpg
|
||||
[9]: https://www.debugpoint.com/wp-content/uploads/2022/08/quicksettings-submenu.webm
|
||||
[10]: https://www.debugpoint.com/dahlia-os-alpha/
|
||||
[11]: https://www.debugpoint.com/wp-content/uploads/2022/05/System-Tray.jpg
|
||||
@ -1,80 +0,0 @@
|
||||
[#]: subject: "Linux Kernel 6.0 is Likely the Next Version Upgrade With Initial Rust Code"
|
||||
[#]: via: "https://news.itsfoss.com/linux-kernel-6-0-reveal/"
|
||||
[#]: author: "Anuj Sharma https://news.itsfoss.com/author/anuj/"
|
||||
[#]: collector: "lkxed"
|
||||
[#]: translator: " "
|
||||
[#]: reviewer: " "
|
||||
[#]: publisher: " "
|
||||
[#]: url: " "
|
||||
|
||||
Linux Kernel 6.0 is Likely the Next Version Upgrade With Initial Rust Code
|
||||
======
|
||||
Linux Kernel’s next upgrade is going to be 6.0, instead of Linux 5.20. That’s what Linus Torvalds is going with. Sounds good!
|
||||
|
||||
![linux kernel][1]
|
||||
|
||||
You might be aware of the fact that Linus Torvalds used an Apple MacBook hardware to release [Linux Kernel 5.19][2].
|
||||
|
||||
But, the news wasn’t limited to one interesting observation.
|
||||
|
||||
Linus Torvalds also mentioned at the end of the [release announcement][3] that he might call the next version upgrade of Linux Kernel as 6.0.
|
||||
|
||||
### Linux Version Numbers Decoded: Why 6.0?
|
||||
|
||||
So, why the change in version numbers for an upgrade?
|
||||
|
||||
To understand the versioning scheme, let us take an example of **Linux Kernel 5.18.5** (that’s what I’m running on my system).
|
||||
|
||||
If you want to check the Linux Kernel version on your system, simply head to the terminal and type in:
|
||||
|
||||
```
|
||||
uname -r
|
||||
```
|
||||
|
||||
* The first number ‘5’ represents the major version
|
||||
* The second number, ’18’ represents the series of minor updates.
|
||||
* The third number, ’15,’ represents the patch version
|
||||
|
||||
The Linux Kernel usually follows the [Semantic Versioning][4] (A versioning system used in open source software).
|
||||
|
||||
However, when it comes to major upgrades, the developers seem to avoid numbers that seem too big.
|
||||
|
||||
So, instead of going with Linux Kernel 5.20, it will just be Linux Kernel 6.0 (or Linux 6.0). There’s no hard rule on this, only when Linus Torvalds gets worried with the number, we have a shorter version number.
|
||||
|
||||
Linus Torvalds mentioned the same for changing the version number in the mailing list:
|
||||
|
||||
> I’ll likely call it 6.0 since I’m starting to worry about getting confused by big numbers again.
|
||||
|
||||
### New Features Coming to Linux 6.0
|
||||
|
||||
If you are curious, here are some features that might be a part of the Linux Kernel 6.0 release:
|
||||
|
||||
* Inclusion of Rust code (early phase)
|
||||
* Real-time Kernel building support
|
||||
* New Hardware support
|
||||
* Usual Improvements to various Filesystems
|
||||
* Scheduler changes
|
||||
|
||||
Most of the anticipated feature additions are likely to be technical changes, so you may not have enough to get excited about as an end-user.
|
||||
|
||||
But, it should be huge if the initial Rust code arrives with the next Linux Kernel upgrade.
|
||||
|
||||
*So, what do you think about the upcoming Linux Kernel 6.0? Do you wish to see Rust kernel code land?*
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: https://news.itsfoss.com/linux-kernel-6-0-reveal/
|
||||
|
||||
作者：[Anuj Sharma][a]
|
||||
选题：[lkxed][b]
|
||||
译者：[译者ID](https://github.com/译者ID)
|
||||
校对：[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出
|
||||
|
||||
[a]: https://news.itsfoss.com/author/anuj/
|
||||
[b]: https://github.com/lkxed
|
||||
[1]: https://news.itsfoss.com/wp-content/uploads/2022/08/linux-kernel-6-0.jpg
|
||||
[2]: https://news.itsfoss.com/linux-kernel-5-19-release/
|
||||
[3]: https://lore.kernel.org/all/CAHk-=wgrz5BBk=rCz7W28Fj_o02s0Xi0OEQ3H1uQgOdFvHgx0w@mail.gmail.com/
|
||||
[4]: https://semver.org/
|
||||
@ -1,92 +0,0 @@
|
||||
[#]: subject: "GitLab Backtracks On Deleting Inactive Projects by Free Users"
|
||||
[#]: via: "https://news.itsfoss.com/gitlab-inactive-projects-policy/"
|
||||
[#]: author: "Ankush Das https://news.itsfoss.com/author/ankush/"
|
||||
[#]: collector: "lkxed"
|
||||
[#]: translator: " "
|
||||
[#]: reviewer: " "
|
||||
[#]: publisher: " "
|
||||
[#]: url: " "
|
||||
|
||||
GitLab Backtracks On Deleting Inactive Projects by Free Users
|
||||
======
|
||||
GitLab almost turned into a villain we never expected with this new policy change. What are your thoughts on it?
|
||||
|
||||
![gitlab][1]
|
||||
|
||||
Right after Microsoft acquired GitHub, many users migrated to GitLab and other [GitHub alternatives][2].
|
||||
|
||||
Considering many popular open-source projects can be found on GitLab, it has a good reputation with developers and project maintainers.
|
||||
|
||||
**Update, Aug 5:** Originally reported by [The Register][3], GitLab planned to remove inactive projects by free user accounts. Now, GitLab seems to have [dropped the idea][4] after netizens expressed their concerns about it.
|
||||
|
||||
> We discussed internally what to do with inactive repositories. \
|
||||
> We reached a decision to move unused repos to object storage. \
|
||||
> Once implemented, they will still be accessible but take a bit longer to access after a long period of inactivity.
|
||||
|
||||
[@gitlab's tweet][5]
|
||||
|
||||
### GitLab Will Move Inactive Repos to Object Storage
|
||||
|
||||
GitLab shared a statement sharing that they will no longer delete inactive projects. Instead, they will move those projects to object storage, making them slower to access.
|
||||
|
||||
GitLab’s Co-founder and CEO, **Sid Sijbrandij**, further clarified that those projects would remain visible to everyone.
|
||||
|
||||
> Archived projects [https://t.co/4rOeJHNilh][6] is a user activated state that signals intent. We're not sure yet but very likely the storage type used is orthogonal to that. Our current plan for object storage [https://t.co/fLRl2TY744][7] would keep the repos visible to everyone.
|
||||
|
||||
[@sytses's tweet][8]
|
||||
|
||||
As per *The Register*, sources who requested anonymity revealed that a new policy was scheduled to come into force in September 2022, which would have resulted in removing several inactive projects on GitLab.
|
||||
|
||||
This move would have helped GitLab save up to **$1 million** yearly in hosting costs.
|
||||
|
||||
Now that they will no longer be deleting those projects, will they save hosting costs by moving projects to object storage?
|
||||
|
||||
*The Register* mentions that there have been internal discussions about the possibility of moving unused repos to object storage, where GitLab’s cost of maintaining it may increase due to required redundant backups.
|
||||
|
||||
**So, what changed in GitLab’s policy now?** Without official clarification by GitLab, we remain clueless.
|
||||
|
||||
### More Decisions to Make
|
||||
|
||||
GitLab hasn’t made any public statements regarding the entire situation. But, **GitLab’s CEO** mentioned the following when it comes to identifying inactive projects:
|
||||
|
||||
> We’re not sure yet. Probably all write operations would keep a project active, creating an issue, a merge request, pushing changes to a branch, etc. We might also keep it active as long as people are doing read operations such as cloning, forking, etc.
|
||||
|
||||
While we no longer have to worry about deleted projects, more clarity on this will be added to this in the coming days.
|
||||
|
||||
### A Valid Excuse: Was it?
|
||||
|
||||
GitLab deleting projects to save disk space was a big deal.
|
||||
|
||||
The entire point of offering free services was to let users host code on their platform, whether the project remains active or not. One can agree that everyone should encourage projects to have some activity. But why should that be a requirement to host your code on a platform that promises free services?
|
||||
|
||||
A developer can simply choose to make a simple tool/program and keep it at GitLab for anyone to find and fork it, with no aim to maintain/update it. Sometimes, the developer may no longer be available or have access to add activity to their projects.
|
||||
|
||||
**For example**, we have plenty of GitHub projects that haven’t seen any activity for years, but people still rely on it, fork it, and use it.
|
||||
|
||||
So, I’m sure you will come across several hundred projects that do not have any activity but are helpful or have a working fork.
|
||||
|
||||
**I think** GitLab, as a company with a good reputation shouldn’t have even thought about such an idea, to begin with.
|
||||
|
||||
*What do you think about GitLab’s original report on auto-deletion policy? Is object storage the perfect alternative for saving old repos? Kindly let me know your thoughts in the comments down below.*
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: https://news.itsfoss.com/gitlab-inactive-projects-policy/
|
||||
|
||||
作者：[Ankush Das][a]
|
||||
选题：[lkxed][b]
|
||||
译者：[译者ID](https://github.com/译者ID)
|
||||
校对：[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出
|
||||
|
||||
[a]: https://news.itsfoss.com/author/ankush/
|
||||
[b]: https://github.com/lkxed
|
||||
[1]: https://news.itsfoss.com/wp-content/uploads/2022/08/gitlab-backdrop-warning.jpg
|
||||
[2]: https://itsfoss.com/github-alternatives/
|
||||
[3]: https://www.theregister.com/2022/08/04/gitlab_data_retention_policy/
|
||||
[4]: https://www.theregister.com/2022/08/05/gitlab_reverses_deletion_policy/
|
||||
[5]: https://twitter.com/gitlab/status/1555325376687226883?ref_src=twsrc%5Etfw
|
||||
[6]: https://docs.gitlab.com/ee/user/project/settings/
|
||||
[7]: https://gitlab.com/groups/gitlab-org/-/epics/4959
|
||||
[8]: https://twitter.com/sytses/status/1555344675761819648?ref_src=twsrc%5Etfw
|
||||
Loading…
Reference in New Issue
Block a user