/
nep-0048-spending-project-funds.html
1020 lines (838 loc) · 60.9 KB
/
nep-0048-spending-project-funds.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
<!DOCTYPE html>
<html lang="en" data-content_root="./" >
<head>
<meta charset="utf-8" />
<meta name="viewport" content="width=device-width, initial-scale=1.0" /><meta name="viewport" content="width=device-width, initial-scale=1" />
<title>NEP 48 — Spending NumPy project funds — NumPy Enhancement Proposals</title>
<script data-cfasync="false">
document.documentElement.dataset.mode = localStorage.getItem("mode") || "";
document.documentElement.dataset.theme = localStorage.getItem("theme") || "light";
</script>
<!-- Loaded before other Sphinx assets -->
<link href="_static/styles/theme.css?digest=8d27b9dea8ad943066ae" rel="stylesheet" />
<link href="_static/styles/bootstrap.css?digest=8d27b9dea8ad943066ae" rel="stylesheet" />
<link href="_static/styles/pydata-sphinx-theme.css?digest=8d27b9dea8ad943066ae" rel="stylesheet" />
<link href="_static/vendor/fontawesome/6.5.1/css/all.min.css?digest=8d27b9dea8ad943066ae" rel="stylesheet" />
<link rel="preload" as="font" type="font/woff2" crossorigin href="_static/vendor/fontawesome/6.5.1/webfonts/fa-solid-900.woff2" />
<link rel="preload" as="font" type="font/woff2" crossorigin href="_static/vendor/fontawesome/6.5.1/webfonts/fa-brands-400.woff2" />
<link rel="preload" as="font" type="font/woff2" crossorigin href="_static/vendor/fontawesome/6.5.1/webfonts/fa-regular-400.woff2" />
<link rel="stylesheet" type="text/css" href="_static/pygments.css?v=fa44fd50" />
<!-- Pre-loaded scripts that we'll load fully later -->
<link rel="preload" as="script" href="_static/scripts/bootstrap.js?digest=8d27b9dea8ad943066ae" />
<link rel="preload" as="script" href="_static/scripts/pydata-sphinx-theme.js?digest=8d27b9dea8ad943066ae" />
<script src="_static/vendor/fontawesome/6.5.1/js/all.min.js?digest=8d27b9dea8ad943066ae"></script>
<script src="_static/documentation_options.js?v=7f41d439"></script>
<script src="_static/doctools.js?v=888ff710"></script>
<script src="_static/sphinx_highlight.js?v=dc90522c"></script>
<script>DOCUMENTATION_OPTIONS.pagename = 'nep-0048-spending-project-funds';</script>
<link rel="icon" href="_static/favicon.ico"/>
<link rel="index" title="Index" href="genindex.html" />
<link rel="search" title="Search" href="search.html" />
<link rel="next" title="NEP X — Template and instructions" href="nep-template.html" />
<link rel="prev" title="NEP 46 — NumPy sponsorship guidelines" href="nep-0046-sponsorship-guidelines.html" />
<meta name="viewport" content="width=device-width, initial-scale=1"/>
<meta name="docsearch:language" content="en"/>
<meta name="docbuild:last-update" content="May 24, 2024"/>
</head>
<body data-bs-spy="scroll" data-bs-target=".bd-toc-nav" data-offset="180" data-bs-root-margin="0px 0px -60%" data-default-mode="">
<a id="pst-skip-link" class="skip-link" href="#main-content">Skip to main content</a>
<div id="pst-scroll-pixel-helper"></div>
<button type="button" class="btn rounded-pill" id="pst-back-to-top">
<i class="fa-solid fa-arrow-up"></i>
Back to top
</button>
<input type="checkbox"
class="sidebar-toggle"
name="__primary"
id="__primary"/>
<label class="overlay overlay-primary" for="__primary"></label>
<input type="checkbox"
class="sidebar-toggle"
name="__secondary"
id="__secondary"/>
<label class="overlay overlay-secondary" for="__secondary"></label>
<div class="search-button__wrapper">
<div class="search-button__overlay"></div>
<div class="search-button__search-container">
<form class="bd-search d-flex align-items-center"
action="search.html"
method="get">
<i class="fa-solid fa-magnifying-glass"></i>
<input type="search"
class="form-control"
name="q"
id="search-input"
placeholder="Search the docs ..."
aria-label="Search the docs ..."
autocomplete="off"
autocorrect="off"
autocapitalize="off"
spellcheck="false"/>
<span class="search-button__kbd-shortcut"><kbd class="kbd-shortcut__modifier">Ctrl</kbd>+<kbd>K</kbd></span>
</form></div>
</div>
<header class="bd-header navbar navbar-expand-lg bd-navbar">
<div class="bd-header__inner bd-page-width">
<label class="sidebar-toggle primary-toggle" for="__primary">
<span class="fa-solid fa-bars"></span>
</label>
<div class="col-lg-3 navbar-header-items__start">
<div class="navbar-item">
<a class="navbar-brand logo" href="content.html">
<img src="_static/numpylogo.svg" class="logo__image only-light" alt="NumPy Enhancement Proposals - Home"/>
<script>document.write(`<img src="_static/numpylogo.svg" class="logo__image only-dark" alt="NumPy Enhancement Proposals - Home"/>`);</script>
</a></div>
</div>
<div class="col-lg-9 navbar-header-items">
<div class="me-auto navbar-header-items__center">
<div class="navbar-item">
<nav class="navbar-nav">
<ul class="bd-navbar-elements navbar-nav">
<li class="nav-item current active">
<a class="nav-link nav-internal" href="index.html">
Index
</a>
</li>
<li class="nav-item">
<a class="nav-link nav-internal" href="scope.html">
The Scope of NumPy
</a>
</li>
<li class="nav-item">
<a class="nav-link nav-internal" href="roadmap.html">
Current roadmap
</a>
</li>
<li class="nav-item">
<a class="nav-link nav-external" href="https://github.com/numpy/numpy/issues?q=is%3Aopen+is%3Aissue+label%3A%2223+-+Wish+List%22">
Wishlist
</a>
</li>
</ul>
</nav></div>
</div>
<div class="navbar-header-items__end">
<div class="navbar-item navbar-persistent--container">
<script>
document.write(`
<button class="btn navbar-btn search-button-field search-button__button" title="Search" aria-label="Search" data-bs-placement="bottom" data-bs-toggle="tooltip">
<i class="fa-solid fa-magnifying-glass"></i>
<span class="search-button__default-text">Search</span>
<span class="search-button__kbd-shortcut"><kbd class="kbd-shortcut__modifier">Ctrl</kbd>+<kbd class="kbd-shortcut__modifier">K</kbd></span>
</button>
`);
</script>
</div>
<div class="navbar-item">
<script>
document.write(`
<button class="btn btn-sm navbar-btn theme-switch-button" title="light/dark" aria-label="light/dark" data-bs-placement="bottom" data-bs-toggle="tooltip">
<span class="theme-switch nav-link" data-mode="light"><i class="fa-solid fa-sun fa-lg"></i></span>
<span class="theme-switch nav-link" data-mode="dark"><i class="fa-solid fa-moon fa-lg"></i></span>
<span class="theme-switch nav-link" data-mode="auto"><i class="fa-solid fa-circle-half-stroke fa-lg"></i></span>
</button>
`);
</script></div>
<div class="navbar-item"><ul class="navbar-icon-links navbar-nav"
aria-label="Icon Links">
<li class="nav-item">
<a href="https://github.com/numpy/numpy" title="GitHub" class="nav-link" rel="noopener" target="_blank" data-bs-toggle="tooltip" data-bs-placement="bottom"><span><i class="fa-brands fa-square-github fa-lg" aria-hidden="true"></i></span>
<span class="sr-only">GitHub</span></a>
</li>
</ul></div>
</div>
</div>
<div class="navbar-persistent--mobile">
<script>
document.write(`
<button class="btn navbar-btn search-button-field search-button__button" title="Search" aria-label="Search" data-bs-placement="bottom" data-bs-toggle="tooltip">
<i class="fa-solid fa-magnifying-glass"></i>
<span class="search-button__default-text">Search</span>
<span class="search-button__kbd-shortcut"><kbd class="kbd-shortcut__modifier">Ctrl</kbd>+<kbd class="kbd-shortcut__modifier">K</kbd></span>
</button>
`);
</script>
</div>
<label class="sidebar-toggle secondary-toggle" for="__secondary" tabindex="0">
<span class="fa-solid fa-outdent"></span>
</label>
</div>
</header>
<div class="bd-container">
<div class="bd-container__inner bd-page-width">
<div class="bd-sidebar-primary bd-sidebar">
<div class="sidebar-header-items sidebar-primary__section">
<div class="sidebar-header-items__center">
<div class="navbar-item">
<nav class="navbar-nav">
<ul class="bd-navbar-elements navbar-nav">
<li class="nav-item current active">
<a class="nav-link nav-internal" href="index.html">
Index
</a>
</li>
<li class="nav-item">
<a class="nav-link nav-internal" href="scope.html">
The Scope of NumPy
</a>
</li>
<li class="nav-item">
<a class="nav-link nav-internal" href="roadmap.html">
Current roadmap
</a>
</li>
<li class="nav-item">
<a class="nav-link nav-external" href="https://github.com/numpy/numpy/issues?q=is%3Aopen+is%3Aissue+label%3A%2223+-+Wish+List%22">
Wishlist
</a>
</li>
</ul>
</nav></div>
</div>
<div class="sidebar-header-items__end">
<div class="navbar-item">
<script>
document.write(`
<button class="btn btn-sm navbar-btn theme-switch-button" title="light/dark" aria-label="light/dark" data-bs-placement="bottom" data-bs-toggle="tooltip">
<span class="theme-switch nav-link" data-mode="light"><i class="fa-solid fa-sun fa-lg"></i></span>
<span class="theme-switch nav-link" data-mode="dark"><i class="fa-solid fa-moon fa-lg"></i></span>
<span class="theme-switch nav-link" data-mode="auto"><i class="fa-solid fa-circle-half-stroke fa-lg"></i></span>
</button>
`);
</script></div>
<div class="navbar-item"><ul class="navbar-icon-links navbar-nav"
aria-label="Icon Links">
<li class="nav-item">
<a href="https://github.com/numpy/numpy" title="GitHub" class="nav-link" rel="noopener" target="_blank" data-bs-toggle="tooltip" data-bs-placement="bottom"><span><i class="fa-brands fa-square-github fa-lg" aria-hidden="true"></i></span>
<span class="sr-only">GitHub</span></a>
</li>
</ul></div>
</div>
</div>
<div class="sidebar-primary-items__start sidebar-primary__section">
<div class="sidebar-primary-item">
<nav class="bd-docs-nav bd-links"
aria-label="Section Navigation">
<p class="bd-links__title" role="heading" aria-level="1">Section Navigation</p>
<div class="bd-toc-item navbar-nav"><ul class="nav bd-sidenav">
<li class="toctree-l1"><a class="reference internal" href="scope.html">The Scope of NumPy</a></li>
<li class="toctree-l1"><a class="reference internal" href="roadmap.html">Current roadmap</a></li>
<li class="toctree-l1"><a class="reference external" href="https://github.com/numpy/numpy/issues?q=is%3Aopen+is%3Aissue+label%3A%2223+-+Wish+List%22">Wish list</a></li>
</ul>
<ul class="current nav bd-sidenav">
<li class="toctree-l1 current active has-children"><a class="reference internal" href="meta.html">Meta-NEPs (NEPs about NEPs or active Processes)</a><input checked="" class="toctree-checkbox" id="toctree-checkbox-1" name="toctree-checkbox-1" type="checkbox"/><label class="toctree-toggle" for="toctree-checkbox-1"><i class="fa-solid fa-chevron-down"></i></label><ul class="current">
<li class="toctree-l2"><a class="reference internal" href="nep-0000.html">NEP 0 — Purpose and process</a></li>
<li class="toctree-l2"><a class="reference internal" href="nep-0023-backwards-compatibility.html">NEP 23 — Backwards compatibility and deprecation policy</a></li>
<li class="toctree-l2"><a class="reference internal" href="nep-0036-fair-play.html">NEP 36 — Fair play</a></li>
<li class="toctree-l2"><a class="reference internal" href="nep-0045-c_style_guide.html">NEP 45 — C style guide</a></li>
<li class="toctree-l2"><a class="reference internal" href="nep-0046-sponsorship-guidelines.html">NEP 46 — NumPy sponsorship guidelines</a></li>
<li class="toctree-l2 current active"><a class="current reference internal" href="#">NEP 48 — Spending NumPy project funds</a></li>
<li class="toctree-l2"><a class="reference internal" href="nep-template.html">NEP X — Template and instructions</a></li>
</ul>
</li>
<li class="toctree-l1 has-children"><a class="reference internal" href="provisional.html">Provisional NEPs (provisionally accepted; interface may change)</a><input class="toctree-checkbox" id="toctree-checkbox-2" name="toctree-checkbox-2" type="checkbox"/><label class="toctree-toggle" for="toctree-checkbox-2"><i class="fa-solid fa-chevron-down"></i></label><ul class="simple">
</ul>
</li>
<li class="toctree-l1 has-children"><a class="reference internal" href="accepted.html">Accepted NEPs (implementation in progress)</a><input class="toctree-checkbox" id="toctree-checkbox-3" name="toctree-checkbox-3" type="checkbox"/><label class="toctree-toggle" for="toctree-checkbox-3"><i class="fa-solid fa-chevron-down"></i></label><ul>
<li class="toctree-l2"><a class="reference internal" href="nep-0041-improved-dtype-support.html">NEP 41 — First step towards a new datatype system</a></li>
<li class="toctree-l2"><a class="reference internal" href="nep-0042-new-dtypes.html">NEP 42 — New and extensible DTypes</a></li>
<li class="toctree-l2"><a class="reference internal" href="nep-0044-restructuring-numpy-docs.html">NEP 44 — Restructuring the NumPy documentation</a></li>
<li class="toctree-l2"><a class="reference internal" href="nep-0051-scalar-representation.html">NEP 51 — Changing the representation of NumPy scalars</a></li>
<li class="toctree-l2"><a class="reference internal" href="nep-0052-python-api-cleanup.html">NEP 52 — Python API cleanup for NumPy 2.0</a></li>
</ul>
</li>
<li class="toctree-l1 has-children"><a class="reference internal" href="open.html">Open NEPs (under consideration)</a><input class="toctree-checkbox" id="toctree-checkbox-4" name="toctree-checkbox-4" type="checkbox"/><label class="toctree-toggle" for="toctree-checkbox-4"><i class="fa-solid fa-chevron-down"></i></label><ul>
<li class="toctree-l2"><a class="reference internal" href="nep-0043-extensible-ufuncs.html">NEP 43 — Enhancing the extensibility of UFuncs</a></li>
<li class="toctree-l2"><a class="reference internal" href="nep-0050-scalar-promotion.html">NEP 50 — Promotion rules for Python scalars</a></li>
<li class="toctree-l2"><a class="reference internal" href="nep-0053-c-abi-evolution.html">NEP 53 — Evolving the NumPy C-API for NumPy 2.0</a></li>
<li class="toctree-l2"><a class="reference internal" href="nep-0054-simd-cpp-highway.html">NEP 54 — SIMD infrastructure evolution: adopting Google Highway when moving to C++?</a></li>
</ul>
</li>
<li class="toctree-l1 has-children"><a class="reference internal" href="finished.html">Finished NEPs</a><input class="toctree-checkbox" id="toctree-checkbox-5" name="toctree-checkbox-5" type="checkbox"/><label class="toctree-toggle" for="toctree-checkbox-5"><i class="fa-solid fa-chevron-down"></i></label><ul>
<li class="toctree-l2"><a class="reference internal" href="nep-0001-npy-format.html">NEP 1 — A simple file format for NumPy arrays</a></li>
<li class="toctree-l2"><a class="reference internal" href="nep-0005-generalized-ufuncs.html">NEP 5 — Generalized universal functions</a></li>
<li class="toctree-l2"><a class="reference internal" href="nep-0007-datetime-proposal.html">NEP 7 — A proposal for implementing some date/time types in NumPy</a></li>
<li class="toctree-l2"><a class="reference internal" href="nep-0010-new-iterator-ufunc.html">NEP 10 — Optimizing iterator/UFunc performance</a></li>
<li class="toctree-l2"><a class="reference internal" href="nep-0013-ufunc-overrides.html">NEP 13 — A mechanism for overriding Ufuncs</a></li>
<li class="toctree-l2"><a class="reference internal" href="nep-0014-dropping-python2.7-proposal.html">NEP 14 — Plan for dropping Python 2.7 support</a></li>
<li class="toctree-l2"><a class="reference internal" href="nep-0015-merge-multiarray-umath.html">NEP 15 — Merging multiarray and umath</a></li>
<li class="toctree-l2"><a class="reference internal" href="nep-0018-array-function-protocol.html">NEP 18 — A dispatch mechanism for NumPy's high level array functions</a></li>
<li class="toctree-l2"><a class="reference internal" href="nep-0019-rng-policy.html">NEP 19 — Random number generator policy</a></li>
<li class="toctree-l2"><a class="reference internal" href="nep-0020-gufunc-signature-enhancement.html">NEP 20 — Expansion of generalized universal function signatures</a></li>
<li class="toctree-l2"><a class="reference internal" href="nep-0022-ndarray-duck-typing-overview.html">NEP 22 — Duck typing for NumPy arrays – high level overview</a></li>
<li class="toctree-l2"><a class="reference internal" href="nep-0027-zero-rank-arrarys.html">NEP 27 — Zero rank arrays</a></li>
<li class="toctree-l2"><a class="reference internal" href="nep-0028-website-redesign.html">NEP 28 — numpy.org website redesign</a></li>
<li class="toctree-l2"><a class="reference internal" href="nep-0029-deprecation_policy.html">NEP 29 — Recommend Python and NumPy version support as a community policy standard</a></li>
<li class="toctree-l2"><a class="reference internal" href="nep-0032-remove-financial-functions.html">NEP 32 — Remove the financial functions from NumPy</a></li>
<li class="toctree-l2"><a class="reference internal" href="nep-0034-infer-dtype-is-object.html">NEP 34 — Disallow inferring ``dtype=object`` from sequences</a></li>
<li class="toctree-l2"><a class="reference internal" href="nep-0035-array-creation-dispatch-with-array-function.html">NEP 35 — Array creation dispatching with __array_function__</a></li>
<li class="toctree-l2"><a class="reference internal" href="nep-0038-SIMD-optimizations.html">NEP 38 — Using SIMD optimization instructions for performance</a></li>
<li class="toctree-l2"><a class="reference internal" href="nep-0040-legacy-datatype-impl.html">NEP 40 — Legacy datatype implementation in NumPy</a></li>
<li class="toctree-l2"><a class="reference internal" href="nep-0049.html">NEP 49 — Data allocation strategies</a></li>
<li class="toctree-l2"><a class="reference internal" href="nep-0055-string_dtype.html">NEP 55 — Add a UTF-8 variable-width string DType to NumPy</a></li>
<li class="toctree-l2"><a class="reference internal" href="nep-0056-array-api-main-namespace.html">NEP 56 — Array API standard support in NumPy's main namespace</a></li>
</ul>
</li>
<li class="toctree-l1 has-children"><a class="reference internal" href="deferred.html">Deferred and Superseded NEPs</a><input class="toctree-checkbox" id="toctree-checkbox-6" name="toctree-checkbox-6" type="checkbox"/><label class="toctree-toggle" for="toctree-checkbox-6"><i class="fa-solid fa-chevron-down"></i></label><ul>
<li class="toctree-l2"><a class="reference internal" href="nep-0002-warnfix.html">NEP 2 — A proposal to build numpy without warning with a big set of warning flags</a></li>
<li class="toctree-l2"><a class="reference internal" href="nep-0003-math_config_clean.html">NEP 3 — Cleaning the math configuration of numpy.core</a></li>
<li class="toctree-l2"><a class="reference internal" href="nep-0004-datetime-proposal3.html">NEP 4 — A (third) proposal for implementing some date/time types in NumPy</a></li>
<li class="toctree-l2"><a class="reference internal" href="nep-0006-newbugtracker.html">NEP 6 — Replacing Trac with a different bug tracker</a></li>
<li class="toctree-l2"><a class="reference internal" href="nep-0008-groupby_additions.html">NEP 8 — A proposal for adding groupby functionality to NumPy</a></li>
<li class="toctree-l2"><a class="reference internal" href="nep-0009-structured_array_extensions.html">NEP 9 — Structured array extensions</a></li>
<li class="toctree-l2"><a class="reference internal" href="nep-0011-deferred-ufunc-evaluation.html">NEP 11 — Deferred UFunc evaluation</a></li>
<li class="toctree-l2"><a class="reference internal" href="nep-0012-missing-data.html">NEP 12 — Missing data functionality in NumPy</a></li>
<li class="toctree-l2"><a class="reference internal" href="nep-0021-advanced-indexing.html">NEP 21 — Simplified and explicit advanced indexing</a></li>
<li class="toctree-l2"><a class="reference internal" href="nep-0024-missing-data-2.html">NEP 24 — Missing data functionality - alternative 1 to NEP 12</a></li>
<li class="toctree-l2"><a class="reference internal" href="nep-0025-missing-data-3.html">NEP 25 — NA support via special dtypes</a></li>
<li class="toctree-l2"><a class="reference internal" href="nep-0026-missing-data-summary.html">NEP 26 — Summary of missing data NEPs and discussion</a></li>
<li class="toctree-l2"><a class="reference internal" href="nep-0030-duck-array-protocol.html">NEP 30 — Duck typing for NumPy arrays - implementation</a></li>
<li class="toctree-l2"><a class="reference internal" href="nep-0031-uarray.html">NEP 31 — Context-local and global overrides of the NumPy API</a></li>
<li class="toctree-l2"><a class="reference internal" href="nep-0037-array-module.html">NEP 37 — A dispatch protocol for NumPy-like modules</a></li>
<li class="toctree-l2"><a class="reference internal" href="nep-0047-array-api-standard.html">NEP 47 — Adopting the array API standard</a></li>
</ul>
</li>
<li class="toctree-l1 has-children"><a class="reference internal" href="rejected.html">Rejected and Withdrawn NEPs</a><input class="toctree-checkbox" id="toctree-checkbox-7" name="toctree-checkbox-7" type="checkbox"/><label class="toctree-toggle" for="toctree-checkbox-7"><i class="fa-solid fa-chevron-down"></i></label><ul>
<li class="toctree-l2"><a class="reference internal" href="nep-0016-abstract-array.html">NEP 16 — An abstract base class for identifying "duck arrays"</a></li>
<li class="toctree-l2"><a class="reference internal" href="nep-0017-split-out-maskedarray.html">NEP 17 — Split out masked arrays</a></li>
</ul>
</li>
</ul>
</div>
</nav></div>
</div>
<div class="sidebar-primary-items__end sidebar-primary__section">
</div>
<div id="rtd-footer-container"></div>
</div>
<main id="main-content" class="bd-main">
<div class="bd-content">
<div class="bd-article-container">
<div class="bd-header-article">
<div class="header-article-items header-article__inner">
<div class="header-article-items__start">
<div class="header-article-item">
<nav aria-label="Breadcrumb">
<ul class="bd-breadcrumbs">
<li class="breadcrumb-item breadcrumb-home">
<a href="content.html" class="nav-link" aria-label="Home">
<i class="fa-solid fa-home"></i>
</a>
</li>
<li class="breadcrumb-item"><a href="index.html" class="nav-link">Roadmap & NumPy enhancement proposals</a></li>
<li class="breadcrumb-item"><a href="meta.html" class="nav-link">Meta-NEPs (NEPs about NEPs or active Processes)</a></li>
<li class="breadcrumb-item active" aria-current="page">NEP 48 —...</li>
</ul>
</nav>
</div>
</div>
</div>
</div>
<div id="searchbox"></div>
<article class="bd-article">
<section id="nep-48-spending-numpy-project-funds">
<span id="nep48"></span><h1>NEP 48 — Spending NumPy project funds<a class="headerlink" href="#nep-48-spending-numpy-project-funds" title="Link to this heading">#</a></h1>
<dl class="field-list simple">
<dt class="field-odd">Author<span class="colon">:</span></dt>
<dd class="field-odd"><p>Ralf Gommers <<a class="reference external" href="mailto:ralf.gommers%40gmail.com">ralf<span>.</span>gommers<span>@</span>gmail<span>.</span>com</a>></p>
</dd>
<dt class="field-even">Author<span class="colon">:</span></dt>
<dd class="field-even"><p>Inessa Pawson <<a class="reference external" href="mailto:inessa%40albuscode.org">inessa<span>@</span>albuscode<span>.</span>org</a>></p>
</dd>
<dt class="field-odd">Author<span class="colon">:</span></dt>
<dd class="field-odd"><p>Stefan van der Walt <<a class="reference external" href="mailto:stefanv%40berkeley.edu">stefanv<span>@</span>berkeley<span>.</span>edu</a>></p>
</dd>
<dt class="field-even">Status<span class="colon">:</span></dt>
<dd class="field-even"><p>Active</p>
</dd>
<dt class="field-odd">Type<span class="colon">:</span></dt>
<dd class="field-odd"><p>Informational</p>
</dd>
<dt class="field-even">Created<span class="colon">:</span></dt>
<dd class="field-even"><p>2021-02-07</p>
</dd>
<dt class="field-odd">Resolution<span class="colon">:</span></dt>
<dd class="field-odd"><p></p></dd>
</dl>
<section id="abstract">
<h2>Abstract<a class="headerlink" href="#abstract" title="Link to this heading">#</a></h2>
<p>The NumPy project has historically never received significant <strong>unrestricted</strong>
funding. However, that is starting to change. This NEP aims to provide
guidance about spending NumPy project unrestricted funds by formulating a set
of principles about <em>what</em> to pay for and <em>who</em> to pay. It will also touch on
how decisions regarding spending funds get made, how funds get administered,
and transparency around these topics.</p>
</section>
<section id="motivation-and-scope">
<h2>Motivation and scope<a class="headerlink" href="#motivation-and-scope" title="Link to this heading">#</a></h2>
<p>NumPy is a fiscally sponsored project of NumFOCUS, a 501(c)(3) nonprofit
organization headquartered in Austin, TX. Therefore, for all legal and
accounting matters the NumPy project has to follow the rules and regulations
for US nonprofits. All nonprofit donations are classified into two categories:
<strong>unrestricted funds</strong> which may be used for any legal purpose appropriate
to the organization and <strong>restricted funds</strong>, monies set aside for a
particular purpose (e.g., project, educational program, etc.).</p>
<p>For the detailed timeline of NumPy funding refer to
<a class="reference internal" href="#numpy-funding-history"><span class="std std-ref">NumPy funding – history and current status</span></a>.</p>
<p>Since its inception and until 2020, the NumPy project has only spent on the order of
$10,000 USD of funds that were not restricted to a particular program. Project
income of this type has been relying on donations from individuals and, from
mid 2019, recurring monthly contributions from Tidelift. By the end of 2020,
the Tidelift contributions increased to $3,000/month, and there’s also a
potential for an increase of donations and grants going directly to the
project. Having a clear set of principles around how to use these funds will
facilitate spending them fairly and effectively. Additionally, it will make it
easier to solicit donations and other contributions.</p>
<p>A key assumption this NEP makes is that NumPy remains a largely
volunteer-driven project, and that the project funds are not enough to employ
maintainers full-time. If funding increases to the point where that assumption
is no longer true, this NEP should be updated.</p>
<p>In scope for this NEP are:</p>
<ul class="simple">
<li><p>Principles of spending project funds: what to pay for, and who to pay.</p></li>
<li><p>Describing how NumPy’s funds get administered.</p></li>
<li><p>Describing how decisions to spend funds get proposed and made.</p></li>
</ul>
<p>Out of scope for this NEP are:</p>
<ul class="simple">
<li><p>Making any decisions about spending project funds on a specific project or
activity.</p></li>
<li><p>Principles for spending funds that are intended for NumPy development, but
don’t fall in the category of NumPy unrestricted funds. This includes most of
the grant funding, which is usually earmarked for certain
activities/deliverables and goes to an Institutional Partner rather than
directly to the NumPy project, and companies or institutions funding specific
features.
<em>Rationale: As a project, we have no direct control over how this work gets
executed (at least formally, until issues or PRs show up). In some cases, we
may not even know the contributions were funded or done by an employee on
work time. (Whether that’s the case or not should not change how we approach
a contribution). For grants though, we do expect the research/project leader
and funded team to align their work with the needs of NumPy and be
receptive to feedback from other NumPy maintainers and contributors.</em></p></li>
</ul>
</section>
<section id="principles-of-spending-project-funds">
<h2>Principles of spending project funds<a class="headerlink" href="#principles-of-spending-project-funds" title="Link to this heading">#</a></h2>
<p>NumPy will likely always be a project with many times more volunteer
contributors than funded people. Therefore having those funded people operate
in ways that attract more volunteers and enhance their participation experience
is critical. That key principle motivates many of the more detailed principles
given below for what to pay for and whom to pay.</p>
<p>The approach for spending funds will be:</p>
<ul class="simple">
<li><p>first figure out what we want to fund,</p></li>
<li><p>then look for a great candidate,</p></li>
<li><p>after that’s settled, determine a fair compensation level.</p></li>
</ul>
<p>The next sections go into detail on each of these three points.</p>
<section id="what-to-pay-for">
<span id="section-what-to-pay-for"></span><h3>What to pay for<a class="headerlink" href="#what-to-pay-for" title="Link to this heading">#</a></h3>
<ol class="arabic simple">
<li><p>Pay for things that are important <em>and</em> otherwise won’t get done.
<em>Rationale: there is way more to be done than there are funds to do all
those things. So count on interested volunteers or external sponsored work
to do many of those things.</em></p></li>
<li><p>Plan for sustainability. Don’t rely on money always being there.</p></li>
<li><p>Consider potential positive benefits for NumPy maintainers and contributors,
maintainers of other projects, end users, and other stakeholders like
packagers and educators.</p></li>
<li><p>Think broadly. There’s more to a project than code: websites, documentation,
community building, governance - it’s all important.</p></li>
<li><p>For proposed funded work, include paid time for others to review your work
if such review is expected to be significant effort - do not just increase
the load on volunteer maintainers.
<em>Rationale: we want the effect of spending funds to be positive for
everyone, not just for the people getting paid. This is also a matter of
fairness.</em></p></li>
</ol>
<p>When considering development work, principle (1) implies that priority should
be giving to (a) the most boring/painful tasks that no one likes doing, and to
necessary structural changes to the code base that are too large to be done by
a volunteer in a reasonable amount of time.</p>
<p>There are also many tasks, activities, and projects outside of
development work that are important and could enhance the project or community
- think of, for example, user surveys, translations, outreach, dedicated
mentoring of newcomers, community organizating, website improvements, and
administrative tasks.</p>
<p>Time of people to perform tasks is also not the only thing that funds can be
used for: expenses for in-person developer meetings or sprints, hosted hardware
for benchmarking or development work, and CI or other software services could
all be good candidates to spend funds on.</p>
</section>
<section id="whom-to-pay">
<h3>Whom to pay<a class="headerlink" href="#whom-to-pay" title="Link to this heading">#</a></h3>
<ol class="arabic simple">
<li><p>All else being equal, give preference to existing maintainers/contributors.</p></li>
<li><p>When looking outside of the current team, consider this an opportunity to
make the project more diverse.</p></li>
<li><p>Pay attention to the following when considering paying someone:</p>
<ul class="simple">
<li><p>the necessary technical or domain-specific skills to execute the tasks,</p></li>
<li><p>communication and self-management skills,</p></li>
<li><p>experience contributing to and working with open source projects.</p></li>
</ul>
</li>
</ol>
<p>It will likely depend on the project/tasks whether there’s already a clear best
candidate within the NumPy team, or whether we look for new people to get
involved. Before making any decisions, the decision makers (according to the
NumPy governance document - currently that’s the Steering Council) should think
about whether an opportunity should be advertised to give a wider group of
people a chance to apply for it.</p>
</section>
<section id="compensating-fairly">
<h3>Compensating fairly<a class="headerlink" href="#compensating-fairly" title="Link to this heading">#</a></h3>
<div class="admonition note">
<p class="admonition-title">Note</p>
<p>This section on compensating fairly will be considered <em>Draft</em> even if this
NEP as a whole is accepted. Once we have applied the approach outlined here
at least 2-3 times and we are happy with it, will we remove this note and
consider this section <em>Accepted</em>.</p>
</div>
<p>Paying people fairly is a difficult topic, especially when it comes to
distributed teams. Therefore, we will only offer some guidance here. Final
decisions will always have to be considered and approved by the group of people
that bears this responsibility (according to the current NumPy governance
structure, this would be the NumPy Steering Council).</p>
<p>Discussions on remote employee compensation tend to be dominated by two
narratives: “pay local market rates” and “same work – same pay”.</p>
<p>We consider them both extreme:</p>
<ul class="simple">
<li><p>“Same work – same pay” is unfair to people living in locations with a higher
cost of living. For example, the average rent for a single family apartment
can differ by a large factor (from a few hundred dollars to thousands of
dollars per month).</p></li>
<li><p>“Pay local market rates” bakes in existing inequalities between countries
and makes fixed-cost items like a development machine or a holiday trip
abroad relatively harder to afford in locations where market rates are lower.</p></li>
</ul>
<p>We seek to find a middle ground between these two extremes.</p>
<p>Useful points of reference include companies like GitLab and
Buffer who are transparent about their remuneration policies (<a class="footnote-reference brackets" href="#id11" id="id1" role="doc-noteref"><span class="fn-bracket">[</span>3<span class="fn-bracket">]</span></a>, <a class="footnote-reference brackets" href="#id12" id="id2" role="doc-noteref"><span class="fn-bracket">[</span>4<span class="fn-bracket">]</span></a>),
Google Summer of Code stipends (<a class="footnote-reference brackets" href="#id13" id="id3" role="doc-noteref"><span class="fn-bracket">[</span>5<span class="fn-bracket">]</span></a>), other open source projects that manage
their budget in a transparent manner (e.g., Babel and Webpack on Open
Collective (<a class="footnote-reference brackets" href="#id14" id="id4" role="doc-noteref"><span class="fn-bracket">[</span>6<span class="fn-bracket">]</span></a>, <a class="footnote-reference brackets" href="#id15" id="id5" role="doc-noteref"><span class="fn-bracket">[</span>7<span class="fn-bracket">]</span></a>)), and standard salary comparison sites.</p>
<p>Since NumPy is a not-for-profit project, we also looked to the nonprofit sector
for guidelines on remuneration policies and compensation levels. Our findings
show that most smaller non-profits tend to pay a median salary/wage. We
recognize merit in this approach: applying candidates are likely to have a
genuine interest in open source, rather than to be motivated purely by
financial incentives.</p>
<p>Considering all of the above, we will use the following guidelines for
determining compensation:</p>
<ol class="arabic simple">
<li><p>Aim to compensate people appropriately, up to a level that’s expected for
senior engineers or other professionals as applicable.</p></li>
<li><p>Establish a compensation cap of $125,000 USD that cannot be exceeded even
for the residents from the most expensive/competitive locations (<a class="footnote-reference brackets" href="#f-pay" id="id6" role="doc-noteref"><span class="fn-bracket">[</span>8<span class="fn-bracket">]</span></a>).</p></li>
<li><p>For equivalent work and seniority, a pay differential between locations
should never be more than 2x.
For example, if we pay $110,000 USD to a senior-level developer from New
York, for equivalent work a senior-level developer from South-East Asia
should be paid at least $55,000 USD. To compare locations, we will use
<a class="reference external" href="https://www.numbeo.com/cost-of-living/">Numbeo Cost of Living calculator</a>
(or its equivalent).</p></li>
</ol>
<p>Some other considerations:</p>
<ul class="simple">
<li><p>Often, compensated work is offered for a limited amount of hours or fixed
term. In those cases, consider compensation equivalent to a remuneration
package that comes with permanent employment (e.g., one month of work should
be compensated by at most 1/12th of a full-year salary + benefits).</p></li>
<li><p>When comparing rates, an individual contractor should typically make 20% more
than someone who is employed since they have to take care of their benefits
and accounting on their own.</p></li>
<li><p>Some people may be happy with one-off payments towards a particular
deliverable (e.g., “triage all open issues for label X for $x,xxx”).
This should be compensated at a lower rate compared to an individual
contractor. Or they may motivate lower amounts for another reason (e.g., “I
want to receive $x,xxx to hire a cleaner or pay for childcare, to free up
time for work on open source).</p></li>
<li><p>When funding someone’s time through their employer, that employer may want to
set the compensation level based on its internal rules (e.g., overhead rates).
Small deviations from the guidelines in this NEP may be needed in such cases,
however they should be within reason.</p></li>
<li><p>It’s entirely possible that another strategy rather than paying people for
their time on certain tasks may turn out to be more effective. Anything that
helps the project and community grow and improve is worth considering.</p></li>
<li><p>Transparency helps. If everyone involved is comfortable sharing their
compensation levels with the rest of the team (or better make it public),
it’s least likely to be way off the mark for fairness.</p></li>
</ul>
<p>We highly recommend that the individuals involved in decision-making about
hiring and compensation peruse the content of the References section of this
NEP. It offers a lot of helpful advice on this topic.</p>
</section>
</section>
<section id="defining-fundable-activities-and-projects">
<h2>Defining fundable activities and projects<a class="headerlink" href="#defining-fundable-activities-and-projects" title="Link to this heading">#</a></h2>
<p>We’d like to have a broader set of fundable ideas that we will prioritize with
input from NumPy team members and the wider community. All ideas will be
documented on a single wiki page. Anyone may propose an idea. Only members of a
NumPy team may edit the wiki page.</p>
<p>Each listed idea must meet the following requirements:</p>
<ol class="arabic simple">
<li><p>It must be clearly scoped: its description must explain the importance to
the project, referencing the NumPy Roadmap if possible, the items to pay for
or activities and deliverables, and why it should be a funded activity (see
<a class="reference internal" href="#section-what-to-pay-for"><span class="std std-ref">What to pay for</span></a>).</p></li>
<li><p>It must contain the following metadata: title, cost, time duration or effort
estimate, and (if known) names of the team member(s) to execute or coordinate.</p></li>
<li><p>It must have an assigned priority (low, medium, or high). This discussion
can originate at a NumPy community meeting or on the mailing list. However,
it must be finalized on the mailing list allowing everyone to weigh in.</p></li>
</ol>
<p>If a proposed idea has been assigned a high priority level, a decision on
allocating funding for it will be made on the private NumPy Steering Council
mailing list. <em>Rationale: these will often involve decisions about individuals,
which is typically hard to do in public. This is the current practice that
seems to be working well.</em></p>
<p>Sometimes, it may be practical to make a single funding decision ad-hoc (e.g.,
“Here’s a great opportunity plus the right person to execute it right now”).
However, this approach to decision-making should be used rarely.</p>
</section>
<section id="strategy-for-spending-saving-funds">
<h2>Strategy for spending/saving funds<a class="headerlink" href="#strategy-for-spending-saving-funds" title="Link to this heading">#</a></h2>
<p>There is an expectation from NumPy individual, corporate, and institutional
donors that the funds will be used for the benefit of the project and the
community. Therefore, we should spend available funds, thoughtfully,
strategically, and fairly, as they come in. For emergencies, we should keep a
$10,000 - $15,000 USD reserve which could cover, for example, a year of CI and
hosting services, 1-2 months of full-time maintenance work, or contracting a
consultant for a specific need.</p>
</section>
<section id="how-project-funds-get-administered">
<h2>How project funds get administered<a class="headerlink" href="#how-project-funds-get-administered" title="Link to this heading">#</a></h2>
<p>We will first summarize how administering of funds works today, and then
discuss how to make this process more efficient and transparent.</p>
<p>Currently, the project funds are held by NumFOCUS in a dedicated account.
NumFOCUS has a small accounting team, which produces an account overview as a
set of spreadsheets on a monthly basis. These land in a shared drive, typically
with about a one month delay (e.g., the balance and transactions for February
are available at the end of March), where a few NumPy team members can access
them. Expense claims and invoices are submitted through the NumFOCUS website.
Those then show up in another spreadsheet, where a NumPy team member must
review and approve each of them before payments are made. Following NumPy
bylaws, the NumFOCUS finance subcommittee, consisting of five people, meets
every six months to review all the project related transactions. (In practice,
there have been so few transactions that we skipped some of these meetings.)</p>
<p>The existing process is time-consuming and error-prone. More transparency and
automation are desirable.</p>
<section id="transparency-about-project-funds-and-in-decision-making">
<h3>Transparency about project funds and in decision making<a class="headerlink" href="#transparency-about-project-funds-and-in-decision-making" title="Link to this heading">#</a></h3>
<p><strong>To discuss: do we want full transparency by publishing our accounts,
transparency to everyone on a NumPy team, or some other level?</strong></p>
<p>Ralf: I’d personally like it to be fully transparent, like through Open
Collective, so the whole community can see current balance, income and expenses
paid out at any moment in time. Moving to Open Collective is nontrivial,
however we can publish the data elsewhere for now if we’d want to.
<em>Note: Google Season of Docs this year requires having an Open Collective
account, so this is likely to happen soon enough.</em></p>
<p>Stefan/Inessa: at least a summary overview should be fully public, and all
transactions should be visible to the Steering Council. Full transparency of
all transactions is probably fine, but not necessary.</p>
<p><em>The options here may be determined by the accounting system and amount of
effort required.</em></p>
</section>
</section>
<section id="numpy-funding-history-and-current-status">
<span id="numpy-funding-history"></span><h2>NumPy funding – history and current status<a class="headerlink" href="#numpy-funding-history-and-current-status" title="Link to this heading">#</a></h2>
<p>The NumPy project received its first major funding in 2017. For an overview of
the early history of NumPy (and SciPy), including some institutions sponsoring
time for their employees or contractors to work on NumPy, see <a class="footnote-reference brackets" href="#id9" id="id7" role="doc-noteref"><span class="fn-bracket">[</span>1<span class="fn-bracket">]</span></a> and <a class="footnote-reference brackets" href="#id10" id="id8" role="doc-noteref"><span class="fn-bracket">[</span>2<span class="fn-bracket">]</span></a>. To
date, NumPy has received four grants:</p>
<ul class="simple">
<li><p>Two grants, from the Alfred P. Sloan Foundation and the Gordon and Betty
Moore Foundation respectively, of about $1.3M combined to the Berkeley
Institute of Data Science. Work performed during the period 2017-2020;
PI Stéfan van der Walt.</p></li>
<li><p>Two grants from the Chan Zuckerberg Foundation to NumFOCUS, for a combined
amount of $335k. Work performed during the period 2020-2021; PI’s Ralf
Gommers (first grant) and Melissa Mendonça (second grant).</p></li>
</ul>
<p>From 2012 onwards NumPy has been a fiscally sponsored project of NumFOCUS.
Note that fiscal sponsorship doesn’t mean NumPy gets funding, rather that it
can receive funds under the umbrella of a nonprofit. See <a class="reference external" href="https://numfocus.org/projects-overview">NumFOCUS Project
Support</a> for more details.</p>
<p>Only since 2017 has the NumPy website displayed a “Donate” button, and since
2019 the NumPy repositories have had the GitHub Sponsors button. Before that,
it was possible to donate to NumPy on the NumFOCUS website. The sum total of
donations from individuals to NumPy for 2017-2020 was about $6,100.</p>
<p>From May 2019 onwards, Tidelift has supported NumPy financially as part of
its “managed open source” business model. From May 2019 till July 2020 this was
$1,000/month, and it started steadily growing after that to about $3,000/month
(as of Feb 2021).</p>
<p>Finally, there has been other incidental project income, for example, some book
royalties from Packt Publishing, GSoC mentoring fees from Google, and
merchandise sales revenue through the NumFOCUS web shop. All of these were
small (two or three figure) amounts.</p>
<p>This brings the total amount of project income which did not already have a
spending target to about $35,000. Most of that is recent, from Tidelift.
Over the past 1.5 years we spent about $10,000 for work on the new NumPy
website and Sphinx theme. Those spending decisions were made by the NumPy
Steering Council and announced on the mailing list.</p>
<p>That leaves about $25,000 in available funds at the time of writing, and
that amount is currently growing at a rate of about $3,000/month.</p>
</section>
<section id="related-work">
<h2>Related work<a class="headerlink" href="#related-work" title="Link to this heading">#</a></h2>
<p>See references. We assume that other open source projects have also developed
guidelines on spending project funds. However, we were unable to find any
examples at the time of writing.</p>
</section>
<section id="alternatives">
<h2>Alternatives<a class="headerlink" href="#alternatives" title="Link to this heading">#</a></h2>
<p><em>Alternative spending strategy</em>: not having cash reserves. The rationale
being that NumPy is important enough that in a real emergency some person or
entity will likely jump in to help out. This is not a responsible approach to
financial stewardship of the project though. Hence, we decided against it.</p>
</section>
<section id="discussion">
<h2>Discussion<a class="headerlink" href="#discussion" title="Link to this heading">#</a></h2>
</section>
<section id="references-and-footnotes">
<h2>References and footnotes<a class="headerlink" href="#references-and-footnotes" title="Link to this heading">#</a></h2>
<aside class="footnote-list brackets">
<aside class="footnote brackets" id="id9" role="doc-footnote">
<span class="label"><span class="fn-bracket">[</span><a role="doc-backlink" href="#id7">1</a><span class="fn-bracket">]</span></span>
<p>Pauli Virtanen et al., “SciPy 1.0: fundamental algorithms for scientific
computing in Python”, <a class="reference external" href="https://www.nature.com/articles/s41592-019-0686-2">https://www.nature.com/articles/s41592-019-0686-2</a>,
2020</p>
</aside>
<aside class="footnote brackets" id="id10" role="doc-footnote">
<span class="label"><span class="fn-bracket">[</span><a role="doc-backlink" href="#id8">2</a><span class="fn-bracket">]</span></span>
<p>Charles Harris et al., “Array programming with NumPy”, <a class="reference external" href="https://www.nature.com/articles/s41586-020-2649-2">https://www.nature.com/articles/s41586-020-2649-2</a>, 2020</p>
</aside>
<aside class="footnote brackets" id="id11" role="doc-footnote">
<span class="label"><span class="fn-bracket">[</span><a role="doc-backlink" href="#id1">3</a><span class="fn-bracket">]</span></span>
<p><a class="reference external" href="https://remote.com/blog/remote-compensation">https://remote.com/blog/remote-compensation</a></p>
</aside>
<aside class="footnote brackets" id="id12" role="doc-footnote">
<span class="label"><span class="fn-bracket">[</span><a role="doc-backlink" href="#id2">4</a><span class="fn-bracket">]</span></span>
<p><a class="reference external" href="https://about.gitlab.com/company/culture/all-remote/compensation/#how-do-you-decide-how-much-to-pay-people">https://about.gitlab.com/company/culture/all-remote/compensation/#how-do-you-decide-how-much-to-pay-people</a></p>
</aside>
<aside class="footnote brackets" id="id13" role="doc-footnote">
<span class="label"><span class="fn-bracket">[</span><a role="doc-backlink" href="#id3">5</a><span class="fn-bracket">]</span></span>
<p><a class="reference external" href="https://developers.google.com/open-source/gsoc/help/student-stipends">https://developers.google.com/open-source/gsoc/help/student-stipends</a></p>
</aside>
<aside class="footnote brackets" id="id14" role="doc-footnote">
<span class="label"><span class="fn-bracket">[</span><a role="doc-backlink" href="#id4">6</a><span class="fn-bracket">]</span></span>
<p>Jurgen Appelo, “Compensation: what is fair?”, <a class="reference external" href="https://blog.agilityscales.com/compensation-what-is-fair-38a65a822c29">https://blog.agilityscales.com/compensation-what-is-fair-38a65a822c29</a>, 2016</p>
</aside>
<aside class="footnote brackets" id="id15" role="doc-footnote">
<span class="label"><span class="fn-bracket">[</span><a role="doc-backlink" href="#id5">7</a><span class="fn-bracket">]</span></span>
<p>Project Include, “Compensating fairly”, <a class="reference external" href="https://projectinclude.org/compensating_fairly">https://projectinclude.org/compensating_fairly</a></p>
</aside>
<aside class="footnote brackets" id="f-pay" role="doc-footnote">
<span class="label"><span class="fn-bracket">[</span><a role="doc-backlink" href="#id6">8</a><span class="fn-bracket">]</span></span>
<p>This cap is derived from comparing with compensation levels at
other open source projects (e.g., Babel, Webpack, Drupal - all in
the $100,000 – $125,000 range) and Partner Institutions.</p>
</aside>
</aside>
<ul class="simple">
<li><p>Nadia Eghbal, “Roads and Bridges: The Unseen Labor Behind Our Digital
Infrastructure”, 2016</p></li>
<li><p>Nadia Eghbal, “Working in Public: The Making and Maintenance of Open
Source”, 2020</p></li>
<li><p><a class="github reference external" href="https://github.com/nayafia/lemonade-stand">nayafia/lemonade-stand</a></p></li>
<li><p>Daniel Oberhaus, <a class="reference external" href="https://www.vice.com/en/article/43zak3/the-internet-was-built-on-the-free-labor-of-open-source-developers-is-that-sustainable">“The Internet Was Built on the Free Labor of Open Source
Developers. Is That Sustainable?”</a>, 2019</p></li>
<li><p>David Heinemeier Hansson, <a class="reference external" href="https://dhh.dk/2013/the-perils-of-mixing-open-source-and-money.html">“The perils of mixing open source and money”</a>, 2013</p></li>
<li><p>Danny Crichton, <a class="reference external" href="https://techcrunch.com/2018/06/23/open-source-sustainability/?guccounter=1">“Open source sustainability”</a>, 2018</p></li>
<li><p>Nadia Eghbal, “Rebuilding the Cathedral”, <a class="reference external" href="https://www.youtube.com/watch?v=VS6IpvTWwkQ">https://www.youtube.com/watch?v=VS6IpvTWwkQ</a>, 2017</p></li>
<li><p>Nadia Eghbal, “Where money meets open source”, <a class="reference external" href="https://www.youtube.com/watch?v=bjAinwgvQqc&t=246s">https://www.youtube.com/watch?v=bjAinwgvQqc&t=246s</a>, 2017</p></li>
<li><p>Eileen Uchitelle, “”The unbearable vulnerability of open source”, <a class="reference external" href="https://www.youtube.com/watch?v=VdwO3LQ56oM">https://www.youtube.com/watch?v=VdwO3LQ56oM</a>, 2017 (the inverted triangle, open source is a funnel)</p></li>
<li><p>Dries Buytaert, “Balancing Makers and Takers to scale and sustain Open Source”, <a class="reference external" href="https://dri.es/balancing-makers-and-takers-to-scale-and-sustain-open-source">https://dri.es/balancing-makers-and-takers-to-scale-and-sustain-open-source</a>, 2019</p></li>
<li><p>Safia Abdalla, “Beyond Maintenance”, <a class="reference external" href="https://increment.com/open-source/beyond-maintenance/">https://increment.com/open-source/beyond-maintenance/</a>, 2019</p></li>
<li><p>Xavier Damman, “Money and Open Source Communities”, <a class="reference external" href="https://blog.opencollective.com/money-and-open-source-communities/">https://blog.opencollective.com/money-and-open-source-communities/</a>, 2016</p></li>
<li><p>Aseem Sood, “Let’s talk about money”, <a class="reference external" href="https://blog.opencollective.com/lets-talk-about-money/">https://blog.opencollective.com/lets-talk-about-money/</a>, 2017</p></li>
<li><p>Alanna Irving, “Has your open source community raised money? Here’s how to spend it.”, <a class="reference external" href="https://blog.opencollective.com/has-your-open-source-community-raised-money-heres-how-to-spend-it/">https://blog.opencollective.com/has-your-open-source-community-raised-money-heres-how-to-spend-it/</a>, 2017</p></li>
<li><p>Alanna Irving, “Funding open source, how Webpack reached $400k+/year”, <a class="reference external" href="https://blog.opencollective.com/funding-open-source-how-webpack-reached-400k-year/">https://blog.opencollective.com/funding-open-source-how-webpack-reached-400k-year/</a>, 2017</p></li>
<li><p>Alanna Irving, “Babel’s rise to financial sustainability”, <a class="reference external" href="https://blog.opencollective.com/babels-rise-to-financial-sustainability/">https://blog.opencollective.com/babels-rise-to-financial-sustainability/</a>, 2019</p></li>
<li><p>Devon Zuegel, “The city guide to open source”, <a class="reference external" href="https://www.youtube.com/watch?v=80KTVu6GGSE">https://www.youtube.com/watch?v=80KTVu6GGSE</a>, 2020 + blog: <a class="reference external" href="https://increment.com/open-source/the-city-guide-to-open-source/">https://increment.com/open-source/the-city-guide-to-open-source/</a></p></li>
</ul>
<p>GitHub Sponsors:</p>
<ul class="simple">
<li><p><a class="reference external" href="https://github.blog/2019-05-23-announcing-github-sponsors-a-new-way-to-contribute-to-open-source/">https://github.blog/2019-05-23-announcing-github-sponsors-a-new-way-to-contribute-to-open-source/</a></p></li>
<li><p><a class="reference external" href="https://github.blog/2020-05-12-github-sponsors-is-out-of-beta-for-sponsored-organizations/">https://github.blog/2020-05-12-github-sponsors-is-out-of-beta-for-sponsored-organizations/</a></p></li>
<li><p><a class="reference external" href="https://blog.opencollective.com/on-github-sponsors/">https://blog.opencollective.com/on-github-sponsors/</a>, 2019</p></li>
<li><p><a class="reference external" href="https://blog.opencollective.com/double-the-love/">https://blog.opencollective.com/double-the-love/</a>, 2020</p></li>
<li><p><a class="reference external" href="https://blog.opencollective.com/github-sponsors-for-companies-open-source-collective-for-people/">https://blog.opencollective.com/github-sponsors-for-companies-open-source-collective-for-people/</a></p></li>
</ul>
</section>
<section id="copyright">
<h2>Copyright<a class="headerlink" href="#copyright" title="Link to this heading">#</a></h2>
<p>This document has been placed in the public domain.</p>
</section>
</section>
</article>
</div>
<div class="bd-sidebar-secondary bd-toc"><div class="sidebar-secondary-items sidebar-secondary__inner">
<div class="sidebar-secondary-item">
<div
id="pst-page-navigation-heading-2"
class="page-toc tocsection onthispage">
<i class="fa-solid fa-list"></i> On this page
</div>
<nav class="bd-toc-nav page-toc" aria-labelledby="pst-page-navigation-heading-2">
<ul class="visible nav section-nav flex-column">
<li class="toc-h2 nav-item toc-entry"><a class="reference internal nav-link" href="#abstract">Abstract</a></li>
<li class="toc-h2 nav-item toc-entry"><a class="reference internal nav-link" href="#motivation-and-scope">Motivation and scope</a></li>
<li class="toc-h2 nav-item toc-entry"><a class="reference internal nav-link" href="#principles-of-spending-project-funds">Principles of spending project funds</a><ul class="nav section-nav flex-column">
<li class="toc-h3 nav-item toc-entry"><a class="reference internal nav-link" href="#what-to-pay-for">What to pay for</a></li>
<li class="toc-h3 nav-item toc-entry"><a class="reference internal nav-link" href="#whom-to-pay">Whom to pay</a></li>
<li class="toc-h3 nav-item toc-entry"><a class="reference internal nav-link" href="#compensating-fairly">Compensating fairly</a></li>
</ul>
</li>
<li class="toc-h2 nav-item toc-entry"><a class="reference internal nav-link" href="#defining-fundable-activities-and-projects">Defining fundable activities and projects</a></li>
<li class="toc-h2 nav-item toc-entry"><a class="reference internal nav-link" href="#strategy-for-spending-saving-funds">Strategy for spending/saving funds</a></li>
<li class="toc-h2 nav-item toc-entry"><a class="reference internal nav-link" href="#how-project-funds-get-administered">How project funds get administered</a><ul class="nav section-nav flex-column">
<li class="toc-h3 nav-item toc-entry"><a class="reference internal nav-link" href="#transparency-about-project-funds-and-in-decision-making">Transparency about project funds and in decision making</a></li>
</ul>
</li>
<li class="toc-h2 nav-item toc-entry"><a class="reference internal nav-link" href="#numpy-funding-history-and-current-status">NumPy funding – history and current status</a></li>
<li class="toc-h2 nav-item toc-entry"><a class="reference internal nav-link" href="#related-work">Related work</a></li>
<li class="toc-h2 nav-item toc-entry"><a class="reference internal nav-link" href="#alternatives">Alternatives</a></li>
<li class="toc-h2 nav-item toc-entry"><a class="reference internal nav-link" href="#discussion">Discussion</a></li>
<li class="toc-h2 nav-item toc-entry"><a class="reference internal nav-link" href="#references-and-footnotes">References and footnotes</a></li>
<li class="toc-h2 nav-item toc-entry"><a class="reference internal nav-link" href="#copyright">Copyright</a></li>
</ul>
</nav></div>
</div></div>
</div>
<footer class="bd-footer-content">
</footer>
</main>
</div>
</div>
<!-- Scripts loaded after <body> so the DOM is not blocked -->
<script src="_static/scripts/bootstrap.js?digest=8d27b9dea8ad943066ae"></script>
<script src="_static/scripts/pydata-sphinx-theme.js?digest=8d27b9dea8ad943066ae"></script>
<footer class="bd-footer">
<div class="bd-footer__inner bd-page-width">
<div class="footer-items__start">
<div class="footer-item">
<p class="copyright">
© Copyright 2017-2018, NumPy Developers.
<br/>
</p>
</div>
<div class="footer-item">
<p class="sphinx-version">
Created using <a href="https://www.sphinx-doc.org/">Sphinx</a> 7.2.6.
<br/>
</p>