https://www.software.ac.uk/research-software-maintenance-fund/round-1

WHAT SSI IS LOOKING FOR

types of work funded could include

1. Technical (updates to code / software)
   a. Developing components / plugins / integrations to improve interoperability
   b. Improving user experience for end users
   c. Structural improvements to the codebase (refactoring / rearchitecting, scalability, porting, testing)
2. Community
   a. Community meetings and outreach to users
   b. Contribution process improvement (including Code of Conduct development)
   c. Sprints, hackathons
   3. Dissemination (including blog posts, case studies)
   a. Governance, strategy, roadmaps and work with advisors to improve sustainability / identify business models
3. Documentation (written material used as reference for users and/or developers)
   a. User manuals
   b. Contributor guides
   c. Project website
   d. Tutorials
4. Training
   a. Hosting in-person or virtual courses and workshops
   b. Mentoring new contributors to the project

requirements

Applicants must demonstrate that the software(s) they maintain:

• Is beyond the prototype / pilot stage and has had at least one stable release;
• Is used by people outside their organisation(s), and is used beyond the immediate collaborators of the software’s developers / wider project team;
• Supports research being carried out in the United Kingdom;
• Is open to feedback and additional contributors; and
• Is committed to developing a roadmap and sustainability / business plan.

Applications supporting multiple research software
projects are encouraged, as are applications that seek to
merge or bridge between similar software.

IDEAS

what about integrations for spatial across geo?

• sciverse/squidpy isaac virshup?
• jwst pointpats users?
• JupyterGIS integrations? ref

obvious connections

• pysal + geopandas for nx & geodata science
• climate impacts? rasterio connections/integration?

plotting

• not performant
• hacky
• not integrated across the interactive explore vs. plot
• cartography?

PySAL documentation

• moving everybody to a consistent framework
• integrated geopandas + pysal

finalizing the movement onto "Graph"

• esda, needs movement anyway
• spreg, luc send serge a detailed draft of the graph engine

postgis/sql integrations

improving capacity for triage and bug addressing

RSOM/pandana integration w/ geopandas?

plan

Levi to draft an outline plan for:

1. renovating/improving UX around plotting/cartography; a little bit of each:
   • stats w/ pysal projects (mapclassify, esda)
   • integration w/ cartopy,
   • smarter use of matplotlib
   • extension to .explore()
2. community manager to handle geopandas triage
3. user studies
   • concrete end-to-end examples of geopandas integrating into a workflow for clients or users.
   • should ideally demonstrate using geopandas w/ multiple packages to accomplish a task (not "just" a GIS read-buffer-join-write flow)
   • python for urban informatics examples (ideally to integrate some of the existing popular packages such as momepy, osmnx, etc.)

Martin to clear 20% overheads limit on international coi

Qunshan to check w/ his research dept about previous applications to schemes like this

buyouts

20% Martin
20-40% Levi
50%-100% of the PDRA for 1.5 years or 2 years. Depending on the budget number.
Roughly 130k in total for one year of G7 PDRA in Glasgow (including everything).
For community building and training, we can budget some time for our data science team to cover. That's much cheaper, 54k in total for 1FTE.
10% for Qunshan