On Thu, Jan 24, 2019 at 4:00 AM, Allan Day wrote:
I'd personally like us to keep the path open for you and provide some
guarantees about Geary being able to use Online Accounts in the
future. I wonder if this should be part of a wider conversation about
Geary becoming GNOME Mail? :)
Seems
On Sun, Feb 3, 2019 at 8:59 PM, Christopher Davis via
desktop-devel-list wrote:
If we keep the mirrors around, then we should at the very least
ensure that pull requests aren't able to be opened at all
on the repos.
GitHub doesn't allow disabling pull requests, that's why we have the
FWIW I only use our GitHub mirrors when our GitLab is running slow. But
that happens often enough
On Mon, Feb 4, 2019 at 10:58 AM, philip.chime...@gmail.com wrote:
Could we take it all the way and just push the PR branch to
"$github_user_name/$branch_name" in the main repository on GitLab,
On Mon, Jun 3, 2019 at 5:40 AM, Allan Day wrote:
If the size of the theme is the issue, do we know what size is
acceptable?
For WebKit to be able to handle this, the required performance
improvement would be measured in orders of magnitude. I don't know
about Firefox.
Without changes in
On Wed, May 29, 2019 at 8:35 AM, Allan Day wrote:
Therefore, before we get too far into planning and implementing this
feature: does anyone know of any serious obstacles they'd face, if we
were to support a dark mode?
WebKit is having trouble with this now:
On Thu, May 30, 2019 at 4:15 AM, Allan Day wrote:
How does this relate to the dark mode in WebKit?
I was hoping that Web would follow the system-wide dark mode
preference, and expose it to websites...
The ideal, desired behavior is to enable dark mode on any websites that
opt-in to dark
On Wed, Jun 5, 2019 at 1:14 PM, Alexander wrote:
Since WebKit supports Apple's dark mode now, I wonder if mail clients
(and also Devhelp/Builder) will be able to provide styles for dark
mode with that.
Well we really don't, not yet. That's what I've been trying to say
Once we do,
On Wed, Jun 5, 2019 at 1:44 AM, Tristan Van Berkom
wrote:
Are you saying that WebKitGTK interprets the system theme and CSS to
render the HTML content ?
Yes, as does Firefox.
___
desktop-devel-list mailing list
desktop-devel-list@gnome.org
Hi,
It looks like the runtime is going to be broken for a couple days due
to https://gitlab.gnome.org/GNOME/gnome-build-meta/issues/181.
You can downgrade to the last good version with:
$ flatpak update
--commit=4935b45d02b85cf5ab09a7ec28f851fcc850f28f0e9b9911808f002c49aee6eb
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
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 Thu, Apr 18, 2019 at 12:29 PM, Milan Crha via desktop-devel-list
wrote:
One thing, with the prepared merge requests [which will need changes
in
the version reference (they reference libecal-2.0 as 3.33.1, while
it'll be a different version)], should I contact respective
maintainers
anyhow
On Sun, Apr 7, 2019 at 6:38 PM, Ty Young via desktop-devel-list
wrote:
If any of these aren't known and reported yet I can report them. I'm
using Arch/Fedora 30 Beta Silverblue.
I'd recommend reporting separate bugs for all of these.
___
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
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 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 Wed, Jun 26, 2019 at 9:04 AM, mcatanz...@gnome.org wrote:
Now Abderrahim has fixed the problems with the last attempt and we
are trying to upgrade to 19.08 again.
Also Tristan. Thanks Tristan!
___
desktop-devel-list mailing list
On Fri, Jun 21, 2019 at 3:16 AM, a.kitouni--- via desktop-devel-list
wrote:
Nightly apps may be broken (as in refuse to start) for up to 24h
until they're rebuilt against the new ABI, so if you depend on a
nigtly app don't update today.
Hi,
I wound up reverting back to the 18.08 runtime due
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
Hi,
GNOME 3.32.1 is now available. This is a stable release containing four
weeks' worth of bugfixes since the 3.32.0 release. Since it only
contains bugfixes, all distributions shipping 3.32.0 should upgrade.
If you want to compile GNOME 3.32.1, you can use the official
BuildStream project
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
On Fri, Apr 26, 2019 at 2:43 AM, Samuel Thibault
wrote:
I guess I am missing something in the process of releasing a version?
Or
is accerciser perhaps just not part of a desktop package set?
Only GNOME core elements are included in the release. accerciser is in
world, not core.
Michael
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
On Fri, Aug 2, 2019 at 5:51 PM, Michael Gratton wrote:
Is there any way to get notification for build failures here? I
frequently don't end up seeing the build failures. Email sent to
people listed in the project's DOAP maybe?
Unfortunately there's currently no way to be notified of build
On Fri, Aug 16, 2019 at 7:31 pm, Alexandre Franke
wrote:
Weekends are usually the time when most translations get done. If you
remove this opportunity, I guess we should consider freezing earlier
too so that translators basically get the same amount of time to do
their job.
I'm a bit confused
On Fri, Aug 16, 2019 at 10:39 pm, Alexandre Franke
wrote:
Indeed. Moreover, in my experience, many maintainers consciously leave
that time for translators and check the status of their module on
Damned lies to see if there’s any team currently working on it and
whether they need to wait just a
Hi,
I'd like to propose moving tarball deadlines for the 3.36 cycle one
business day earlier, from Mondays to Fridays, while leaving the
overall release deadline on Wednesday. That way, we can have the
weekend for trying to build the release. This will allow release team
more time to resolve
Hi,
Epiphany 3.34 is going to be a pretty crashy release, because we've
developed a memory corruption problem that seems almost impossible to
debug:
https://gitlab.gnome.org/GNOME/epiphany/issues/876
The bug report shows valgrind crashes on startup. I've tried to get a
working asan build
Eh, perhaps bad timing, but I was just running valgrind over geary
after a geary crash, and noticed:
https://bugs.webkit.org/show_bug.cgi?id=199295
which I had totally forgotten about.
I don't know whether that's our problem or not, but probably no sense
in worrying about mystery memory
On Sat, Aug 17, 2019 at 4:41 PM, mcatanz...@gnome.org wrote:
The bug report shows valgrind crashes on startup. I've tried to get a
working asan build of Tech Preview, but haven't been successful.
If anyone is willing to help with asan, that would be great.
Unfortunately we never solved this
Hi developers,
As of 45 minutes ago, we are now in hard code freeze for GNOME 3.34.0!
No further code changes may be made without permission from release
team.
The goal of this freeze is to improve the quality of GNOME 3.34. If you
think a code change will improve quality, has low risk of
On Tue, Sep 3, 2019 at 6:45 AM, Bastien Nocera
wrote:
Maybe release 3.32.x as a 3.34 instead if that's the problem?
We absolutely could, but have no way to know where the memory
corruption was actually introduced.
It could be an Epiphany regression (not unlikely). But it could also be
a
On Thu, Sep 12, 2019 at 2:45 AM, Milan Crha via desktop-devel-list
wrote:
As a real life example, I skipped 3.32.5 this year, because there was
no code change in the stable branch with which the users could
benefit.
The late stables are for bug fixes, from my point of view.
I wondered about
On Thu, Sep 12, 2019 at 8:22 AM, Bastien Nocera
wrote:
This is very important for the maintainers of libraries that live in
the GNOME runtime. Do we have a full list of those? What happens if
there are security issues that crop up in the meanwhile?
Security issues that crop up in the
On Fri, Sep 6, 2019 at 6:56 PM, Javier Jardón
wrote:
the final release is scheduled next Wednesday!
Oops, it will really be Thursday, September 12. The release was
originally scheduled for Wednesday because I'm bad at picking good
dates. You might still have stale calendar events scheduled
On Tue, Aug 6, 2019 at 10:20 AM, mcatanz...@gnome.org wrote:
So that leaves just Quadrapassel and Tali in need of help:
We have a volunteer for Quadrapassel too, so every game is now
assigned. Thanks all!
Although gnome-klotski, gnome-robots, and gnome-tetravex are assigned,
these are
On Tue, Aug 6, 2019 at 5:07 AM, Arnaud Bonatti
wrote:
Yes, I’ve by two times tried to avoid some work for translators in
original ways, and some of them have been not happy with that. We’ve
already discussed about that, and I’ve understood in the process
that
nothing is really doable here
On Tue, Aug 6, 2019 at 4:59 AM, Alberto Ruiz wrote:
I can take care of mahjongg, although not before next week as I am on
vacation and won't have access to a computer.
Thanks Alberto!
___
desktop-devel-list mailing list
Hi,
I'm trying to find new maintainers for the following games:
four-in-a-row, gnome-klotski, gnome-robots, gnome-mahjongg,
gnome-tetravex, quadrapassel, tali
The first three in the list used to be lightly maintained by me, but I
don't want to keep releasing them. I'll continue to care for
On Tue, Aug 6, 2019 at 1:17 PM, Mart Raudsepp wrote:
I can try my hand on Tali, if needed, as long as it remains written in
C. I don't feel strongly about it at all, just to help, so basically
if
no-one else steps up..
Was going to offer for both, but then found that the other one is
vala.
Hi developers!
It's that time of the year again: a new stable release, 3.34, fast
approaching. That means it's time to lock down our feature set and go
into bugfixing mode. As usual, the following freezes are now in effect:
* API/ABI freeze
* Feature freeze
* UI freeze
* String change
Hi developers and testers,
GNOME 3.33.90 is now available, slightly ahead of schedule for a change!
This is the first beta release for GNOME 3.34. To ensure the quality of
the final release, we have entered feature freeze, UI freeze, and API
freeze, so now is a good time for distributors
Hi,
This release will be delayed, probably until next week. We're still
working out problems with dependencies.
Michael
___
desktop-devel-list mailing list
desktop-devel-list@gnome.org
https://mail.gnome.org/mailman/listinfo/desktop-devel-list
On Wed, Jul 24, 2019 at 5:19 AM, Javier Jardón
wrote:
Little reminder: "The Freeze" is only a week and a half away (5th of
August),
so please be sure to finish on time all those awesome features you
have been working
on this cycle
Hi all,
To help the next release go smoother, I'd encourage
On Fri, Jun 28, 2019 at 9:36 AM, mcatanz...@gnome.org wrote:
Bug is
https://mail.gnome.org/archives/desktop-devel-list/2019-June/msg00018.html
Sorry: https://gitlab.gnome.org/GNOME/gnome-software/issues/723
___
desktop-devel-list mailing list
Hi again,
We've discovered that updating with GNOME Software will break your
flatpak apps. You must update with the flatpak CLI to fix this, not
with GNOME Software. Everything should be in good shape after you do a
one-time update using the CLI.
Bug is
Hi,
Please take a moment to look through your .doap files and remove any
old/inactive maintainers, or switch them from tags to
tags. There seem to be many projects just adding new
maintainers but never removing old ones, as if in fear of perhaps
offending the former maintainers. But it
101 - 147 of 147 matches
Mail list logo
