Markus wrote:
From: Matt Youell:
On Sep 29, 3:29 am, Igal Koshevoy <i...@pragmaticraft.com> wrote:
Lastly, please remember to publish events to Calagator in advance, they
help me and others remember that there are meetings coming up.
Calagator needs a repeat button. There's no getting around it. Manual
adds are a PITA and (obviously) prone to human error. (Like totally
forgetting to post.)
As our envoy to Calagotoria, please make that happen. #kthxbye :)
If the argument against auto-repeats is that cruft would accumulate and
no one would own removing it, how about a "pester me to schedule the
next one" button that send the created an e-mail with a link that would
pre-fill the form with what the auto-repeater would have done
(including setting pester me) a week or so before the next meeting?
Markus & Matt, {I'm also CC'ing pdx-tech-calendar}
Thanks for the suggestions. I've been too swamped with other events to
work on this, although I hope to have some free time after
WhereCampPDX[1] over.
Providing a way to clone an existing event should be fairly easy. E.g.,
you search for and display an old WestsideProggers meeting, click a
"clone" or "repeat" link (or something similar), would then get a "new
event" form pre-filled with the old content but the date/time cleared.
This should be easy to do and speed up the process of creating a new
event similar to a past one. I created a ticket for implementing this
earlier:
http://code.google.com/p/calagator/issues/detail?id=399
Sending people reminder emails is a good idea, but is more technically
complex because it requires more infrastructure changes. We'd need to
implement user accounts (we can extract them from openconferenceware or
pdxruby2), come up with a way to prevent this from sending spam, redo
the export system which currently lets anyone download the entire raw
database because we don't want to publish people's emails and other
account details, and come up with some way for anonymous developers to
download data with sanitized user accounts they can take over for local
development. This isn't "hard" but would take a fair number of hours to
get production ready, as well as requiring some emergency triage as
edge cases break in production, and I want to work on other things
first.
Anyway, if someone wants to get started on these or other tasks, feel
free to do so and send us pull request or patch when you've made
progress.
-igal
[1] WhereCampPDX, October 2-4, is a free unconference for
geo-technology professionals and enthusiasts. Learn more at
http://wherecamppdx.org/