This is awesome! We will be porting it to ACS Classic 3.4.10, which looks easy. This should help a little with openacs 4.x because the db api and security schemes are similar. Any thoughts on making it group-scoped rather than user-scoped? We'd want to offer a blog to every student organization. We were going to abuse the enhanced-news module for that but I like this UI better and things like email alerts and full-text-search are already handled. I guess we don't really need to change any code since there's nothing stopping a group that owns an email address from creating an ACS "user" with their group name, but it'd be cleaner if we could just make the club group the admin group for the bboard. (Is there anywhere in bboard that requires the admin group to be group_type='admin'?)
