In reply to: MerriLUG email frequency

On 4/13/07, Bill McGonigle <[EMAIL PROTECTED]> wrote:
... such that users can RSVP to stop getting reminders
if they want ...

 Gate the auto email announcements to separate lists,
gnhlug-announce-7-days, gnhlug-announce-same-day,
gnhlug-announce-30-days, whatever.  Subscribe existing gnhlug-announce
to all of them.  Somewhat clunky, but it would give us user-controlled
flexibility for cheap.

... give a head-count for the hall/restaurant ...

 Reply-to the coordinator, and s/he keeps track for it manually, as
we do now.  If someone comes up with a better idea, change it then.

The third half ...

 Heh.  :)

... is for LUG rustlers to use it for keeping track of
speakers, their bios, attendance, event slides, etc.

 Hyperlinks to the wiki.  Pages for speakers or events, as needed.

 The web works because not everything is the same, but everything can
still touch everything else.  Unix philosophy.

As much of it being self-service as possible (speakers can upload their
own slides, etc.)

 Our wiki allows self-registration, file uploads, page creation now.
If "fear of wikis" is an obstacle, one *nice* thing about TWiki's is
that it lets you create "forms" that "write wiki pages for you".  So
we could have a form that lets speakers submit their bio information
to one page, and their slides to another.

... is a nice goal for offloading grunt-work from overpaid chairs.

 Absolutely.  But since the "overpaid chairs" are also the "overpaid
sysadmins", anything that saves us effort is a good thing.  :)

There's a certain point at which you're putting more into glue code
than doing a re-implementation ...

 I like grand designs, too.  But consider this: Take existing
software that does everything else well, and improve it to
interoperate better with other components.  That is even *more* meta.
:)  Not only does that benefit other LUGs, it benefits other people
who want to hook the existing software into something completely
different.

 Don't write a foo-tool that can also hook into your unique
application.  Write a foo-tool that can also hook into *any* unique
application.  If needed, create a foo-tool-hooking-into protocol.

-- Ben
_______________________________________________
gnhlug-org mailing list
[EMAIL PROTECTED]
http://mail.gnhlug.org/mailman/listinfo/gnhlug-org/

Reply via email to