LISTSERV mailing list manager LISTSERV 16.5

Help for CODE4LIB Archives


CODE4LIB Archives

CODE4LIB Archives


CODE4LIB@LISTS.CLIR.ORG


View:

Message:

[

First

|

Previous

|

Next

|

Last

]

By Topic:

[

First

|

Previous

|

Next

|

Last

]

By Author:

[

First

|

Previous

|

Next

|

Last

]

Font:

Proportional Font

LISTSERV Archives

LISTSERV Archives

CODE4LIB Home

CODE4LIB Home

CODE4LIB  June 2016

CODE4LIB June 2016

Subject:

Re: Formalizing Code4Lib?

From:

"Edward M. Corrado" <[log in to unmask]>

Reply-To:

Code for Libraries <[log in to unmask]>

Date:

Mon, 13 Jun 2016 13:30:01 -0500

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (140 lines)

Generally speaking, what the fiduciary agent normally would get rewarded in
money. Arrangements can vary of course, but basically they would get a
portion of the income of the event.

Edward

On Mon, Jun 13, 2016 at 1:11 PM, Shaun D. Ellis <[log in to unmask]>
wrote:

> I agree that securing a permanent fiscal agent is the only way to sustain
> the annual conference at the current level, but I think there are ways to
> make a less formal commitment.  What I don’t understand is what any
> fiduciary agent gets out of such a deal.  There is significant risk and
> overhead for anyone to take this on.  What is the reward?
>
> Overhead
> It’s not just about fronting money and signing contracts.  There is people
> power involved too.  For 2016, I reviewed every contract and agreement that
> came through because my hide was on the line if we screwed up.  It’s not
> hard to miss something in the fine print, or to find estimates and invoices
> that don’t add up.  Furthermore, there were people in our finance
> department who had to do extra work to set up the account, cut checks,
> double-check contracts, communicate with vendors, etc.
>
> Risk
> While we have not yet gone "into the red" on an annual Code4Lib conference
> (knock on wood), it is certainly possible unless there is a degree of
> vigilance on the part of the organizers.  Because you have different
> organizers each year there can be large fluctuations when it comes to
> fundraising/sponsorship effort and experience.  The same goes for
> researching, negotiating, and comparing vendor and venue prices.  We do
> pass on documentation as best we can, but the process is rarely cookie
> cutter.
>
> Reward
> Is the reward simply “thanks” and a pat on the back?  ¯\_(ツ)_/¯  (For what
> it’s worth, I could see a high-visibility sponsor spot given to this org
> since it's a form of in-kind donated resources.)
>
> Even if Code4Lib were to form a non-profit to strictly handle the annual
> conf, someone’s hide needs to be on the line to make sure there’s proper
> oversight of funds, budgets are properly formed and adhered to, contracts
> are not putting the org at risk, and so on.  To me, that sounds like a
> dedicated employee of the non-profit.
>
> -Shaun
>
> On Jun 13, 2016, at 1:30 PM, Rogan Hamby <[log in to unmask]<mailto:
> [log in to unmask]>> wrote:
>
> There are a variety of options but I think it's fairly safe to say that it
> would require some additional organization.  If another body took Code4Lib
> under it's umbrella they would want organizational contacts and some
> arrangements in place with whatever served as the governance of Code4Lib
> (and I use the term governance here very loosely).  And at the other end of
> the spectrum if Code4Lib did something like become a non-profit there are a
> number of IRS requirements it would have to observe in terms of a board,
> bylaws, etc....
>
> Note, I'm sure there are other options, those are just the two that occur
> to me off the top of my head from opposing ends of the "we have to be a
> formal entity spectrum."
>
> On Mon, Jun 13, 2016 at 12:55 PM, Akerman, Laura <[log in to unmask]<mailto:
> [log in to unmask]>> wrote:
>
> Would "finding a permanent fiduciary agent" call for some degree of
> organizational formalization?  Wouldn't somebody or bodies have to "sign
> for" Code4Lib on this agreement with this agent, and wouldn't their role
> therefore have to be, to some degree, permanent?
>
> Sorry, but just wondering...
>
> Laura
>
> -----Original Message-----
> From: Code for Libraries [mailto:[log in to unmask]] On Behalf Of
> Salazar, Christina
> Sent: Friday, June 10, 2016 5:26 PM
> To: [log in to unmask]<mailto:[log in to unmask]>
> Subject: Re: [CODE4LIB] Formalizing Code4Lib?
>
> Yes I think it's time to do so and I also felt that there was significant
> support for the idea.
>
> I think perhaps the title "formalizing Code4Lib" might be a bit misleading
> though... We might want to frame the idea as "finding a permanent fiduciary
> agent" or something along those lines. This way, we don't have to think
> about major changes all at once.
>
> I imagine it would help those who plan for Code4Lib 2017 as well, assuming
> that there will be a physical one.
>
> Christina Salazar
> Systems Librarian
> John Spoor Broome Library
> California State University, Channel Islands
> 805/437-3198
>
>
> -----Original Message-----
> From: Code for Libraries [mailto:[log in to unmask]] On Behalf Of
> Brian Rogers
> Sent: Friday, June 10, 2016 2:20 PM
> To: [log in to unmask]<mailto:[log in to unmask]>
> Subject: Re: [CODE4LIB] Formalizing Code4Lib?
>
> Since the Chattanooga Planning Committee inadvertently prompted this
> newest round of conversations around some degree of formalization, would it
> be useful if we threw together a follow-up survey for the community, to
> test the waters around support (or lack there of) for the notion of
> formalizing, to the extent that it allows for a stable place to house the
> annual conference funds? And if it seems like there is overwhelming support
> for the idea, a group of volunteers can band together at that point to
> pursue options to present back to the community?
>
> ________________________________
>
> This e-mail message (including any attachments) is for the sole use of
> the intended recipient(s) and may contain confidential and privileged
> information. If the reader of this message is not the intended
> recipient, you are hereby notified that any dissemination, distribution
> or copying of this message (including any attachments) is strictly
> prohibited.
>
> If you have received this message in error, please contact
> the sender by reply e-mail message and destroy all copies of the
> original message (including attachments).
>
>
>
>
> --
> --------------------------------------------------------------
> Rogan R. Hamby, Data and Project Analyst
> Equinox - Open Your Library
> [log in to unmask]<mailto:[log in to unmask]>
> 1-877-OPEN-ILS | www.esilibrary.com
>
>

Top of Message | Previous Page | Permalink

Advanced Options


Options

Log In

Log In

Get Password

Get Password


Search Archives

Search Archives


Subscribe or Unsubscribe

Subscribe or Unsubscribe


Archives

November 2024
October 2024
September 2024
August 2024
July 2024
June 2024
May 2024
April 2024
March 2024
February 2024
January 2024
December 2023
November 2023
October 2023
September 2023
August 2023
July 2023
June 2023
May 2023
April 2023
March 2023
February 2023
January 2023
December 2022
November 2022
October 2022
September 2022
August 2022
July 2022
June 2022
May 2022
April 2022
March 2022
February 2022
January 2022
December 2021
November 2021
October 2021
September 2021
August 2021
July 2021
June 2021
May 2021
April 2021
March 2021
February 2021
January 2021
December 2020
November 2020
October 2020
September 2020
August 2020
July 2020
June 2020
May 2020
April 2020
March 2020
February 2020
January 2020
December 2019
November 2019
October 2019
September 2019
August 2019
July 2019
June 2019
May 2019
April 2019
March 2019
February 2019
January 2019
December 2018
November 2018
October 2018
September 2018
August 2018
July 2018
June 2018
May 2018
April 2018
March 2018
February 2018
January 2018
December 2017
November 2017
October 2017
September 2017
August 2017
July 2017
June 2017
May 2017
April 2017
March 2017
February 2017
January 2017
December 2016
November 2016
October 2016
September 2016
August 2016
July 2016
June 2016
May 2016
April 2016
March 2016
February 2016
January 2016
December 2015
November 2015
October 2015
September 2015
August 2015
July 2015
June 2015
May 2015
April 2015
March 2015
February 2015
January 2015
December 2014
November 2014
October 2014
September 2014
August 2014
July 2014
June 2014
May 2014
April 2014
March 2014
February 2014
January 2014
December 2013
November 2013
October 2013
September 2013
August 2013
July 2013
June 2013
May 2013
April 2013
March 2013
February 2013
January 2013
December 2012
November 2012
October 2012
September 2012
August 2012
July 2012
June 2012
May 2012
April 2012
March 2012
February 2012
January 2012
December 2011
November 2011
October 2011
September 2011
August 2011
July 2011
June 2011
May 2011
April 2011
March 2011
February 2011
January 2011
December 2010
November 2010
October 2010
September 2010
August 2010
July 2010
June 2010
May 2010
April 2010
March 2010
February 2010
January 2010
December 2009
November 2009
October 2009
September 2009
August 2009
July 2009
June 2009
May 2009
April 2009
March 2009
February 2009
January 2009
December 2008
November 2008
October 2008
September 2008
August 2008
July 2008
June 2008
May 2008
April 2008
March 2008
February 2008
January 2008
December 2007
November 2007
October 2007
September 2007
August 2007
July 2007
June 2007
May 2007
April 2007
March 2007
February 2007
January 2007
December 2006
November 2006
October 2006
September 2006
August 2006
July 2006
June 2006
May 2006
April 2006
March 2006
February 2006
January 2006
December 2005
November 2005
October 2005
September 2005
August 2005
July 2005
June 2005
May 2005
April 2005
March 2005
February 2005
January 2005
December 2004
November 2004
October 2004
September 2004
August 2004
July 2004
June 2004
May 2004
April 2004
March 2004
February 2004
January 2004
December 2003
November 2003

ATOM RSS1 RSS2



LISTS.CLIR.ORG

CataList Email List Search Powered by the LISTSERV Email List Manager