I agree that event posting should be limited to admins and moderators by default. If people want expanded access in their apps, they can easily change that. Commenting on events also seems logical, with e-mail notifications for anyone who has RSVP'd.
Thanks! Bruno On Tue, Jul 21, 2009 at 11:24 PM, James.d <[email protected]> wrote: > > Here's my vote 1 & 2 > > 1. There should at least be a events posting role, perhaps just bundle > it in with moderators? > 2. Comments on events seems pretty easy and straight forward > > > > On Jul 21, 7:18 pm, eksatx <[email protected]> wrote: > > The latest events stuff (including RSVPs) is now in edge. I look > > forward to hearing feedback about it. > > > > Where should it go next? Please try to keep in mind I am looking for > > ideas that apply very broadly to everybody and thus belong in core. > > If you have a very specific need then you should probably add that by > > over-riding the base CE stuff. > > > > Some ideas I am considering: > > > > 1. Events are now only added by the administrator. Should events be > > more like blog posts where all users can add events? You could then > > view events per user. Perhaps the Events list would collate all > > events by date. Perhaps this could use a review system where all > > users can submit events, but only the administrator can publish. > > > > 2. RSVPs don't allow including a note. Should they? Perhaps a better > > solution would be to enable comments for Events -- then you add your > > comment to the event, not the RSVP (ala Facebook). > > > > 3. Reminder emails for events. > > > > 4. Export. Output as iCal? Links to add to Google calendar or Yahoo! > > calendar? RSS feed of Events? > > > > I guess I'm looking for a consensus on the top one or two features > > that everybody thinks is essential. > > > > On Jul 14, 12:19 am, eksatx <[email protected]> wrote: > > > > > I think I have the RSVP stuff finished. I beefed up the validation > > > (make sure people can't RSVP foreventsin the past, etc.) and wrote > > > unit and functional tests. > > > > > In keeping with the rest of the site design it should probably be > > > AJAXified. I always like to start with the simplest, old-school > > > interface first to make sure the design holds together. I think I'll > > > push it out in its current state. If everybody likes it then I'll add > > > AJAX-y goodness. > > > > > On Jul 13, 12:13 am, eksatx <[email protected]> wrote: > > > > > > So far so good. > > > > > > The next step is implementing RSVPs forevents. > > > > > > I am pretty close to having something. > > > > > > Each event shows a list of attendees. Users can RSVP for an event > and > > > > enter the number of people they are bringing. Attendees can update > > > > their count of guests and/or retract their RSVP. > > > > > > I've got to bang away at it a bit to see what I may have missed and > > > > write some tests. > > > > > > With any luck I'll have something for you to check out in the next > few > > > > days. > > > > > > On Jul 9, 9:56 pm, mike muldoon <[email protected]> wrote: > > > > > > > > I also took the liberty of adding the calendar_date_select. I > have > > > > > > used this gem on a bunch of sites and I have found it to work > well. > > > > > > > Frickin awesomeness! I was installing this just today, nicely done! > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "CommunityEngine" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/communityengine?hl=en -~----------~----~----~----~------~----~------~--~---
