[fedocal] #23: Desktop or CLI client
by fedocal
#23: Desktop or CLI client
-------------------------+--------------------
Reporter: pingou | Owner:
Type: enhancement | Status: new
Priority: minor | Milestone: Future
Component: API | Version:
Keywords: |
-------------------------+--------------------
In the long term it might be cool if we have a cli or desktop client for
fedocal.
This might need, more work on the API (beside all the work on the client).
--
Ticket URL: <https://fedorahosted.org/fedocal/ticket/23>
fedocal <https://fedorahosted.org/fedocal>
A web-based calendar application for Fedora
7 years, 5 months
[fedocal] #54: Add CalDAV support
by fedocal
#54: Add CalDAV support
-------------------------+-------------------------
Reporter: lbrabec | Owner:
Type: enhancement | Status: new
Priority: major | Milestone: Future
Component: fedocal | Version: development
Keywords: |
-------------------------+-------------------------
It would be nice to have support for CalDAV for easy use of fedocal with
Thunderbird or Evolution.
--
Ticket URL: <https://fedorahosted.org/fedocal/ticket/54>
fedocal <https://fedorahosted.org/fedocal>
A web-based calendar application for Fedora
8 years
[fedocal] #132: Some full-day events seems to span two days (in google calendar)
by fedocal
#132: Some full-day events seems to span two days (in google calendar)
---------------------+-------------------------
Reporter: kparal | Owner:
Type: defect | Status: new
Priority: minor | Milestone: Future
Component: fedocal | Version: development
Keywords: |
---------------------+-------------------------
We have these two test days defined in our QA calendar:
* i18n Test Day, https://apps.fedoraproject.org/calendar/QA/2014/9/1/#m764
* Wayland Test Day,
https://apps.fedoraproject.org/calendar/QA/2014/9/1/#m420
Both of them look like a single full-day event in Fedocal, and even in
Zimbra and Evolution. But in Google Calendar, only Wayland looks like a
single day, and i18n looks like spanning two days (with an indication that
it's from 2AM first day to 2AM second day). Look at the attachment.
They both seemed to be stored the same way:
{{{
Stored as:
Start: 2014-09-02 - 00:00:00 UTC
End: 2014-09-03 - 00:00:00 UTC
}}}
and
{{{
Stored as:
Start: 2014-09-04 - 00:00:00 UTC
End: 2014-09-05 - 00:00:00 UTC
}}}
ical export says:
{{{
BEGIN:VEVENT
UID:20140825T134824Z-55530@fedocal01.phx2.fedoraproject.org
DTSTART;VALUE=DATE:20140902
DTEND;VALUE=DATE:20140903
DESCRIPTION:<i>This is temporary placeholder meeting\, it will be updated<
/i>\n\nWe will test Wayland in upcoming Fedora 21.\n
LOCATION:fedora-test-day@irc.freenode.net
ORGANIZER:lbrabec\, pschindl
SUMMARY:i18n Test Day
TRANSP:TRANSPARENT
END:VEVENT
}}}
(there is a wrong description, but I don't want to touch it, because it
might "fix" the bug:))
and
{{{
BEGIN:VEVENT
UID:20140825T134824Z-37071@fedocal01.phx2.fedoraproject.org
DTSTART;VALUE=DATE:20140904
DTEND;VALUE=DATE:20140905
DESCRIPTION:*This is temporary placeholder meeting\, it will be updated*\n
\nWe will test Wayland in upcoming Fedora 21.\n\n
LOCATION:fedora-test-day@irc.freenode.net
ORGANIZER:kparal\, lbrabec\, pschindl
SUMMARY:Wayland Test Day
TRANSP:TRANSPARENT
END:VEVENT
}}}
I have no idea where the difference is, but there has to be some. Ideas?
--
Ticket URL: <https://fedorahosted.org/fedocal/ticket/132>
fedocal <https://fedorahosted.org/fedocal>
A web-based calendar application for Fedora
9 years, 2 months