Re: Proposal: Replace all references to master/slave in GNOME modules

2019-04-24 Thread Daniel Mustieles García via desktop-devel-list
Hi Michael, Please stop lying about changes in Django, Rust or Python branches' names... they stil use «master» for the main branch. Here are the changes those projects are discussing: Djando: db configuration. The comments in the issue you've mentioned are an interesting reading... did you read

Re: Proposal: Replace all references to master/slave in GNOME modules

2019-04-24 Thread Ross Burton
On Thu, 25 Apr 2019 at 06:21, wrote: > This should go without saying, but master branches are not a reference > to slavery, rather to canonicity. What Michael said. Replacing Master/Slave terminology is a worthwhile task, but that doesn't mean doing a blanket search-and-replace for 'master'. No

Re: Proposal: Replace all references to master/slave in GNOME modules

2019-04-24 Thread mcatanzaro
This should go without saying, but master branches are not a reference to slavery, rather to canonicity. The master branch is the canonical branch, the primary copy. The relevant dictionary definition here (Merriam-Webster) is "an original from which copies can be made." As was pointed out b

Re: Proposal: Replace all references to master/slave in GNOME modules

2019-04-24 Thread Timm Bäder
Can't we just focus in the literally thousands of bug report we have absolutely nobody to work on instead? That would, like, actually improve the life of people. This is almost one month too late. On April 25, 2019 3:46:57 AM GMT+02:00, Michael Gratton wrote: >Hi all, > >I'd like to formally p

Proposal: Replace all references to master/slave in GNOME modules

2019-04-24 Thread Michael Gratton
Hi all, I'd like to formally propose as a GNOME Goal that GNOME modules replace references to the terms "master" and "slave". This is a worthwhile thing to do for social inclusiveness[0]. Many FOSS and non-FOSS projects, including Django[1], Python[2], and Rust[3] and the ISC[4]) have already

Re: Heads up: Geary mainline development branch renamed to `mainline`

2019-04-24 Thread Michael Gratton
On Wed, Apr 24, 2019 at 13:31, Daniel Mustieles García wrote: So hardcoding the name "mainline" to the list of branches that Damned Lies' looks up resolves the problem for you... and tomorrow another maintainer decides to rename it's master branch to whatever_non_offensive_name and DL breaks a

Re: Heads up: Geary mainline development branch renamed to `mainline`

2019-04-24 Thread Daniel Mustieles García via desktop-devel-list
So hardcoding the name "mainline" to the list of branches that Damned Lies' looks up resolves the problem for you... and tomorrow another maintainer decides to rename it's master branch to whatever_non_offensive_name and DL breaks again until a patch is submited... no, sorry but this is not a solut

Re: Please do a release if you have removed/changed a build dependency recently

2019-04-24 Thread Javier Jardón
On Wed, 24 Apr 2019 at 00:21, Javier Jardón wrote: > > Hi, > > we currently have to apply these to make be able to compile the GNOME > 3.33.1 release: > > b8f6e28 Revert "sdk/vte.bst: port to meson" Apologies, vte was already tagged when I sent this emal Cheers, Javier Jardón GNOME Release Te

Please do a release if you have removed/changed a build dependency recently

2019-04-24 Thread Javier Jardón
Hi, we currently have to apply these to make be able to compile the GNOME 3.33.1 release: b8f6e28 Revert "sdk/vte.bst: port to meson" 7156f2b Revert "elements/core-deps/libvirt-glib.bst: It doesn't depend on intltool anymore" 1196f6a Revert "elements/core-deps/libgsf.bst: It doesn't depend on int