Last active
March 24, 2021 15:42
-
-
Save hobu/8bdca018fe0ada0660ea3562813e46d5 to your computer and use it in GitHub Desktop.
faq.md
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
# Why is GDAL raising money? | |
GDAL is not hobby software. It is a critical piece of data management and | |
processing infrastructure for open source, commercial, and government geospatial software. | |
GDAL's primary maintainer can no longer sustain supporting | |
maintenance of the project and its core dependencies (PROJ, libgeotiff, etc) as | |
part of taking small jobs adding new features to the software. | |
The purpose of raising the money is to provide some substantial long-acting resources | |
that give the project the ability to address software, testing, and project | |
challenges that do not attract individual sponsorship attention. With | |
a pool of resources that are not earmarked for features, it can | |
attack usability, performance, and modernization challenges that benefit everyone. | |
The effort provides at least three years at the proposed level, | |
which will give the project time to stage multi-year efforts that do not | |
disrupted the existing GDAL user base, and it will provide the baseline | |
resources to allow day-to-day maintenance operations to continue uninterrupted. | |
# That's a lot of money. Why so much? | |
Maintenance and development of GDAL requires extensive software engineering and | |
domain experience. Capable software engineers who can operate in public are also | |
a limited resource. The resources provided by this effort will allow maintenance activities to continue | |
*and* allow the project to support on boarding additional | |
developers to tackle various needs of the project that have been ignored due to | |
lack of direct funding interest. | |
# Why didn't you ask my organization? | |
We just haven't gotten to you yet :) | |
# My organization wants to sponsor. How can we do that? | |
FIXME | |
# What is NumFOCUS and why is the project using that foundation rather than using OSGeo for this effort? | |
NumFOCUS is a US-based 501(c)(3) tax-exempt non-profit that is already managing | |
funding for many individual software projects using this model such as Numpy, | |
Jupyter, pandas, Julia, and SciPy. They have staff, policies, procedures, and | |
infrastructure for managing the financial support of open source software | |
projects with this funding model. Many organizations in the initial list of | |
sponsors are already funding projects through NumFOCUS, and adding GDAL to the | |
roster improves efficiency on their side. | |
OSGeo does not have staff and procedures to manage tracking workloads and | |
payments. OSGeo also does not provide tax-exempt status for contributions. | |
NumFOCUS has established relationships with a large number of the initial | |
sponsors. These properties are why the GDAL PSC has chosen the NumFOCUS path | |
for management of this effort. | |
# So GDAL is a NumFOCUS project now? | |
Not exactly. GDAL will be a project within NumFOCUS under the "Grantor-Grantee Model". | |
OSGeo is still the primary foundational "home" of GDAL such as it is, but NumFOCUS | |
is providing this financial vehicle and service to the project under the purview of | |
its charter. | |
# What is the project going to do with the money? | |
* The GDAL PSC will control the purse strings. Contributors seeking resources | |
will submit a proposal to the PSC (RFC-style, but not public) describing the | |
tasks and efforts they will seek to achieve. Any substantial efforts with | |
external impacts will continue to be required to use the GDAL RFC process as | |
described in RFC FIXME. | |
* Developers will be able submit requests to the GDAL PSC for 'maintenance | |
work units', which could encompass ticket i/o and related code improvements, | |
CI grooming, mailing list gardening, and fuzzing response activities. | |
* A significant portion (25% per year if possible) of the resources will be targeted toward | |
*growing* new active developers into the project. Examples of this include | |
soliciting ticket and code contributors with funding if they show interest | |
and aptitude, and providing resources to mentor and support junior developers who are | |
working into roles in the project. These activities are | |
extremely hard to do without financial support. | |
* Spot resources will be available to attack needs that have difficulty finding | |
funded attention, such as API improvements in support of specific application | |
niches and subsystem refreshes like build, tests, and CI. The GDAL PSC could | |
fund significant RFCs that demonstrate need and agreement on an ad hoc basis. | |
* The GDAL PSC will delegate some resources to GDAL-related projects and | |
dependencies – libtiff, libgeotiff, PROJ, shapelib, and the various language | |
bindings and libraries. If more resources than the GDAL project itself can | |
use are available for a particular year, the project will open them up to the | |
wider community of related libraries and users to repurpose them. | |
# How can the resources be used? | |
The funds cannot be used benefit an individual contributor or be directed by a | |
contributor through the non-profit organization. For example, a fictional | |
Imagery Corp cannot fund NumFOCUS with explicit intent to have those resources | |
used to fix bugs or add features that benefit Imagery Corp. Imagery Corp can | |
still continue to solicit GDAL active contributors, or actively contribute the | |
fixes themselves, to achieve their goals with the software. | |
# How is this going to impact GDAL software releases? | |
A primary goal of this effort is to provide resources needed to allow the current | |
GDAL maintainer to | |
keep up the existing release schedule and cadence. Without these resources, the | |
schedule was likely to have significantly stretched out to one or two | |
maintenance releases per year. | |
# Can I use some of the funding to support fixing something? | |
Quite possibly. The GDAL PSC will provide a proposal template where you will | |
need to describe the issue(s), propose the approach and impacts of it, and | |
state your cost to complete the effort. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment