Hi Eric, I also prefer option 2.
While I think that this is best hosted at an academic institution, if that doesn’t pan out I can provide a server for it (CentOS-ish or Ubuntu). Thanks, Cary I would rather not get involved with the software. > On Mar 24, 2016, at 2:29 AM, Eric Lease Morgan <emor...@nd.edu> 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
