On 2/9/06, Caleb Phillips <[EMAIL PROTECTED]> wrote: > Thinking about recurring events in our application, I wonder if it is > really a good idea for one user to "own" a recurring event. For > instance, if I created a weekly hackfest event for the next year, and > then I fell off a cliff, how would we deal with this? Perhaps the > make-events-as-we go system is more fitting for an anarchy like PDX.rb.
That's precisely the reason we didn't implement recurring events to start. I could imagine a system where recurring events still had per-occurrance owners, but that starts to get complex pretty quickly. There's also still no real administrative interface (other than the Rails console and Postgres CLI, of course) to handle re-assigning events in scenarios like the you described, where someone leaves the group after creating an event. -Lennon _______________________________________________ PdxRuby-dev mailing list [email protected] http://lists.pdxruby.org/mailman/listinfo/pdxruby-dev
