After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 743981 - Enable authentication for evolution-data-server calendars
Enable authentication for evolution-data-server calendars
Status: RESOLVED WONTFIX
Product: california
Classification: Other
Component: backing
master
Other Linux
: Normal normal
: ---
Assigned To: California Maintainers
California Maintainers
gnome[unmaintained]
Depends on: 743961
Blocks:
 
 
Reported: 2015-02-04 11:46 UTC by Milan Crha
Modified: 2019-10-10 14:00 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Milan Crha 2015-02-04 11:46:51 UTC 
After recent changes for evolution-data-server 3.13.90 [1], the clients should
take care of authentication of the sources (books, calendars,...) on their own.
To make it easier, eds provides a libedataserverui-1.2 library with necessary
functionality which also evolution itself uses.

I'd like to help here, but I see you've written everything in vala, which is not a language I'm aware of. Nonetheless, I can at least point you to the proposed changes to gnome-contacts, they are in C and can be found at bug #743979 comment #0. You might want to implement something similar, except of not using E_SOURCE_EXTENSION_ADDRESS_BOOK in the code, but rather E_SOURCE_EXTENSION_CALENDAR.

[1] https://mail.gnome.org/archives/evolution-hackers/2015-February/msg00000.html
Comment 1 André Klapper 2019-10-10 14:00:28 UTC 
California is not under active development anymore and saw its last non-cosmetic code changes in March 2016: https://gitlab.gnome.org/Archive/california/commits/master

Its codebase has been archived in https://gitlab.gnome.org/Archive/california/issues/1

Closing this report as WONTFIX as part of GNOME Housekeeping to reflect reality. Please feel free to reopen this ticket if anyone takes the responsibility for active development again.

You may want to use `gnome-calendar`.