Burning Man (SpankyFromBRC?) ideas
Many of the needs expressed can be met by using the existing
event types field, but by simply expanding the existing event types and then being able to easily filter/search for certain event types. Also, the possiblity of customiing the fields that are available for each type. (ATSENG?) Below are some event types that were mentioned:
- resource (reservation)
We need to be sure that the existing recurring events features are solid and flexible.
- Able to edit one single event in a series.
- Edit entire series
The ability to add a set of users to an event and then easilty notify all of them about the event. These users should be able to come from existing team rosters, the entire user/member set, or by adding any arbitrary email address. The system would need to be sure any users that might appear in two groups would only be notified once. It was noted that being able to return to an event at a later date and renotify the entire set of participants of a change to (or simply a reminder for) the event. Having the ability to set an automatic reminder as well. For instance, when creating the event, one would choose "Remind participants 2 weeks prior."
In the simplest scenario, an event notification would be sent to the users email, but it was suggested that users may have different preferences for how they would like to be notified. Therefore a
notification preference, set by the user would seem to be the easiest way to accomplish this. When the system was preparing to deliver the notifications, it would check each users preference and deliver the notifications in that manner. Suggested notification types were:
- SMS (probably simply via email as well)
- Chat message
- Extranet visibility (push to portlet?)
Think Evite. Users who are notified are sent a link to the event. They can click the link and mark whether they can attend or not with a comment. This system could eventually be expanded to use workflow, in that if not enough people reply or can attend, the event does not get published or pushing into some workflow state. This is only a potential though.
Users would like to have views that can be saved. These views would be a set of filters, so for instance, I might save a view that is "upcoming deadlines from accounting" or "all meetings", or "all meetings that use this resource".
The ability to use iCal or other .ics-compatible application to add/edit/remove events in the system. The system should be able to take edits in either the local or remote setting. Therefore, edits within the systema are reflected in remote sync and remote edits are posted to the system. This should be teamspace aware.
The ability to share an event across mutiple teams.
Increase Ease of Use:
- More calendar-like views (Month/Week/Day)
- Easily printable
- Different CSS skins?
A user can sign up for a reminder for an event if they choose, and have that reminder delivered by a preferred method.
More publishing states:
- playa cal?
Making sure a resource is not reserved at the same time. Certain other types of events should also not clash.
Potential to have something like Free/Busy, where a meeting is proposed but not confirmed until a suitable time that all (or a threshold percentage of) participants can attend.
The ability of someone to act as a proxy for another user regarding scheduling/responding to events, as in the scenario of someone with a secretary.
Nate Aune's (natea) ideas
1) merge Kapil's changes back into Calendaring trunk (http://plone.org/products/calendaring)
3) recurring events (see Lennart Regebro from Nuxeo comments on this subject: http://blogs.nuxeo.com/sections/blogs/lennart_regebro/2005_08_29_indexing-events)
4) configurable default views (month, week, day) perhaps using CMFDynamicViewFTI?
5) creating calendars using Smart Folder criteria (i.e. all events, just events in this folder, etc.)
6) fixing of bugs (http://sourceforge.net/tracker/?atid=689513&group;_id=55262&func;=browse)
8) nicer view templates. maybe steal images/CSS from Mambo calendar product: http://www.bostonphp.org/index.php?option=com_extcalendar&Itemid;=33
9) explore CalCore? from Nuxeo as an alternative to Calendaring. Alan Runyan (runyaga) highly recommended CalCore?. http://www.cps-project.org/sections/projects/calendar_server/calcore-1-3-0-released
Justin Ryan's (bitmonk) ideas
I want to design an xp-ish project management system where you can
start a project by dumping an iCalendar into your site and dropping
tasks (skinned poi issues, probably) into folderish events, which i
suppose for this implementation should be combined with poi trackers..
i dunno, poi doesn't want to be customized, but i think it's a simple
enough design to be re-used. Regardless of my crazy ideas, this is
what I meant by
this flavour of customization earlier. I think
Calendaring should provide useful interfaces for people who want to do
calendar-ish work in plone.
We also talked about providing calendar views on other content, I think this is a great idea. I'd also like for content objects to have a way of flagging a date in the calendar portlet, i.e. a project is due on nov 15, when i load it, perhaps it has a method of forcing the portlet to change.
Bill Fenner's (fenestro) ideas
- Time zone support. I realize this might mean hitting up DateTime? and ATEvent? but I think it's important.
- Syndication (ical) of a group of events, via a topic or a smart folder or something. I have DTML to do this for a topic but I think this is a useful base ability.
- (Maybe related to #2) - publishing a calendar to view, but not have the events show up in "all site events" - e.g., if I want to provide a view of http://www.ofcourseimright.com/ietf64-breaks.ics but don't want to clutter the portal events list with hundreds of events for that week. (I've used PloneiCalendar? for this in the past, but it won't parse the calendar this time and don't want to try to debug its parser.)
- Low priority, but might be interesting: investigate "CalDAV>? - it would be nice to see if Zope could make a CalDAV? implementation easy. There's an evolution-caldav client to try testing against.
- Dunno if this fits in this context, but I'd like to use calendars for resource scheduling - if a Calendaring folder was able to have a constraint that two events couldn't overlap, that might be most of the work.
- If we're looking at hcalendar, we should be aware that the hcalendar timezone and repeat support is almost nonexistent - luckily, so is Calendaring's!
- Talking about views, I really like phpicalendar's views, especially of overlapping events (unfortunately the sample calendar doesn't have any of those) - but see http://phpicalendar.net/phpicalendar/day.php
Jeff Kowalczyk's ideas
I was going to suggest that an add-in product installing a series of high-quality calendar display views for Smart Folder would be useful.
Most likely, display views would be applicable to other folderish containers, and it would allow a single point of collaboration on making the best possible ZPT HTML for all the standard calendar representations:
day summary, day-by-hour, week summary, week-by-day, week-by-day-by-hour, month summary, month calendar, 3 month calendar, year summary, year monthly calendar with date text, year, multi-year compact calendar (like existing portlet calendar)
... and so on. I suspect if the mechanism and compatible products are in place to use calendar display views, we'll have the community collaborating to provide top-notch calendar display capabilities in no time at all. Calendaring apps will likely follow the display candy.
I agree, I was just going to suggest that Justin experiment to see
whether all Calendar use cases can't be addressed by (possibly complex)
smart folder criteria. This would include questions of
appointments, and aggregate nested calendars, etc. If you imagine
smart folder results that look like calendars, they're already pretty
It seems to me that stock smart folders + calendar display views will get any calendar display app most of the way there. In this case, eye candy may in fact be the most important thing.
IMHO, It would be more useful to refine a richer Event (as in ATEvent? content type) standard interface/schema, to facilitate easy criteria access for recurrence, etc., than to derive a specialized query type from smart folder.
I really like the wizard idea for smart folders used as calendars. Specialized wizards for smart folder configuration would be a good tool in general, especially with a dump() method like ATSchemaEditorNG?. I'd like to see products that just add those, like the products adding only Calendar views discussed earlier.
Alexander Limi's (limi) ideas:
This is sexy, and I want it in Calendaring:
On a related note, I've spent some time in a customer project with tesdal lately, and we've come up with good, accessible and easy-to-generate week views and overlap detection. Expect to see some template code soon. ;)
(Added by antgel 30/11/05) After a discussion with bitmonk on IRC, it would be interesting to see how support for non-Gregorian calendars could be implemented. This is driven from the fact that we need a Hebrew calendar on a site we're building for a customer. We do not particularly need to be able to display it. It's more about the mappings between the two.
For example, 1st Tishri is the religious New Year. This usually falls around September / October in the Gregorian calendar. We would want the user to be able to enter that date, and when they submit the event, have it published on e.g. 17th September or whenever.
More than that, we need recurring events to work. or example, if I input an event for the 1st Tishri every year, I want it to appear in the Gregorian calendar as 17th Sept, then 10th October the following year, then whenever it's correct for each year.
I expect that any solution to this will probably include optional display of the Hebrew calendar as a trivial side-effect, but I'm new to Plone, so don't really know the implications yet.
Hope this makes sense, let me know if not.
More useful info at:
Mapping algorithm looks like: http://www.geocities.com/DafAWeek/HebCal.html