 |
 |
I didn't actually research the tool (EasyDiscuss). We were assured by the person making the annoucement that all conversation could be automatically forwarded to email, and that input could be by email as well. But I don't know. Cindy -----Original Message----- From: Code for Libraries [mailto:[log in to unmask]] On Behalf Of Paul Hoffman Sent: Thursday, March 24, 2016 9:37 AM To: [log in to unmask] Subject: Re: [CODE4LIB] code4lib mailing list On Thu, Mar 24, 2016 at 01:17:52PM +0000, Harper, Cynthia wrote: > It was just announced at the Innovative Users group meeting that that > listserv is moving to EasyDiscuss > http://extensions.joomla.org/extension/easydiscuss. Here are the so-called benefits of EasyDiscuss: | Use EasyDiscuss as a forum to manage your customers inquiries, build | closer customer loyalty, build credibility, engage in multiple | conversations, gather valuable experience from users, or simply build | a repository of information that grows over time. EasyDiscuss is as | good as Yahoo! Answers! <URL:http://extensions.joomla.org/extension/easydiscuss> No mention of e-mail at all. If I were an Innovative user I would say "No thanks!". Paul. > -----Original Message----- > From: Code for Libraries [mailto:[log in to unmask]] On Behalf > Of Jason Bengtson > Sent: Thursday, March 24, 2016 9:06 AM > To: [log in to unmask] > Subject: Re: [CODE4LIB] code4lib mailing list > > Yeah, I like option two as well. I could live with option one if need be, but like Matt and Eric I'm not that keen on Google data mining the list. > > Best regards, > > *Jason Bengtson, MLIS, MA* > Assistant Director, IT Services > K-State Libraries > 414 Hale Library > Manhattan, KS 66506 > 785-532-7450 > [log in to unmask] > www.jasonbengtson.com > > On Thu, Mar 24, 2016 at 7:38 AM, Matt Sherman > <[log in to unmask]> > wrote: > > > I have no technical answers to the questions you pose, but I second > > Option #2. > > > > On Thu, Mar 24, 2016 at 5:29 AM, Eric Lease Morgan <[log in to unmask]> wrote: > > > > > Alas, the Code4Lib mailing list software will most likely need to > > > be migrated before the end of summer, and I’m proposing a number > > > possible options for the lists continued existence. > > > > > > I have been managing the Code4Lib mailing list since its inception > > > about twelve years ago. This work has been both a privilege and an > > > honor. The list itself runs on top of the venerable LISTSERV > > > application and is > > hosted > > > by the University of Notre Dame. The list includes about 3,500 > > subscribers, > > > and traffic very very rarely gets over fifty messages a day. But > > > alas, University support for LISTSERV is going away, and I believe > > > the > > University > > > wants to migrate the whole kit and caboodle to Google Groups. > > > > > > Personally, I don’t like the idea of Code4Lib moving to Google Groups. > > > Google knows enough about me (us), and I don’t feel the need for > > > them to know more. Sure, moving to Google Groups includes a large > > > convenience factor, but it also means we have less control over > > > our own computing environment, let alone our data. > > > > > > So, what do we (I) do? I see three options: > > > > > > 0. Let the mailing list die — Not really an option, in my opinion > > > 1. Use Google Groups - Feasible, (probably) reliable, but with > > > less control > > > 2. Host it ourselves - More difficult, more responsibility, all > > > but absolute control > > > > > > Again, personally, I like Option #2, and I would probably be > > > willing to host the list on my one of my computers, (and after a > > > bit of DNS > > trickery) > > > complete with a code4lib.org domain. > > > > > > What do y’all think? If we go with Option #2, then where might we > > > host > > the > > > list, who might do the work, and what software might we use? > > > > > > — > > > Eric Lease Morgan > > > Artist- And Librarian-At-Large > > > > > -- Paul Hoffman <[log in to unmask]> Systems Librarian Fenway Libraries Online c/o Wentworth Institute of Technology 550 Huntington Ave. Boston, MA 02115 (617) 442-2384 (FLO main number)