Re: [CODE4LIB] code4lib mailing list

> Alas, the Code4Lib mailing list software will most likely need to be migrated > before the end of summer… On Monday Wayne Graham (CLIR/DLF) and I are hoping to migrate the Code4Lib mailing list to a different domain. We don’t think any archives, subscriptions, nor preferences will get lost

Re: [CODE4LIB] code4lib mailing list [clir]

On Jun 7, 2016, at 10:11 AM, Eric Lease Morgan 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... >> >> Our list — Code4Lib

Re: [CODE4LIB] code4lib mailing list [dlf]

On May 12, 2016, at 8:30 AM, Eric Lease Morgan 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... > > Our list — Code4Lib —

Re: [CODE4LIB] code4lib mailing list [dlf]

On Mar 24, 2016, at 10:29 AM, Eric Lease Morgan 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... Our list — Code4Lib — will be

Re: [CODE4LIB] code4lib mailing list [domain]

I, too, have no preference in branding. Regarding DLF's offer to host the list, I think that's a good idea too (thank you, Bethany!) thanks, ranti. On Mon, Mar 28, 2016 at 12:02 PM, William Denton wrote: > On 27 March 2016, Eric Lease Morgan wrote: > > Everybody, please share

Re: [CODE4LIB] code4lib mailing list [domain]

On 27 March 2016, Eric Lease Morgan wrote: Everybody, please share with the rest of us your opinion about our mailing list’s domain. This need to move from the University of Notre Dame is a possible opportunity to have our list come from the cod4lib.org domain. For example, the address of the

Re: [CODE4LIB] code4lib mailing list [domain]

+1 On Mar 27, 2016 23:51, "Stuart A. Yeates" wrote: > On Monday, 28 March 2016, Mark Sandford wrote: > > > > > > > > > > > > > Everybody, please share with the rest of us your opinion about our > > mailing > > > list’s domain. This need to move from the

Re: [CODE4LIB] code4lib mailing list [domain]

On Monday, 28 March 2016, Mark Sandford wrote: > > > > > > > > Everybody, please share with the rest of us your opinion about our > mailing > > list’s domain. This need to move from the University of Notre Dame is a > > possible opportunity to have our list come from the

Re: [CODE4LIB] code4lib mailing list [domain]

> > > > Everybody, please share with the rest of us your opinion about our mailing > list’s domain. This need to move from the University of Notre Dame is a > possible opportunity to have our list come from the cod4lib.org domain. > For example, the address of the list might become >

Re: [CODE4LIB] code4lib mailing list [domain]

On Mar 25, 2016, at 1:24 PM, Bethany Nowviskie wrote: > Dear all — I’ve been getting this as a digest, so apologies that I’m only > seeing the thread on the future of the mailing list now! > > CLIR/DLF is running the same version of ye olde LISTSERV as Notre Dame, to >

Re: [CODE4LIB] code4lib mailing list

First off, thank you Eric for all of the work over the years supporting this listserv. I really like Bethany's proposal for CLIR/DLF to host and migrate. Support from the highest level of DLF combined with organization experience running the software sounds like the most sustainable plan I have

Re: [CODE4LIB] code4lib mailing list

Thank you, Bethany! I am in full support of this. DLF++ -Shaun > On Mar 25, 2016, at 8:24 AM, Bethany Nowviskie wrote: > > Dear all — I’ve been getting this as a digest, so apologies that I’m only > seeing the thread on the future of the mailing list now! > > CLIR/DLF is

Re: [CODE4LIB] code4lib mailing list

Dear all — I’ve been getting this as a digest, so apologies that I’m only seeing the thread on the future of the mailing list now! CLIR/DLF is running the same version of ye olde LISTSERV as Notre Dame, to support DLF-ANNOUNCE, some of our working group lists, and (now) all of the discussion

Re: [CODE4LIB] code4lib mailing list

+1 Eric, I'm glad to see the outpouring of appreciation and wanted to chime in with my own. Tim On 3/24/16, 4:06 PM, "Code for Libraries on behalf of Cynthia Ng" wrote: >While I have little to add to what others have already

Re: [CODE4LIB] code4lib mailing list

Cary Gordon writes > You can get enough server for this from AWS for $5-10/mo. The problem is not the ram or the disk space. It's in the policy issues around email. Many organizations have outsourced their email to gmail these days. I doubt "enough server" was the deciding factor. --

Re: [CODE4LIB] code4lib mailing list

Sounds like a reasonable plan, so we might as well give it a shot. Thanks for all your hard work on this. On Thu, Mar 24, 2016 at 4:28 PM, Cary Gordon wrote: > You can get enough server for this from AWS for $5-10/mo. > > Cary > > > On Mar 24, 2016, at 1:13 PM, Thomas

Re: [CODE4LIB] code4lib mailing list

Regarding the mailing list, here is what I propose to do: 1. Upgrade my virtual server to include more RAM and disk space. 2. Install and configure Mailman. 3. Ask people to subscribe to a bogus list so I/we can practice. 4. Evaluate. 5. If evaluation is successful, then migrate

