GNOME issueshttps://gitlab.gnome.org/groups/GNOME/-/issues2020-07-05T22:13:06Zhttps://gitlab.gnome.org/GNOME/gnome-nibbles/-/issues/48Release July tarballs2020-07-05T22:13:06ZIulian RaduRelease July tarballsSaturday, July 4th is the deadline for releasing the following tarballs:
* GNOME 3.37.3 unstable tarballs
* GNOME 3.36.4 stable tarballs
* GNOME 3.34.8 oldstable tarballs
We have changes for all 3 of these.
@arnaudb As you've made most...Saturday, July 4th is the deadline for releasing the following tarballs:
* GNOME 3.37.3 unstable tarballs
* GNOME 3.36.4 stable tarballs
* GNOME 3.34.8 oldstable tarballs
We have changes for all 3 of these.
@arnaudb As you've made most of the changes recently to the repository, is it OK if I make releases off of all 3 branches today? Or is there something we should get in before doing that? Thanks!2020-07-04https://gitlab.gnome.org/GNOME/gnome-mines/-/issues/50Longer left-click adds a marker to a field2021-05-02T16:13:57ZAndre KlapperLonger left-click adds a marker to a fieldIn my understanding,
* a left click uncovers a field.
* a right click adds a marker to a field.
However, in 3.36 on Wayland (Fedora 32), left-clicking on a field and not immediately releasing the mouse also adds a marker.
This is unw...In my understanding,
* a left click uncovers a field.
* a right click adds a marker to a field.
However, in 3.36 on Wayland (Fedora 32), left-clicking on a field and not immediately releasing the mouse also adds a marker.
This is unwanted and disruptive.GNOME 3.36Robert RothRobert Roth2020-08-01https://gitlab.gnome.org/GNOME/gnome-nibbles/-/issues/50Release August tarballs2020-08-08T12:01:19ZIulian RaduRelease August tarballsSaturday, August 8th is the deadline for releasing the following tarballs:
* GNOME 3.37.90 beta tarballs
* GNOME 3.36.5 stable tarballs
* GNOME 3.34.9 oldstable tarballsSaturday, August 8th is the deadline for releasing the following tarballs:
* GNOME 3.37.90 beta tarballs
* GNOME 3.36.5 stable tarballs
* GNOME 3.34.9 oldstable tarballsIulian RaduIulian Radu2020-08-08https://gitlab.gnome.org/GNOME/libdazzle/-/issues/55Release please2020-07-07T15:14:51ZMichael CatanzaroRelease pleaseHi, Builder 3.37.1 is not buildable because it depends on unreleased libdazzle 3.37.0+. Nobody can use that release. This is not urgent, so no need to worry about it this week, just please do a libdazzle release sometime before 3.37.90.
...Hi, Builder 3.37.1 is not buildable because it depends on unreleased libdazzle 3.37.0+. Nobody can use that release. This is not urgent, so no need to worry about it this week, just please do a libdazzle release sometime before 3.37.90.
CC @akitouni (release manager for 3.37.90 who will suffer the build failure if you forget to do this :)2020-08-08https://gitlab.gnome.org/GNOME/glade/-/issues/454Release please2020-07-14T11:27:55ZMichael CatanzaroRelease pleaseHi, we need a new Glade release since you dropped the autotools build. Please do a release prior to the 3.37.90 release deadline. Thanks!Hi, we need a new Glade release since you dropped the autotools build. Please do a release prior to the 3.37.90 release deadline. Thanks!Juan Pablo UgarteJuan Pablo Ugarte2020-08-08https://gitlab.gnome.org/GNOME/gnome-clocks/-/issues/123Release please2020-08-08T09:41:23ZMichael CatanzaroRelease pleaseWe need a new 3.37 release due to the libhandy dependency change. I'm going to work around this for 3.37.3, so it's not urgent, but please make sure to release a new tarball before the 3.37.90 tarball deadline. Thanks!We need a new 3.37 release due to the libhandy dependency change. I'm going to work around this for 3.37.3, so it's not urgent, but please make sure to release a new tarball before the 3.37.90 tarball deadline. Thanks!2020-08-08https://gitlab.gnome.org/GNOME/geary/-/issues/866(CVE-2020-24661) Invalid certificates not checked against locally pinned cert...2020-09-13T05:42:09ZDamian Poddebniak(CVE-2020-24661) Invalid certificates not checked against locally pinned certificates when GCR support not availableIf there is no read-write PKCS#11 store accessible by GCR (e.g, gnome-keyring-daemon is not installed, the gnome-keyring user PKCS#11 store is not installed or enabled, or gnome-keyring has dropped support for it, again), and an exceptio...If there is no read-write PKCS#11 store accessible by GCR (e.g, gnome-keyring-daemon is not installed, the gnome-keyring user PKCS#11 store is not installed or enabled, or gnome-keyring has dropped support for it, again), and an exception for an invalid TLS certificate has previously been allowed by the user for a specific server identity (e.g. the host name/IP address configured for the service), then subsequent connections to the same server identity will be accepted without comparing the certificate presented by the server with the certificate that was originally presented and pinned.
This allows e.g. MITM attacks against connections with the same configured identity when using invalid certificates.
This can be mitigated by any of: a) ensuring your system is [correctly configured](https://wiki.gnome.org/Apps/Geary/FAQ#Not_running_GNOME_3.3F) WRT PKCS#11 stores, b) not using invalid certificates (including self-signed certificates), c) not creating exceptions for invalid certificates.
----
Original description:
**Bug Summary**
Geary accepts self-signed X.509 certificates when doing STARTTLS (and probably also implicit TLS). This allows a Meddler-in-the-Middle (MitM) to steal emails and user credentials.
**Your installation**
* Geary version: geary-3.34.2 (NixOS)
* Installation method: nix-env -i
* Desktop environment: KDE
* Operating system and version: https://channels.nixos.org/nixos-20.03/latest-nixos-x86_64-linux.ova
* Email provider: not important
**Steps to reproduce**
1. Setup a local mailserver with an "invalid" X.509 certificate, i.e. self-signed, one where the root-CA is not trusted by the operating system, etc.
(I used mkcert, https://github.com/FiloSottile/mkcert)
2. Try to connect Geary to that mail server and observe that no warning is displayed.
**What did you expect to happen?**
Geary should under no circumstances just proceed with the connection. It must issue a warning and obtain user permission to do so. IMHO Thunderbird is a good example how to do it properly.
**Relevant logs and/or screenshots**
<!-- Do not remove the following line -->3.36.32020-08-27https://gitlab.gnome.org/GNOME/quadrapassel/-/issues/33The next shape is incorrect2020-09-14T22:43:46ZJohn WardThe next shape is incorrectWhen you see the next next shape it is incorrect.When you see the next next shape it is incorrect.John WardJohn Ward2020-09-12https://gitlab.gnome.org/GNOME/gnome-software/-/issues/1079Document use case statement for gnome-software2020-12-01T14:50:47ZPhilip WithnallDocument use case statement for gnome-softwareIn order to clarify decision making and roadmapping for gnome-software, it might help to have a clear statement of the use case for gnome-software, and for that to be documented (say, in the readme).
Here’s a suggestion to kick-start di...In order to clarify decision making and roadmapping for gnome-software, it might help to have a clear statement of the use case for gnome-software, and for that to be documented (say, in the readme).
Here’s a suggestion to kick-start discussion:
> gnome-software aims to allow users to easily find new apps for their computer, decide if those apps are what they need, and install them. It keeps users’ OS and apps up to date without them having to think about it, and gives them confidence that their system is up to date. It provides a place to query or prompt the user about pending updates if needed. It allows users to remove apps once they are no longer needed. It supports popular distributions, subject to those distributions maintaining their distro-specific integration code.
What do people think? I’d like to get this sorted out in the next week so that subsequent decisions can be made on the basis of it.Philip WithnallPhilip Withnall2020-10-15https://gitlab.gnome.org/GNOME/gnome-software/-/issues/1078Examine roadmaps for distros’ use of gnome-software2020-12-18T18:17:55ZPhilip WithnallExamine roadmaps for distros’ use of gnome-softwareFor the purposes of planning any possible architectural or maintenance changes to gnome-software, it would be useful to know how different distros use gnome-software, and how that usage is likely to change in the next 1-3 years (the peri...For the purposes of planning any possible architectural or maintenance changes to gnome-software, it would be useful to know how different distros use gnome-software, and how that usage is likely to change in the next 1-3 years (the period of time over which we’re going to have to maintain the next iteration of gnome-software).
(Distro list from [here](https://distrowatch.com/dwres.php?resource=major), up to date as of October 2020, plus Endless OS and Silverblue, and Alpine because they’ve proposed an apk plugin.)
List below updated on 2020-10-15 to take comments below into account.
Distributions which use gnome-software
===
* Alpine Linux/Postmarket OS ([more](https://gitlab.gnome.org/GNOME/gnome-software/-/issues/1078#note_930487) [detail](https://gitlab.gnome.org/GNOME/gnome-software/-/issues/1078#note_930586)): uses apk (not apt!) for everything; flatpak is available if you install `gnome-software-plugin-flatpak`
* Arch Linux: uses pacman (via packagekit), seemingly for everything; flatpak is available, but not preferred (aiui)
* Debian: uses apt for everything; flatpak is available, but not preferred (aiui)
* Endless OS: uses OSTree for the base OS (via eos-updater), flatpak for UI apps; this is unlikely to change in the next few years
* Fedora ([more detail](https://gitlab.gnome.org/GNOME/gnome-software/-/issues/1078#note_930424)): uses dnf for everything, flatpak apps are shipped in default install and going to be increasingly used in future, but there’s no roadmap for obsoleting package-based apps
* Mageia ([more](https://gitlab.gnome.org/GNOME/gnome-software/-/issues/1078#note_930447) [detail](https://gitlab.gnome.org/GNOME/gnome-software/-/issues/1078#note_930588)): uses dnf (via packagekit) for everything; flatpak is available but no repos are configured by default; no plans to prefer anything other than dnf in the future
* MX Linux: uses apt, seemingly for everything
* openSUSE ([more](https://gitlab.gnome.org/GNOME/gnome-software/-/issues/1078#note_930450) [detail](https://gitlab.gnome.org/GNOME/gnome-software/-/issues/1078#note_930588)): uses zypp (via packagekit) for everything; flatpak is available, but not preferred and no repos are configured by default; this is unlikely to change in the next few years
* RHEL/CentOS: uses dnf for OS, flatpak for faster-moving UI apps; this is unlikely to change in the next few years
* Silverblue: uses OSTree for the base OS, rpm-ostree for layering additional RPM packages on top, and flatpak for UI apps; [explicit assertion that ‘package layering is generally done from the command line’](https://docs.fedoraproject.org/en-US/fedora-silverblue/getting-started/#package-layering); this is likely to evolve in the next few years, but the direction is uncertain
* Ubuntu: uses apt + snaps, emphasis seems to be shifting to preferring snaps for apps; apt for OS updates; uses gnome-software rebranded as ‘Ubuntu Software’
Distributions which *don’t* use gnome-software
===
(For info only)
* Gentoo: uses portage for everything; flatpak is available, but not preferred (aiui)
* Linux Mint: uses apt + flatpaks, emphasis seems to be shifting to preferring flatpaks for apps; apt for OS updates
* Pop!_OS ([more detail](https://gitlab.gnome.org/GNOME/gnome-software/-/issues/1078#note_933543)): uses Pop!_Shop, which is derived from Elementary’s AppCenter.
I am only really familiar with Endless OS, Fedora and Debian, so I may have made mistakes here — especially with the longer-term outlook for different distributions. Feedback and corrections welcome. In a week’s time, I’ll collate the data we have and draw some conclusions about things like the need for offline updates or which plugins we need to support.Philip WithnallPhilip Withnall2020-10-15https://gitlab.gnome.org/GNOME/gnome-software/-/issues/513Source is says "installed" instead of the proper source2020-10-08T15:32:47ZAndreas NilssonSource is says "installed" instead of the proper source![Screenshot_from_2018-11-01_18-34-56](/uploads/1eb2cf26d37c2681f3f9aa2dcbd8d4f0/Screenshot_from_2018-11-01_18-34-56.png)
This happens only for content from Fedora. For content from flathub it correctly says "flathub".
Version: 3.30.5 ...![Screenshot_from_2018-11-01_18-34-56](/uploads/1eb2cf26d37c2681f3f9aa2dcbd8d4f0/Screenshot_from_2018-11-01_18-34-56.png)
This happens only for content from Fedora. For content from flathub it correctly says "flathub".
Version: 3.30.5 on Fedora 292020-10-22https://gitlab.gnome.org/GNOME/gnome-software/-/issues/184Duplicate entries shown for installed snaps2020-10-12T03:51:07ZBugzillaDuplicate entries shown for installed snaps## Submitted by Robert Ancell `@robert.ancell`
Assigned to **Robert Ancell `@robert.ancell`**
**[Link to original bug (#783772)](https://bugzilla.gnome.org/show_bug.cgi?id=783772)**
## Description
Two entries are shown for install...## Submitted by Robert Ancell `@robert.ancell`
Assigned to **Robert Ancell `@robert.ancell`**
**[Link to original bug (#783772)](https://bugzilla.gnome.org/show_bug.cgi?id=783772)**
## Description
Two entries are shown for installed snaps - one for the .desktop file and one for the snap. We need to combine these.2020-10-23https://gitlab.gnome.org/GNOME/gnome-calendar/-/issues/653Migration of gnome-calendar-list to GNOME Discourse instance2023-02-11T03:03:58ZOlav VittersMigration of gnome-calendar-list to GNOME Discourse instanceHello,
I'm writing to you as I think you (as maintainer) are the owner of the mailing list https://gitlab.gnome.org/GNOME/gnome-calculator/-/issues/186.
We've set up https://discourse.gnome.org a year and a half ago, as part of an atte...Hello,
I'm writing to you as I think you (as maintainer) are the owner of the mailing list https://gitlab.gnome.org/GNOME/gnome-calculator/-/issues/186.
We've set up https://discourse.gnome.org a year and a half ago, as part of an attempt at making the GTK mailing list more friendly to newcomers. This experiment seems to have proven itself well enough, and has since expanded to other territories as well. As such, we believe it is time to make the same switch for most of our mailing lists. The discussion around the move is held at https://gitlab.gnome.org/GNOME/Initiatives/-/issues/18 .
This means that the https://gitlab.gnome.org/GNOME/gnome-calculator/-/issues/186 mailing list will be archived in favour of continued discussion at GNOME's Discourse instance. No need to worry that this will mess with your workflow: it is still possible to get notifications by email by subscribing to the appropriate tags and/or posts. You can also still reply by e-mail if you prefer. Just like before, it's also possible to receive a general weekly digest.
The proposed closure of this mailing list will be on: Oct 30th, 2020 (or earlier if acceptable by you)
As a subscriber of this mailing list please create an account on https://discourse.gnome.org/. It's unfortunately not possible to automatically migrate the existing subscribers to Discourse. In case you wonder what will happen to the current mailing list after the closure date: the archives will remain public though you won't be able to subscribe or send emails to the current list.
For https://gitlab.gnome.org/GNOME/gnome-calculator/-/issues/186 the new discussions would take place in the Applications category on Discourse using the (to be created) 'gnome-calendar' tag (or maybe: calendar?).
For further information on Discourse, please see the following topics:
* https://discourse.gnome.org/t/interacting-with-discourse-via-email/46
* https://discourse.gnome.org/t/tags-and-watching/94
Do you agree with moving the list over to Discourse?
On behalf of the Discourse migration volunteers.
Cheers,
Olav2020-10-30https://gitlab.gnome.org/GNOME/gnome-calculator/-/issues/186Migration of gnome-calculator-list to GNOME Discourse instance2020-10-31T10:37:45ZOlav VittersMigration of gnome-calculator-list to GNOME Discourse instanceHello,
I'm writing to you as I think you (as maintainer) are the owner of the mailing list https://mail.gnome.org/archives/gnome-calculator-list/.
We've set up https://discourse.gnome.org a year and a half ago, as part of an attempt at...Hello,
I'm writing to you as I think you (as maintainer) are the owner of the mailing list https://mail.gnome.org/archives/gnome-calculator-list/.
We've set up https://discourse.gnome.org a year and a half ago, as part of an attempt at making the GTK mailing list more friendly to newcomers. This experiment seems to have proven itself well enough, and has since expanded to other territories as well. As such, we believe it is time to make the same switch for most of our mailing lists. The discussion around the move is held at https://gitlab.gnome.org/GNOME/Initiatives/-/issues/18 .
This means that the https://mail.gnome.org/archives/gnome-calculator-list/ mailing list will be archived in favour of continued discussion at GNOME's Discourse instance. No need to worry that this will mess with your workflow: it is still possible to get notifications by email by subscribing to the appropriate tags and/or posts. You can also still reply by e-mail if you prefer. Just like before, it's also possible to receive a general weekly digest.
The proposed closure of this mailing list will be on: Oct 30th, 2020 (or earlier if acceptable by you)
As a subscriber of this mailing list please create an account on https://discourse.gnome.org/. It's unfortunately not possible to automatically migrate the existing subscribers to Discourse. In case you wonder what will happen to the current mailing list after the closure date: the archives will remain public though you won't be able to subscribe or send emails to the current list.
For https://mail.gnome.org/archives/gnome-calculator-list/ the new discussions would take place in the Applications category on Discourse using the (to be created) 'gnome-calculator' tag (or maybe: 'calculator'?).
For further information on Discourse, please see the following topics:
* https://discourse.gnome.org/t/interacting-with-discourse-via-email/46
* https://discourse.gnome.org/t/tags-and-watching/94
Do you agree with moving the list over to Discourse?
On behalf of the Discourse migration volunteers.
Cheers,
OlavGNOME 402020-10-30https://gitlab.gnome.org/GNOME/meld/-/issues/508Migration of meld-list to GNOME Discourse instance2020-11-01T05:04:24ZOlav VittersMigration of meld-list to GNOME Discourse instanceHello,
I'm creating this issue for the maintainer of meld; the owner of the mailing list https://mail.gnome.org/archives/meld-list/.
We've set up https://discourse.gnome.org a year and a half ago, as part of an attempt at making the GT...Hello,
I'm creating this issue for the maintainer of meld; the owner of the mailing list https://mail.gnome.org/archives/meld-list/.
We've set up https://discourse.gnome.org a year and a half ago, as part of an attempt at making the GTK mailing list more friendly to newcomers. This experiment seems to have proven itself well enough, and has since expanded to other territories as well. As such, we believe it is time to make the same switch for most of our mailing lists. The discussion around the move is held at https://gitlab.gnome.org/GNOME/Initiatives/-/issues/18 .
This means that the https://mail.gnome.org/archives/meld-list/ mailing list will be archived in favour of continued discussion at GNOME's Discourse instance. No need to worry that this will mess with your workflow: it is still possible to get notifications by email by subscribing to the appropriate tags and/or posts. You can also still reply by e-mail if you prefer. Just like before, it's also possible to receive a general weekly digest.
The proposed closure of this mailing list will be on: Oct 30th, 2020 (or earlier if acceptable by you)
As a subscriber of this mailing list please create an account on https://discourse.gnome.org/. It's unfortunately not possible to automatically migrate the existing subscribers to Discourse. In case you wonder what will happen to the current mailing list after the closure date: the archives will remain public though you won't be able to subscribe or send emails to the current list.
For https://mail.gnome.org/archives/meld-list/ the new discussions would take place in the Applications category on Discourse using the (to be created) 'meld' tag.
For further information on Discourse, please see the following topics:
* https://discourse.gnome.org/t/interacting-with-discourse-via-email/46
* https://discourse.gnome.org/t/tags-and-watching/94
Do you agree with moving the list over to Discourse?
On behalf of the Discourse migration volunteers.
Cheers, Olav2020-10-30https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/1158Migration of gnomecc-list to GNOME Discourse instance2023-10-22T08:30:19ZOlav VittersMigration of gnomecc-list to GNOME Discourse instanceHello,
I'm creating this issue for the maintainer of gnome-control-center; the owner of the mailing list https://mail.gnome.org/archives/gnomecc-list/.
We've set up https://discourse.gnome.org a year and a half ago, as part of an attem...Hello,
I'm creating this issue for the maintainer of gnome-control-center; the owner of the mailing list https://mail.gnome.org/archives/gnomecc-list/.
We've set up https://discourse.gnome.org a year and a half ago, as part of an attempt at making the GTK mailing list more friendly to newcomers. This experiment seems to have proven itself well enough, and has since expanded to other territories as well. As such, we believe it is time to make the same switch for most of our mailing lists. The discussion around the move is held at https://gitlab.gnome.org/GNOME/Initiatives/-/issues/18 .
This means that the https://mail.gnome.org/archives/gnomecc-list/ mailing list will be archived in favour of continued discussion at GNOME's Discourse instance. No need to worry that this will mess with your workflow: it is still possible to get notifications by email by subscribing to the appropriate tags and/or posts. You can also still reply by e-mail if you prefer. Just like before, it's also possible to receive a general weekly digest.
The proposed closure of this mailing list will be on: Oct 30th, 2020 (or earlier if acceptable by you)
As a subscriber of this mailing list please create an account on https://discourse.gnome.org/. It's unfortunately not possible to automatically migrate the existing subscribers to Discourse. In case you wonder what will happen to the current mailing list after the closure date: the archives will remain public though you won't be able to subscribe or send emails to the current list.
For https://mail.gnome.org/archives/gnomecc-list/ the new discussions would take place in the Applications and Platform categories on Discourse using the (to be created) 'control-center' tag (other suggestions welcome!).
For further information on Discourse, please see the following topics:
* https://discourse.gnome.org/t/interacting-with-discourse-via-email/46
* https://discourse.gnome.org/t/tags-and-watching/94
Do you agree with moving the list over to Discourse?
On behalf of the Discourse migration volunteers.
Cheers,
Olav2020-10-30https://gitlab.gnome.org/GNOME/Initiatives/-/issues/23Migration of gnome-bugsquad mailing list to GNOME Discourse instance2020-11-02T13:41:55ZOlav VittersMigration of gnome-bugsquad mailing list to GNOME Discourse instanceHello Andre,
I'm writing to you as I think you're the owner of the mailing list https://mail.gnome.org/archives/gnome-bugsquad/.
We've set up https://discourse.gnome.org a year and a half ago, as part of an attempt at making the GTK ma...Hello Andre,
I'm writing to you as I think you're the owner of the mailing list https://mail.gnome.org/archives/gnome-bugsquad/.
We've set up https://discourse.gnome.org a year and a half ago, as part of an attempt at making the GTK mailing list more friendly to newcomers. This experiment seems to have proven itself well enough, and has since expanded to other territories as well. As such, we believe it is time to make the same switch for most of our mailing lists. The discussion around the move is held at https://gitlab.gnome.org/GNOME/Initiatives/-/issues/18 .
This means that the https://mail.gnome.org/archives/gnome-bugsquad/ mailing list will be archived in favour of continued discussion at GNOME's Discourse instance. No need to worry that this will mess with your workflow: it is still possible to get notifications by email by subscribing to the appropriate tags and/or posts. You can also still reply by e-mail if you prefer. Just like before, it's also possible to receive a general weekly digest.
The proposed closure of this mailing list will be on: Oct 30th, 2020 (or earlier if acceptable by you)
As a subscriber of this mailing list please create an account (GNOME LDAP will work) on https://discourse.gnome.org/. It's unfortunately not possible to automatically migrate the existing subscribers to Discourse. In case you wonder what will happen to the current mailing list after the closure date: the archives will remain public though you won't be able to subscribe or send emails to the current list.
For https://mail.gnome.org/archives/gnome-bugsquad/ I'm not sure where the new discussions should take place. Maybe ask for a new Teams section on Discourse? Or maybe in the Community section, though that feels a bit weird?
Anyway, for further information on Discourse, please see the following topics:
* https://discourse.gnome.org/t/interacting-with-discourse-via-email/46
* https://discourse.gnome.org/t/tags-and-watching/94
Do you agree with moving the list over to Discourse?
On behalf of the Discourse migration volunteers.
Cheers,
Olav2020-10-30https://gitlab.gnome.org/GNOME/gedit/-/issues/366Migration of gedit-list to GNOME Discourse instance2024-03-12T18:40:02ZOlav VittersMigration of gedit-list to GNOME Discourse instanceHello,
I'm creating this issue for the owner of the mailing list https://mail.gnome.org/archives/gedit-list/.
We've set up https://discourse.gnome.org a year and a half ago, as part of an attempt at making the GTK mailing list more fri...Hello,
I'm creating this issue for the owner of the mailing list https://mail.gnome.org/archives/gedit-list/.
We've set up https://discourse.gnome.org a year and a half ago, as part of an attempt at making the GTK mailing list more friendly to newcomers. This experiment seems to have proven itself well enough, and has since expanded to other territories as well. As such, we believe it is time to make the same switch for most of our mailing lists. The discussion around the move is held at https://gitlab.gnome.org/GNOME/Initiatives/-/issues/18 .
This means that the https://mail.gnome.org/archives/gedit-list/ mailing list will be archived in favour of continued discussion at GNOME's Discourse instance. No need to worry that this will mess with your workflow: it is still possible to get notifications by email by subscribing to the appropriate tags and/or posts. You can also still reply by e-mail if you prefer. Just like before, it's also possible to receive a general weekly digest.
The proposed closure of this mailing list will be on: Oct 30th, 2020 (or earlier if acceptable by you)
As a subscriber of this mailing list please create an account on https://discourse.gnome.org/. It's unfortunately not possible to automatically migrate the existing subscribers to Discourse. In case you wonder what will happen to the current mailing list after the closure date: the archives will remain public though you won't be able to subscribe or send emails to the current list.
For https://mail.gnome.org/archives/gedit-list/ the new discussions would take place in the Applications category on Discourse using the (to be created) 'gedit' tag.
For further information on Discourse, please see the following topics:
* https://discourse.gnome.org/t/interacting-with-discourse-via-email/46
* https://discourse.gnome.org/t/tags-and-watching/94
Do you agree with moving the list over to Discouse?
On behalf of the Discourse migration volunteers.
Cheers, Olav2020-10-30https://gitlab.gnome.org/GNOME/gitg/-/issues/303Migration of gitg-list to GNOME Discourse instance2023-01-09T03:14:16ZOlav VittersMigration of gitg-list to GNOME Discourse instanceHello,
I'm creating this issue for the owner of the mailing list https://mail.gnome.org/archives/gitg-list/.
We've set up https://discourse.gnome.org a year and a half ago, as part of an attempt at making the GTK mailing list more frie...Hello,
I'm creating this issue for the owner of the mailing list https://mail.gnome.org/archives/gitg-list/.
We've set up https://discourse.gnome.org a year and a half ago, as part of an attempt at making the GTK mailing list more friendly to newcomers. This experiment seems to have proven itself well enough, and has since expanded to other territories as well. As such, we believe it is time to make the same switch for most of our mailing lists. The discussion around the move is held at https://gitlab.gnome.org/GNOME/Initiatives/-/issues/18 .
This means that the https://mail.gnome.org/archives/gitg-list/ mailing list will be archived in favour of continued discussion at GNOME's Discourse instance. No need to worry that this will mess with your workflow: it is still possible to get notifications by email by subscribing to the appropriate tags and/or posts. You can also still reply by e-mail if you prefer. Just like before, it's also possible to receive a general weekly digest.
The proposed closure of this mailing list will be on: Oct 30th, 2020 (or earlier if acceptable by you)
As a subscriber of this mailing list please create an account on https://discourse.gnome.org/. It's unfortunately not possible to automatically migrate the existing subscribers to Discourse. In case you wonder what will happen to the current mailing list after the closure date: the archives will remain public though you won't be able to subscribe or send emails to the current list.
For https://mail.gnome.org/archives/gitg-list/ the new discussions would take place in the Applications category on Discourse using the (to be created) 'gitg' tag.
For further information on Discourse, please see the following topics:
* https://discourse.gnome.org/t/interacting-with-discourse-via-email/46
* https://discourse.gnome.org/t/tags-and-watching/94
Do you agree with moving the list over to Discouse?
On behalf of the Discourse migration volunteers.
Cheers, Olav2020-10-30https://gitlab.gnome.org/GNOME/gnome-internet-radio-locator/-/issues/25Migration of girl-list to GNOME Discourse instance2023-11-12T07:58:57ZOlav VittersMigration of girl-list to GNOME Discourse instanceHello,
I'm creating this issue for the owner of the mailing list https://mail.gnome.org/archives/girl-list/.
We've set up https://discourse.gnome.org a year and a half ago, as part of an attempt at making the GTK mailing list more frie...Hello,
I'm creating this issue for the owner of the mailing list https://mail.gnome.org/archives/girl-list/.
We've set up https://discourse.gnome.org a year and a half ago, as part of an attempt at making the GTK mailing list more friendly to newcomers. This experiment seems to have proven itself well enough, and has since expanded to other territories as well. As such, we believe it is time to make the same switch for most of our mailing lists. The discussion around the move is held at https://gitlab.gnome.org/GNOME/Initiatives/-/issues/18 .
This means that the https://mail.gnome.org/archives/girl-list/ mailing list will be archived in favour of continued discussion at GNOME's Discourse instance. No need to worry that this will mess with your workflow: it is still possible to get notifications by email by subscribing to the appropriate tags and/or posts. You can also still reply by e-mail if you prefer. Just like before, it's also possible to receive a general weekly digest.
The proposed closure of this mailing list will be on: Oct 30th, 2020 (or earlier if acceptable by you)
As a subscriber of this mailing list please create an account on https://discourse.gnome.org/. It's unfortunately not possible to automatically migrate the existing subscribers to Discourse. In case you wonder what will happen to the current mailing list after the closure date: the archives will remain public though you won't be able to subscribe or send emails to the current list.
For https://mail.gnome.org/archives/girl-list/ the new discussions would take place in the Applications category on Discourse using the (to be created) 'girl' tag (better suggestion welcome!).
For further information on Discourse, please see the following topics:
* https://discourse.gnome.org/t/interacting-with-discourse-via-email/46
* https://discourse.gnome.org/t/tags-and-watching/94
Do you agree with moving the list over to Discouse?
On behalf of the Discourse migration volunteers.
Cheers, Olav2020-10-30