Re: Announcement: this mailing list will be retired by the end of Oct 2022
On Fri, Oct 21, 2022 at 01:32:37PM -0400, Gregory Leblanc via foundation-list wrote: > Foundation members, > > I know that this has been coming for a while but as a former contributor > who generally just wants to keep tabs on the major changes and > announcements, this particular change will mean that I probably don't keep > tabs on anything. There's no obvious replacement on 'discourse.gnome.org'. > The closest I can see is a 'community' category which is entirely too > broad. Entering the 'foundation-announce' tag, which is how I interpreted > the information below, yields nothing. Given the immense talents involved > with Gnome, I'm sad that no one came up with a better solution than simply > dropping foundation-announce. Have you tried the "announcement" tag? https://discourse.gnome.org/tags/c/community/8/announcement Neil ___ foundation-list mailing list foundation-list@gnome.org https://mail.gnome.org/mailman/listinfo/foundation-list
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 ___ foundation-list mailing list foundation-list@gnome.org https://mail.gnome.org/mailman/listinfo/foundation-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 -- devel-announce-list mailing list devel-announce-list@gnome.org https://mail.gnome.org/mailman/listinfo/devel-announce-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 ___ foundation-list mailing list foundation-list@gnome.org https://mail.gnome.org/mailman/listinfo/foundation-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 -- devel-announce-list mailing list devel-announce-list@gnome.org https://mail.gnome.org/mailman/listinfo/devel-announce-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 ___ foundation-announce mailing list foundation-announce@gnome.org https://mail.gnome.org/mailman/listinfo/foundation-announce
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 ___ foundation-list mailing list foundation-list@gnome.org https://mail.gnome.org/mailman/listinfo/foundation-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: Decision making in Debian
On Thu, Jul 14, 2022 at 09:15:37AM +, Stefano Rivera wrote: > Hi Dashamir (2022.07.14_08:31:51_+) > > But I have seen recently a very long discussion thread in a mailing list, > > with pros and cons about introducing Discourse as an alternative or > > replacement to mailing lists, and the result of the discussion was not > > clear at all (at least I could not understand it). I am also not sure what > > happened with the Discourse initiative, was it finally tried or not. > > That was less of a discussion, and more of someone who is new to our > community making a noise about how we are doing things wrong and should > be doing them differently. I think most people roll their eyes and mark > the thread as read. Many suggestions like this have been discussed > before, many times, without any concrete actions coming out of them. > As the person who was driving the Discourse initiative, I do take slight objection to being described as someone who was new to the community, or characterised as "making a noise". In fact, the reason that things did not progress was due to the massive amount of stop energy at trying to improve our processes. I simply gave up in engaging with Debian rather than trying to push for what I (still) believe will improve engagement with new maintainers. Neil signature.asc Description: PGP signature
Re: Board of Directors Candidacy - Sammy Fung
On Tue, 2022-06-07 at 03:51 +0800, Sammy Fung wrote: > After my 10-year involvement at GNOME Asia Committee, I suggest that > the young outreach is an important task to sustain the GNOME and open > source community. By connecting global GNOME & F/OSS contributors and > local open source communities, it enables that more students will > become the future contributors in the GNOME and open source > communities. > Just for the record, I second Sammy's candidacy. Neil -- Neil McGovern Executive Director, The GNOME Foundation ___ foundation-list mailing list foundation-list@gnome.org https://mail.gnome.org/mailman/listinfo/foundation-list
Re: Running for the GNOME Foundation Board of Directors.
On Wed, 2022-06-01 at 14:05 -0700, Jeremy Allison via foundation- announce wrote: > Hi all at the GNOME Foundation, > > I would respectfully like to submit my candidacy for the GNOME > Foundation Board of Directors. I am the co-creator of the Samba Free > Software Project, and am employed as Samba maintainer by Google's > Open > Source Programs Office. > I also second this nomination. Neil -- Neil McGovern Executive Director, The GNOME Foundation ___ foundation-list mailing list foundation-list@gnome.org https://mail.gnome.org/mailman/listinfo/foundation-list
Bug#1010571: shotwell: No pubishing plugins available
Package: shotwell Version: 0.30.15-1 Severity: important Dear Maintainer, When trying to publish some photos, shotwell complains that there aren't any compatable publishing plugins enabled. Looking in Edit -> Preferences -> Plugins, none appear. From the terminal, the following errors occur: (shotwell:257710): GLib-GIO-CRITICAL **: 16:14:53.825: g_file_get_child: assertion '!g_path_is_absolute (name)' failed (shotwell:257710): GLib-GIO-CRITICAL **: 16:14:53.825: g_file_get_child: assertion 'G_IS_FILE (file)' failed (shotwell:257710): GLib-GIO-CRITICAL **: 16:14:53.825: g_file_get_child: assertion 'G_IS_FILE (file)' failed L 257710 2022-05-04 16:14:53 [CRT] plugins_search_for_plugins: assertion 'G_TYPE_CHECK_INSTANCE_TYPE (dir, g_file_get_type ())' failed https://bugs.launchpad.net/ubuntu/+source/shotwell/+bug/1969439 may also hold some clues. Thanks, Neil -- Package-specific info: -- System Information: Debian Release: bookworm/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.17.0-1-amd64 (SMP w/8 CPU threads; PREEMPT) Kernel taint flags: TAINT_USER, TAINT_WARN Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages shotwell depends on: ii dbus-user-session [default-dbus-session-bus] 1.14.0-1 ii dbus-x11 [dbus-session-bus] 1.14.0-1 ii dconf-cli 0.40.0-3 ii libc6 2.33-7 ii libcairo-gobject2 1.16.0-5 ii libcairo2 1.16.0-5 ii libexif12 0.6.24-1 ii libgcr-base-3-1 3.40.0-4 ii libgcr-ui-3-1 3.40.0-4 ii libgdata220.18.1-2 ii libgdk-pixbuf-2.0-0 2.42.8+dfsg-1 ii libgee-0.8-2 0.20.5-2 ii libgexiv2-2 0.14.0-1 ii libglib2.0-0 2.72.1-1 ii libgphoto2-6 2.5.27-1 ii libgphoto2-port12 2.5.27-1 ii libgstreamer-plugins-base1.0-01.20.1-1 ii libgstreamer1.0-0 1.20.1-1 ii libgtk-3-03.24.33-1 ii libgudev-1.0-0237-2 ii libjson-glib-1.0-01.6.6-1 ii libpango-1.0-01.50.6+ds-2 ii libpangocairo-1.0-0 1.50.6+ds-2 ii libraw20 0.20.2-2 ii librsvg2-common 2.52.5+dfsg-3+b1 ii libsoup2.4-1 2.74.2-3 ii libsqlite3-0 3.38.2-1 ii libunity9 7.1.4+19.04.20190319-6 ii libwebkit2gtk-4.0-37 2.36.0-3+b1 ii libxml2 2.9.13+dfsg-1+b1 ii shotwell-common 0.30.15-1 shotwell recommends no packages. shotwell suggests no packages. -- no debconf information -- signature.asc Description: PGP signature
Re: General Resolution: Statement regarding Richard Stallman's readmission to the FSF board result
On Sun, Apr 18, 2021 at 06:58:49PM +0100, Barak A. Pearlmutter wrote: > If the winning option in an election is part of a preference cycle, > then it (by definition) has the property that there exists some other > option that a majority of the voters preferred. In some elections that > is unavoidable: we need to pick one DPL, and if they're in a cycle so > be it; if there's a tie we can just toss a coin. But in others, like > the RMS GR, it seems like it would be a rather bad property and we'd > be better off treating it as FD and trying again later. > For info, we use cloneproof Schwartz sequential dropping to resolve these ties. The simple version is that we work out the cycle, and then drop the lowest margin, in this case the 1, so "Debian will not issue a pubilc statement" would still win. A full description is at https://en.wikipedia.org/wiki/Schulze_method Neil signature.asc Description: PGP signature
Re: FSF in the advisory board
On Fri, 2021-03-26 at 11:11 -0300, Germán Poo-Caamaño wrote: > Hi, > > The Gnome Foundation signed the letter calling the board of the Free > Software Foundation to step down and for Richard Stallman to be > removed > from all leadership position. The same letter that also asks to stop > supporting the FSF. > > Is the board considering removing the FSF from the advisory board? > > For consistency, I think we should do it temporarily. > I can't speak for the board, but my view is that we should wait until the FSF has had time for a fuller response before formally making any changes to the advisory board. In the mean time though, I've hidden the FSF logo from our website in case that is seen as an endorsement. Neil -- Neil McGovern Executive Director, The GNOME Foundation ___ foundation-list mailing list foundation-list@gnome.org https://mail.gnome.org/mailman/listinfo/foundation-list
Re: General resolution: ratify https://github.com/rms-open-letter/rms-open-letter.github.io
Please, as a previous vote runner, can we only have 5 seconders rather than the (currently) 82 DDs who have signed it so far? On Wed, Mar 24, 2021 at 01:54:16PM -0700, Steve Langasek wrote: > Text of GR > > The Debian Project co-signs the statement regarding Richard Stallman's > readmission to the FSF seen at > https://github.com/rms-open-letter/rms-open-letter.github.io/blob/main/index.md. > > The text of this statement is given below. > > Richard M. Stallman, frequently known as RMS, has been a dangerous force in > the free software community for a long time. He has shown himself to be > misogynist, ableist, and transphobic, among other serious accusations of > impropriety. These sorts of beliefs have no place in the free software, > digital rights, and tech communities. With his recent reinstatement to the > Board of Directors of the Free Software Foundation, we call for the entire > Board of the FSF to step down and for RMS to be removed from all leadership > positions. > > We, the undersigned, believe in the necessity of digital autonomy and the > powerful role user freedom plays in protecting our fundamental human rights. > In order to realize the promise of everything software freedom makes > possible, there must be radical change within the community. We believe in > a present and a future where all technology empowers – not oppresses – > people. We know that this is only possible in a world where technology is > built to pay respect to our rights at its most foundational levels. While > these ideas have been popularized in some form by Richard M. Stallman, he > does not speak for us. We do not condone his actions and opinions. We do > not acknowledge his leadership or the leadership of the Free Software > Foundation as it stands today. > > There has been enough tolerance of RMS’s repugnant ideas and behavior. We > cannot continue to let one person ruin the meaning of our work. Our > communities have no space for people like Richard M. Stallman, and we will > not continue suffering his behavior, giving him a leadership role, or > otherwise holding him and his hurtful and dangerous ideology as acceptable. > > We are calling for the removal of the entire Board of the Free Software > Foundation. These are people who have enabled and empowered RMS for years. > They demonstrate this again by permitting him to rejoin the FSF Board. It > is time for RMS to step back from the free software, tech ethics, digital > rights, and tech communities, for he cannot provide the leadership we need. > We are also calling for Richard M. Stallman to be removed from all > leadership positions, including the GNU Project. > > We urge those in a position to do so to stop supporting the Free Software > Foundation. Refuse to contribute to projects related to the FSF and RMS. > Do not speak at or attend FSF events, or events that welcome RMS and his > brand of intolerance. We ask for contributors to free software projects to > take a stand against bigotry and hate within their projects. While doing > these things, tell these communities and the FSF why. > > We have detailed several public incidents of RMS's behavior. Some of us > have our own stories about RMS and our interactions with him, things that > are not captured in email threads or on video. We hope you will read what > has been shared and consider the harm that he has done to our community and > others. > > End Text of GR I second this GR. Neil -- signature.asc Description: PGP signature
Re: Infrastructure | Gitlab reorganisation (#333)
Neil McGovern commented: Let's ping the sysadmins here explicitly: cc: @averi @barthalion -- Reply to this email directly or view it on GitLab: https://gitlab.gnome.org/Infrastructure/Infrastructure/-/issues/333#note_841118 You're receiving this email because of your account on gitlab.gnome.org. ___ gnome-infrastructure mailing list gnome-infrastructure@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-infrastructure
Re: Infrastructure | cloud.gnome.org - calendar reminder emails aren't sent (#15)
Neil McGovern commented: This was deployed in nextcloud 17.0.1, so it should now work. -- Reply to this email directly or view it on GitLab: https://gitlab.gnome.org/Infrastructure/Infrastructure/-/issues/15#note_775916 You're receiving this email because of your account on gitlab.gnome.org. ___ gnome-infrastructure mailing list gnome-infrastructure@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-infrastructure
Re: Testing Discourse for Debian - Moderation concepts
On Wed, Apr 15, 2020 at 03:40:40PM +0200, Ansgar wrote: > On Wed, 2020-04-15 at 08:56 +0100, Neil McGovern wrote: > > The point of the trust levels is to distribute the moderation. Whatever > > metric we come up with, it will involve a certain amount of actually > > using the site, and engaging with the community. > > Looking at some topics on meta.discourse.org, people explicitly use > trust levels as a "reward" tool to increase "user participation" in > some metric. [1] mentions this for example, but it's not the only topic > talking about reward systems or gamification in Discourse. > I think to be accurate, this should be rephrased as "some people, who are not discourse developers explicitly use..." - I know this may seem pedantic, but posting an example of where someone's priorities are doesn't mean that Debian would have the same priorities. > Badges and other systems serve the same purpose. I conceed that it certainly can, but I would ask you to consider that there are also other uses. As the discourse developers themselves have stated, a number of the badges are there to help guide new users on how to use Discourse features, and the badge notifications quickly drop off. Additionally, each badge can be customised and individually enabled/disabled. Note: I am not making a judgement here on the suitability of any particular badge or trying to balance if the badge award system is good or bad. In fact, the *whole thing* can be disabled, or a custom one addeed to encourage people to log in once an hour, or to like every post, should we wish to do so. I simply ask that motivations are not ascribed to what is going on when other possibilities exist. > (I can do those tricks too ;-) SCNR this one time...) > *grins* Neil -- signature.asc Description: PGP signature
Re: [Summary] Discourse for Debian
Hi Brian, On Wed, Apr 15, 2020 at 10:12:21AM -0400, Brian Gupta wrote: > Do we have to start by making it a mandatory switch? I don't feel consensus to > move to discourse will be impossible in the long term but it's normal for > human > beings to resist change, especially during a time of otherwise great stress. > I think we're miles away from making it a mandatory switch! In fact, I explictly stated this in my initial email: > What about the mailing lists? > This may or may not be a replacement for any particular list. I suspect > there are some thet would benefit greatly from having Discourse be the > primary interaction, and other places where this would be less suitable. > > Be specific! > Ok... I think debian-user, debian-vote and possibly debian-project would > be better off in Discourse. I think debian-devel-announce should stay as > an email list (for now). However, I am not suddenly proposing that we shut > those lists down. The aim of this exercise is to see if Discourse would > work well for us. The whole point of this is to evaluate if Discourse would work for Debian at all, rather than if it should be the primary communication platform. I think that discussion is very different. > How do you feel about making discourse.debian.org, and making it a fully > supported tool, that's fully backed up, and available as an alternative for > new > lists? He can have another discussion later about migrating existing lists. > Personally, I think that would be fantastic, and the idea behind this initial call for testing is to determine if I should be spending my time, and aiming for a discourse.debian.org instance, or if there is no appetite for that. Neil -- signature.asc Description: PGP signature
Re: [Summary] Discourse for Debian
On Wed, Apr 15, 2020 at 07:22:53AM -0400, The Wanderer wrote: > Would you be willing to list out which points it is from the given > "cons" category which you see as positives? > I'd really rather not at this stage, as I'm already seemingly having to spend time talking about how Discourse is set up, rather than what I was trying to do. I don't want to end up in a big debate on where "requires account" or "distributed moderation based on trust levels" sits. The point of this Discourse instance is to try and see if there is interest in moving to it rather than smartlists for community discussions. If there is sufficient interest, we can then find a group of people who want to consider these tradeoffs and who are willing to help with the way categories are organised, for example. If there is sufficient pushback, I'll delete the instance, move on with my life, and conclude that no one in Debian can possibly try and innovate or do new things unless it is either: * 100% optional for people, or * made completely compatable with the old way of doing things Apologies if the frustration is showing, but hopefully you can see where this is coming from. Neil signature.asc Description: PGP signature
Re: Testing Discourse for Debian - Moderation concepts
On Wed, Apr 15, 2020 at 12:47:06PM +0200, Ansgar wrote: > I'm not concerned about marking messages read after some time and > keeping the view time in ephermal storage for that. But that's not > what Discourse does: as described elsewhere it stores all read times > persistently on the server; that would not be neccessary for marking > posts as read even on a web application. No, but it is required for things like knowing which posts in a topic is popular, so should be used for auto-summary. It also is used to reduce abuse, as a normal new user would spend time reading topics before posting for the first time. > Evolution also keep track of the mouse cursor, but that is something > different from recording clickstreams and evaluating them to increase > user participation as some people do. Your reply seems to put both on > the same level. My point is that it's unhelpful to automatically equate "user tracking" to something undesireable. > > Interestingly, I've generally mixed replying via email with visiting > > the > > site. I would agree that it's not en par with the web UI, but I don't > > think it ever can be, due to email being designed rather differently. > > >From my tries with Discourse, it just silently stripped all quotes out > from the reply. > Perhaps this is: https://meta.discourse.org/t/single-quote-block-dropped-in-email-reply/144802 > Is this documented in some discoverable place or hidden? I've still not > managed to discover any documentation for Discourse targeting the user > (compared to admin or API documentation). > https://discourse.mozilla.org/c/meta/faq/244 Generally, there isn't a central user documentation, because each discourse instacne can be configured quite heavily, depending on each community need. Neil -- signature.asc Description: PGP signature
Re: Testing Discourse for Debian - Moderation concepts
On Wed, Apr 15, 2020 at 11:08:45AM +0200, Martin wrote:
> On 2020-04-15 08:56, Neil McGovern wrote:
> > Could I point out that the email program you wrote this message in is
> > doing the same?
>
> Could you elaborate on that? Ansgar seems to use
> "User-Agent: Evolution 3.36.1-1"
> (While I'm using mutt.) How do such UAs track reading behaviour?
>
Evolution tracks how long you've looked at a message in order to mark it
read. This is configurable in Preferences -> Mail Preferences -> Mark
messages read after X seconds. My point is that one cannot simply say
"user tracking is bad", as it may be required for actual functionality.
User tracking is also known as "saving state" :)
> > Quoting does work in most circumstances. Could you explain what
> > additional funtionality is missing?
>
> Speeking for myself, I find the email support in Discourse poor,
> to the point, that I would not advertise it. It is useful for
> notifications, but by far not en par with the web UI.
Interestingly, I've generally mixed replying via email with visiting the
site. I would agree that it's not en par with the web UI, but I don't
think it ever can be, due to email being designed rather differently.
> After reading more about Discourses many features ("likes"...),
> this is completely understandable that one cannot mimic one
> medium via the other. Trying so, will lead only to frustration.
Just on this one, you can a little. Replying with a +1 will turn your
email into a "like". Currently supported actions are:
* +1 or like: likes the post
* watch: watches the topic
* track: tracks the topic
* mute: mutes the topic
> Btw. do you know by accident, how I can "lurk" in Discourse via
> email? E.g. Let's say, I'm subscribed to debian-project, but
> only to know what is going on. Can I subscribe to a "category"?
Yes. You can subscribe to categories, topics and tags (or combinations
of them). For example, if you only ever care about m68k, you could watch
#m68k and get a notification email for that across all categories.
Neil
--
signature.asc
Description: PGP signature
Re: Testing Discourse for Debian - Moderation concepts
Hi Ansgar, To start with, I want to say that I found your mail to be quite frustrating. I feel it may have been more constructive to phrase concerns as questions, rather than stating them as facts, and ascribing motivations or inferances which simply aren't correct. That said, I'll try and reply to the factual bits. On Tue, Apr 14, 2020 at 02:30:52PM +0200, Ansgar wrote: > The "trust levels" though are one of the features that I don't like: in > particular "Trust Level 3 - Regular" mostly requires to constantly > visit the site every day (or every other day), read x% of all posts and > topics (even though they might not be relevant to your interest or in a > foreign language you don't speak), ... to not get demoted again. This is the default configuration. It can be changed to pretty much any limit we want, including zero. However, I should point out that the additional important abilities gained at this level are that the user can: * Recategorize and rename topics * TL3 spam flags cast on TL0 user posts immediately hide the post * TL3 flags cast on TL0 user posts in sufficient diversity will auto-silence the user and hide all their posts The point of the trust levels is to distribute the moderation. Whatever metric we come up with, it will involve a certain amount of actually using the site, and engaging with the community. > The system also requires tracking active read time and such; I don't > really like a system doing that... Could I point out that the email program you wrote this message in is doing the same? Exactly how this work and the reason for it being required is explained here: https://meta.discourse.org/t/how-does-post-tracking-work-in-discourse/115790 > The notifications to welcome new people or that the system hasn't seem > someone for some time[1] also seem designed to manipulate people into > spending more time on the system. Could you explain this please? I feel that having a notification (which only appears for people who regularly interact with the site) that someone is new to the community to be useful. > The claim of Discourse having an excellent email interface also feels > exagerrated: unless I missed something[2] it seems very basic. One can > send and receive messages, but quoting in replies already doesn't work > as usual and any additional functionality isn't exposed at all as far > as I can tell. Quoting does work in most circumstances. Could you explain what additional funtionality is missing? > > Instead, it encourages community members to flag posts. If a post receives > > sufficient flags, it is then automatically hidden. Users may chose to > > "unhide" the post for themseleves if they wish to view it. > > > > These are then sent to the moderating team to agree, disagree or > > ignore the flag. > > What decides who is in the moderation team? That seems to be something > different from the trust levels? Yes. At the moment those in the moderation team is... well, me. I would expect to follow something similar to Mozilla: https://discourse.mozilla.org/t/updates-to-moderation-guidelines/2 > I would also expect Discourse to have some way to entirely remove > messages, or at least remove the original content fully and replace it > with a notice that the message was removed; who can do that? Also the > moderation team? Yes, that is correct. Neil -- signature.asc Description: PGP signature
Re: [Summary] Discourse for Debian
I'm just going to correct things that are factually incorrect here, rather than label them as pros/cons. I feel a number of things you have put in the cons column are advantages. On Tue, Apr 14, 2020 at 01:31:56PM -0700, Ihor Antonov wrote: > - Not 100% GPL - some javascript scripts loaded into users browser are not > free Could you please let me know which scripts these are? > - makes it harder to use for people with limited abilities An example here would be useful. > - requires login This is incorrect. Anonymous reading and posting is possible. > - achievements/badges/other gamification of the process > - trust levels are revoked if you don't use web interface often enough to > maintain current trust level These are based on the default configuration and can be changed to suit Debian's needs > - currently no way to request removal of collected user's data This is incorrect. Neil
Re: Testing Discourse for Debian
On Tue, Apr 14, 2020 at 03:57:08PM +0200, Martin wrote: > Is the API stable in general, or only this particular function? If you're using the stable branch of Discourse, then the API is stable :) > I ask in the context of #956705: "ITP: python-pydiscourse -- > Python library for working with Discourse". Upstream says: > > > * Provide functional parity with the Discourse API, for the > > currently supported version of Discourse (something of a > > moving target) > > > > The order here is important. The Discourse API is itself > > poorly documented > The head version is indeed in flux somewhat, although I'm personally running the "tests-passed" branch in production with API integrations, and I've not had any incompatability problems. The documentation is at docs.discourse.org. I woudn't say it's poorly documented, but possibly incomplete. Neil -- signature.asc Description: PGP signature
Re: Testing Discourse for Debian
On Mon, Apr 13, 2020 at 02:16:48PM -0700, Sean Whitton wrote: > Do you think that would end up capturing all discussions, with possibly > a few weeks delay? Is it typical in Discourse use to lock/close threads > after a certain point? And do you think the API is stable enough for us > to start doing something like this? > That's entirely dependant on the configuration :) For example, on GNOME's Discourse instance, I have a few categories where it is set to close 14 days after the last reply. Then again, people can also request that they're reopened... I suspect the API should be stable enough for this, if people wanted to store discussions in a form that isn't discourse itself. Neil signature.asc Description: PGP signature
Re: Testing Discourse for Debian
On Sun, Apr 12, 2020 at 07:39:34PM +0200, Enrico Zini wrote: > Does Discourse have some kind of export feature, that one could > postprocess to get for example a mailbox of annotated emails? > Yes, though I think there's just automated ways of doing this for the entire database, or for your *own* data at the moment. It would be fairly trivial to do this yourself though, as Discoruse is primarily two things: 1) An API 2) A webpage that consumes that API. If you can do it via the web, you can do it via the API. Neil -- signature.asc Description: PGP signature
Re: Testing Discourse for Debian - Alternate interactions
I am going to try and split this out into two replies, so those following along can see the different issues. The irony of the difficulty on doing this within email may or may not be lost for others. On Sun, Apr 12, 2020 at 02:43:31PM -0700, Ihor Antonov wrote: > - There are only 2 browsers out there in existence (Firefox and Chrome > variants) and duopoly in browser market is already alarming enough. > There are much more email clients available. > I have tried Epiphany, which works fine for reading and replying. I have tried with dillo and lynx, which work fine without Javascript enabled at all for reading. You can also interact with Discourse via email. > 2. I can't now use email the way I did. Discord's email interface is > subpar in spite of what sales people tell you. So If I want "a > first-class citizen" experience I am stuck with option 1 > This is correct. Discourse interaction by email can never be as good as interacting with it via a fully featured web browser. This is because, well, email isn't a fully featured web browser. There is a commitment to improve the email integration from at least one Discourse employee, who also happens to be a Debian Developer. I but do want to emphasise the point I made in my original mail: > It should be noted however, that there is not 1:1 feature partiy with > email and the web interface, as Discorse does things that can't easily > be done with email. For the majority of users though, email > interaction should be "good enough". Neil
Re: Testing Discourse for Debian - Moderation concepts
I am going to try and split this out into two replies, so those following along can see the different issues. The irony of the difficulty on doing this within email may or may not be lost for others. On Sun, Apr 12, 2020 at 02:43:31PM -0700, Ihor Antonov wrote: > > You have to trust the moderators, > > So far I am not convinced that I can trust you to moderate. > > > and you have to have some mechanism to > > evaluate that trust and to discuss it and possibly revoke it if something > > goes horribly awry. > > Prevention should always be the first step. Something WILL go wrong but you > are > too blinded by the immediate sugar candy in front of you. > I just want to state, I won't debate any issues around freedom of speech. I believe that these do not apply in this context - especially with Debian being a private entity. Now, I do believe you have a comment on moderation, and how this is done. This requires me to explain two concepts in Discourse - trust levels and flags. Firstly, trust levels. These are the levels of "trust" that the platform has in any particular user. Instead of explaining it here, please have a read of the following: https://blog.discourse.org/2018/06/understanding-discourse-trust-levels/ The short version is that the more a particular account interacts with the community in a positive way, the more trust the system has about them, and the more privileges they are afforded to assist in moderation. Secondly, flags. Discourse has the opinion that moderation cannot be proactive with a small group of users - this doesn't scale. Instead, it encourages community members to flag posts. If a post receives sufficient flags, it is then automatically hidden. Users may chose to "unhide" the post for themseleves if they wish to view it. These are then sent to the moderating team to agree, disagree or ignore the flag. This will unhide the post, or keep it hidden and offer an opportunity for the moderator to suggest the original author edits their post in light of the number of flags they got. If an author does so, the post automatically unhides. All these actions are logged, and affects the trust levels above. In fact, every time an admin performs any action on a user, this is logged. I hope this explains how I believe that moderation is more powerful on Discourse, but also more practical, transparent and accountable. Neil
Re: Testing Discourse for Debian
On Mon, Apr 13, 2020 at 04:54:28AM +0900, Charles Plessy wrote: > In that sense, I would expect structured discussion systems such as > Discourse to be a potential time saver, and therefore lower the barrier > for contribution to everybody: those who contribute their point of view, > and those who summarise them. > Just on this point, Discourse has an auto-summarise feature. This isn't meant to replace a human summary creator, but should help with megathreads and save people time. For example: https://meta.discourse.org/t/feedback-on-new-hamburger-and-user-menus/32519 has 231 posts, and an estimated read time of 29 minutes. If you click on "Summarize this Topic", it drops that down to less than 50 posts. Neil -- signature.asc Description: PGP signature
Testing Discourse for Debian
Hi folks, For a little while, I've been keen to see how we can improve our communication methods, both to make it more accessible to newcomers and to take advantage of more featureful tooling than has been traditionally possible with email lists. As such, I set up an instance of Discourse[0] at https://discourse.debian.net, and am now asking for a wider input on if this is something the project wishes to use and if I should spend my time pursuing. FAQ === Is it Free Software? Yes. It's GPLv2+. Who else uses it? Lots of people. GNOME, Mozilla, Ubuntu, Fedora to name a few What about the mailing lists? This may or may not be a replacement for any particular list. I suspect there are some thet would benefit greatly from having Discourse be the primary interaction, and other places where this would be less suitable. Be specific! Ok... I think debian-user, debian-vote and possibly debian-project would be better off in Discourse. I think debian-devel-announce should stay as an email list (for now). However, I am not suddenly proposing that we shut those lists down. The aim of this exercise is to see if Discourse would work well for us. Email is still important to me! Fine, you can interact with Discorse by email rather than the web interface. It should be noted however, that there is not 1:1 feature partiy with email and the web interface, as Discorse does things that can't easily be done with email. For the majority of users though, email interaction should be "good enough". Why are you doing this? I have two motivations. First, is moderation. Discourse has built in tools to allow community moderation on a much better scale than our email lists. Secondly, I genuinely believe that ease of access to new contributors is of paramount importance to the project. What about X software instead? Feel free to explore other solutions. I've already done evaluations, and I'm pretty much set on this as the correct way forward. If there is insufficient interest in moving forward with Discourse, I'll leave it to others to invest time. What about forums.debian.net? I have no interest in interacting with a community of users and moderators who allow blatent Code of Conduct violations to go unchecked. What's next? I'd appreciate people testing Discourse. If you have any questions, then I'm happy to answer them. Thanks, Neil [0] https://www.discourse.org/ signature.asc Description: PGP signature
GUADEC 2020 moves to online conference
Hi all, I've just posted the following to our website, and to discourse at https://discourse.gnome.org/t/guadec-2020-moves-to-online-conference/3067 - After a lot of careful consideration and consultation with the local organizing team, the GNOME Foundation has decided that GUADEC 2020 will take place entirely online due to the COVID-19 pandemic. The event will feature the expected high quality content, streamed over the internet for anyone to participate. Mexico will now host GUADEC 2021, and we are planning for GUADEC 2022 to be in Latvia. “Although over three months away, there is no way we could ensure that the event could continue in a way that would keep our community safe.” said Neil McGovern, Executive Director of the GNOME Foundation. “It is with a heavy heart that, after consultation with the local organizing team, we won’t be visiting Mexico with GUADEC this year.” We at the GNOME Foundation love GUADEC, it’s a once-a-year event that brings us together to collaborate, celebrate, and learn; meet our colleagues and friends; and strengthen the most special part of the GNOME project — the community. While we will miss meeting in-person, we are excited for the new opportunities that meeting online will bring to the event. People who weren’t able to participate previously will be able to. We’ll have a much wider pool of potential speakers and session facilitators, as visas and travel fees will no longer be an issue. We’re looking into creative and innovative ways to bring new types of socializing, sponsor representation, and community time to GUADEC 2020. Due to the new format, we are re-opening the Call for Papers. We’ll be keeping you updated on things as they develop, on GNOME.org, the Engagement Blog and on social media. Follow, subscribe, or just check in! - Thanks, -- Neil McGovern Executive Director, The GNOME Foundation ___ foundation-announce mailing list foundation-announce@gnome.org https://mail.gnome.org/mailman/listinfo/foundation-announce
GUADEC 2020 moves to online conference
Hi all, I've just posted the following to our website, and to discourse at https://discourse.gnome.org/t/guadec-2020-moves-to-online-conference/3067 - After a lot of careful consideration and consultation with the local organizing team, the GNOME Foundation has decided that GUADEC 2020 will take place entirely online due to the COVID-19 pandemic. The event will feature the expected high quality content, streamed over the internet for anyone to participate. Mexico will now host GUADEC 2021, and we are planning for GUADEC 2022 to be in Latvia. “Although over three months away, there is no way we could ensure that the event could continue in a way that would keep our community safe.” said Neil McGovern, Executive Director of the GNOME Foundation. “It is with a heavy heart that, after consultation with the local organizing team, we won’t be visiting Mexico with GUADEC this year.” We at the GNOME Foundation love GUADEC, it’s a once-a-year event that brings us together to collaborate, celebrate, and learn; meet our colleagues and friends; and strengthen the most special part of the GNOME project — the community. While we will miss meeting in-person, we are excited for the new opportunities that meeting online will bring to the event. People who weren’t able to participate previously will be able to. We’ll have a much wider pool of potential speakers and session facilitators, as visas and travel fees will no longer be an issue. We’re looking into creative and innovative ways to bring new types of socializing, sponsor representation, and community time to GUADEC 2020. Due to the new format, we are re-opening the Call for Papers. We’ll be keeping you updated on things as they develop, on GNOME.org, the Engagement Blog and on social media. Follow, subscribe, or just check in! - Thanks, -- Neil McGovern Executive Director, The GNOME Foundation ___ foundation-list mailing list foundation-list@gnome.org https://mail.gnome.org/mailman/listinfo/foundation-list
Re: FTP Team -- call for volunteers
On Wed, Mar 18, 2020 at 12:25:24PM -0400, Theodore Y. Ts'o wrote: > > 2) We would be very limited in what checks we could actually do on new > > packages. If we look too closely at packages, we stop being a > > distributor, and start being a publisher. I'm not sure that we want to > > move towards just being a distribution platform, rather than actually > > doing QA checks. > > I'm confused. As near as I can tell, we already are looking super > closely at new packages. > Yes, and there's the problem. To move from a situation where we try and say "we're a distributor, not a publisher", then we would need to stop doing some of those checks, or at least work out a way of automating them. Apologies if the below is stuff you already know, but it may be useful for others. Please also note, this is an oversimplification of the way that this all works. There are two models of getting software from third parties into the hands of users - one is to be a "publisher", and one is to be a "distributor". Both are ways of trying to reduce the risk of putting on the web some bad software (as in, trademark infringing, copyright infringing etc). In the "publishing" model, you accept some software from a third party. You then run various checks on it, making sure it has a good licence, it complies with trademark and copyright law, and then we publish it. This is the way that Debian works at the moment. In the "distribution" model, you accept some software from a third party, and put it on the web. You don't look at it closely, but rely on your terms of service which says that the initial uploader is responsible for everything they upload, and making sure it is distributable etc. This is the way that sals/github/google play store etc work. To relieve the work on ftpmasters, some people are suggesting we move from the former to the latter. Now, imagine you have a law suit where Debian has shipped some proprietary code to millions of users. The upstream for this isn't happy. They come to Debian and complain. Debian says "oh, but we're just a distributor. The liability lies with the person who uploaded it". Unfortunately, we're doing checks on the package. Upstream can then claim that becasue we're looking at and approving packages, we're not just a platform who distributes software, we're actively publishing it by having editorial control over what gets published or not. So, to ease the burden on ftp-masters by trying to say that > the responsibility of the right to redistribute of the uploaded > software be moved on the uploader instead as suggested by Alexis, means we need to be very careful about /not/ looking too closely at what we put out. Sorry for the long mail, but hoepfully this clarifies. Neil -- signature.asc Description: PGP signature
Re: What are your thoughts on discourse?
On Wed, Mar 18, 2020 at 10:05:58PM +0200, Jonathan Carter wrote: > (since it's a test site I guess that might be invalid one day) It is very, very likely to be invalid in the coming weeks/months. I shall endeavour to copy any replies to the topic over to this list for posterity. Neil signature.asc Description: PGP signature
Re: Question to Brian: why not submit your plan for a Debian Foundation to a GR ?
On Thu, Mar 19, 2020 at 12:57:55AM +0800, Martin Michlmayr wrote: > * Louis-Philippe Véronneau [2020-03-18 12:52]: > > Would you care to elaborate on what "the Yorba determination" is? I > > couldn't find anything online about this... > > There was a time when the IRS didn't approve any new 501(c)(3) > applications for open source related organizations and basically put > them on ice. > > I thought this got resolved though in the meantime (years ago). > > https://blogs.gnome.org/jnelson/2014/06/30/the-new-501c3-and-the-future-of-free-software-in-the-united-states/ > https://opensource.org/node/840 > The two links from Martin are probably the best background reading. the tldr versions is: making FOSS is not enough to gain 501c3 status by itself. Neil -- signature.asc Description: PGP signature
Re: Question to Brian: why not submit your plan for a Debian Foundation to a GR ?
Hi Brian, On Wed, Mar 18, 2020 at 12:53:10AM -0400, Brian Gupta wrote: > > I understand coming up with a solid business plan for a "Debian > > Foundation" is not something that can be done in a few weeks. > > You are correct. It's going to take 6-12 months of work to create the > foundation, > and that includes drafting by-laws. > Just to confirm here, are you proposing the creation of a new 501(c)(3) public charity? If so, how have you considered the impact of the Yorba determination (which took 4 years) on the ability of Debian to create a new 501(c)(3)? Thanks, Neil signature.asc Description: PGP signature
Re: FTP Team -- call for volunteers
Hi Scott, On Sat, Mar 14, 2020 at 10:43:33PM +, Scott Kitterman wrote: > As long as there are people involved, a certain amount of it is > inevitable. Putting it in the requirements is bowing to reality. The > FTP Team sometimes has to make unpopular decisions and it's inevitable > that people won't always react well. > > If Sean hadn't mentioned it, I think it would have been a disservice > to potential volunteers. People should know what they are signing up > for. Honestly it's not a lot of the feedback, most of what we get > back is positive, but it's enough that it's worth mentioning. > I think that mentioning it is absolutely the right thing to do, and I'm certainly aware (having been release manager for *mumble* years) that unpopular decisions can lead to unpleasant reactions. I think my point is that we should strive to reach the point where it's not inevitable, and that our reality can change. It should never be the case that making a hard decision leads to abusive messages, and I believe as a project we must act to try and achieve this goal. For leadership roles, such as release manager, or ftp master, I think it's doubly important. Putting aside the issue of current volunteers, and the project's duty to ensure a safe and welcoming environment, this affects the overall ability for the project to attract new volunteers at all. These key posts can be aspirational for new contributors - the concept that one day you could be an ftp-master is attractive. However, if we accept that in order to reach one of these key roles you have to be willing to accept a certain level of abuse, then we have failed to produce that welcoming community, and will fail to attract and retain a diverse and thriving team. This is obviously not something that ftp-masters can solve, but I think it is useful to highlight this issue for the wider project. Thanks, Neil -- signature.asc Description: PGP signature
Re: FTP Team -- call for volunteers
Hi Scott, On Sat, Mar 14, 2020 at 10:43:33PM +, Scott Kitterman wrote: > As long as there are people involved, a certain amount of it is > inevitable. Putting it in the requirements is bowing to reality. The > FTP Team sometimes has to make unpopular decisions and it's inevitable > that people won't always react well. > > If Sean hadn't mentioned it, I think it would have been a disservice > to potential volunteers. People should know what they are signing up > for. Honestly it's not a lot of the feedback, most of what we get > back is positive, but it's enough that it's worth mentioning. > I think that mentioning it is absolutely the right thing to do, and I'm certainly aware (having been release manager for *mumble* years) that unpopular decisions can lead to unpleasant reactions. I think my point is that we should strive to reach the point where it's not inevitable, and that our reality can change. It should never be the case that making a hard decision leads to abusive messages, and I believe as a project we must act to try and achieve this goal. For leadership roles, such as release manager, or ftp master, I think it's doubly important. Putting aside the issue of current volunteers, and the project's duty to ensure a safe and welcoming environment, this affects the overall ability for the project to attract new volunteers at all. These key posts can be aspirational for new contributors - the concept that one day you could be an ftp-master is attractive. However, if we accept that in order to reach one of these key roles you have to be willing to accept a certain level of abuse, then we have failed to produce that welcoming community, and will fail to attract and retain a diverse and thriving team. This is obviously not something that ftp-masters can solve, but I think it is useful to highlight this issue for the wider project. Thanks, Neil -- signature.asc Description: PGP signature
Re: FTP Team -- call for volunteers
On Sun, Mar 15, 2020 at 08:13:37PM +0100, Alexis Murzeau wrote: > If it's just about legal risk, couldn't the responsibility of the > right to redistribute of the uploaded software be moved on the > uploader instead ? > So the uploader takes the responsibility of any redistribution of the > uploaded software by Debian itself, the same way if he would have > uploaded it to a social media are whatever. > > That way, the legal responsibility burden is distributed on many > peoples instead of a small number. If one is not sure that the > software is distributable, he can mail the upstream maintainers for a > clue. > I am also not a lawyer, but have consulted with lawyers over similar questions. This doesn't mean that Debian should consider this legal advice, as Debian's situation is different than the one I have asked about. In theory, yes - this would move the liability to the uploader. However, there are two issues with this: 1) The liability now rests with the uploader. This isn't something that has really been done before, and we'd need to make sure that we're comfortable with this. 2) We would be very limited in what checks we could actually do on new packages. If we look too closely at packages, we stop being a distributor, and start being a publisher. I'm not sure that we want to move towards just being a distribution platform, rather than actually doing QA checks. Neil -- signature.asc Description: PGP signature
Re: FTP Team -- call for volunteers
Hi debian-project and ftpmaster folks, On Sat, Mar 14, 2020 at 01:37:59PM -0700, Sean Whitton wrote: > - cope well with flames in response to your decisions > - after training, comfortable with being on the other end of the > ftpmaster@ alias, which receives a huge volume of > not-always-pleasant messages daily. I hope I am not the only one to be deeply concerned that this should be a requirement on volunteers. For me, it is absolutely unacceptable that people should put up with unplesentness or flames that come from doing a difficult job. Putting this in the requirements is, for me, a failure of the project. Sean: do you have any ideas on how we can reduce this aspect of the valuable work that ftpmasters do? Do you have some (anonymised) examples of the areas of abuse that you receive perhaps? Thanks, Neil -- signature.asc Description: PGP signature
Re: FTP Team -- call for volunteers
Hi debian-project and ftpmaster folks, On Sat, Mar 14, 2020 at 01:37:59PM -0700, Sean Whitton wrote: > - cope well with flames in response to your decisions > - after training, comfortable with being on the other end of the > ftpmaster@ alias, which receives a huge volume of > not-always-pleasant messages daily. I hope I am not the only one to be deeply concerned that this should be a requirement on volunteers. For me, it is absolutely unacceptable that people should put up with unplesentness or flames that come from doing a difficult job. Putting this in the requirements is, for me, a failure of the project. Sean: do you have any ideas on how we can reduce this aspect of the valuable work that ftpmasters do? Do you have some (anonymised) examples of the areas of abuse that you receive perhaps? Thanks, Neil -- signature.asc Description: PGP signature
Tom Marble: Advocate
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 I support Ton's request to become a Debian Developer, Uploading. I can't speak for Tom's ability to package, but I do know him as a key member of the project, and his influence in wider FOSS circles is unsurpassed by many. I was shocked to find out he wasn't a full member already, and thoroughly recommend that he is granted full rights immediately. Neil -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEgheiBV5XBDsogwVOf1W7EqQPhi4FAl5JwDAACgkQf1W7EqQP hi7wmA//enqVpQ55CfPpodvLpzJc4no2bHFedzzKVqR9aVECxiW3EtxnajN63Xme QBbfshvfmGgRdIxao4HMAaAM4lRRR+5ZHpSw0jGh7BrzDTlFGQorP5y8jKaCAgGH 6KTLG2waVwkSt8CwDs8Pl71vPM8VmHApJWDX9SniCCNcBmnjJDZqXUFJrXaAtiSj g2JJT6TeZ05u7PixHGtOYTkzZF2kMAk8qlNVuSGEuwDXU4iTbldifcifje5c4VC9 fi9xXh+8BMSCrUAk+GB8Pp3+MYBi9IVxLd9GIPQKpM7m8qaY1cdJoQ0OhyOPWTzq DcsbqfpyotFpFJL8e2M9dcvCxGZz6s9jg5STuYayxs166dUYxXm6aSy/y0u4cuvY JD7wCTCDkQcAmD105ePAx81QWF8nWFUaWLKdpJdSyc7WI1cCbtfnMnmR9ttWM6Ms VA5xu5SNLZsq5m0yTnLN5ECBjF5Qk2u6TwQf9eDHnTrm9t6MH8vte9whLzUHb8ya 6kR9VdqdVgjilKoTfQwWfL5EQcVQ1TXger5v+7iWabJ28CMjKE/FBhnfGZVDos7e jX3LMPgwwXhzG7RZvNmoNAMdGXBVK784x6P3zm9i/ecZPFDgLaKLVUYFQGl8ozK9 Wn1qqrvhgAiTwZmnlZpt+/P8vbnu/IiLw60MFCVVjGoqqGGQTo0= =OMUD -END PGP SIGNATURE- Neil McGovern (via nm.debian.org) For details and to comment, visit https://nm.debian.org/process/629 -- https://nm.debian.org/process/629
Infrastructure | Installing odoo modules error (#244)
Neil McGovern created an issue:
https://gitlab.gnome.org/Infrastructure/Infrastructure/issues/244
Hi folks,
When I try and install a new app on odoo, the following error occurs:
```
Odoo Server Error
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/odoo/http.py", line 651, in
_handle_exception
return super(JsonRequest, self)._handle_exception(exception)
File "/usr/lib/python3/dist-packages/odoo/http.py", line 310, in
_handle_exception
raise pycompat.reraise(type(exception), exception, sys.exc_info()[2])
File "/usr/lib/python3/dist-packages/odoo/tools/pycompat.py", line 87, in
reraise
raise value
File "/usr/lib/python3/dist-packages/odoo/http.py", line 693, in dispatch
result = self._call_function(**self.params)
File "/usr/lib/python3/dist-packages/odoo/http.py", line 342, in
_call_function
return checked_call(self.db, *args, **kwargs)
File "/usr/lib/python3/dist-packages/odoo/service/model.py", line 97, in
wrapper
return f(dbname, *args, **kwargs)
File "/usr/lib/python3/dist-packages/odoo/http.py", line 335, in checked_call
result = self.endpoint(*a, **kw)
File "/usr/lib/python3/dist-packages/odoo/http.py", line 937, in __call__
return self.method(*args, **kw)
File "/usr/lib/python3/dist-packages/odoo/http.py", line 515, in response_wrap
response = f(*args, **kw)
File "/usr/lib/python3/dist-packages/odoo/addons/web/controllers/main.py",
line 938, in call_button
action = self._call_kw(model, method, args, {})
File "/usr/lib/python3/dist-packages/odoo/addons/web/controllers/main.py",
line 926, in _call_kw
return call_kw(request.env[model], method, args, kwargs)
File "/usr/lib/python3/dist-packages/odoo/api.py", line 689, in call_kw
return call_kw_multi(method, model, args, kwargs)
File "/usr/lib/python3/dist-packages/odoo/api.py", line 680, in call_kw_multi
result = method(recs, *args, **kwargs)
File "", line 2, in button_immediate_install
File "/usr/lib/python3/dist-packages/odoo/addons/base/module/module.py", line
71, in check_and_log
return method(self, *args, **kwargs)
File "/usr/lib/python3/dist-packages/odoo/addons/base/module/module.py", line
449, in button_immediate_install
return self._button_immediate_function(type(self).button_install)
File "/usr/lib/python3/dist-packages/odoo/addons/base/module/module.py", line
543, in _button_immediate_function
modules.registry.Registry.new(self._cr.dbname, update_module=True)
File "/usr/lib/python3/dist-packages/odoo/modules/registry.py", line 85, in
new
odoo.modules.load_modules(registry._db, force_demo, status, update_module)
File "/usr/lib/python3/dist-packages/odoo/modules/loading.py", line 380, in
load_modules
loaded_modules, update_module, models_to_check)
File "/usr/lib/python3/dist-packages/odoo/modules/loading.py", line 274, in
load_marked_modules
perform_checks=perform_checks, models_to_check=models_to_check
File "/usr/lib/python3/dist-packages/odoo/modules/loading.py", line 153, in
load_module_graph
registry.init_models(cr, model_names, {'module': package.name})
File "/usr/lib/python3/dist-packages/odoo/modules/registry.py", line 311, in
init_models
func()
File "/usr/lib/python3/dist-packages/odoo/models.py", line 275, in _reflect
self.env['ir.model.fields']._reflect_model(self)
File "/usr/lib/python3/dist-packages/odoo/addons/base/ir/ir_model.py", line
813, in _reflect_model
self._reflect_field(field)
File "/usr/lib/python3/dist-packages/odoo/addons/base/ir/ir_model.py", line
789, in _reflect_field
(module, xmlid, record._name, record.id))
File "/usr/lib/python3/dist-packages/odoo/sql_db.py", line 155, in wrapper
return f(self, *args, **kwargs)
File "/usr/lib/python3/dist-packages/odoo/sql_db.py", line 232, in execute
res = self._obj.execute(query, params)
psycopg2.InternalError: unexpected data beyond EOF in block 195 of relation
base/16385/19774
HINT: This has been seen to occur with buggy kernels; consider updating your
system.
```
/cc @averi @barthalion
#/confidential
--
Reply to this email directly or view it on GitLab:
https://gitlab.gnome.org/Infrastructure/Infrastructure/issues/244
You're receiving this email because of your account on gitlab.gnome.org.
___
gnome-infrastructure mailing list
gnome-infrastructure@gnome.org
https://mail.gnome.org/mailman/listinfo/gnome-infrastructure
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
Infrastructure | New account for staffer (#226)
Neil McGovern created an issue: https://gitlab.gnome.org/Infrastructure/Infrastructure/issues/226 ### Account details Please provide the following information: 1. Your full name Melissa Wu 2. Permanent email address Melissa Wu - though needs a staff-mail account too. 3. Requested account name. Please note nicknames are NOT allowed (https://wiki.gnome.org/AccountsTeam/AccountNamePolicy) mwu 4. Explanation why you think you should get an account Staff for coding education challenge 5. Attach (do not paste inline!) the public part of your passphrase protected SSH version 2 key pair (usually ~/.ssh/id_rsa.pub). [Public.key](/uploads/44842909fa801083dc2fb8a30cb93051/Public.key) /cc @averi -- Reply to this email directly or view it on GitLab: https://gitlab.gnome.org/Infrastructure/Infrastructure/issues/226 You're receiving this email because of your account on gitlab.gnome.org. ___ gnome-infrastructure mailing list gnome-infrastructure@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-infrastructure
Infrastructure | Discourse 500 error (#216)
Neil McGovern created an issue: https://gitlab.gnome.org/Infrastructure/Infrastructure/issues/216 When visiting a thread with a poll, a 500 internal server error occurs. Example: https://discourse.gnome.org//t/is-it-time-to-turn-shell-extension-version-locking-back-on/809 >From the logs: ```NoMethodError (undefined method `chart_type' for #) /discourse/vendor/bundle/ruby/2.6.0/gems/activemodel-6.0.1/lib/active_model/attribute_methods.rb:431:in `method_missing'``` I suspect that a gem has gone out of sync somewhere, perhaps an upgrade of the container may fix it. /cc @averi @barthalion #/confidential -- Reply to this email directly or view it on GitLab: https://gitlab.gnome.org/Infrastructure/Infrastructure/issues/216 You're receiving this email because of your account on gitlab.gnome.org. ___ gnome-infrastructure mailing list gnome-infrastructure@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-infrastructure
Re: Infrastructure | Verify gnome.org with Google Search Console (#80)
Neil McGovern commented: An update here. After a considerable amount of back and forth, we are all verified. There's some related issues, but we should have more gitlab issues for those. I think this one can be closed. -- Reply to this email directly or view it on GitLab: https://gitlab.gnome.org/Infrastructure/Infrastructure/issues/80#note_662535 You're receiving this email because of your account on gitlab.gnome.org. ___ gnome-infrastructure mailing list gnome-infrastructure@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-infrastructure
Re: Question Under Proposal D: Compile Time Option
On Mon, Dec 02, 2019 at 05:18:35PM +0100, Thomas Goirand wrote: > On 11/29/19 11:32 PM, Sam Hartman wrote: > > Imagine that we have a program that has compile time support for systemd > > and for other mechanisms. It provides enhanced functionality when built > > against systemd, but when so built, it cannot run without systemd. > > > Is this a real life case (if so, please name the package...), or just a > pure fictional one, just because you love debating? > Or a hypothetical one, but one which could be fairly reasonable to expect. This GR seems to be trying to put in place a statement on what exactly we mean by support, and so considering things which may reasonably happen in the future is something that we should do. I don't find your phrasing as a binary choice useful, and ascribing motives to Sam seems disingenuous. Neil -- signature.asc Description: PGP signature
Infrastructure | RocketChat new version available (#211)
Neil McGovern created an issue: https://gitlab.gnome.org/Infrastructure/Infrastructure/issues/211 Hia, It looks like RocketChat 2.3.0 is now availabel which fixes a few bugs we've been having with the current 2.0.0 version. Could an upgrade be done at some point? Thanks! -- Reply to this email directly or view it on GitLab: https://gitlab.gnome.org/Infrastructure/Infrastructure/issues/211 You're receiving this email because of your account on gitlab.gnome.org. ___ gnome-infrastructure mailing list gnome-infrastructure@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-infrastructure
Re: Standing behind GNOME Foundation against Rothschild Patent Imaging LLC?
On Mon, Sep 30, 2019 at 02:29:38PM +0100, Neil McGovern wrote: > On Sun, Sep 29, 2019 at 12:25:53AM +0100, Andy Simpkins wrote: > > Where can I contribute to the war chest in order to help fund fighting this? > On Sat, Sep 28, 2019 at 09:03:37PM -0400, Paul Tagliamonte wrote: > > Aye aye! We should distribute a fundraising site more widely among Debian > > for anyone in our community who is willing to donate to the collective > > defense of our tools. > > At the point when we require significant funds to fight this, I'll > address it. At the moment, we're very much in the preliminary stages of > this legal case. More generally, I'm talking to other folk around how to > make sure that GNOME and free software isn't attacked in future. > > Apologies for not being able to provide more clarity at this stage, I'm > sure you'll understand why! > For those not following closely, we've now filed our motion to dismiss, response and counterclaim: https://www.gnome.org/news/2019/10/gnome-files-defense-against-patent-troll/ Our strategy is to not only get the case dropped or dismissed, but to take out the patent as well. We do need funds to do this, and for those who are kind enough to donate, please do so at https://secure.givelively.org/donate/gnome-foundation-inc/gnome-patent-troll-defense-fund If you can't, please help spread the word. Neil -- signature.asc Description: PGP signature
Infrastructure | New staff-mail address (#193)
Neil McGovern created an issue: https://gitlab.gnome.org/Infrastructure/Infrastructure/issues/193 Hi folks, Can we please have care...@gnome.org set up? This is needed for Odoo to poll from to import job applications into the system. Neil -- Reply to this email directly or view it on GitLab: https://gitlab.gnome.org/Infrastructure/Infrastructure/issues/193 You're receiving this email because of your account on gitlab.gnome.org. ___ gnome-infrastructure mailing list gnome-infrastructure@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-infrastructure
Re: Issue #15 - Misleading "Linux" link on /projects/debian/
On Sun, Oct 06, 2019 at 07:48:08AM -0400, Philippe Cloutier wrote: > I am extremely knowledgeable about Debian and happen to have been an > important member of its communication team for years. I am not saying that > removal is best, but I can assure you it is a valid option. > Could you clarify this point? This is inaccurate to put it lightly. Neil signature.asc Description: PGP signature ___ Spi-general mailing list Spi-general@lists.spi-inc.org http://lists.spi-inc.org/listinfo/spi-general
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: Standing behind GNOME Foundation against Rothschild Patent Imaging LLC?
Thanks Chris and all for the support that's been shown in this thread, it really does mean a lot while we're going through this complex period. On Sun, Sep 29, 2019 at 12:25:53AM +0100, Andy Simpkins wrote: > Having read the 'claim' being made, I for one, can not see there being > a case to answer, however my experience does not cover the American > patant/legal systems. To me this looks like a classic case of patent > tolling. Any and all instaces of which SHOULD be taken into court to > be struck down and the patent invalidated. On no account should these > trolls be allowed to walk away without a legal rulling against them. > At the moment, I'm not going to publicly state our strategy or position on the patent in question, as anything I do say wouldn't be legally privileged. However, I think I can say that my concern isn't just about GNOME and this case, but how free software projects are affected by this sort of patent activity more widely. On Sun, Sep 29, 2019 at 12:25:53AM +0100, Andy Simpkins wrote: > Where can I contribute to the war chest in order to help fund fighting this? On Sat, Sep 28, 2019 at 09:03:37PM -0400, Paul Tagliamonte wrote: > Aye aye! We should distribute a fundraising site more widely among Debian > for anyone in our community who is willing to donate to the collective > defense of our tools. At the point when we require significant funds to fight this, I'll address it. At the moment, we're very much in the preliminary stages of this legal case. More generally, I'm talking to other folk around how to make sure that GNOME and free software isn't attacked in future. Apologies for not being able to provide more clarity at this stage, I'm sure you'll understand why! Neil -- signature.asc Description: PGP signature
Re: Moving foundation-list to discourse?
On Wed, 2019-09-04 at 11:09 +0100, Allan Day wrote: > I think with Discourse you have to opt in to get email notifications? > That could be an issue. Certainly with things like the AGM, the board > is required to serve notice to all members. Yes, you do. Although for AGM notices etc, I don't think it's sufficient to simply post to a mailing list. For this year's one, we sent an individual mail to each member. Neil -- Neil McGovern Executive Director, The GNOME Foundation ___ foundation-list mailing list foundation-list@gnome.org https://mail.gnome.org/mailman/listinfo/foundation-list
Re: Moving foundation-list to discourse?
On Wed, 2019-09-04 at 01:51 -0400, Richard Stallman wrote: > I have heard that there is a gateway between Discourse and email. > Is it possible to use that here? > It's already in place. Neil -- Neil McGovern Executive Director, The GNOME Foundation ___ foundation-list mailing list foundation-list@gnome.org https://mail.gnome.org/mailman/listinfo/foundation-list
Re: Moving foundation-list to discourse?
On Fri, 2019-08-30 at 11:10 +0200, Alexandre Franke wrote: > Not objecting at all but I think this raises a couple questions as to > what it would entail, most notable regarding board meeting minutes > and other announcements. Currently, most of them are sent to the > foundation-announce list which I assume we want to keep, but then any > followup discussion lands on foundation-list. I’m not sure how that > would work with Discourse. I would imagine actually, that it may be better to just post these to Discourse, in the community category. There's a couple of ways that we can improve visibility by using tags and stickies for important things (for example, we already have the #announcements tag: https://discourse.gnome.org/tags/announcement) We could add a #minutes tag too. One advantage of this is that users can subscribe to a particular tag, and get notifications about those. Would that make sense? Neil -- Neil McGovern Executive Director, The GNOME Foundation ___ foundation-list mailing list foundation-list@gnome.org https://mail.gnome.org/mailman/listinfo/foundation-list
Re: GNOME Foundation 2019 Annual General Meeting (AGM)
On Wed, 2019-07-24 at 13:03 -0700, Nuritzi Sanchez wrote: > > About the vote: > > This year, there will be a vote about bylaw changes that the Board > > is proposing, including changes to Board terms and updating the > > bylaws to make them more gender-neutral. These proposed changes are > > attached to this email. Dear all, For information, the results of these votes were: gender_neutral.patch: Yes - 73, No - 2 board-terms.patch: Yes - 69, No - 5, Abstain - 1 These have therefore been adopted. Neil -- Neil McGovern Executive Director, The GNOME Foundation ___ foundation-list mailing list foundation-list@gnome.org https://mail.gnome.org/mailman/listinfo/foundation-list
Re: [guadec-list] GUADEC 2019 Videos?
Hi there, These will appear at https://guadec.ubicast.tv/latest/ and on the YouTube channel once they're processed. Thanks, Neil Sent from TypeApp On 28 Aug 2019, 23:56, at 23:56, Luna Jernberg via guadec-organization wrote: >Hello! > >Missed all of the GUADEC video stream, due to being home sick and being >busy at dayjob and it ends tommorow afternoon so was wondering if you >will >upload all the videos somewhere this year? > > > > >___ >guadec-organization mailing list >guadec-organizat...@gnome.org >https://mail.gnome.org/mailman/listinfo/guadec-organization ___ guadec-list mailing list guadec-list@gnome.org https://mail.gnome.org/mailman/listinfo/guadec-list
Infrastructure | 2019.gnome.asia leads to 404 (#169)
Neil McGovern created an issue: ### Summary It seems the current gnoma.asia site actually just leads to a github 404 page. I assume it should be directed somewhere useful. /cc @averi -- Reply to this email directly or view it on GitLab: https://gitlab.gnome.org/Infrastructure/Infrastructure/issues/169 You're receiving this email because of your account on gitlab.gnome.org. ___ gnome-infrastructure mailing list gnome-infrastructure@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-infrastructure
Infrastructure | New service: chat.gnome.org (#168)
Neil McGovern created an issue: ### Summary We would like to trial use of Rocket.Chat for a communication system for the foundation, rather than relying on IRC, Matrix and Telegram, and the fragmentation that occurs. Can we please have an instance of rocket chat at chat.gnome.org? OpenShift instructions are at https://rocket.chat/docs/installation/paas-deployments/openshift/ /cc @averi -- Reply to this email directly or view it on GitLab: https://gitlab.gnome.org/Infrastructure/Infrastructure/issues/168 You're receiving this email because of your account on gitlab.gnome.org. ___ gnome-infrastructure mailing list gnome-infrastructure@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-infrastructure
Infrastructure | staff-mail LE certificate expired (#167)
Neil McGovern created an issue: Hi, It seems that the Let's Encrypt Certificate for staff-mail.gnome.org expired on 25/08/19 /cc @averi l -- Reply to this email directly or view it on GitLab: https://gitlab.gnome.org/Infrastructure/Infrastructure/issues/167 You're receiving this email because of your account on gitlab.gnome.org. ___ gnome-infrastructure mailing list gnome-infrastructure@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-infrastructure
Re: help
Hi! On Thu, Aug 15, 2019 at 07:09:18PM +, seydi mouhamadou moustapha ndiaye wrote: > I'm a student in computer engineering field from africa and I look for a > mentor who can help me to accurate my computer skills mainly on coding. > That's fantastic, it's really good to see new people come along and want to help out, thank you for your time! >From what you've said, probably the best way of getting involved in Debian is through packaging software for inclusion in the distribution. There are a number of guides that run through this, which are linked from https://wiki.debian.org/DebianMentorsFaq If you're not sure on areas that need help, installing the how-can-i-help package will give you some ideas. Finally, I would suggest dropping a mail over to the debian-mentors mailing list, there's a load of people there who can assist you. You can find that list at http://lists.debian.org/debian-mentors. There's also support on IRC via the #debian-mentors channel. More information on IRC can be found at https://wiki.debian.org/IRC Hope this helps, Neil
Re: Moving foundation-list to discourse?
Hi Olav, On Tue, 2019-08-13 at 18:28 +, Olav Vitters wrote: > it has been around half a year since GNOME started to host a > Discourse[0] instance, which was generally well received. > > Listadmin wise (I'm NOT the admin here!), mailman is not really nice > to > use. If something ends up in the moderation queue it'll take quite a > bit > of effort for a moderator to look at it. > > Discourse is free software (including the Javascript) and the > dependencies are also free software. > > You can sign up in various ways. First of all there's regular > email+password. It also allows single-sign on systems, like Google > and > Github, to authenticate yourself. Lastly (and preferred way) if you > have > a GNOME LDAP account already, you're strongly encouraged to use that > method of authentication. > > You can still use email to interact with Discourse, and a guide is > available[2]. The interaction is both ways (sending and receiving). > It's > even possible to make Discourse behave like an mailing list. > > For specific questions or feedback on Discourse, please post in the > appropriate category[3]. > > Do people agree to move this to Discourse? Does anyone have > objections > or concerns? I didn't check with the current list admins btw. > As another data point, all GTK (and builder) discussions have moved to discourse, and I know the Docs teams are also willing to transition. GTK has seen much more activity on there than all GTK lists combined with mailman. In general, I would suggest that the foundation list moves over, unless there are actually any serious objections. Perhaps a discussion at GUADEC could also be had. If there's no objections, I'm happy to help manage the transition, with an aim of retiring this list by the end of October. Comments please! Neil -- Neil McGovern Executive Director, The GNOME Foundation ___ foundation-list mailing list foundation-list@gnome.org https://mail.gnome.org/mailman/listinfo/foundation-list
Re: Nepotism, Conflict of interest: Debian GSoC/Outreachy/OSI board
Hi, On Mon, 2019-07-22 at 15:16 +, Mollamby via foundation-list wrote: > One of the conflicts of interest comes across to GNOME > I have full confidence in our staff, and consider your comments here decisive and harmful. Please do not post here again. Neil -- Neil McGovern Executive Director, The GNOME Foundation ___ foundation-list mailing list foundation-list@gnome.org https://mail.gnome.org/mailman/listinfo/foundation-list
Re: [guadec-list] Registration for GUADEC 2019 is now open!
Hi Alex, On Thu, 2019-07-18 at 10:54 +0300, Kiwi TCMS wrote: > На 18.07.19 г. в 2:26 ч., Kristi Progri написа: > > Hi all, > > > > The GUADEC organizers are pleased to announce that the > > *registration for GUADEC > > 2019* is now open. > > Hello Kristi, > when are you going to announce which proposals have been approved and > which ones > have not been approved? Website says schedule announcement was due in > June but > so far I haven't seen anything for my submissions. > Please accept my apologies for the delay here, which was due to a number of technical issues with our conference software, and key volunteers being unavoidably busy at critical times. We hope to get this resolved in the next couple of days and to notify everyone and publish the schedule. Neil -- Neil McGovern Executive Director, The GNOME Foundation ___ foundation-list mailing list foundation-list@gnome.org https://mail.gnome.org/mailman/listinfo/foundation-list
Re: [guadec-list] Registration for GUADEC 2019 is now open!
Hi Alex, On Thu, 2019-07-18 at 10:54 +0300, Kiwi TCMS wrote: > На 18.07.19 г. в 2:26 ч., Kristi Progri написа: > > Hi all, > > > > The GUADEC organizers are pleased to announce that the > > *registration for GUADEC > > 2019* is now open. > > Hello Kristi, > when are you going to announce which proposals have been approved and > which ones > have not been approved? Website says schedule announcement was due in > June but > so far I haven't seen anything for my submissions. > Please accept my apologies for the delay here, which was due to a number of technical issues with our conference software, and key volunteers being unavoidably busy at critical times. We hope to get this resolved in the next couple of days and to notify everyone and publish the schedule. Neil -- Neil McGovern Executive Director, The GNOME Foundation ___ guadec-list mailing list guadec-list@gnome.org https://mail.gnome.org/mailman/listinfo/guadec-list
Re: [guadec-list] Registration for GUADEC 2019 is now open!
Hi Alex, On Thu, 2019-07-18 at 10:54 +0300, Kiwi TCMS wrote: > На 18.07.19 г. в 2:26 ч., Kristi Progri написа: > > Hi all, > > > > The GUADEC organizers are pleased to announce that the > > *registration for GUADEC > > 2019* is now open. > > Hello Kristi, > when are you going to announce which proposals have been approved and > which ones > have not been approved? Website says schedule announcement was due in > June but > so far I haven't seen anything for my submissions. > Please accept my apologies for the delay here, which was due to a number of technical issues with our conference software, and key volunteers being unavoidably busy at critical times. We hope to get this resolved in the next couple of days and to notify everyone and publish the schedule. Neil -- Neil McGovern Executive Director, The GNOME Foundation ___ engagement-list mailing list engagement-list@gnome.org https://mail.gnome.org/mailman/listinfo/engagement-list
Re: [guadec-list] GUADEC 2019 : Problem on registration page!
On Sat, 2019-07-20 at 12:49 +0300, Anastasios Lisgaras via guadec-list wrote: > Hello, > > Unfortunately, I try to sign up and buy my ticket for this year's > conference and I can not. > When I was trying to buy the ticket from the mastercard card from > «National Bank of Greece» ( https://www.nbg.gr/en ) > > Returns the following error : > "The card was declined" Looking at the logs, it seems the card has been declined by the bank for an unknown reason. It suggests "The customer needs to contact their card issuer for more information." Neil -- Neil McGovern Executive Director, The GNOME Foundation ___ guadec-list mailing list guadec-list@gnome.org https://mail.gnome.org/mailman/listinfo/guadec-list
Re: Apt-secure and upgrading to bullseye
On Wed, Jul 10, 2019 at 07:51:18PM +0100, Julian Gilbey wrote: > Thanks to everyone for suggestions; I discovered "apt update" through > a Google search. > I've submitted a patch against the release notes to explicitly mention this: https://salsa.debian.org/ddp-team/release-notes/merge_requests/50 > But I realised later that this is going to bite all users when they > come to upgrade from buster. Perhaps some aptitude and apt-get > patches can go into a stable (buster) point release, so that fewer > users are hurt by this in 2-3 years' time? It is quite a showstopper! > Given the release notes tell people to use "apt update", I'd be interested to know if there was any documentation you read or followed during the upgrade. If you didn't use the release notes, is there a reason why? Could a tl;dr version make you more likely to read them? Neil -- signature.asc Description: PGP signature
Re: Minutes of the board meeting of June 24, 2019
On Tue, 2019-07-09 at 14:52 -0500, mcatanz...@gnome.org wrote: > I agree with Meg that it would be a bit sad to lose our only North > America event indeed (especially since it only occurs every second > year), but I guess events happen where people are willing to host > them > Indeed, it's something I'm aware of too, and it's part of the reason we're having a large (3 team) simultaneous hackfest next week in Portland: https://wiki.gnome.org/Hackfests/WestCoastHackfest I'm also exploring options of holding something in Mexico, possibly next year. Neil -- Neil McGovern Executive Director, The GNOME Foundation ___ foundation-list mailing list foundation-list@gnome.org https://mail.gnome.org/mailman/listinfo/foundation-list
Re: GNOME ASIA logo competition
(re-ordering slightly for flow) On Tue, 2019-07-02 at 22:15 -0400, Richard Stallman wrote: > The term "MIT license" is ambiguous -- it stands for either the X11 > license or the Expat license. You can tell which by looking at the > actual license text in the source and comparing with those two > entries > in https://gnu.org/licenses/license-list.html. In FSF terms, it's the Expat licence. > The source pointers are needed because these pages contain compiled > code. (More precisely, minified -- but that is a kind of > compilation.) It is ok to use minified code, but it needs to come > with the corresponding source code. Luckily, the full and corresponding source code is available. I think, however, what you're asking is for is a pointer in a format that is machine readable by LibreJS. > It is possible to fix the problem by adding a machine-recognizable > license notice for the appropriate license at the top of the > pertinent > pages, plus a source code pointer for each page. See > https://gnu.org/software/librejs/free-your-javascript.html for > documentation. I had a look at that, it seems that the implementation of Web Labels table: a) doesn't support wildcarding or regexes b) requires a physical link to be added to every page rather than fetching from a known location. Given that we are keen to avoid divergence from upstream, at a minimum I would want to see the above added to LibreJS before we can reliably produce a Web Label table. Do you know if there's plans to add this functionality? Neil -- Neil McGovern Executive Director, The GNOME Foundation ___ foundation-list mailing list foundation-list@gnome.org https://mail.gnome.org/mailman/listinfo/foundation-list
Re: GNOME ASIA logo competition
(re-ordering slightly for flow) On Tue, 2019-07-02 at 22:15 -0400, Richard Stallman wrote: > The term "MIT license" is ambiguous -- it stands for either the X11 > license or the Expat license. You can tell which by looking at the > actual license text in the source and comparing with those two > entries > in https://gnu.org/licenses/license-list.html. In FSF terms, it's the Expat licence. > The source pointers are needed because these pages contain compiled > code. (More precisely, minified -- but that is a kind of > compilation.) It is ok to use minified code, but it needs to come > with the corresponding source code. Luckily, the full and corresponding source code is available. I think, however, what you're asking is for is a pointer in a format that is machine readable by LibreJS. > It is possible to fix the problem by adding a machine-recognizable > license notice for the appropriate license at the top of the > pertinent > pages, plus a source code pointer for each page. See > https://gnu.org/software/librejs/free-your-javascript.html for > documentation. I had a look at that, it seems that the implementation of Web Labels table: a) doesn't support wildcarding or regexes b) requires a physical link to be added to every page rather than fetching from a known location. Given that we are keen to avoid divergence from upstream, at a minimum I would want to see the above added to LibreJS before we can reliably produce a Web Label table. Do you know if there's plans to add this functionality? Neil -- Neil McGovern Executive Director, The GNOME Foundation ___ engagement-list mailing list engagement-list@gnome.org https://mail.gnome.org/mailman/listinfo/engagement-list
Re: GNOME ASIA logo competition
On Mon, 2019-07-01 at 22:11 -0400, Richard Stallman wrote: > > There are 29 logos competing with each other and you can vote for > your 3 > > favorites by leaving a comment here: > > https://gitlab.gnome.org/Teams/Events/GNOMEAsia/issues/46 > > I am sad to report that this page seems to require nonfree Javascript > code. Looking at the page with LibreJS to protect me from nonfree > Javascript code, I don't see any of the logos. All JavaScript served on that page comes from GNOME hosted servers and it is all MIT licensed, as is the entirety of GitLab CE, which is what we're running. Neil -- Neil McGovern Executive Director, The GNOME Foundation ___ engagement-list mailing list engagement-list@gnome.org https://mail.gnome.org/mailman/listinfo/engagement-list
Re: GNOME ASIA logo competition
On Mon, 2019-07-01 at 22:11 -0400, Richard Stallman wrote: > > There are 29 logos competing with each other and you can vote for > your 3 > > favorites by leaving a comment here: > > https://gitlab.gnome.org/Teams/Events/GNOMEAsia/issues/46 > > I am sad to report that this page seems to require nonfree Javascript > code. Looking at the page with LibreJS to protect me from nonfree > Javascript code, I don't see any of the logos. All JavaScript served on that page comes from GNOME hosted servers and it is all MIT licensed, as is the entirety of GitLab CE, which is what we're running. Neil -- Neil McGovern Executive Director, The GNOME Foundation ___ foundation-list mailing list foundation-list@gnome.org https://mail.gnome.org/mailman/listinfo/foundation-list
Infrastructure | Cron for civicrm not running (#150)
New Issue was created. Issue 150: https://gitlab.gnome.org/Infrastructure/Infrastructure/issues/150 Author:Neil McGovern Assignees: It seems that the cronjob that civicrm needs to be running, isn't. Could this be activated as we have a mail scheduled to go out? -- Reply to this email directly or view it on GitLab: https://gitlab.gnome.org/Infrastructure/Infrastructure/issues/150 You're receiving this email because of your account on gitlab.gnome.org. ___ gnome-infrastructure mailing list gnome-infrastructure@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-infrastructure
Re: Infrastructure | Set up Connfa! CMS and Integration Server GUADEC 2019 and future GUADECs (#147)
Neil McGovern commented: @averi - Could you have a prod at this? I think it's blocking the app deployment -- Reply to this email directly or view it on GitLab: https://gitlab.gnome.org/Infrastructure/Infrastructure/issues/147#note_531878 You're receiving this email because of your account on gitlab.gnome.org. ___ gnome-infrastructure mailing list gnome-infrastructure@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-infrastructure
New GNOME Foundation staffer - Strategic Initiatives Manager
Dear Foundation members, I'm very pleased to announce that Molly de Blanc joined us yesterday (23rd April) to take on the role of Strategic Initiatives Manager. This role is crucial to ensure we continue to have a sustainable and growing Foundation. I'm greatly looking forward to her getting up to speed and seeing the impact her work will have, not only on fundraising, but also on community engagement. Molly comes from the Free Software Foundation where she was the Campaigns Manager, working on community organizing around digital rights issues. She's also a member of the Board of Directors of the Open Source Initiative, and on the Debian Outreach and Anti-harassment teams. Regularly speaking at conferences around the world, she has represented multiple projects in community and corporate contexts. I'm sure you'll all give her a warm welcome in this new role! Neil -- Neil McGovern Executive Director, The GNOME Foundation ___ foundation-announce mailing list foundation-announce@gnome.org https://mail.gnome.org/mailman/listinfo/foundation-announce
New GNOME Foundation staffer - Strategic Initiatives Manager
Dear Foundation members, I'm very pleased to announce that Molly de Blanc joined us yesterday (23rd April) to take on the role of Strategic Initiatives Manager. This role is crucial to ensure we continue to have a sustainable and growing Foundation. I'm greatly looking forward to her getting up to speed and seeing the impact her work will have, not only on fundraising, but also on community engagement. Molly comes from the Free Software Foundation where she was the Campaigns Manager, working on community organizing around digital rights issues. She's also a member of the Board of Directors of the Open Source Initiative, and on the Debian Outreach and Anti-harassment teams. Regularly speaking at conferences around the world, she has represented multiple projects in community and corporate contexts. I'm sure you'll all give her a warm welcome in this new role! Neil -- Neil McGovern Executive Director, The GNOME Foundation ___ foundation-list mailing list foundation-list@gnome.org https://mail.gnome.org/mailman/listinfo/foundation-list
Re: Infrastructure | Nextcloud client failing to sync with server (#129)
Neil McGovern commented: Possibly related: https://github.com/nextcloud/desktop/issues/819 -- Reply to this email directly or view it on GitLab: https://gitlab.gnome.org/Infrastructure/Infrastructure/issues/129#note_484325 You're receiving this email because of your account on gitlab.gnome.org. ___ gnome-infrastructure mailing list gnome-infrastructure@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-infrastructure
Infrastructure | Nextcloud client failing to sync with server (#129)
New Issue was created. Issue 129: https://gitlab.gnome.org/Infrastructure/Infrastructure/issues/129 Author:Neil McGovern Assignee: Running the nextcloud client (v2.5.1git), cloud.gnome.org fails to sync with the error: "A HTTP transmission error happened. The server file discovery reply is missing" The relevant extract from the log seems to be: ``` [OCC::DiscoverySingleDirectoryJob::directoryListingIteratedSlot Missing properties: "GUADEC 2018" 2 0 1554623257 "DNVS" "" "-001516d402115c3e" [csync_ftw opendir failed for - errno 10011 [OCC::SyncEngine::handleSyncError ERROR during csync_update : "A HTTP transmission error happened. The server file discovery reply is missing data." [OCC::ActivityWidget::addError Item "nextcloud" retrieved resulted in "A HTTP transmission error happened. The server file discovery reply is missing data." ``` /cc averi -- Reply to this email directly or view it on GitLab: https://gitlab.gnome.org/Infrastructure/Infrastructure/issues/129 You're receiving this email because of your account on gitlab.gnome.org. ___ gnome-infrastructure mailing list gnome-infrastructure@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-infrastructure
Re: Infrastructure | This is a Test! (#126)
Neil McGovern commented: A test comment! -- Reply to this email directly or view it on GitLab: https://gitlab.gnome.org/Infrastructure/Infrastructure/issues/126#note_480095 You're receiving this email because of your account on gitlab.gnome.org. ___ gnome-infrastructure mailing list gnome-infrastructure@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-infrastructure
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: Infrastructure | cloud.gnome.org - calendar reminder emails aren't sent (#15)
Neil McGovern commented: https://github.com/nextcloud/server/pull/3044 - WIP upstream for this support -- View it on GitLab: https://gitlab.gnome.org/Infrastructure/Infrastructure/issues/15#note_472789 You're receiving this email because of your account on gitlab.gnome.org. ___ gnome-infrastructure mailing list gnome-infrastructure@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-infrastructure
Re: Moving Engagement List to Discourse
On Fri, 2019-03-01 at 12:00 -0500, Christopher Davis via engagement- list wrote: > After investingating Discourse esterday, I do have some objections > that I think should be considered. Though the software itself is > free, > the mobile app is proprietrary It's licensed under MIT: https://github.com/discourse/DiscourseMobile/blob/master/LICENSE.txt > and the Android version has a hard dependency > on the proprietary Google Chrome app. I don't think we should force > developers to > use proprietary applications for out official communication channels. I've tested and used Firefox on Android to access the mobile site. Native notifications work fine, and you can add this to your home screen. It works perfectly well and is probably the preferred method for use on mobile. > Mailing lists do not have this problem because there are many free > software > e-mail clients. Luckily, email interaction with Discourse continues to work fine, should you wish to use it that way: https://discourse.gnome.org/t/interacting-with-discourse-via-email/46/3 Neil -- Neil McGovern Executive Director, The GNOME Foundation ___ engagement-list mailing list engagement-list@gnome.org https://mail.gnome.org/mailman/listinfo/engagement-list
Re: Discourse instance
On Sat, 2019-03-02 at 21:07 +, Philip Withnall wrote: > Well, I suspect LRN would probably appreciate a ‘windows’ tag. I've added a topic in Site Suggestions for these to collate them :) Neil -- Neil McGovern Executive Director, The GNOME Foundation ___ gtk-devel-list mailing list gtk-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/gtk-devel-list
Re: Moving Engagement List to Discourse
I think we're trying not to diverge from upstream, otherwise we'll need to maintain a branch. I've submitted a PR though to upstream for a config there. Neil On Sat, 2019-03-02 at 08:22 +0100, Bastian Ilso wrote: > Whoops! You're right. > > Maybe something worth clarifying in the login window? > > Thanks for the help! > > -Bastian > > On fre, Mar 1, 2019 at 5:54 PM, Neil McGovern wrote: > > Your username is bastianilso, not the full email address. Make sure > > you > > click on the ldap button :) It's the same username and password (I > > think) that you use to log in to account.gnome.org > > > > Neil > > > > On Fri, 2019-03-01 at 17:49 +0100, Bastian Ilso wrote: > > > Great to see! > > > > > > I am having some trouble logging in with LDAP. It says > > > > > > "Sorry, there was an error authorizing your account. Perhaps you > > > did > > > not approve authorization?" > > > > > > > > > I am trying to log in using the "bastiani...@gnome.org" account. > > > > > > > > > -Bastian > > > > > > On fre, Mar 1, 2019 at 5:29 PM, Neil McGovern > > > wrote: > > > > On Thu, 2019-02-07 at 08:57 -0500, s...@ramkrishna.me wrote: > > > > > I brought this up in Telegram but didn't receive any > > > objections. > > > > > > > > > > > > > Hi all, > > > > > > > > News on the Discourse front - this is now live! Have a visit > > > at > > > > https://discourse.gnome.org > > > > > > > > You can log in via LDAP, or sign up with email/google/github. > > > > > > > > I've created an Engagement category, so everything can go in > > > there: > > > > https://discourse.gnome.org/c/community/engagement > > > > > > > > In case you really don't want to use a web interface (although > > > I > > > > would > > > > strongly recommend it, it's really rather nice), you can also > > > > interact > > > > via email, some instructions are available at: > > > > > > > https://discourse.gnome.org/t/interacting-with-discourse-via-email/46 > > > > > > > > Additionally, if you're a Foundation member, let me know by > > > sending > > > > me > > > > (nmcgovern) a message on Discourse, and I'll add you to the > > > group > > > > which > > > > gives you a little flair and a 'GNOME Team' title by your > > > posts. > > > > > > > > Finally, when logging in, you'll get a message from discobot. > > > This > > > > friendly bot will guide you through the basic functionality. > > > You > > > > can > > > > skip it if you want, but you'll miss out on getting a badge ( > > > > https://discourse.gnome.org/badges) > > > > > > > > Any questions, let me know. > > > > > > > > Thanks, > > > > Neil > > > > -- > > > > Neil McGovern > > > > Executive Director, The GNOME Foundation > > > > > > > > ___ > > > > engagement-list mailing list > > > > engagement-list@gnome.org > > > > https://mail.gnome.org/mailman/listinfo/engagement-list > > -- > > Neil McGovern > > Executive Director, The GNOME Foundation > > -- Neil McGovern Executive Director, The GNOME Foundation ___ engagement-list mailing list engagement-list@gnome.org https://mail.gnome.org/mailman/listinfo/engagement-list
Re: Discourse instance
On Fri, 2019-03-01 at 19:34 +, Neil McGovern wrote: > Ah, yes. You can do that! > I'm also aware of the irony of replying here, rather than on the discourse instance so others can see and learn. We have a site feedback category :) Neil -- Neil McGovern Executive Director, The GNOME Foundation ___ gtk-devel-list mailing list gtk-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/gtk-devel-list
Re: Discourse instance
On Fri, 2019-03-01 at 19:14 +0100, Ernestas Kulik wrote: > I haven’t gone through the tutorial with discobot, but seems that 2FA > is not going to work with LDAP logins, right? Yes... in a way. Turning on 2FA requires a password and with LDAP logins, Discourse has a null password for your account. You can generate a password for your account by using the forgotten password link. This will then enable you to turn on 2FA. Note: this means that you won't be able to log in with LDAP (or in fact, Google or Github) I guess it comes down to your desire for security vs ease of use. LDAP is easier, but can't do 2FA. Local Discourse accounts can do 2FA, but that's another password to remember. Neil -- Neil McGovern Executive Director, The GNOME Foundation ___ gtk-devel-list mailing list gtk-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/gtk-devel-list
Re: Discourse instance
On Fri, 2019-03-01 at 20:37 +0300, LRN via gtk-devel-list wrote: > Well, what i mean is that i'd like to be able to be notified of > topics that are > relevant to me, and one way to do that is to allow topics to be > tagged and > allow people to subscribe to tags. Ah, yes. You can do that! https://discourse.gnome.org/tags/ Click on a tag, and you can update your watching status. The number of tags are limited at the moment, so if you have any ideas for other tags you want to add, let me know and I'll add them. > Also, related: if i watch a topic, do i get email notifications for > each > message? If not, i'd have to enable the ML mode. Yes. Watching mode notifies you every time there's a new post in a topic or category you're watching. > Also, email notifications are > issued once per topic, right? So, if the topic subject changes (like > how an > email thread can split by changing the topic), i won't be notified? The way it works in Discourse is slightly different. Instead of splitting a thread by changing the subject, you split the actual topic in two to form a new one. Once that split happens, you should get notified that there's a new topic. That split is done by a moderator rather than a user, as the user can just make a new post. Neil -- Neil McGovern Executive Director, The GNOME Foundation ___ gtk-devel-list mailing list gtk-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/gtk-devel-list
Re: Discourse instance
On Fri, 2019-03-01 at 19:52 +0300, LRN via gtk-devel-list wrote: > On 01.03.2019 18:41, Emmanuele Bassi via gtk-devel-list wrote: > > Feedback is very much appreciated. > > > > Need moar tags! > Tag suggestions welcome :) Neil -- Neil McGovern Executive Director, The GNOME Foundation ___ gtk-devel-list mailing list gtk-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/gtk-devel-list
Re: Moving Engagement List to Discourse
On Thu, 2019-02-07 at 08:57 -0500, s...@ramkrishna.me wrote: > I brought this up in Telegram but didn't receive any objections. > Hi all, News on the Discourse front - this is now live! Have a visit at https://discourse.gnome.org You can log in via LDAP, or sign up with email/google/github. I've created an Engagement category, so everything can go in there: https://discourse.gnome.org/c/community/engagement In case you really don't want to use a web interface (although I would strongly recommend it, it's really rather nice), you can also interact via email, some instructions are available at: https://discourse.gnome.org/t/interacting-with-discourse-via-email/46 Additionally, if you're a Foundation member, let me know by sending me (nmcgovern) a message on Discourse, and I'll add you to the group which gives you a little flair and a 'GNOME Team' title by your posts. Finally, when logging in, you'll get a message from discobot. This friendly bot will guide you through the basic functionality. You can skip it if you want, but you'll miss out on getting a badge ( https://discourse.gnome.org/badges) Any questions, let me know. Thanks, Neil -- Neil McGovern Executive Director, The GNOME Foundation ___ engagement-list mailing list engagement-list@gnome.org https://mail.gnome.org/mailman/listinfo/engagement-list
Re: Infrastructure | New discourse instance (#99)
Neil McGovern commented: @tomtryf Updated -- View it on GitLab: https://gitlab.gnome.org/Infrastructure/Infrastructure/issues/99#note_449108 You're receiving this email because of your account on gitlab.gnome.org. ___ gnome-infrastructure mailing list gnome-infrastructure@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-infrastructure
Re: Infrastructure | New discourse instance (#99)
Neil McGovern commented: @tomtryf - Installed. Do you fancy having a look at discourse.gnome.org and seeing what it's like? -- View it on GitLab: https://gitlab.gnome.org/Infrastructure/Infrastructure/issues/99#note_448862 You're receiving this email because of your account on gitlab.gnome.org. ___ gnome-infrastructure mailing list gnome-infrastructure@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-infrastructure
