Bastien Nocera wrote:
> I haven't looked at library-web because I have a whole bunch of work
> that I'd need to do with it, but not the bandwidth...
I pushed an untested minimal change.
Fred
___
desktop-devel-list mailing list
On Mon, Jun 15, 2020 at 9:00 AM Bastien Nocera wrote:
>
> Doing some thread grave digging.
Just as an FYI - in terms of happening - I see it very likely that
github and gitlab are all going to be changing the name of the default
branch in git. (I talked to Nuritzi - and she said discussions have
On Mon, 2019-05-06 at 21:13 +0200, Frederic Peters wrote:
> Bastien Nocera wrote:
>
> > - How?
> >
> > It is possible to rename the "master" branch in git. It's also
> > possible
> > to add a "link" of sorts so that software that specifically
> > references
> > "master" can be made to work with
Doing some thread grave digging.
On Sat, 2019-05-04 at 15:18 +0200, Bastien Nocera wrote:
> On Sat, 2019-05-04 at 12:32 +0200, drago01 via desktop-devel-list
> wrote:
> > https://dictionary.cambridge.org/amp/english/master
> >
> > Master / slave relation is just one of the possible meanings but
Bastien Nocera wrote:
> - How?
>
> It is possible to rename the "master" branch in git. It's also possible
> to add a "link" of sorts so that software that specifically references
> "master" can be made to work with the new name[5].
I checked and there is an hardcoded reference (git) master
On Fri, May 03, 2019 at 12:09:11PM +0200, Bastien Nocera wrote:
> On Thu, 2019-04-25 at 11:46 +1000, Michael Gratton wrote:
> > Hi all,
> >
> > I'd like to formally propose as a GNOME Goal that GNOME modules
> > replace references to the terms "master" and "slave". [...] The scope
> > would be to
On 4 May 2019, at 17:47, drago01 wrote:
>
> "The term master copy has a unique meaning in art that predates the
> modern term. In art, a master copy is the process of drawing or
> painting a copy of a another artist's work. It is most common to copy
> the work of a master artist, hence the
On Saturday, May 4, 2019, Bastien Nocera wrote:
> On Sat, 2019-05-04 at 12:32 +0200, drago01 via desktop-devel-list
> wrote:
> > https://dictionary.cambridge.org/amp/english/master
> >
> > Master / slave relation is just one of the possible meanings but not
> > in the context of master copy
> >
On Sat, May 4, 2019 at 10:44 AM Ask Hjorth Larsen via
desktop-devel-list wrote:
> * The proposed link between master branch and slavery is based on
> arguments that require a dictionary and etymological analysis. But if
> we think master has bad connotations, this is a question of how it
>
Am Fr., 3. Mai 2019 um 14:46 Uhr schrieb Bastien Nocera :
>
> On Fri, 2019-05-03 at 14:07 +0200, Carmen Bianca Bakker wrote:
> > Je ven, 2019-05-03 je 12:09 +0200, Bastien Nocera skribis:
> > > - Why?
> > >
> > > For the same reasons we'd want to change master/slave references.
> > > Though it
I don't like the direction this thread has taken. It has devolved into
infighting between one another, and as such I think it best to end it here.
People have made their opinions known, and no more minds are likely to be
changed in either direction with the tone of the discussion as it is now.
On
On Sat, May 4, 2019 at 4:22 AM, Bastien Nocera
wrote:
The person you quoted is a troll. In fact, I'm not sure there's any
comments on that issue that aren't trolls (apart from the OP and the
repository owner).
Ah OK then, fooled me because he took a such strong plausibly-sincere
stance
On Sat, 2019-05-04 at 12:32 +0200, drago01 via desktop-devel-list
wrote:
> https://dictionary.cambridge.org/amp/english/master
>
> Master / slave relation is just one of the possible meanings but not
> in the context of master copy
>
> "an original version of something from which copies can be
On Sat, 2019-05-04 at 11:33 +0200, Bastien Nocera wrote:
>
> I don't have a good answer for this. I didn't find an explanation one
> way or the other, but there are uses of "slave copies" that aren't
> "copied from master" in Google, but usually not in
> recording/publishing
> fields.
>
> I just
On Saturday, May 4, 2019, Bastien Nocera wrote:
> On Sat, 2019-05-04 at 01:28 +0200, Matthias Klumpp wrote:
> > Am Fr., 3. Mai 2019 um 15:36 Uhr schrieb Carmen Bianca Bakker
> > :
> > > Je ven, 2019-05-03 je 14:45 +0200, Bastien Nocera skribis:
> > > > [...]
> > > > If we agree that the "master"
On Sat, 2019-05-04 at 01:28 +0200, Matthias Klumpp wrote:
> Am Fr., 3. Mai 2019 um 15:36 Uhr schrieb Carmen Bianca Bakker
> :
> > Je ven, 2019-05-03 je 14:45 +0200, Bastien Nocera skribis:
> > > [...]
> > > If we agree that the "master" in the git branch name is the same
> > > "master" that's used
On Fri, 2019-05-03 at 18:31 -0500, mcatanz...@gnome.org wrote:
> On Fri, May 3, 2019 at 5:57 PM, Bastien Nocera
> wrote:
> > Seriously Michael, you’re embarrassing yourself.
>
> I don't feel very embarrassed. Your suggested alternative name,
> "main,"
> is clearly considered to be offensive by
On Sat, May 4, 2019 at 2:31 AM wrote:
> On Fri, May 3, 2019 at 5:57 PM, Bastien Nocera
> wrote:
> > Seriously Michael, you’re embarrassing yourself.
>
> I don't feel very embarrassed. Your suggested alternative name, "main,"
> is clearly considered to be offensive by at least one of the very
On Fri, May 3, 2019 at 5:57 PM, Bastien Nocera
wrote:
Seriously Michael, you’re embarrassing yourself.
I don't feel very embarrassed. Your suggested alternative name, "main,"
is clearly considered to be offensive by at least one of the very same
people who don't like "master," and who
Am Fr., 3. Mai 2019 um 15:36 Uhr schrieb Carmen Bianca Bakker
:
>
> Je ven, 2019-05-03 je 14:45 +0200, Bastien Nocera skribis:
> > [...]
> > If we agree that the "master" in the git branch name is the same
> > "master" that's used in "master copy" meaning "the original", "the one
> > medium that
> On 4 May 2019, at 00:29, mcatanz...@gnome.org wrote:
>
>> On Fri, May 3, 2019 at 5:09 AM, Bastien Nocera wrote:
>> - And to what?
>> A few possible names were mentioned/used. "mainline" was thought to
>> have strong connections to drug use, "release" (use in the contributor
>> covenant)
On Fri, May 3, 2019 at 5:09 AM, Bastien Nocera
wrote:
- And to what?
A few possible names were mentioned/used. "mainline" was thought to
have strong connections to drug use, "release" (use in the contributor
covenant) seems to restrictive (we also do releases from other
branches). I like
On Fri, 2019-05-03 at 15:35 +0200, Carmen Bianca Bakker wrote:
> Je ven, 2019-05-03 je 14:45 +0200, Bastien Nocera skribis:
> > >
> > If we agree that the "master" in the git branch name is the same
> > "master" that's used in "master copy" meaning "the original", "the
> > one
> > medium that
Je ven, 2019-05-03 je 14:45 +0200, Bastien Nocera skribis:
> > Can this assertion be backed up by anything substantive? This keeps
> > being said, and I'm willing to believe it, but no actual arguments
> > are
> > being made as to _why_ this is.
> >
> > Specifically, this question needs an
On Fri, May 3, 2019 at 8:08 AM Carmen Bianca Bakker
wrote:
> The shitstorm is to be expected one way or another. The only difference
> would be whether GNOME or The Linux Foundation is smeared in internet
> comments as "SJWs changing things and I don't like it".
Better us than them, because
On Fri, 2019-05-03 at 14:07 +0200, Carmen Bianca Bakker wrote:
> Je ven, 2019-05-03 je 12:09 +0200, Bastien Nocera skribis:
> > - Why?
> >
> > For the same reasons we'd want to change master/slave references.
> > Though it usually isn't paired up with "slave" (excluding the
> > "gitslave" addon),
Je ven, 2019-05-03 je 12:09 +0200, Bastien Nocera skribis:
> - Why?
>
> For the same reasons we'd want to change master/slave references.
> Though it usually isn't paired up with "slave" (excluding the
> "gitslave" addon), it still has strong connotations of subjugation, and
> some ties with the
On Fri, 2019-05-03 at 08:36 +0200, Daniel Mustieles García via desktop-
devel-list wrote:
> The problem is that he is not only writting a summary. He has renamed
> master branch in GitLab, he has noticed people in Ubuntu about this
> change, he has ignored us when we have said his arguments about
On Wed, 2019-05-01 at 12:48 +0100, Richard Hughes via desktop-devel-
list wrote:
> On Wed, 1 May 2019 at 12:38, Michael Gratton wrote:
> > They have also been successful in getting other projects to use
> > more
> > inclusive language. For example, MongoDB initially refused to stop
> > using the
On Wed, 2019-05-01 at 21:58 +1000, Michael Gratton wrote:
> On Wed, May 1, 2019 at 21:52, Michael Gratton wrote:
> > On Wed, May 1, 2019 at 12:48, Richard Hughes
> > wrote:
> > > On Wed, 1 May 2019 at 12:38, Michael Gratton wrote:
> > > > They have also been successful in getting other
On Thu, 2019-04-25 at 11:46 +1000, Michael Gratton wrote:
> Hi all,
>
> I'd like to formally propose as a GNOME Goal that GNOME modules
> replace references to the terms "master" and "slave". [...] The scope
> would be to replace occurrences of the terms appearing [...] git
> repositories
I
On Fri, 2019-05-03 at 08:47 +0200, Daniel Mustieles García via desktop-
devel-list wrote:
>
>
> El mié., 1 may. 2019 a las 14:39, Michael Gratton ()
> escribió:
> > On Wed, May 1, 2019 at 14:30, Carmen Bianca Bakker
> > wrote:
> > >
> > > I think the problem is that, when prompted why we
On Wed, 2019-05-01 at 10:08 -0500, mcatanz...@gnome.org wrote:
> On Wed, May 1, 2019 at 6:08 AM, Michael Gratton wrote:
> > This has already been covered in the original proposal under
> > objection (1) "It doesn't matter". As has already been discussed,
> > what actually doesn't matter is what
El mié., 1 may. 2019 a las 14:39, Michael Gratton () escribió:
> On Wed, May 1, 2019 at 14:30, Carmen Bianca Bakker
> wrote:
> >
> > I think the problem is that, when prompted why we should make this
> > change, you said that we need only look at Python to see why this
> > change is good. But
El mié., 1 may. 2019 a las 3:49, Ask Hjorth Larsen ()
escribió:
> Am Mi., 1. Mai 2019 um 01:07 Uhr schrieb Michael Gratton :
> >
> > On Tue, Apr 30, 2019 at 17:53, Daniel Mustieles García
> > wrote:
> > > What has happened with this? We have a repo with a non-standard
> > > branch name and no
El mié., 1 may. 2019 a las 1:06, Michael Gratton () escribió:
> On Tue, Apr 30, 2019 at 17:53, Daniel Mustieles García
> wrote:
> > What has happened with this? We have a repo with a non-standard
> > branch name and no consensus for a global change, do we?
>
> Just trying to find the time to
El mié., 1 may. 2019 a las 4:58, Germán Poo-Caamaño ()
escribió:
> On Wed, 2019-05-01 at 03:49 +0200, Ask Hjorth Larsen via desktop-devel-
> list wrote:
> > Am Mi., 1. Mai 2019 um 01:07 Uhr schrieb Michael Gratton <
> > m...@vee.net>:
> > > On Tue, Apr 30, 2019 at 17:53, Daniel Mustieles García
>
On Wed, 2019-05-01 at 15:53 +0200, Carmen Bianca Bakker wrote:
> Je mer, 2019-05-01 je 23:31 +1000, Michael Gratton skribis:
> > On Wed, May 1, 2019 at 15:19, Carmen Bianca Bakker
> >
> > > > I did however point out that Python has replaced uses of the
> > > > term
> > > > "master", and we
> On 25 Apr 2019, at 02:46, Michael Gratton wrote:
>
> I deliberately chose "mainline" for Geary's mainline branch name because it
> has the same auto-complete prefix as "master", for example. Want to check out
> the mainline branch? Just type "git co m", just like you always have.
>
On Thu, Apr 25, 2019 at 02:02:43PM +0200, jtojnar--- via desktop-devel-list
wrote:
> On Thu, 25 Apr, 2019 at 11:21 AM, Daniel Playfair Cal via desktop-devel-list
> wrote:
> > "master/slave" -> "leader/follower"
>
> Please note that leader/follower terms are commonly associated with
>
On Wed, May 1, 2019, 15:24 Michael Gratton wrote:
> On Wed, May 1, 2019 at 14:32, Ernestas Kulik
> wrote:
> > On Wed, 2019-05-01 at 21:38 +1000, Michael Gratton wrote:
> >>
> >> After deliberately setting out to make the project more inclusive,
> >> Python has reversed a five-year-long trend
On Wed, 2019-05-01 at 23:31 +1000, Michael Gratton wrote:
> It is telling that no one is complaining about replacing uses of
> "slave" by itself alone.
What a completely bizarre thing to say.
The word "slave" doesn't have a whole slew of homonyms with different
meanings. Only one verb.
So
Je ĵaŭ, 2019-05-02 je 01:10 +1000, Daniel Playfair Cal skribis:
> As English speakers, we choose how our language evolves. It is a choice to
> keep using a word just as it is a choice to swap it for a new one. It is not
> censorship to make a choice one way or the other. Nobody in this thread
Just a few comments I think are worth making:
- The word "master" as in master branch is an synonym/analogy/reference,
not a coincidence. Language develops together with history, and the
meanings of words constantly evolve. If a word has multiple meanings, it is
usually because the
On Wed, May 1, 2019 at 6:08 AM, Michael Gratton wrote:
This has already been covered in the original proposal under
objection (1) "It doesn't matter". As has already been discussed,
what actually doesn't matter is what you or I think, it is the people
who have been affected by the language we
On Wed, May 1, 2019 at 12:22 AM, Tristan Van Berkom
wrote:
We should also not show favoritism of one set of cultural values over
another, I feel that censorship to this degree is a very western
concept which we should not lend any credit to. Ask has already
pointed
out that the possible
Je mer, 2019-05-01 je 23:31 +1000, Michael Gratton skribis:
> On Wed, May 1, 2019 at 15:19, Carmen Bianca Bakker
>
> > > I did however point out that Python has replaced uses of the term
> > > "master", and we should do the same.
> >
> > We should. But not all instances of "master" are equally
On Wed, May 1, 2019 at 15:19, Carmen Bianca Bakker
I did however point out that Python has replaced uses of the term
"master", and we should do the same.
We should. But not all instances of "master" are equally
problematic—that's the main debate here. I don't see anybody here
disagreeing
On Wed, May 1, 2019 at 14:32, Ernestas Kulik
wrote:
On Wed, 2019-05-01 at 21:38 +1000, Michael Gratton wrote:
After deliberately setting out to make the project more inclusive,
Python has reversed a five-year-long trend of declining number of
core
devs and it has been increasing ever
Je mer, 2019-05-01 je 22:38 +1000, Michael Gratton skribis:
> On Wed, May 1, 2019 at 14:30, Carmen Bianca Bakker
> wrote:
> > I think the problem is that, when prompted why we should make this
> > change, you said that we need only look at Python to see why this
> > change is good. But Python
On Wed, 2019-05-01 at 15:03 +0300, Alberts Muktupāvels via desktop-
devel-list wrote:
>
> Numbers please? For example how many contributors GNOME has lost last
> year?
> Do you speak about one or two people? Hundreds people? More?
To be fair, I think that even losing one or two could have a
On Wed, May 1, 2019 at 14:30, Carmen Bianca Bakker
wrote:
I think the problem is that, when prompted why we should make this
change, you said that we need only look at Python to see why this
change is good. But Python did NOT change the name of their master
branch, so it's a disingenuous
Hi Günther,
On Wed, May 1, 2019 at 14:16, Günther Wagner wrote:
i read this list with interest because its a controversial topic. What
i want to know: lets take the approach and rename all master-branches
to something different. Anyone thought about that this will lead to
more usage of master
On Wed, 2019-05-01 at 21:38 +1000, Michael Gratton wrote:
>
> After deliberately setting out to make the project more inclusive,
> Python has reversed a five-year-long trend of declining number of
> core
> devs and it has been increasing ever since. They have for example,
> in
> the last three
Hi Michael,
Je mer, 2019-05-01 je 21:52 +1000, Michael Gratton skribis:
> On Wed, May 1, 2019 at 12:48, Richard Hughes
> wrote:
> > On Wed, 1 May 2019 at 12:38, Michael Gratton wrote:
> > > They have also been successful in getting other projects to use more
> > > inclusive language. For
Hi Michael,
i read this list with interest because its a controversial topic. What
i want to know: lets take the approach and rename all master-branches
to something different. Anyone thought about that this will lead to
more usage of master than it is used now? People will come up in
IRC and
On Wed, 2019-05-01 at 15:03 +0300, Alberts Muktupāvels wrote:
>
> Numbers please? For example how many contributors GNOME has lost last
> year? Do you speak about one or two people? Hundreds people? More?
General numbers for authors and commits can be found at the beginning
of every Release Notes
On Wed, May 1, 2019 at 2:09 PM Michael Gratton wrote:
> Hi Tristan,
>
> On Wed, May 1, 2019 at 14:22, Tristan Van Berkom via desktop-devel-list
> wrote:
> > Instead, by opening the door to censorship of words which are not
> > themselves inherently vulgar or foul (i.e. 'master' is not
On Wed, May 1, 2019 at 21:52, Michael Gratton wrote:
On Wed, May 1, 2019 at 12:48, Richard Hughes
wrote:
On Wed, 1 May 2019 at 12:38, Michael Gratton wrote:
They have also been successful in getting other projects to use
more
inclusive language. For example, MongoDB initially refused to
On Wed, May 1, 2019 at 13:46, Ask Hjorth Larsen
wrote:
Also what does Python have to do with this? What specific gains came
from renaming their branch? https://github.com/python/cpython . It
looks to me like they did not rename the branch. This sort of stuff
has been pointed out to you in
On Wed, 1 May 2019 at 12:38, Michael Gratton wrote:
> They have also been successful in getting other projects to use more
> inclusive language. For example, MongoDB initially refused to stop
> using the term "master", but then relented after Python did so.
That's misrepresenting it *AGAIN*.
Am Mi., 1. Mai 2019 um 13:09 Uhr schrieb Michael Gratton :
>
> In the end, as the experience Python has had clearly shows, we will
> gain much, much more by being inclusive than we lose by entertaining a
> small minority who would rather we aren't.
You imply that some of us desire GNOME
On Wed, May 1, 2019 at 13:16, Ernestas Kulik
wrote:
On Wed, 2019-05-01 at 21:08 +1000, Michael Gratton wrote:
In the end, as the experience Python has had clearly shows, we will
gain much, much more by being inclusive than we lose by entertaining
a small minority who would rather we aren't.
On Wed, 1 May 2019 at 06:23, Tristan Van Berkom via desktop-devel-list
wrote:
> Proposing that we replace references to master/slave relationships with
> other terminology and proposing that we eliminate the usage of both
> words entirely are two entirely different proposals, this is a proposal
>
On Wed, 2019-05-01 at 21:08 +1000, Michael Gratton wrote:
> In the end, as the experience Python has had clearly shows, we will
> gain much, much more by being inclusive than we lose by entertaining
> a
> small minority who would rather we aren't.
Excuse me if I missed this, but can you
Hi Tristan,
On Wed, May 1, 2019 at 14:22, Tristan Van Berkom via desktop-devel-list
wrote:
Instead, by opening the door to censorship of words which are not
themselves inherently vulgar or foul (i.e. 'master' is not considered
a
'swear word'), we are creating an atmosphere where people
Hi Matthias,
I am replying to your post because I think it is masterfully written
and agree with it.
That said, the opinions expressed here are my own, I urge people to
not confuse my own arguments with Matthias's, and consider
these separately.
On Fri, 2019-04-26 at 19:11 +0200, Matthias
On Wed, 2019-05-01 at 03:49 +0200, Ask Hjorth Larsen via desktop-devel-
list wrote:
> Am Mi., 1. Mai 2019 um 01:07 Uhr schrieb Michael Gratton <
> m...@vee.net>:
> > On Tue, Apr 30, 2019 at 17:53, Daniel Mustieles García
> > wrote:
> > > What has happened with this? We have a repo with a
Am Mi., 1. Mai 2019 um 01:07 Uhr schrieb Michael Gratton :
>
> On Tue, Apr 30, 2019 at 17:53, Daniel Mustieles García
> wrote:
> > What has happened with this? We have a repo with a non-standard
> > branch name and no consensus for a global change, do we?
>
> Just trying to find the time to write
On Tue, Apr 30, 2019 at 17:53, Daniel Mustieles García
wrote:
What has happened with this? We have a repo with a non-standard
branch name and no consensus for a global change, do we?
Just trying to find the time to write up a summary of where we are at
and a draft plan to move forward.
Oh
On Tue, 2019-04-30 at 17:53 +0200, Daniel Mustieles García wrote:
> What has happened with this? We have a repo with a non-standard
> branch name and no consensus for a global change, do we?
The repository in question, Geary, has had a git configuration change
applied so that the old branch name
What has happened with this? We have a repo with a non-standard branch name
and no consensus for a global change, do we?
El sáb., 27 abr. 2019 a las 15:19, Bastien Nocera ()
escribió:
> On Sat, 2019-04-27 at 14:13 +0200, Ask Hjorth Larsen via desktop-devel-
> list wrote:
> >
>
> > This sounds
On Sat, 2019-04-27 at 14:13 +0200, Ask Hjorth Larsen via desktop-devel-
list wrote:
>
> This sounds beautiful, but mindless prescriptivism like this won't
> help any of the peoples you mention. Want to help? Donate money
> where it matters. Vote for someone good. Avoid buying smartphones
>
Am Sa., 27. Apr. 2019 um 01:09 Uhr schrieb Michael Gratton :
>
> On Fri, Apr 26, 2019 at 20:33, Ask Hjorth Larsen via desktop-devel-list
> wrote:
> >
> > 0) It is problematic to work with hundreds of projects when they do
> > not use the same branch name (translators like myself), but this time
>
On Fri, Apr 26, 2019 at 20:33, Ask Hjorth Larsen via desktop-devel-list
wrote:
0) It is problematic to work with hundreds of projects when they do
not use the same branch name (translators like myself), but this time
we want to make it consistent, so ...
Hence this is proposing to make the
Am Fr., 26. Apr. 2019 um 19:11 Uhr schrieb Matthias Klumpp
:
>
> Am Fr., 26. Apr. 2019 um 18:12 Uhr schrieb :
> > I'm a little surprised that nobody has yet mentioned the elephant in
> > the room. The definition of "git" is not very inclusive:
>
> [ ...]
>
> Please don't ready any of the
Am Fr., 26. Apr. 2019 um 18:12 Uhr schrieb :
> I'm a little surprised that nobody has yet mentioned the elephant in
> the room. The definition of "git" is not very inclusive:
>
> [...]
I really did not want to comment on this thread initially, but I would
like to add a thought to this afterall:
Hi,
On Fri, 2019-04-26 at 11:12 -0500, mcatanz...@gnome.org wrote:
> Shall we install our own inclusive symlink for git now, to avoid
> potentially-unpleasant connotations?
Would we be in the position of doing so?
My feeling is that we can control the branch names more easily than the
On Fri, 26 Apr 2019 at 17:12, wrote:
>
> I'm a little surprised that nobody has yet mentioned the elephant in
> the room. The definition of "git" is not very inclusive:
>
What did I say, upthread, about falling into the "slippery slope" fallacy,
and sticking to the topic of discussion?
Do we
I'm a little surprised that nobody has yet mentioned the elephant in
the room. The definition of "git" is not very inclusive:
From https://www.merriam-webster.com/dictionary/git:
British
: a foolish or worthless person
Or from https://www.thefreedictionary.com/git:
n. Chiefly British
I've seen this thread so far and I'd like to add my POV.
I don't thing master is an offensive word because in Portuguese, among
other meanings, it also means "matrix".
Any choosen work will have a different meaning depending upon culture,
tradition and spoken-language.
We can't though forget to
Hi Michael,
Je ven, 2019-04-26 je 09:24 +1000, Michael Gratton skribis:
> On Thu, Apr 25, 2019 at 09:02, Carmen Bianca Bakker
> wrote:
> > Defaults and conventions matter. One reason I like GNOME so much is
> > because the defaults are amazing. And while "master" is a bit of a
> > sucky
On Fri, Apr 26, 2019 at 09:55, Michael Gratton wrote:
On Thu, Apr 25, 2019 at 14:40, Florian Müllner
wrote:
On Thu, Apr 25, 2019 at 1:45 PM Carlos Soriano
wrote:
For making this change properly, I have some questions:
- Is there a possibility to redirect master to any other name
Hi Adel,
On Fri, 2019-04-26 at 04:29 +0200, drago01 via desktop-devel-list wrote:
> Assuming there is a problem in the first place which I doubt. I never
> heard of a case where someone refused to contribute to a project just
> because the default branch is called master.
>
> I'd suggest to
Hi,
On Fri, 2019-04-26 at 11:07 +1000, Peter Hutterer wrote:
> Which is the crux of the matter really: whatever you're going to pick
> will have different connotations in other languages. Many ESL
> speakers
> will primarily think in their own language and substitute the words
> to
> English.
On Friday, April 26, 2019, Michael Gratton wrote:
> On Thu, Apr 25, 2019 at 09:02, Carmen Bianca Bakker <
> car...@carmenbianca.eu> wrote:
>
>> Defaults and conventions matter. One reason I like GNOME so much is
>> because the defaults are amazing. And while "master" is a bit of a
>> sucky
On 26/4/19 24:56 , mcatanz...@gnome.org wrote:
Hard to believe this is a serious discussion that we're actually having.
On Thu, Apr 25, 2019 at 7:02 AM, jtojnar--- via desktop-devel-list
wrote:
On Thu, 25 Apr, 2019 at 11:21 AM, Daniel Playfair Cal via
desktop-devel-list wrote:
On Thu, Apr 25, 2019 at 14:40, Florian Müllner
wrote:
On Thu, Apr 25, 2019 at 1:45 PM Carlos Soriano
wrote:
For making this change properly, I have some questions:
- Is there a possibility to redirect master to any other name
somehow?
Oh, that is a good question. A quick search finds
On Thu, Apr 25, 2019 at 09:02, Carmen Bianca Bakker
wrote:
Defaults and conventions matter. One reason I like GNOME so much is
because the defaults are amazing. And while "master" is a bit of a
sucky default, it still has a lot of weight as a default. And I
question whether it is worth the
> They all come from the same word with the same connotations:
> https://en.wiktionary.org/wiki/master
Connotations listed on the Wiktionary page for master differ a lot. The way git
and audio engineers use the word master, it's the 13th definition from the
link, meaning an original.
As a person from a part of the world where slavery has been basically
nonexistent after the end of the Middle Ages, it is very hard for me to
imagine the effect the word itself has on people from areas where the
presence of slavery is still felt today. Being an engineer, whenever I
encounter a
Je ĵaŭ, 2019-04-25 je 09:53 -0400, Pat Suwalski skribis:
> On 2019-04-25 6:43 a.m., Bastien Nocera wrote:
> > It's non-gender neutral, which was mentioned earlier in the thread.
> >
> > See the master/maiden section of:
> >
Hard to believe this is a serious discussion that we're actually having.
On Thu, Apr 25, 2019 at 7:02 AM, jtojnar--- via desktop-devel-list
wrote:
On Thu, 25 Apr, 2019 at 11:21 AM, Daniel Playfair Cal via
desktop-devel-list wrote:
"master/slave" -> "leader/follower"
Please note that
El jue., 25 abr. 2019 a las 16:40, Andre Klapper () escribió:
> On Thu, 2019-04-25 at 16:24 +0200, Daniel Mustieles García wrote:
> > The next change we could discuss is about to remove daemons, parents
> > killing child process, zombies...
>
> Feel free to start that discussion if daemons and
On Thu, 2019-04-25 at 16:24 +0200, Daniel Mustieles García wrote:
> The next change we could discuss is about to remove daemons, parents
> killing child process, zombies...
Feel free to start that discussion if daemons and zombies bother you.
Trying to create a more welcoming environment by
Emmanuele, that was only a joke, to try to calm things down ;-)
My main target is to talk about the current change in Geary's master
branch. Once fixed or resolved that point, we can discuss the next step
El jue., 25 abr. 2019 a las 16:27, Emmanuele Bassi ()
escribió:
>
>
> On Thu, 25 Apr 2019
On Thu, Apr 25, 2019 at 10:22 AM, Pat Suwalski wrote:
Doesn't change the fact that it's accurate, and is the correct
computer terminology.
Surely if GNOME can be inclusive of someone who uses SJW as a slur, we
can accomodate someone who has a different understanding of the words
master
On Thu, 25 Apr 2019 at 15:24, Daniel Mustieles García via
desktop-devel-list wrote:
> The next change we could discuss is about to remove daemons, parents
> killing child process, zombies...
>
Let's not play the tiresome "slippery slope" fallacy, here, and try to
stick to the topic of the
I would suggest to you that trying to be "inclusive" turns a lot of
people off, making it overall less inclusive. ie, negative gains.
Sorry, but I strongly disagree with that. GNOME's inclusiveness is the
only reason I participate as
a person of color. I've also seen a wealth of diversity in
The next change we could discuss is about to remove daemons, parents
killing child process, zombies...
I'd vote for fixing the current change in branch name first and once done
that discuss and comment about language, slavery and whatever we consider
we could apply to our project to be more less
1 - 100 of 140 matches
Mail list logo
