librariesio / supporters

🙇 Details of our supporters and our commitments to them

Supporters 📚

Libraries.io is a project of Brave New Software. The project is supported by the following organisations until 1st January 2018:

• Brave New Software
• The Alfred P. Sloan Foundation
• The Ford Foundation

This repository contains the details of our contractual obligations to our fiscal sponsor Brave New Software and any commitments we have made in exchange for financial support. This respository also contains any successful application for financial support in full.

Aim

Our aim here are simple. Complete transparency and accountabilty of our actions on behalf of our community, by the community.

On Financial Support

We acknowledge that is it very difficult to accept financial support for a project without influencing its direction. We have taken great care to ensure that our supporters share our values, are aligned with our strategy and happy to support our work. That said we must accept that in order to work full-time on Libraires.io there must be a degree of compromise with regard to establishing and meeting shared goals in exchange for financial support.

Commitments

Any commitment we have made to a supporter will be ticketed in this repository. Any tickets upon which a commitment depends will be referenced bilaterally from this repository.

Contributing

Please feel free to comment upon, take issue at or otherwise hold the project, our obligations and our interpretation of those obligations to account using comments.

supporters's Issues

"Add API and bulk data download options"

See librariesio/libraries.io#197 concerning API endpoints and
librariesio/libraries.io#198 regarding documentation.

Establish board of governance or advisor board

Appoint a board of governance up to five members or advisory board of at least five members

• create long list of potential advisors
• create invitation pack (letter, mission, values, strategy, commitments, challenges)
• send invitation pack to long list
• create advisors team and add members
• publish advisors on libraries.io

Increase contributions to Libraries.io

Increase in contributors to the libraries.io codebases validated through an increase in code contributions, bug reports and feature requests.

Create a libraries.io blog?

Hey all, I see things like this:

https://twitter.com/teabass/status/841350906155266050
https://twitter.com/teabass/status/842149968794259457

and I'm really interested in knowing more about these kind of events and how people are using libraries.io - IMO they'd make great blog posts

In CocoaPods we do aim to do blog posts for major events, meetups and major releases (basically anything non-transitory) - it might do y'all well to have something similar

Reimplement support for Meteor

Currently implementation uses https://atmospherejs.com's json API (which has now been removed 'due to poor performance').

Would also be nice if it inc. dependencies...

Incorporate libraries.io data into at least two other projects in scientific software assesment

Special mention here to http://depsy.org/ who are doing the necessary work to scrape references of software in scientific papers. With libraries.io data we could trace the value (if citation is considered a currency in academia) of individual libraries to others an therefore the value provided by the institution that produced it. Also worth mentioning the three Moore-Sloan DSE http://msdse.org/ partners.

Increase use of Libraries.io

Increase usage to

• 20k registered users,
• 8k monitored repositories,
• 40m req/month

Add support for GitLab and BitBucket users

To add support for users of GitLab and BitBucket to

• use their accounts on these services to authenticate on libraries.io
• view, monitor and otherwise interact with repositories hosted on GitLab or BitBucket.

Development and initial implementation of a robust sustainability plan

In order to create unrestricted, influence-free financial support to cover both the core team and incidental expenses.

• scope out all available avenues
• discount those that are against values
• discount those that are at odds with strategy
• pursue those that remain

Release dependency graph and metric data under a permissive licence.

Specifically one which can be used by the scientific and research communities.

• define requirements for a licence
• explore available licences
• decide on a licence
• decide on formats
• register doi https://www.crossref.org/services/content-registration/
• release data

Achieve parity across supported package managers

To add, to the extent possible, any metric gathered for any one package manage to any other package manager supported by libraries.io.

Substantial growth in usage from .edu domains

• establish baseline figure (pref from Sept/Nov '16)
• add notice to privacy statement (if needed)
• enable domain-based tracking

Indications of demand from research community

Represented by new research and tool-development collaborations in 2017. Again no firm success measure here, to be established.

Establish a 'baseline' of metrics to measure impact on FOSS projects

The primary outcome of this support is to establish a baseline of metrics for all projects monitored by Libraries.io, in order to demonstrate the impact of work under this grant [and] the wider community.

The baseline data will surface through the interface, for individual users and organisations to utilise directly on the libraries.io website and through the API.

Add details of fiscal sponsor

Should include at least a copy of the agreement we have signed with Brave New Software.

Add details of Alfred P. Sloan Foundation

Should contain

• successful application for financial support
• subsequent agreement between Alfred P. Sloan Foundation and Brave New Software
• announcement
• tickets for commitments to Alfred P. Sloan Foundation

Outreach through presentations to scientific software communities

present our work at a minimum of four events with community, academic, research and industry audiences

Event's We're Speaking at in 2017

Event	Location	When
TICTec	Florence, ITA	Apr
Brighton Ruby	Brighton, UK	July

Event's We're Attending in 2017

Event	Location	When
FOSDEM	Brussels, BEL	Feb
Maintainerati	London, UK	May
$ustain	San Francisco, CA	Jun
Mozilla Festival	London, UK	Oct

Events We're Considering in 2017

Event	Location	When
Collaborations Workshop	Leeds, UK	Mar
FLOSS Spring	Manchester, UK	Mar
CSV Conf	Portland, OR	May
PyCon	Portland, OR	May
Mining Software Repositories	Buenos Aires, AR	May
GitHub Satellite	London, UK	May
JuliaConf	Berkeley, CA	Jun
SPA Conf	London, UK	Jun
GraphDay	SFO, CA	Jun
Open Source Bridge	Portland, OR	Jun
PolyConf	Paris, FR	July
DebCon	Montreal, CA	Aug
All Things Open	Raleigh, NC	Oct
OSCON Europe	London, UK	Oct
Open Source Summit EU	Prague, CZ	Oct
FORCE11	Munich, Ger	Oct
Moore-Sloan DSE Summit	TBC	Oct
WSSEPE5	TBC	TBC
SciPy	TBC	TBC

Events We're Considering in 2018

Event	Location	When
FOSDEM	Brussels, BEL	Feb
Isle of Ruby	Devon, UK	Spring

Add details for Ford Foundation

Should contain

• successful application for financial support
• announcement
• subsequent agreement between Ford Foundation and Brave New Software
• tickets for commitments to Ford Foundation

Formalise at least two working relationships

Formalise at least two working relationships with significant institutions currently working on identifying or supporting our digital infrastructure.

Increase number of libraries monitored by libraries.io to 4m

At the current, organic rate of 5k projects/day we should reach this goal.

Add README.md

Should set out

• Who we are
• Why this repository exists
• How we're going to use this repository
• How to contribute