Hi,
On Mon, Feb 11, 2019 at 4:46 PM Allan Day wrote:
> The “documents” source type is primarily used by GNOME Documents to
> access Google Drive. […]
> GNOME Documents is able to use the “files” source type as an
> alternative to the documents type, and can be converted so that it can
> continue
On Fri, 15 Feb 2019 20:19:11 +
Emmanuele Bassi via desktop-devel-list wrote:
> Hi Joanne;
>
> the switch to Meson for various libraries broke the expectations of
> library-web, which is used to populate developer.gnome.org. The scripts
> expect the HTML for the API reference to be in the
> On 17 Feb 2019, at 18:18, Alexandre Franke wrote:
>
> Hi,
>
>> On Mon, Feb 11, 2019 at 4:46 PM Allan Day wrote:
>> The “documents” source type is primarily used by GNOME Documents to
>> access Google Drive. […]
>> GNOME Documents is able to use the “files” source type as an
>> alternative
Hi,
Every so often I look at a change like
https://gitlab.gnome.org/GNOME/tracker/merge_requests/58 or
https://gitlab.gnome.org/GNOME/tracker-miners/issues/49, which change or
remove the behaviour of Meson configuration options.
Do we have a policy for if/when we can do breaking changes to Meson
> On 17 Feb 2019, at 04:04, mcatanz...@gnome.org wrote:
>
>> 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
>>
On Sat, Feb 16, 2019 at 7:58 PM wrote:
> 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
On Sun, 17 Feb, 2019 at 4:58 AM, Michael Terry wrote:
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.
Seconded!
Also, Debarshi, sorry for jumping