Re: [CODE4LIB] code4lib mailing list

You can get enough server for this from AWS for $5-10/mo. Cary > On Mar 24, 2016, at 1:13 PM, Thomas Krichel wrote: > > Paul Hoffman writes > >> If you're interested, Eric, I have some experience with Mailman (though >> not with Listserv) and would be happy if I can --

Re: [CODE4LIB] code4lib mailing list

Paul Hoffman writes > If you're interested, Eric, I have some experience with Mailman (though > not with Listserv) and would be happy if I can -- I have some scripts to > do bulk operations (add or remove subscribers, etc.) and could also help > to migrate the list archive. I find that

Re: [CODE4LIB] code4lib mailing list

While I have little to add to what others have already said, I do want to add my thanks for your long term efforts and work on starting and continuing the mailing list. On Thu, Mar 24, 2016 at 2:29 AM, Eric Lease Morgan wrote: > Alas, the Code4Lib mailing list software will most

Re: [CODE4LIB] code4lib mailing list

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

Re: [CODE4LIB] code4lib mailing list

On Thu, Mar 24, 2016 at 10:39:03AM -0400, Ranti Junus wrote: > Mailman is easy to administer, but it has a huge caveat: when a user > request a password (reminder, etc.), it sends it as an email in plain text. Fortunately, list administrators can disable the monthly password reminder. Site

Re: [CODE4LIB] code4lib mailing list

I have been on mailman lists, like Fedora Linux, for ages and any command that a user or other can do with the "password" that is sent through mail is also verified by an email. So, someone could try to make your list user recieve a digest or quit the list, etc. but it wouldn't happen if you

Re: [CODE4LIB] code4lib mailing list

On Thu, Mar 24, 2016 at 10:39 AM, Ranti Junus wrote: > Thank you, Eric, for the heads up and your guardianships... > > Mailman is easy to administer, but it has a huge caveat: when a user > request a password (reminder, etc.), it sends it as an email in plain text.

Re: [CODE4LIB] code4lib mailing list

On Thu, Mar 24, 2016 at 6:37 AM, Paul Hoffman wrote: > No mention of e-mail at all. If I were an Innovative user I would say > "No thanks!". The Demo shows that it's possible to subscribe to instantaneous email messages for new posts: http://easydiscuss.stackideas.com/ HTH,

Re: [CODE4LIB] code4lib mailing list

And more public praise for you, Eric. Thank you for maintaining the code4lib listserv throughout the years, through the good times and the flame wars, through outages and message overflows. Maintainer and moderator roles are difficult ones to perform long term, and you have diligently performed

Re: [CODE4LIB] code4lib mailing list

[mailto:CODE4LIB@LISTSERV.ND.EDU] On Behalf Of Paul Hoffman Sent: Thursday, March 24, 2016 9:37 AM To: CODE4LIB@LISTSERV.ND.EDU Subject: Re: [CODE4LIB] code4lib mailing list On Thu, Mar 24, 2016 at 01:17:52PM +, Harper, Cynthia wrote: > It was just announced at the Innovative Users group meet

Re: [CODE4LIB] code4lib mailing list

On 3/24/16 5:29 AM, Eric Lease Morgan 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

Re: [CODE4LIB] code4lib mailing list

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, Likewise, I can recommend Mailman. I was the admin of a Mailman server supporting a few dozen lists while at Minitex and found it to be really robust. It has somewhat fewer subscriber options than Listserv if I recall, but the web UI is orders

Re: [CODE4LIB] code4lib mailing list

Thank you for the heads-up, the previous work, and the offer of future work. I second mailman - it seems to have a good community and continues active development. On Thu, Mar 24, 2016 at 5:29 AM, Eric Lease Morgan wrote: > Alas, the Code4Lib mailing list software will most

Re: [CODE4LIB] code4lib mailing list

Reading Paul's response, it occurs to me that I neglected to thank you for for your work on this front, Eric. We all appreciate it. I wish I had some good suggestions for the technical implementation of option 2, but I don't. We're migrating servers here at KSU for various reasons, and, with that

Re: [CODE4LIB] code4lib mailing list

; Sent: Thursday, March 24, 2016 9:06 AM > To: CODE4LIB@LISTSERV.ND.EDU > 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. > >

Re: [CODE4LIB] code4lib mailing list

In addition to the negatives you list for Google Groups, I also wanted to mention that some institutions only have partial integration with Google Apps, which don’t include Google Groups. For example, Princeton faculty and staff are not able to fully use Google Groups features, such as

Re: [CODE4LIB] code4lib mailing list

On Thu, Mar 24, 2016 at 10:29:20AM +0100, Eric Lease Morgan 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

Re: [CODE4LIB] code4lib mailing list

: Thursday, March 24, 2016 9:06 AM To: CODE4LIB@LISTSERV.ND.EDU 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

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

Re: [CODE4LIB] code4lib mailing list

I would suggest Mailman: https://www.gnu.org/software/mailman/ ./r On Mar 24, 2016 05:29, "Eric Lease Morgan" 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

Re: [CODE4LIB] code4lib mailing list

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 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