Re: [CODE4LIB] Governance for Code4Lib (was: What's so bad about bylaws?)

2017-07-25 Thread EDWIN VINCENT SPERR
Sounds like a start! 

Don't have a copy of Robert's handy, but I think there are more-or-less 
established procedures for bootstrapping governance structures to get one 
started. Once initial bylaws are in place, you have a formal process for 
getting input for further iterations.

One point of order -- if we're going to call a vote on an important issue, it's 
vital that all stakeholders know what's going on. So, a separate message (with 
a suitably "officialish" subject line) to the list announcing the vote? Is 
there any need to send a separate message to recent conference attendees, or is 
it a safe assumption that they are all subscribed to the list?

Ed Sperr
Clinical Information Librarian
AU/UGA Medical Partnership
Athens, GA
esp...@uga.edu | esp...@stmarysathens.org

-Original Message-
From: Code for Libraries [mailto:CODE4LIB@LISTS.CLIR.ORG] On Behalf Of 
Andromeda Yelton
Sent: Monday, July 24, 2017 9:32 PM
To: CODE4LIB@LISTS.CLIR.ORG
Subject: Re: [CODE4LIB] Governance for Code4Lib (was: What's so bad about 
bylaws?)

In my experience on the LITA board (which Code4lib most emphatically is not), 
there are sometimes discussions where all the substantive issues have been put 
on the table but we have not managed to make a decision, and eventually I 
realized that is because unstructured discussion is not a mechanism for making 
decisions. In the LITA context, the remedy for indecisiveness is to *call the 
question* - to put a motion on the table and make a vote happen, because votes, 
unlike discussions, are decisions.

I believe this discussion has already put the substantive issues on the table, 
and Code4lib is failing to reach a decision - the same decision it failed to 
reach last year - because it lacks a mechanism for calling the question; 
discussion thus eventually peters out without a mechanism for closure. 
Do-ocracy has been, and I hope and expect will continue to be, a fantastic 
means for Code4lib to produce deliverables - conferences, journals, discussion 
spaces, codes of conduct - but those are all situations where self-nominating 
do-o-crats speak for the *project*, for the deliverable, and not for the 
governance of the community as a whole. I don't think any one of us, or even 
defined group of us, has the legitimacy to speak for us all in that way.

So we are...not making decisions about governance because we lack a governance 
structure with which to make decisions?

