Re: Moving final mailman lists over to discourse
On Sat, Oct 01, 2022 at 12:53:15PM -0500, meg ford via devel-announce-list wrote: > Travel Committee didn’t have any activity during the pandemic travel bans, > but we are using it again now that we’re back to finding travel. Can you > please migrate it? > Sure - you've already got a category on Discourse for the travel committee, and people can email travel-commit...@discourse.gnome.org :) Neil ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Moving final mailman lists over to discourse
On Thu, 2022-09-29 at 14:18 -0300, Rafael Fontenelle wrote: > Hi Neil, > > Reading your list-of-lists.txt attachment I noticed that some mailing > lists used by language teams in Damned Lies are in the "Lists to > close" category. These mailing lists are used by Damned Lies to send > notifications of translation activities. If closed there's a chance > it > could break Damned Lies notifications, and I don't think Damned Lies > is not able to notify Discourse. Damned Lies can indeed notify Discourse - there's an email interface if needed, which is what the release team ended up doing. However, I think a better idea is to rethink the workflow a little... I'll follow up on the issue :) > > I recommend double-checking that with GTP coordinators. > > The language team lists I found in the text file are: There's a couple missing from your list (like -cyr) and a couple that haven't seen postings since 2009 (like -latin), but yes. Let's continue over on https://gitlab.gnome.org/Infrastructure/damned-lies/-/issues/325 :) Neil -- Neil McGovern Executive Director, The GNOME Foundation ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Moving final mailman lists over to discourse
Hi folks, On Mon, 2022-08-22 at 14:36 +0100, Neil McGovern wrote: > > As mentioned about three years ago, there's a desire to retire > > mailman > > and its dependencies on python2. Discussion is now happening on > > discourse.gnome.org. > > > > Over the coming month, I'll be going through each list that > > remains, > > seeing if they're still alive and moving them over [0] > > I've gone through every mailing list that we host, and broadly split them into two categories - lists that can be closed and ones that should be migrated to discourse. For those which should close, they've had very low activity (in some cases, zero...). For those that should move, I've made sure that there's tags in place so people can filter for a specific subject if they want. Please see the attached. For both, the archives will be preserved, but they won't accept or distribute any new mail after the end of October. Again, as a reminder, if you have any automation that's posting to mailing lists, let me know (Thanks to the release team for having already done so :P). Thanks, Neil -- Neil McGovern Executive Director, The GNOME Foundation Lists to close - gnome-outreachy-list outreachy-admins-list flattr-list fundraising gnome-hispano-board-list intern-alumni-list interns-list internships-admin opw-admins-list opw-list opw-opportunities-list beast ekiga-list engagement-committee-private f-spot-list fonts girl-list glom-devel-list gnome-ar-list gnome-asia-list gnome-ca-list gnome-cl-list gnome-cn-list gnome-color-manager-list gnome-cs-list gnome-cy-list gnome-cyr gnome-db-list gnome-de gnome-devel-list gnome-devtools gnome-doc-devel-list gnome-el-list gnome-eo-list gnome-es-list gnome-et-list gnome-flashback-list gnome-fr-list gnome-fy-list gnome-ge-list gnome-gl-list gnome-hispano-list gnome-hu-list gnome-in-list gnome-ir-list gnome-l10n-ta-list gnome-latin-list gnome-list gnome-lk-list gnome-network-list gnome-nl-list gnome-no gnome-office-list gnome-os-list gnome-pe-list gnome-pk-list gnome-power-manager-list gnome-pt_br-list gnome-se-list gnome-sk-list gnome-themes-list gnome-turk gnome-tw-list gnome-us-list gnome-vi-list gnome-web-list gnomecc-list goocanvas-list grilo-list gtk-doc-list gtk-osx-devel-list gtk-osx-users-list gtk-vnc-list gtranslator-list guadec-organization guadec-papers guadec-volunteers-list gugmasters-list gvfs-list language-bindings latexila-list legal-list Legal-updates-list libgee-list libpeas-list libsigc-list Mailman nautilus-list orca-es-list outreach-list outreachy-opportunities-list planner-list python-hackers-list rust-list sfbay-social-list travel-committee wm-spec-list Lists to move to Discourse - asia-summit-list balsa-list brasero-list cheese-list desktop-devel-list devel-announce-list dia-list distributor-list docs-feedback easytag-list eog-list evince-list evolution-hackers evolution-list foundation-announce foundation-list games-list gegl-developer-list gimp-developer-list gimp-docs-list gimp-gui-list gimp-user-list gimp-web-list gitg-list gmime-devel-list gnome-accessibility-devel gnome-accessibility-list gnome-doc-list gnome-i18n gnome-it-list gnome-shell-extensions-list gnome-women-list gnote-list gnumeric-list gthumb-list gtk-perl-list gtkmm-list libchamplain-list libsoup-list libxmlplusplus-list mc mc-devel networkmanager-list orca-list ostree-list planner-dev-list xml xslt ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Moving final mailman lists over to discourse
Hi folks, As mentioned about three years ago, there's a desire to retire mailman and its dependencies on python2. Discussion is now happening on discourse.gnome.org. Over the coming month, I'll be going through each list that remains, seeing if they're still alive and moving them over [0] The main large ones that remain are foundation-(announce-)list and desktop-(announce-)list. If you have any automatic email senders for those, please let me know so we can either update your scripts to use the API, or just update the email address. Thanks, Neil [0] See https://discourse.gnome.org/t/how-to-move-a-mailing-list-to-discourse/1642/7 -- Neil McGovern Executive Director, The GNOME Foundation ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Matrix IRC bridge considered harmful
On Wed, 2020-02-12 at 20:21 +0100, Alexandre Franke wrote: > > My concern would be the "federal" nature of matrix where people > > don't need a > > gnome.org specific chat account to join a room. Whilst there are a > > lot of > > arguments for this I'm increasingly convinced it's an anti-feature > > especially > > if we want to enforce CoC (which, of course, we do) > > > That was a concern for Mozilla too. I don’t know the details, but > they have a solution for that it seems. See e.g. the Community safety > section in the [annoucement]( > https://discourse.mozilla.org/t/synchronous-messaging-at-mozilla-the-decision/50620 > ). > The solution they're using is federation turned off. Neil -- Neil McGovern Executive Director, The GNOME Foundation ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: up-for-grabs.net for newcomers initiative
On Wed, 2019-10-02 at 03:23 +0200, Andre Klapper wrote: > On Wed, 2019-10-02 at 01:40 +0530, Gaurav Agrawal wrote: > > Up for grabs can give us more reach in that regard, because here > > people will not search for organizations but rather on their skills > > and related areas. > > In my understanding, up-for-grabs.net requires projects to use the > proprietary Github.com service for issue tracking. > GNOME does not use Github for issue tracking but gitlab.gnome.org. > Please correct me if I misunderstood. > I don't believe it requires Github, especially given that Gitlab itself has listings on there that point to their own gitlab instance :) Neil -- Neil McGovern Executive Director, The GNOME Foundation ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Annual Gitlab Statistics, anyone?
On Tue, 2019-03-26 at 10:57 +0100, Jose Manrique Lopez de la Fuente via desktop-devel-list wrote: > Hi, > > I've added gjs. Please, check it here: > http://46.101.128.86:5601 > > I hope to have some time during following days to fix some issues. > That's really rather nice, thanks for looking in to it! Neil -- Neil McGovern Executive Director, The GNOME Foundation ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Managing Google API key secrets
On Mon, 2019-03-25 at 12:43 -0400, Michael Terry wrote: > Another interesting tidbit from that page is that Google prefers that > you send the user to the system browser for the consent screen, > rather than loading it in-app in a GtkWebKit frame or whatever > (presumably so that the user knows they're actually on a Google page > and the app isn't phishing them for their Google password). I think this is currently one of the sticking points I'm having when going through the verification process - there's not really the understanding of what a native 'app' is. So thanks for that clarity! Neil -- Neil McGovern Executive Director, The GNOME Foundation ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Extension review
On Sun, 2019-03-24 at 21:43 -0400, Sriram Ramkrishna wrote: > Talk to me and Neil. We have a general idea on what we want done .. > Just to confirm though, is this for working on the extension review infrastructure, or actually doing reviews? That may change the answer :) Neil -- Neil McGovern Executive Director, The GNOME Foundation ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Clarifications regarding GNOME Online Accounts
On Mon, 2019-02-18 at 09:52 -0600, mcatanz...@gnome.org wrote: > On Sun, Feb 17, 2019 at 7:20 AM, Sam Thursfield > wrote: > > 3. continue distributing a "GNOME key" with the source code, and > > hope > > that Google don't mind > > I suggest we don't continue to willfully violate Google's terms of > service now that the issue has been brought to our attention. The > only > reasonable option seems to be to shut down our Google integration. > Not > just from g-o-a, but also the Safe Browsing support in Epiphany. > Hi Michael, I think first, I'll reach out to Google folks to see if this can be adjusted. I suspect it's an oversight - a lot of the issues that are being brought up seem to infer that this is being thought of as a webapp centric use, rather than how we do it natively. Neil -- Neil McGovern Executive Director, The GNOME Foundation ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
