 |
 |
I also am unsure, Eric, how you imagine we could have a "smaller" annual meeting. Clearly the community wants to go. It is large. Tickets sell out quickly. I couldn't have gotten a ticket for this year's even if I had not been in the process of moving to Notre Dame and thus between funding, because I was in meetings during the ticket sales and hadn't expected them to go that fast. Who would get to decide who gets to go to this small, not-big-deal Code4Lib? Longtime insiders like you? People who've only been around a few years and thus have more to gain like me? Students? People lucky enough not to be in meetings when tickets go on sale? On Tue, Jun 7, 2016 at 5:36 PM, Ruth Tillman <[log in to unmask]> wrote: > ++ to Tom on this as I see a tremendous emotional and bureaucratic expense > every year for the organizing committee (or at least the last 2, where I've > paid attention to it). It is certainly distributed in different locales who > are hosting, but it already exists. I don't think we can deny that it's > there just because we don't happen to be involved in it this year. > > On Tue, Jun 7, 2016 at 4:55 PM, Tom Johnson < > [log in to unmask]> wrote: > >> > Can you say more about what you expect "the emotional and bureaucratic >> expense" to be? >> >> And especially, how it doesn't just reflect the existing costs of running >> the conferences? Do we really believe there is overhead associated with >> establishing a fiscal organization once, rather than doing it on the fly >> each year? >> >> - Tom >> >> On Tue, Jun 7, 2016 at 1:53 PM, Mike Giarlo <[log in to unmask]> >> wrote: >> >> > Can you say more about what you expect "the emotional and bureaucratic >> > expense" to be? >> > >> > -Mike >> > >> > ________________________________________ >> > From: Code for Libraries <[log in to unmask]> on behalf of Eric >> > Lease Morgan <[log in to unmask]> >> > Sent: Tuesday, June 7, 2016 13:49 >> > To: [log in to unmask] >> > Subject: Re: [CODE4LIB] Formalizing Code4Lib? >> > >> > > I'm also interested in investigating how to formalize Code4Lib as an >> > > entity, for all of the reasons listed earlier in the thread… >> > >> > >> > -1 because I don’t think the benefits will outweigh the emotional and >> > bureaucratic expense. We already have enough rules. >> > >> > — >> > ELM >> > >> > > > > -- > > Ruth Kitchin Tillman > > Digital Collections Librarian > > Hesburgh Libraries > > 113 Hesburgh Library > > o: 574-631-6067 > > e: [log in to unmask] > > -- Ruth Kitchin Tillman Digital Collections Librarian Hesburgh Libraries 113 Hesburgh Library o: 574-631-6067 e: [log in to unmask]