Foodle v3.0 includes a number of new features / changes, where the most important new feature is calendar integration.
This second part of the beta testing, will focus on calendar testing.
The goal of the current implementation of calendar integration in Foodle, is that users that respond to a Foodle with several dates, may select to instead of manually typing in which dates that is OK, it is connected to the user’s calendar in such a way that it is automatically filled out, and kept in sync with the calendar. That means that if the user adds a new event to his/her calendar, the Foodle will be automatically updated to reflect this.
In order for this to work, both the user and the Foodle needs to be calendar-enabled.
The connection between Foodle and the calendar system is using RFC2445 iCalendar, with VFreeBusy records.
When you log in to Foodle, in the footer, you should see the text: Foodle is connected to your calendar. Like this:
![]()
For UNINETT employees, Foodle automatically discovers the iCalendar export of the user, based on information from Feide. iCalendar export isonly enabled for user’s that have been using the UNINETT CALdav server.
Here is a current list of users that have enabled CALdav:

Contact me if you are unsure whether you have enabled CALdav or not. Contact Gurvinder about how to connect to CALdav the first time.
After you have enabled CALdav, you would need to logout and in again on Foodle.
Users that are not eployees of UNINETT, and uses OpenIdP, contact me about connecting to your existing iCalendar (suchg as Google Calendar or others..).
Here is a test Foodle. Try connect it with your calendar:
If Foodle is connected with your calendar, you will get a switch like this:

where you may select whether to type in manual dates, or respond with connecting the Foodle to your calendar.
Important: Because of caching, you should allow Foodle upto 60 seconds before changes in your calendar is reflected on the Foodle.
If things are not working as expected, the debug tab may help you dig into what is wrong. Please report to me if something is not working as expected.
In order for the Foodle to work with calendaring, Foodle MUST reckognize all the columns as timestamps/dates.
When you create a new Foodle, first select to work with date columns:

Enter a set of dates and time slots. If you specify one time (such as 10:00) Foodle will default to check availability one hour from the beginning of the time slot. If you specify a range (such as 10:00-12:00), Foodle will use that range when checking availability.
Here is an example of what you can fill-in:

On the bottom of the page, you will see a green light if all columns are reckognized as valid date/time slots. You can click more details to see what columns are not reckognized:

Foodle is now available on:
Currently only login through Feide + OpenIdP is activated.
Foodle 3.0 uses the same database as the production Foodle, but the content follows an updated format.
You should not respond to foodles created on foodle.feide.no using foodl.org! It will cause foodle.feide.no
> Hi Andreas,
> How can I connect my Google Apps Calendar, here is the ICS free/busy URL?
> Regards
> Glenn
Hi Glenn.
Currently the idea is that Foodle auto discovers your calendar. This is configured for each institusion or sent through the IdP as an attribute.
What I have done is added your calendar to Feide OpenIdP to your user (gwearen) as an attribute 'labeledURI'.
You can now try to login to (with openidp)
https://foodl.org/foodle/Tester-kalender-i-fremtid-4ca1d
and respond with your calendar.
Let me know how it works!
Looking forward to hear from you.
Kind regards,
Andreas.