Discussion Using ALAConnect for RBMS Executive Committee work

We have had partial success in using ALAConnect to discuss the charge for the new Regional Workshops Committee. Some issues to consider about using this format for inter-meeting work:

• Inter-meeting work of the Exec Comm is meant to be transparent to all interested parties. Discussions marked "Public" are viewable by anyone, but only members may post. You do not have to be a member of the RBMS Executive Committee in order to join the ALAConnect Group.

• Members of the Executive Committee are expected to have a "subscription" to this group and to be set for regular email notification. 
• Discussions that precede a vote will take place as a "Discussion," while votes of the committee will be presented as a "Poll/Vote." While anyone may join in a discussion, votes are meant to be limited to committee members, although I don't think there's a way to technically enforce it.
• A post to rbms@ala.org should be made when a new discussion starts. That way RBMS members can drop in and out without worrying that they're missing something of interest to them.
• This is intended to be an experiment, and this method of conducting inter-meeting work should be evaluated after 6 months or a year.

I'm still learning about the ins and outs of submitting comments and getting email notices. I recently submitted a new comment for the Regional Workshops discussion, but the only buttons available were "save" and "preview." So I "saved" but didn't get an email notification. In starting this new discussion, however, the buttons are "submit" and "preview," which makes me doubt whether my previous comment was actually posted.