On Sat, Feb 16, 2019 at 2:57 PM, Nathan Graule via desktop-devel-list
wrote:
A solution would be for distribution package maintainers to use the
binary tarball as a base instead of sources - this way the build can
be
done with secrets (ie. using GitLab CI and environment variable
secrets) and
A solution would be for distribution package maintainers to use the
binary tarball as a base instead of sources - this way the build can be
done with secrets (ie. using GitLab CI and environment variable
secrets) and sent to distributions for packaging. This certainly puts
GNOME in a unique
On Sat, Feb 16, 2019 at 12:57 PM, mcatanz...@gnome.org wrote:
It's not clear to me how g-o-a can continue to exist, then. Also,
Epiphany's Safe Browsing support. (How do Firefox and Chromium make
this work?)
Turns out it's a new restriction that took effect on January 16, 2019.
So probably
On Sat, Feb 16, 2019 at 11:58 AM, Michael Terry
wrote:
“Developer credentials (such as passwords, keys, and client IDs)
are intended to be used by you and identify your API Client. You will
keep your credentials confidential and make reasonable efforts to
prevent and discourage other API
Thank you for the clarification! As someone that had been confused about the
intent and ended up relying on GOA in my third party app, it’s nice to see the
intention spelled out so clearly.
I just wanted to mention an interesting challenge in having open source apps
handle this themselves.