That said, I have seen an actual decision-making mechanism proposed in this
discussion: fire up the diebold-o-tron and vote on incorporation/do 
nothing/fiscal sponsorship (with a second vote, if needed, to choose among 
sponsors). This seems like a very *Code4lib* way of doing things. Assuming we 
reached some quorum (to put a number on the table, say "70% times the number of 
posters to the list in the last year"), is there anyone here who would not find 
the outcome of that decision to be legitimate?

On Mon, Jul 24, 2017 at 6:36 PM, Kim, Bohyun 
wrote:

> Jonathan is right, Cary. I am on this year's LPC for the next year's 
> C4L conference at DC, and we are already working with DLF as a fiscal sponsor.
> No legal entity status was required.
>
> Bohyun
>
>
> 
> From: Code for Libraries  on behalf of 
> Jonathan Rochkind 
> Sent: Monday, July 24, 2017 6:18 PM
> To: CODE4LIB@LISTS.CLIR.ORG
> Subject: Re: [CODE4LIB] Governance for Code4Lib (was: What's so bad 
> about
> bylaws?)
>
> > The bottom line is that we need some sort of entity if we want enter 
> > into
> an agreement with a fiscal agent or sponsor. Otherwise, there is no 
> "we” to enter into said agreement.
>
> I've said this before and I'll keep saying it, this is not true that 
> you need a legal entity to have your project fiscally sponsored by a 
> fiscal sponsor. I know of many projects (not library related, 
> generally
> 'charitable') which become fiscally sponsored without having any legal 
> incorporation or other legal entity. The project is legally a project 
> of the fiscal sponsor.
>
> It is very common. It is a common way for "charitable" projects to 
> start out, without legally incorporating at all, perhaps to legally 
> incorporate and separate from the fiscal sponsor at a later date.
>
> If the people we are talking to for fiscal sponsorship are fine with 
> this, it is a common thing.
>
> Jonathan
>
> On Mon, Jul 24, 2017 at 6:04 PM, Cary Gordon  wrote:
>
> > This is what the FCIG has been working on.
> >
> > The bottom line is that we need some sort of entity if we want enter 
> > into an agreement with a fiscal agent or sponsor. Otherwise, there is no 
> > "we”
> to
> > enter into said agreement.
> >
> > Cary
> >
> > > On Jul 24, 2017, at 1:03 PM, EDWIN VINCENT SPERR 
> wrote:
> > >
> > > Again, it is great that things have worked out so well for so 
> > > long. And
> > there is nothing about the process of formalization that requires 
> > (or is even intended

Re: [CODE4LIB] Governance for Code4Lib (was: What's so bad about bylaws?)

2017-07-25 Thread Jason Bengtson
+1

Best regards,

*Jason Bengtson*


*http://www.jasonbengtson.com/ *

On Tue, Jul 25, 2017 at 7:17 AM, EDWIN VINCENT SPERR  wrote:

> Sounds like a start!
>
> Don't have a copy of Robert's handy, but I think there are more-or-less
> established procedures for bootstrapping governance structures to get one
> started. Once initial bylaws are in place, you have a formal process for
> getting input for further iterations.
>
> One point of order -- if we're going to call a vote on an important issue,
> it's vital that all stakeholders know what's going on. So, a separate
> message (with a suitably "officialish" subject line) to the list announcing
> the vote? Is there any need to send a separate message to recent conference
> attendees, or is it a safe assumption that they are all subscribed to the
> list?
>
> Ed Sperr
> Clinical Information Librarian
> AU/UGA Medical Partnership
> Athens, GA
> esp...@uga.edu | esp...@stmarysathens.org
>
> -Original Message-
> From: Code for Libraries [mailto:CODE4LIB@LISTS.CLIR.ORG] On Behalf Of
> Andromeda Yelton
> Sent: Monday, July 24, 2017 9:32 PM
> To: CODE4LIB@LISTS.CLIR.ORG
> Subject: Re: [CODE4LIB] Governance for Code4Lib (was: What's so bad about
> bylaws?)
>
> In my experience on the LITA board (which Code4lib most emphatically is
> not), there are sometimes discussions where all the substantive issues have
> been put on the table but we have not managed to make a decision, and
> eventually I realized that is because unstructured discussion is not a
> mechanism for making decisions. In the LITA context, the remedy for
> indecisiveness is to *call the question* - to put a motion on the table and
> make a vote happen, because votes, unlike discussions, are decisions.
>
> I believe this discussion has already put the substantive issues on the
> table, and Code4lib is failing to reach a decision - the same decision it
> failed to reach last year - because it lacks a mechanism for calling the
> question; discussion thus eventually peters out without a mechanism for
> closure. Do-ocracy has been, and I hope and expect will continue to be, a
> fantastic means for Code4lib to produce deliverables - conferences,
> journals, discussion spaces, codes of conduct - but those are all
> situations where self-nominating do-o-crats speak for the *project*, for
> the deliverable, and not for the governance of the community as a whole. I
> don't think any one of us, or even defined group of us, has the legitimacy
> to speak for us all in that way.
>
> So we are...not making decisions about governance because we lack a
> governance structure with which to make decisions?
>
> That said, I have seen an actual decision-making mechanism proposed in this
> discussion: fire up the diebold-o-tron and vote on incorporation/do
> nothing/fiscal sponsorship (with a second vote, if needed, to choose among
> sponsors). This seems like a very *Code4lib* way of doing things. Assuming
> we reached some quorum (to put a number on the table, say "70% times the
> number of posters to the list in the last year"), is there anyone here who
> would not find the outcome of that decision to be legitimate?
>
> On Mon, Jul 24, 2017 at 6:36 PM, Kim, Bohyun 
> wrote:
>
> > Jonathan is right, Cary. I am on this year's LPC for the next year's
> > C4L conference at DC, and we are already working with DLF as a fiscal
> sponsor.
> > No legal entity status was required.
> >
> > Bohyun
> >
> >
> > 
> > From: Code for Libraries  on behalf of
> > Jonathan Rochkind 
> > Sent: Monday, July 24, 2017 6:18 PM
> > To: CODE4LIB@LISTS.CLIR.ORG
> > Subject: Re: [CODE4LIB] Governance for Code4Lib (was: What's so bad
> > about
> > bylaws?)
> >
> > > The bottom line is that we need some sort of entity if we want enter
> > > into
> > an agreement with a fiscal agent or sponsor. Otherwise, there is no
> > "we” to enter into said agreement.
> >
> > I've said this before and I'll keep saying it, this is not true that
> > you need a legal entity to have your project fiscally sponsored by a
> > fiscal sponsor. I know of many projects (not library related,
> > generally
> > 'charitable') which become fiscally sponsored without having any legal
> > incorporation or other legal entity. The project is legally a project
> > of the fiscal sponsor.
> >
> > It is very common. It is a common way for "charitable" projects to
> > start out, without legally incorporating at all, perhaps to legally
> > incorporate and separate from the fiscal sponsor at a later date.
> >
> > If the people we are talking to for fiscal sponsorship are fine with
> > this, it is a common thing.
> >
> > Jonathan
> >
> > On Mon, Jul 24, 2017 at 6:04 PM, Cary Gordon 
> wrote:
> >
> > > This is what the FCIG has been working on.
> > >
> > > The bottom line is that we need some sort of entity if we want enter
> > > into an agreement with a fiscal agent or sponsor. Otherwise, 

[CODE4LIB] Notice of Funding Opportunities - FY 2018 - IMLS

2017-07-25 Thread James Neal
Of potential interest to members of this list. Please consider helping to
distribute widely.



*IMLS Accepting Applications for National Leadership and Laura Bush 21st
Century Librarian Grants*



https://www.imls.gov/news-events/news-releases/imls-accepting-applications-national-leadership-and-laura-bush-21st#sthash.vAqITMUc.uxfs

James Neal

james3n...@gmail.com
301-273-5221

"Mastery of language affords remarkable power." - Frantz Fanon

“[T]he tragedy of life doesn't lie in not reaching your goal. The tragedy
lies in having no goal to reach. It isn't a calamity to die with dreams
unfulfilled, but it is a calamity not to dream It is not a disgrace not
to reach the stars, but it is a disgrace to have no stars to reach for. Not
failure, but low aim is sin."
— Benjamin Elijah Mays, American educator and president of Morehouse
College (1895-1984)

TWITTER: http://www.twitter.com/james3neal

INSTAGRAM: https://instagram.com/james3neal/

TUMBLR: http://james3neal.tumblr.com/

G+:  gplus.to/james3neal

PINTEREST: http://www.pinterest.com/james3neal/pins/


[CODE4LIB] Job Posting: Software developer for digital newspapers project (deadline extended)

2017-07-25 Thread Eben English
*** DEADLINE EXTENDED, NEW JOB LINK BELOW ***

** please excuse any cross-posting **

http://employment.utah.edu/salt-lake-city-ut/software-developer/11FFF5F83B5644D3BA3A0D1FE4CBC07F/job/

The University of Utah’s Marriott Library and the Boston Public Library
(BPL) are looking for a skilled, creative, and motivated software developer
to help us improve the way libraries store and share digitized historic
newspapers. This 20-month full-time telecommuting position, which includes
excellent benefits, is funded by a grant from the Institute of Museum and
Library Services (IMLS). The goals of the project will be to develop a set
of modular, open-source software plugins for ingesting, describing,
discovering, displaying, and disseminating digitized newspaper content
within the popular Samvera (formerly known as Hydra; https://samvera.org/)
and Fedora Commons (http://fedorarepository.org/) digital asset management
system framework. Due to the temporary nature of this position, the
Marriott Library will not be able to sponsor work-authorization visas.

The project addresses an acute need among institutions providing digital
access to cultural heritage materials. Newspaper content poses unique
challenges for management and dissemination, especially in terms of
article-level access. Our goal is to provide robust support for managing
both physical (microfilm reels, pages, digital files) and intellectual
(issues, articles) objects, as well as supporting descriptive metadata
specific to newspaper content.

The successful candidate will join a distributed team of passionate and
talented developers and technologists from The University of Utah and
Boston Public Library. We will employ a development process informed by
Agile development frameworks, emphasizing frequent communication, adaptive
planning driven by user needs, iterative development, frequent delivery of
releases, continuous refinement, and flexible adaptation to changing
requirements. You will also work with committees and Interest Groups
representing key stakeholders, who will provide guidance on project
planning, vision, and sustainability, as well as feedback on the code. (See
https://wiki.duraspace.org/display/samvera/Samvera+Newspapers+Interest+Group
for
more.)

This is a telecommuting/remote position. See the link above for more
information on qualifications, responsibilities, and compensation. For full
consideration, please apply by July 31, 2017.


[CODE4LIB] Job posting: Systems Librarian, Tulane University

2017-07-25 Thread Maurice, Candace A
Job Title

[https://selfservice.tulane.edu/OA_HTML/cabo/images/swan/t.gif]

Systems Librarian


Location

[https://selfservice.tulane.edu/OA_HTML/cabo/images/swan/t.gif]

New Orleans, LA, US


Organization Name

[https://selfservice.tulane.edu/OA_HTML/cabo/images/swan/t.gif]

Howard-Tilton Memorial Library, TULANE UNIVERSITY




Posting Summary

[https://selfservice.tulane.edu/OA_HTML/cabo/images/swan/t.gif]







The Systems Librarian takes an innovative, service-centric approach to the 
oversight of several key information management and discovery systems (Voyager, 
Primo, ILLiad). S/he will be responsible for ensuring the optimal performance 
of these systems, which will include: enabling data integration across 
distributed and heterogeneous local and external data sources; providing 
statistical, usage, and collection reports in support of decision making for 
library collections and services; and promptly reporting issues/problems to 
vendor(s) with follow-through until resolution. Additionally, the Systems 
Librarian has secondary (back-up) responsibility for the link resolver 
(currently SFX), and proxy authentication systems. As a technology liaison to 
library departments, s/he participates in formal task groups and committees, 
both standing and ad-hoc, to analyze and improve systems and services. S/he 
will have programming skills consummate with the Library’s technology goals and 
ambitions and will serve as part of a technology team that includes web 
development, digital collections, and digital publishing initiatives.


REQUIRED KNOWLEDGE, SKILLS, ABILITIES/COMPETENCIES TYPICALLY NEEDED TO PERFORM 
THIS JOB SUCCESSFULLY:

  *   Experience managing integrated library systems and resource discovery 
tools, link resolvers, and
  *   proxy authentication systems
  *   Experience managing Windows and Unix based servers
  *   Demonstrated ability to work with database management systems and scripts 
(e.g., MS SQL,
  *   MySQL, Oracle, or MS Access) and writing queries in SQL
  *   Programming in XSLT, PHP, Ruby, or Python
  *   Experience with Web standards and scripting using HTML, XML, CSS, 
JavaScript or JQuery
  *   Demonstrated analytical, technical, and troubleshooting skills for 
complex applications
  *   Significant experience in project management
  *   Strong service orientation
  *   Proficiency in written and interpersonal communication
  *   Ability to succeed both independently and in a collaborative team 
environment
  *   Ability to function fully and competently at technology competency Levels 
I, II and III outlined in
  *   HTML Core Technology Competencies for Employees. (See 
https://library.tulane.edu/sites/library.tulane.edu/files/documents/core_technology_competencies.pdf
 )




Minimum Qualifications

[https://selfservice.tulane.edu/OA_HTML/cabo/images/swan/t.gif]






ESSENTIAL FUNCTIONS:

  *   Responsible for all aspects of the Integrated Library System (Voyager) 
and the resource discovery tool (Primo)
  *   Serves as primary contact with Ex Libris for Voyager and Primo
  *   Provides functional support for all Voyager modules, and creation of 
custom SQL reports
  *   Implements enhancements and customizations as determined by relevant 
library committees or responsible administrators
  *   Integrates locally developed and third-party applications
  *   Serves as backup system administrator for SFX, MetaLib and EZProxy for 
troubleshooting and reporting system problems
  *   Maintains current awareness of library technologies; investigates 
emerging information technologies and assesses their potential for library use
  *   Librarianship is an evolving profession and the Systems Librarian is 
expected to develop expertise in emerging technologies. He or she is expected 
to lead and/or participate in new and innovative library projects. Exhibits a 
willingness to assume additional duties whether or not specifically mentioned 
in this job description. This librarian works cooperatively with staff and 
other librarians as well as with faculty, students, and other librarians at 
other libraries. He or she contributes service to library committees and task 
forces as well as to the profession


Minimum Education

[https://selfservice.tulane.edu/OA_HTML/cabo/images/swan/t.gif]






  *   ALA-accredited MLS or another graduate degree in information technology, 
computer science, or other technology field
  *   At least two years’ relevant experience in an academic or research library


Preferred Qualifications

[https://selfservice.tulane.edu/OA_HTML/cabo/images/swan/t.gif]






  *   Familiarity with bibliographic record structure and classification systems
  *   Experience with Primo, Voyager, Islandora, ArchivesSpace and ILLiad
  *   Experience integrating a wide variety of third-party applications into 
library information systems
  *   Knowledge of authentication using LDAP and Shibboleth
  *   Proficiency with standard computer hardware and desktop applications, 

[CODE4LIB] Job: Head of Digital Programs & Services - LSU Libraries

2017-07-25 Thread Gina R Costello
Louisiana State University Libraries is looking for a collaborative, 
forward-thinking individual with experience managing digital projects and  
people to lead and manage the day-to-day operations for digitization, web 
services, digital library management, digital preservation, and digital 
scholarship/digital humanities.

The past two years have been a time of growth for the LSU Libraries with major 
technology projects such as the development of the statewide Louisiana Digital 
Library in Islandora, start of a Digital Scholarship Lab to support campus-wide 
digital projects, website migration to Drupal, launch of a university 
institutional repository, and implementation of ArchivesSpace and Aeon. Our 
technology team continues to grow and we would love to have you on board.

LSU, located in state capital Baton Rouge, is the state's flagship university 
with over 31,000 students and 1,300 faculty. Learn more about LSU and Baton 
Rouge by visiting http://www.lsu.edu/about/index.php

JOB ANNOUNCEMENT

Head of Digital Programs & Services
Apply via: 
https://lsu.wd1.myworkdayjobs.com/LSU/job/LSU---Baton-Rouge/Assistant-Librarian_R0183-1

Position Description:
Reporting to the Associate Dean for Technology Initiatives, the Head of Digital 
Programs will be forward-thinking, capable of conveying technical issues to 
diverse constituencies, enjoy working in a collaborative team environment, and 
be experienced with varied digital services/systems. He/she will promote the 
Libraries at state and national arenas and develop collaborative relationships 
with Libraries' departments and campus units/departments to ensure continued 
digital collections growth and a robust web presence. Incumbent is responsible 
for managing day-to-day operations of the following areas: web services, 
digitization, digital library management, digital preservation, and digital 
scholarship/digital humanities and supervising 6 FTE.

Job Responsibilities
*   35% Develops innovative and effective strategies for the Libraries' 
digitization and preservation operations; Develops and documents policies and 
procedures designed to ensure the access and preservation of digital assets; 
Monitors trends in the reformatting and digital arenas and recommends 
activities to anticipate developing needs; Establishes and maintains compliance 
with national standards relating to accessibility and preservation of digital 
information.
*   25% Serves as an ambassador for the Libraries digital programs by 
building and maintaining effective working relationships to foster productive 
collaborations with all levels of the organization, with the university 
community, and external partners; Serves as a main contact for all partners in 
digital project development and digital preservation; Assists in securing 
administrative and/or external funding through grants and contracts to 
facilitate future digital collection growth.
*   15% Supervises the development and management of the Libraries' online 
presence which includes all web pages and systems such as the Louisiana Digital 
Library and Discovery, digital exhibitions, and digital scholarship.
*   15% Works to meet tenure and promotion requirements.
*   10% Works closely with Libraries IT/Systems team to ensure continued 
development of the Louisiana Digital Library platform and other systems such as 
ArchivesSpace; Works with Resource Description & Metadata Services to 
coordinate the development of metadata to support the discovery and management 
of digital content including digital scholarship, digitized collections, 
born-digital archives, and research data.

Minimum Qualifications
*   Master degree from an ALA-accredited library school or other relevant 
degree.
*   5 years' experience managing digital projects, services, and related 
personnel.
*   Management skills in innovative & changing technology environment.
*   Experience bringing complex digital projects to completion.
*   Substantial knowledge of digital libraries, digital preservation, and 
digital scholarship.
*   Ability to build and maintain effective working relationships and 
foster productive collaboration.

Preferred Qualifications
*   3 years working in a higher education setting, preferably an academic 
library managing digital projects.
*   Grant applications & funded projects.
*   Understanding of technology issues & best practices in libraries/higher 
ed.
*   Involvement in professional association or discipline.
*   Familiarity with Islandora or other Fedora-based system, ArchivesSpace, 
and web development practices.




Gina R. Costello
Associate Dean for Technology Initiatives
Interim Associate Dean for Special Collections
LSU Libraries
Louisiana State University
295 Middleton Library, Baton Rouge, LA  70803
office 225-578-3686 | mobile 225-362-2793
gcos...@lsu.edu | lsu.edu | 
lib.lsu.edu

Re: [CODE4LIB] Governance for Code4Lib

2017-07-25 Thread Eric Hellman
To follow up on Andromeda's calling the question, we need to do some things in 
addition to the usual dieboldotron.

1. There's a point of fact that is still being disputed/discussed: whether 
formalization is required by potential fiscal sponsor. It's straightforward to 
answer this before any poll is conducted -  ask the potential fiscal sponsors 
to weigh in on the question.

2. There's been conflicting suggestions as to the voting method. (Approval vs. 
ranked). The scary word "quorum" has been mentioned. There also needs to be 
some discussion and consensus on exactly what the options to be voted on will 
say. Probably this works better with issues in a github repo.

And I have to point out that right after asserting that Code4Lib "lacks a 
mechanism for calling the question", Andromeda invoked a Code4Lib mechanism for 
calling the question.

Eric


> On Jul 24, 2017, at 9:32 PM, Andromeda Yelton  
> wrote:
> 
> In my experience on the LITA board (which Code4lib most emphatically is
> not), there are sometimes discussions where all the substantive issues have
> been put on the table but we have not managed to make a decision, and
> eventually I realized that is because unstructured discussion is not a
> mechanism for making decisions. In the LITA context, the remedy for
> indecisiveness is to *call the question* - to put a motion on the table and
> make a vote happen, because votes, unlike discussions, are decisions.
> 
> I believe this discussion has already put the substantive issues on the
> table, and Code4lib is failing to reach a decision - the same decision it
> failed to reach last year - because it lacks a mechanism for calling the
> question; discussion thus eventually peters out without a mechanism for
> closure. Do-ocracy has been, and I hope and expect will continue to be, a
> fantastic means for Code4lib to produce deliverables - conferences,
> journals, discussion spaces, codes of conduct - but those are all
> situations where self-nominating do-o-crats speak for the *project*, for
> the deliverable, and not for the governance of the community as a whole. I
> don't think any one of us, or even defined group of us, has the legitimacy
> to speak for us all in that way.
> 
> So we are...not making decisions about governance because we lack a
> governance structure with which to make decisions?
> 
> That said, I have seen an actual decision-making mechanism proposed in this
> discussion: fire up the diebold-o-tron and vote on incorporation/do
> nothing/fiscal sponsorship (with a second vote, if needed, to choose among
> sponsors). This seems like a very *Code4lib* way of doing things. Assuming
> we reached some quorum (to put a number on the table, say "70% times the
> number of posters to the list in the last year"), is there anyone here who
> would not find the outcome of that decision to be legitimate?
> 
> On Mon, Jul 24, 2017 at 6:36 PM, Kim, Bohyun 
> wrote:
> 
>> Jonathan is right, Cary. I am on this year's LPC for the next year's C4L
>> conference at DC, and we are already working with DLF as a fiscal sponsor.
>> No legal entity status was required.
>> 
>> Bohyun
>> 
>> 
>> 
>> From: Code for Libraries  on behalf of Jonathan
>> Rochkind 
>> Sent: Monday, July 24, 2017 6:18 PM
>> To: CODE4LIB@LISTS.CLIR.ORG
>> Subject: Re: [CODE4LIB] Governance for Code4Lib (was: What's so bad about
>> bylaws?)
>> 
>>> The bottom line is that we need some sort of entity if we want enter into
>> an agreement with a fiscal agent or sponsor. Otherwise, there is no "we” to
>> enter into said agreement.
>> 
>> I've said this before and I'll keep saying it, this is not true that you
>> need a legal entity to have your project fiscally sponsored by a fiscal
>> sponsor. I know of many projects (not library related, generally
>> 'charitable') which become fiscally sponsored without having any legal
>> incorporation or other legal entity. The project is legally a project of
>> the fiscal sponsor.
>> 
>> It is very common. It is a common way for "charitable" projects to start
>> out, without legally incorporating at all, perhaps to legally incorporate
>> and separate from the fiscal sponsor at a later date.
>> 
>> If the people we are talking to for fiscal sponsorship are fine with this,
>> it is a common thing.
>> 
>> Jonathan
>> 
>> On Mon, Jul 24, 2017 at 6:04 PM, Cary Gordon  wrote:
>> 
>>> This is what the FCIG has been working on.
>>> 
>>> The bottom line is that we need some sort of entity if we want enter into
>>> an agreement with a fiscal agent or sponsor. Otherwise, there is no "we”
>> to
>>> enter into said agreement.
>>> 
>>> Cary
>>> 
 On Jul 24, 2017, at 1:03 PM, EDWIN VINCENT SPERR 
>> wrote:
 
 Again, it is great that things have worked out so well for so long. And
>>> there is nothing about the process of formalization that requires (or is
>>> even intended to bring about) the sidelining of the folks who have worked
>

Re: [CODE4LIB] Governance for Code4Lib

2017-07-25 Thread Esmé Cowles
On Jul 25, 2017, at 10:58 AM, Eric Hellman  wrote:
> 
> To follow up on Andromeda's calling the question, we need to do some things 
> in addition to the usual dieboldotron.
> 
> 1. There's a point of fact that is still being disputed/discussed: whether 
> formalization is required by potential fiscal sponsor. It's straightforward 
> to answer this before any poll is conducted -  ask the potential fiscal 
> sponsors to weigh in on the question.

Hasn't that been settled by Bohyun's message yesterday?

> On Jul 24, 2017, at 6:36 PM, Kim, Bohyun  wrote:
> 
> Jonathan is right, Cary. I am on this year's LPC for the next year's C4L 
> conference at DC, and we are already working with DLF as a fiscal sponsor. No 
> legal entity status was required.


Or is there some question that the requirements may be different for a 
long-term fiscal sponsorship, as opposed to a one-time sponsorship?

-Esmé

Re: [CODE4LIB] Governance for Code4Lib

2017-07-25 Thread Bethany Nowviskie
Hi, folks — this is just to clarify that, from the CLIR/DLF point of view, no 
incorporation or greater formalization than already exists in the community 
would be necessary for us to extend our current fiscal sponsorship (of the 
conference, etc.) to the long term.

Coral quoted it earlier, but here’s the relevant bit from the FCIG report:

CLIR would not request any control over Code4Lib’s organizational/"governance” 
processes, or that Code4Lib adopt CLIR’s or DLF’s bylaws.
In terms of contact persons between Code4Lib and CLIR/DLF, CLIR expressed 
familiarity with Code4Lib’s current operational processes, and indicated that 
they would be fine with these processes continuing: "Single point of contact, 
changing annually, and without a required connection to CLIR or DLF is fine. In 
short, the practice of having local organizing committees and rotating 
leadership over the conference and other activities that currently exists in 
Code4Lib would be acceptable. We work with some other groups who operate in 
this way, and were also comfortable taking on hosting of the Code4Lib listserv 
recently, knowing and appreciating how grassroots leadership happens in the 
community!"

We’re not big on red tape, either, and I think — even though it can get messy 
or stall out a little, sometimes! — decision-making, leadership, and lazy 
consensus in C4L is a wonder to behold, not to be overly messed-with.

Happy to answer any questions, when voting plans get to the right stage. I 
understand a message from Galen on behalf of the FCIG is on its way. — B.

Bethany Nowviskie
Director of the Digital Library Federation (DLF) at CLIR
Research Associate Professor of Digital Humanities, UVa
diglib.org | clir.org | 
ndsa.org | nowviskie.org | she/her/hers


--

Date:Tue, 25 Jul 2017 11:18:03 -0400
From:Esmé Cowles mailto:escow...@ticklefish.org>>
Subject: Re: Governance for Code4Lib

On Jul 25, 2017, at 10:58 AM, Eric Hellman 
mailto:e...@hellman.net>> wrote:

To follow up on Andromeda's calling the question, we need to do some things in 
addition to the usual dieboldotron.

1. There's a point of fact that is still being disputed/discussed: whether 
formalization is required by potential fiscal sponsor. It's straightforward to 
answer this before any poll is conducted -  ask the potential fiscal sponsors 
to weigh in on the question.

Hasn't that been settled by Bohyun's message yesterday?

On Jul 24, 2017, at 6:36 PM, Kim, Bohyun 
mailto:b...@hshsl.umaryland.edu>> wrote:

Jonathan is right, Cary. I am on this year's LPC for the next year's C4L 
conference at DC, and we are already working with DLF as a fiscal sponsor. No 
legal entity status was required.

Or is there some question that the requirements may be different for a 
long-term fiscal sponsorship, as opposed to a one-time sponsorship?

-Esmé


Re: [CODE4LIB] Governance for Code4Lib

2017-07-25 Thread Eric Hellman

Eric Hellman
President, Free Ebook Foundation
Founder, Unglue.it https://unglue.it/
https://go-to-hellman.blogspot.com/
twitter: @gluejar

> On Jul 25, 2017, at 11:18 AM, Esmé Cowles  wrote:
> 
> On Jul 25, 2017, at 10:58 AM, Eric Hellman  wrote:
>> 
>> To follow up on Andromeda's calling the question, we need to do some things 
>> in addition to the usual dieboldotron.
>> 
>> 1. There's a point of fact that is still being disputed/discussed: whether 
>> formalization is required by potential fiscal sponsor. It's straightforward 
>> to answer this before any poll is conducted -  ask the potential fiscal 
>> sponsors to weigh in on the question.
> 
> Hasn't that been settled by Bohyun's message yesterday?

> 
>> On Jul 24, 2017, at 6:36 PM, Kim, Bohyun  wrote:
>> 
>> Jonathan is right, Cary. I am on this year's LPC for the next year's C4L 
>> conference at DC, and we are already working with DLF as a fiscal sponsor. 
>> No legal entity status was required.
> 
> 
> Or is there some question that the requirements may be different for a 
> long-term fiscal sponsorship, as opposed to a one-time sponsorship?
> 
> -Esmé


There were multiple threads with conflicting assertions. Bethany's post answers 
definitively as to CLIR. From the discussion, I understand that LITA also 
requires 2 LITA members as point of contact. It may be that other organizations 
may have different requirements, but I think we have enough to proceed.




signature.asc
Description: Message signed with OpenPGP using GPGMail


Re: [CODE4LIB] Governance for Code4Lib

2017-07-25 Thread Roy Tennant
Well then, I know how I will vote. Why fix what ain't broke? As I recall,
that was our response to me calling the non-profit question back at the
first Code4Lib Conference. Since there was no strong reason to become a
non-profit at that time, we shrugged our shoulders and moved on. Since
CLIR/DLF is fine with the way things are, then so am I.
Roy

On Tue, Jul 25, 2017 at 10:06 AM, Bethany Nowviskie 
wrote:

> Hi, folks — this is just to clarify that, from the CLIR/DLF point of view,
> no incorporation or greater formalization than already exists in the
> community would be necessary for us to extend our current fiscal
> sponsorship (of the conference, etc.) to the long term.
>
> Coral quoted it earlier, but here’s the relevant bit from the FCIG report:
>
> CLIR would not request any control over Code4Lib’s
> organizational/"governance” processes, or that Code4Lib adopt CLIR’s or
> DLF’s bylaws.
> In terms of contact persons between Code4Lib and CLIR/DLF, CLIR expressed
> familiarity with Code4Lib’s current operational processes, and indicated
> that they would be fine with these processes continuing: "Single point of
> contact, changing annually, and without a required connection to CLIR or
> DLF is fine. In short, the practice of having local organizing committees
> and rotating leadership over the conference and other activities that
> currently exists in Code4Lib would be acceptable. We work with some other
> groups who operate in this way, and were also comfortable taking on hosting
> of the Code4Lib listserv recently, knowing and appreciating how grassroots
> leadership happens in the community!"
>
> We’re not big on red tape, either, and I think — even though it can get
> messy or stall out a little, sometimes! — decision-making, leadership, and
> lazy consensus in C4L is a wonder to behold, not to be overly messed-with.
>
> Happy to answer any questions, when voting plans get to the right stage. I
> understand a message from Galen on behalf of the FCIG is on its way. — B.
>
> Bethany Nowviskie
> Director of the Digital Library Federation (DLF) at CLIR
> Research Associate Professor of Digital Humanities, UVa
> diglib.org | clir.org | ndsa.org<
> http://ndsa.org> | nowviskie.org | she/her/hers
>
>
> --
>
> Date:Tue, 25 Jul 2017 11:18:03 -0400
> From:Esmé Cowles  escow...@ticklefish.org>>
> Subject: Re: Governance for Code4Lib
>
> On Jul 25, 2017, at 10:58 AM, Eric Hellman mailto:eric@
> hellman.net>> wrote:
>
> To follow up on Andromeda's calling the question, we need to do some
> things in addition to the usual dieboldotron.
>
> 1. There's a point of fact that is still being disputed/discussed: whether
> formalization is required by potential fiscal sponsor. It's straightforward
> to answer this before any poll is conducted -  ask the potential fiscal
> sponsors to weigh in on the question.
>
> Hasn't that been settled by Bohyun's message yesterday?
>
> On Jul 24, 2017, at 6:36 PM, Kim, Bohyun  b...@hshsl.umaryland.edu>> wrote:
>
> Jonathan is right, Cary. I am on this year's LPC for the next year's C4L
> conference at DC, and we are already working with DLF as a fiscal sponsor.
> No legal entity status was required.
>
> Or is there some question that the requirements may be different for a
> long-term fiscal sponsorship, as opposed to a one-time sponsorship?
>
> -Esmé
>


Re: [CODE4LIB] Governance for Code4Lib

2017-07-25 Thread Coral Sheldon-Hess
While I'm usually all for calling the question as quickly as possible(!),
the FCIG is waiting on proposals from OLF and DuraSpace, before we hold the
vote -- we already have one of those, and it just needs to be put into the
report/shared out -- so that the community can make as well-informed a
decision, with as many good options, as possible.

Best,
Coral

On Tue, Jul 25, 2017 at 1:23 PM, Roy Tennant  wrote:

> Well then, I know how I will vote. Why fix what ain't broke? As I recall,
> that was our response to me calling the non-profit question back at the
> first Code4Lib Conference. Since there was no strong reason to become a
> non-profit at that time, we shrugged our shoulders and moved on. Since
> CLIR/DLF is fine with the way things are, then so am I.
> Roy
>
> On Tue, Jul 25, 2017 at 10:06 AM, Bethany Nowviskie 
> wrote:
>
> > Hi, folks — this is just to clarify that, from the CLIR/DLF point of
> view,
> > no incorporation or greater formalization than already exists in the
> > community would be necessary for us to extend our current fiscal
> > sponsorship (of the conference, etc.) to the long term.
> >
> > Coral quoted it earlier, but here’s the relevant bit from the FCIG
> report:
> >
> > CLIR would not request any control over Code4Lib’s
> > organizational/"governance” processes, or that Code4Lib adopt CLIR’s or
> > DLF’s bylaws.
> > In terms of contact persons between Code4Lib and CLIR/DLF, CLIR expressed
> > familiarity with Code4Lib’s current operational processes, and indicated
> > that they would be fine with these processes continuing: "Single point of
> > contact, changing annually, and without a required connection to CLIR or
> > DLF is fine. In short, the practice of having local organizing committees
> > and rotating leadership over the conference and other activities that
> > currently exists in Code4Lib would be acceptable. We work with some other
> > groups who operate in this way, and were also comfortable taking on
> hosting
> > of the Code4Lib listserv recently, knowing and appreciating how
> grassroots
> > leadership happens in the community!"
> >
> > We’re not big on red tape, either, and I think — even though it can get
> > messy or stall out a little, sometimes! — decision-making, leadership,
> and
> > lazy consensus in C4L is a wonder to behold, not to be overly
> messed-with.
> >
> > Happy to answer any questions, when voting plans get to the right stage.
> I
> > understand a message from Galen on behalf of the FCIG is on its way. — B.
> >
> > Bethany Nowviskie
> > Director of the Digital Library Federation (DLF) at CLIR
> > Research Associate Professor of Digital Humanities, UVa
> > diglib.org | clir.org | ndsa.org<
> > http://ndsa.org> | nowviskie.org | she/her/hers
> >
> >
> > --
> >
> > Date:Tue, 25 Jul 2017 11:18:03 -0400
> > From:Esmé Cowles  > escow...@ticklefish.org>>
> > Subject: Re: Governance for Code4Lib
> >
> > On Jul 25, 2017, at 10:58 AM, Eric Hellman  eric@
> > hellman.net>> wrote:
> >
> > To follow up on Andromeda's calling the question, we need to do some
> > things in addition to the usual dieboldotron.
> >
> > 1. There's a point of fact that is still being disputed/discussed:
> whether
> > formalization is required by potential fiscal sponsor. It's
> straightforward
> > to answer this before any poll is conducted -  ask the potential fiscal
> > sponsors to weigh in on the question.
> >
> > Hasn't that been settled by Bohyun's message yesterday?
> >
> > On Jul 24, 2017, at 6:36 PM, Kim, Bohyun  mailto:
> > b...@hshsl.umaryland.edu>> wrote:
> >
> > Jonathan is right, Cary. I am on this year's LPC for the next year's C4L
> > conference at DC, and we are already working with DLF as a fiscal
> sponsor.
> > No legal entity status was required.
> >
> > Or is there some question that the requirements may be different for a
> > long-term fiscal sponsorship, as opposed to a one-time sponsorship?
> >
> > -Esmé
> >
>


Re: [CODE4LIB] Governance for Code4Lib

2017-07-25 Thread Edward M. Corrado
I would like to thank Bethany Nowviskie (from the CLIR/DLF side) and Bohyun
Kim (from the local planning committee side) for chiming in about it not
being necessary for  incorporation or greater formalization than already
exists in the [Code4Lib] community would be necessary for [CLIR/DLF]  to
extend our current fiscal sponsorship (of the conference, etc.) to the long
term."

I think this is very useful (and, at least for me, compelling) information

Edward


On Tue, Jul 25, 2017 at 10:23 AM, Roy Tennant  wrote:

> Well then, I know how I will vote. Why fix what ain't broke? As I recall,
> that was our response to me calling the non-profit question back at the
> first Code4Lib Conference. Since there was no strong reason to become a
> non-profit at that time, we shrugged our shoulders and moved on. Since
> CLIR/DLF is fine with the way things are, then so am I.
> Roy
>
> On Tue, Jul 25, 2017 at 10:06 AM, Bethany Nowviskie 
> wrote:
>
> > Hi, folks — this is just to clarify that, from the CLIR/DLF point of
> view,
> > no incorporation or greater formalization than already exists in the
> > community would be necessary for us to extend our current fiscal
> > sponsorship (of the conference, etc.) to the long term.
> >
> > Coral quoted it earlier, but here’s the relevant bit from the FCIG
> report:
> >
> > CLIR would not request any control over Code4Lib’s
> > organizational/"governance” processes, or that Code4Lib adopt CLIR’s or
> > DLF’s bylaws.
> > In terms of contact persons between Code4Lib and CLIR/DLF, CLIR expressed
> > familiarity with Code4Lib’s current operational processes, and indicated
> > that they would be fine with these processes continuing: "Single point of
> > contact, changing annually, and without a required connection to CLIR or
> > DLF is fine. In short, the practice of having local organizing committees
> > and rotating leadership over the conference and other activities that
> > currently exists in Code4Lib would be acceptable. We work with some other
> > groups who operate in this way, and were also comfortable taking on
> hosting
> > of the Code4Lib listserv recently, knowing and appreciating how
> grassroots
> > leadership happens in the community!"
> >
> > We’re not big on red tape, either, and I think — even though it can get
> > messy or stall out a little, sometimes! — decision-making, leadership,
> and
> > lazy consensus in C4L is a wonder to behold, not to be overly
> messed-with.
> >
> > Happy to answer any questions, when voting plans get to the right stage.
> I
> > understand a message from Galen on behalf of the FCIG is on its way. — B.
> >
> > Bethany Nowviskie
> > Director of the Digital Library Federation (DLF) at CLIR
> > Research Associate Professor of Digital Humanities, UVa
> > diglib.org | clir.org | ndsa.org<
> > http://ndsa.org> | nowviskie.org | she/her/hers
> >
> >
> > --
> >
> > Date:Tue, 25 Jul 2017 11:18:03 -0400
> > From:Esmé Cowles  > escow...@ticklefish.org>>
> > Subject: Re: Governance for Code4Lib
> >
> > On Jul 25, 2017, at 10:58 AM, Eric Hellman  eric@
> > hellman.net>> wrote:
> >
> > To follow up on Andromeda's calling the question, we need to do some
> > things in addition to the usual dieboldotron.
> >
> > 1. There's a point of fact that is still being disputed/discussed:
> whether
> > formalization is required by potential fiscal sponsor. It's
> straightforward
> > to answer this before any poll is conducted -  ask the potential fiscal
> > sponsors to weigh in on the question.
> >
> > Hasn't that been settled by Bohyun's message yesterday?
> >
> > On Jul 24, 2017, at 6:36 PM, Kim, Bohyun  mailto:
> > b...@hshsl.umaryland.edu>> wrote:
> >
> > Jonathan is right, Cary. I am on this year's LPC for the next year's C4L
> > conference at DC, and we are already working with DLF as a fiscal
> sponsor.
> > No legal entity status was required.
> >
> > Or is there some question that the requirements may be different for a
> > long-term fiscal sponsorship, as opposed to a one-time sponsorship?
> >
> > -Esmé
> >
>


Re: [CODE4LIB] Governance for Code4Lib

2017-07-25 Thread Edward M. Corrado
We waited 13 or so years, so what's a few more days? I agree that we should
wait for all the information to come in from OLF and DuraSpace.

Edward

On Tue, Jul 25, 2017 at 10:34 AM, Coral Sheldon-Hess  wrote:

> While I'm usually all for calling the question as quickly as possible(!),
> the FCIG is waiting on proposals from OLF and DuraSpace, before we hold the
> vote -- we already have one of those, and it just needs to be put into the
> report/shared out -- so that the community can make as well-informed a
> decision, with as many good options, as possible.
>
> Best,
> Coral
>
> On Tue, Jul 25, 2017 at 1:23 PM, Roy Tennant  wrote:
>
> > Well then, I know how I will vote. Why fix what ain't broke? As I recall,
> > that was our response to me calling the non-profit question back at the
> > first Code4Lib Conference. Since there was no strong reason to become a
> > non-profit at that time, we shrugged our shoulders and moved on. Since
> > CLIR/DLF is fine with the way things are, then so am I.
> > Roy
> >
> > On Tue, Jul 25, 2017 at 10:06 AM, Bethany Nowviskie  >
> > wrote:
> >
> > > Hi, folks — this is just to clarify that, from the CLIR/DLF point of
> > view,
> > > no incorporation or greater formalization than already exists in the
> > > community would be necessary for us to extend our current fiscal
> > > sponsorship (of the conference, etc.) to the long term.
> > >
> > > Coral quoted it earlier, but here’s the relevant bit from the FCIG
> > report:
> > >
> > > CLIR would not request any control over Code4Lib’s
> > > organizational/"governance” processes, or that Code4Lib adopt CLIR’s or
> > > DLF’s bylaws.
> > > In terms of contact persons between Code4Lib and CLIR/DLF, CLIR
> expressed
> > > familiarity with Code4Lib’s current operational processes, and
> indicated
> > > that they would be fine with these processes continuing: "Single point
> of
> > > contact, changing annually, and without a required connection to CLIR
> or
> > > DLF is fine. In short, the practice of having local organizing
> committees
> > > and rotating leadership over the conference and other activities that
> > > currently exists in Code4Lib would be acceptable. We work with some
> other
> > > groups who operate in this way, and were also comfortable taking on
> > hosting
> > > of the Code4Lib listserv recently, knowing and appreciating how
> > grassroots
> > > leadership happens in the community!"
> > >
> > > We’re not big on red tape, either, and I think — even though it can get
> > > messy or stall out a little, sometimes! — decision-making, leadership,
> > and
> > > lazy consensus in C4L is a wonder to behold, not to be overly
> > messed-with.
> > >
> > > Happy to answer any questions, when voting plans get to the right
> stage.
> > I
> > > understand a message from Galen on behalf of the FCIG is on its way. —
> B.
> > >
> > > Bethany Nowviskie
> > > Director of the Digital Library Federation (DLF) at CLIR
> > > Research Associate Professor of Digital Humanities, UVa
> > > diglib.org | clir.org | ndsa.org<
> > > http://ndsa.org> | nowviskie.org | she/her/hers
> > >
> > >
> > > --
> > >
> > > Date:Tue, 25 Jul 2017 11:18:03 -0400
> > > From:Esmé Cowles  > > escow...@ticklefish.org>>
> > > Subject: Re: Governance for Code4Lib
> > >
> > > On Jul 25, 2017, at 10:58 AM, Eric Hellman  > eric@
> > > hellman.net>> wrote:
> > >
> > > To follow up on Andromeda's calling the question, we need to do some
> > > things in addition to the usual dieboldotron.
> > >
> > > 1. There's a point of fact that is still being disputed/discussed:
> > whether
> > > formalization is required by potential fiscal sponsor. It's
> > straightforward
> > > to answer this before any poll is conducted -  ask the potential fiscal
> > > sponsors to weigh in on the question.
> > >
> > > Hasn't that been settled by Bohyun's message yesterday?
> > >
> > > On Jul 24, 2017, at 6:36 PM, Kim, Bohyun  > mailto:
> > > b...@hshsl.umaryland.edu>> wrote:
> > >
> > > Jonathan is right, Cary. I am on this year's LPC for the next year's
> C4L
> > > conference at DC, and we are already working with DLF as a fiscal
> > sponsor.
> > > No legal entity status was required.
> > >
> > > Or is there some question that the requirements may be different for a
> > > long-term fiscal sponsorship, as opposed to a one-time sponsorship?
> > >
> > > -Esmé
> > >
> >
>


Re: [CODE4LIB] Governance for Code4Lib

2017-07-25 Thread Galen Charlton
Hi,

On Tue, Jul 25, 2017 at 10:58 AM, Eric Hellman  wrote:
> 1. There's a point of fact that is still being disputed/discussed: whether 
> formalization
>  is required by potential fiscal sponsor. It's straightforward to answer this 
> before any
>  poll is conducted -  ask the potential fiscal sponsors to weigh in on the 
> question.

DLF/CLIR has responded to this question, and the ALA/LITA section of
the FCIG report also speaks to this question.

Regarding the broader question of whether Code4Lib can seek a fiscal
sponsor as an unincorporated organization, I agree with Jonathan and
others that it is possible. Here's some additional light reading in
support of that point: [1] [2].

> 2. There's been conflicting suggestions as to the voting method. (Approval 
> vs. ranked).
> The scary word "quorum" has been mentioned. There also needs to be some 
> discussion
> and consensus on exactly what the options to be voted on will say. Probably 
> this works
> better with issues in a github repo.

I like Coral's suggestion [3] to hold a single vote that poses several
questions. As Coral mentioned just now, the FCIG is expecting
proposals from OLF and DuraSpace soon and will update the report as
they come in. My initial message this month [4] proposed 14 to 25
August for the vote. Based on the discussion so far, we may well be
able to hold a vote sooner.

I agree with the sentiment that some have expressed that the voting
period should be loudly announced. I also think that it should be at
least two weeks long.

> And I have to point out that right after asserting that Code4Lib "lacks a 
> mechanism for
> calling the question", Andromeda invoked a Code4Lib mechanism for calling the 
> question.

And I would like to emphasize that from my point of view, Code4Lib
already has a governance mechanism, or at least a decision mechanism,
and it's one that I think can suffice for the short- and medium-term.
We have used the Diebold-o-tron over the years to choose conference
hosts and local planning committees, thereby expressing trust that
each LPC would work to put on a good conference and responsibly use
any seed money that was passed on from the previous year.

It's not a far stretch to extend this sort of community vote to cover
the following questions:

* whether to incorporate, adopt a fiscal sponsor, or do nothing (and
in fact, I see no other way that this decision could be made by and on
behalf of the community)
* if need be, identifying and confirming people that the community
trusts to be point on incorporating and/or negotiating with potential
fiscal sponsors
* approving a MOU with a fiscal sponsor or bylaws in case we incorporate
* periodically choosing conference LPCs and/or named contacts with a
fiscal sponsor
* discussing and approving funding requests for Code4Lib activities
outside of the annual conference

In the long run, that sort of "committee-of-the-whole" — or at least
"commitee-of-those-who-care-to-vote" — decision-making may continue to
work well for us, or may need tweaking. In fact, I expect that there
will need to be tweaks and governance discussions (hopefully no more
painful than necessary). There's a difference between a group that has
no assets other than the time and energy that its members care to
spend on it, and a group that has collective control of a bank
account. Not accounting for and discussing that change would be a
mistake — governing ourselves takes work! and money complicates
matters! — but I also think that we don't need to figure out a whole
new governance structure all at once, though we may need to more fully
document how we currently make decisions.

[1] https://www.americanbar.org/publications/blt/2015/05/04_bradrick.html
[2] 
https://www.probonopartner.org/wp-content/uploads/2016/01/Fiscal-Sponsorships-11.09.pdf
[3] https://lists.clir.org/cgi-bin/wa?A2=CODE4LIB;7084ab47.1707
[4] https://lists.clir.org/cgi-bin/wa?A2=CODE4LIB;5632c274.1707

Regards,

Galen
-- 
Galen Charlton
Infrastructure and Added Services Manager
Equinox Open Library Initiative
phone:  1-877-OPEN-ILS (673-6457)
email:  g...@equinoxinitiative.org
web:  https://equinoxInitiative.org
direct: +1 770-709-5581
cell:   +1 404-984-4366


[CODE4LIB] Job: Sr. Software Engineer at Getty Research Institute

2017-07-25 Thread Code4Lib Jobs
Job Summary:

The Getty Research Institute is seeking a skilled and knowledgable full stack 
developer for a permanent, full-time position. This position will contribute to 
multiple projects that will provide our users with the ability to search, 
explore, analyze, share, and annotate the objects and information stored in our 
archival and special collections and art historical databases.

Reporting to the Software Development Team Lead, this position independently 
executes all software life cycle tasks, including process and requirements 
analysis, system design, programming, developing, implementing, testing, 
modifying, troubleshooting and maintaining software. Works on systems of large 
size and complexity.

Major Job Responsibilities:

Conceptualizes design, implements, and develops solutions for complex 
system/programs independently
Works with a variety of users to gain information, and develop intra-system 
tradeoffs between different users, as necessary; interacts with a diverse 
client base and outside vendor contacts
Documents system builds and application configurations; maintains and updates 
documentation as needed
Provides technical analysis, design, development, conversion, and 
implementation work
Works as a project leader, as needed, for projects of moderate complexity
Serves as a technical resource for applications
Compares, evaluates, and implements new features and technologies, and 
integrates them into the computing environment
Follows team software development methodology
Mentors lower level software developers

Qualifications:

Bachelor's degree in a related field or a combination of education and relevant 
experience
5-8 years software development experience

Knowledge, Skills and Abilities:

Expertise in JavaScript programming, libraries, and frameworks (jQuery, 
AngularJS, Vue)
Expertise in one or more OOP languages and server-side frameworks (Python, 
Django)
Demonstrated experience building highly interactive, image-intensive web 
applications, with foreign language script support
Expertise in designing, developing, testing, and deploying applications
Proficient with data modeling, database design and scalability
Proficient with Linux based operating systems (RHEL & Ubuntu)
Knowledge of information security concepts, techniques, and tools
Experience working with version control (Git) and issue tracking systems
Ability to define and solve logical problems for highly technical applications
Strong communication skills with both technical and non-technical clients
Ability to lead activities on structured team development projects
Ability to quickly learn and use new skills and tools

Bonus:

Demonstrated experience implementing IIIF or Open Annotation interfaces a plus
Demonstrated experience implementing GIS interfaces a plus
Familiarity with Linked Data concepts a plus



Brought to you by code4lib jobs: 
https://jobs.code4lib.org/jobs/27723-sr-software-engineer


[CODE4LIB] Update of FCIG report - new Appendix B regarding Educopia

2017-07-25 Thread Galen Charlton
Hi,

The FCIG's report has been updated to add an Appendix B summarizing
the results of our discussions with Educopia earlier this year.

The updated report is available in various formats:

* Wiki: https://wiki.code4lib.org/FCIG_Report
* PDF: https://wiki.code4lib.org/images/a/a0/Fcig_report.pdf
* Markdown: 
https://github.com/gmcharlt/code4lib-fcig/blob/master/Report_of_the_Code4Lib_Fiscal_Continuity_Interest_Group.md

Educopia's partnership program does not fit well with the sort of
fiscal sponsorship model that other organizations mentioned in the
report can offer. However, were Code4Lib to pursue establishing an
independent nonprofit organization, some of the services Educopia
offers with respect to helping to develop collaborative communities
may be of interest.

As mentioned in another thread, the FCIG expects to make more updates
to the report shortly to append up to two more proposals for other
organizations to act as a fiscal sponsor for Code4Lib.

Regards,

Galen
-- 
Galen Charlton
Infrastructure and Added Services Manager
Equinox Open Library Initiative
phone:  1-877-OPEN-ILS (673-6457)
email:  g...@equinoxinitiative.org
web:  https://equinoxInitiative.org
direct: +1 770-709-5581
cell:   +1 404-984-4366


[CODE4LIB] Early Bird Registration Ends Soon for Regular Expressions

2017-07-25 Thread Jodie Borgerding
Regular Expressions
August 21 & 23, 10 am - 12 pm (CDT)

This course is an introduction to managing and editing data by learning the 
syntax and construction of a regular expression, which is a sequence of 
characters that define a search (and sometimes replace) pattern. The basic 
characters used to construct a pattern will be discussed and then the patterns 
will be used in hands-on examples. Regular expressions are used in integrated 
library system search/replace reports, and some text editors (like Notepad++). 
Register today at https://www.amigos.org/node/4546. Early bird registration 
ends July 31.

View our entire training schedule at http://www.amigos.org/continuing_education.

Jodie



Jodie Borgerding
Consulting & Education Services Manager
Amigos Library Services
1190 Meramec Station Road, Suite 207 | Ballwin, MO  63021-6902
800-843-8482 x2897 | 972-340-2897(direct)
www.amigos.org | 
borgerd...@amigos.org
[facebook logo][twitter 
icon]

[cid:image001.png@01D2C964.EB2811B0]
Check out our member benefits