forked from numba/numba
-
Notifications
You must be signed in to change notification settings - Fork 0
/
CODEOWNERS
Validating CODEOWNERS rules...
98 lines (96 loc) · 3.84 KB
/
CODEOWNERS
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
# Numba's codeowners file is dual purpose, it:
#
# 1. Provides information to github about who should be requested to review a PR
# 2. Provides contributors/czars general information about who to contact
# first about various parts of the code base. A lot of concepts in Numba are
# necessarily spread throughout the code base, consequently some of the
# "code ownership"/first contact is concept based opposed to file/directory
# based.
#
# ------------------------------------------------------------------------------
# Information for github
# ------------------------------------------------------------------------------
# These people are the default "owners" for everything in the repo unless a
# later match is made, they will automatically be requested to review PRs.
* @sklam @stuartarchibald
# Owners of specific parts of the code, will be requested to review if a PR
# touches code in the matched pattern
/numba/cuda/ @gmarkall
/numba/parfors/ @DrTodd13
/numba/stencils/ @DrTodd13
# ------------------------------------------------------------------------------
# Information for contributors
# ------------------------------------------------------------------------------
# This section provides a rough list of who to contact first for help with
# various parts/concepts in the code base, first contact does not imply
# ownership!
#
# Parts of the code base:
#
# * Parfors/Parallel Accelerator (@DrTodd13)
# - Array Analysis (@DrTodd13)
# - Parfors transforms (@DrTodd13)
# * Stencils (@DrTodd13)
# * Experimental:
# - Jitclasses (@sklam)
# - StructRef (@sklam)
# * Typed containers:
# - Typed.List (@esc)
# - Typed.Dict (@sklam)
# * Documentation (Needs first contact/owner)
# * NumPy (Needs first contact/owner)
# - ufuncs (Needs first contact/owner)
# - linalg (@stuartarchibald)
# - Implementation of specific functions (Needs first contact/owner)
# - Parallel backends/threading layers (@stuartarchibald)
# * CPython implementation (Needs first contact/owner)
# * Extension API (Needs first contact/owner)
# * AOT (Needs first contact/owner)
# * Compiler:
# - Type inference (@sklam)
# - Bytecode analysis/CFA/DFA (@sklam)
# - Compiler Pipeline infrastructure (@stuartarchibald)
# - Compiler passes:
# - Rewrites (Needs first contact/owner)
# - Branch pruning (@stuartarchibald)
# - Literal unroll (@stuartarchibald)
# - Rewrite Semantic Constants (@stuartarchibald)
# - MakeFunction To Jit function (@stuartarchibald)
# - Overload and function inlining (@stuartarchibald)
# - With Lifting (@sklam)
# - Exception handling (@sklam)
# - Literally (@sklam)
# - SSA (@sklam)
# - lowering.py, codegen.py (@sklam)
# - Datamodels/call conventions (@sklam)
# - Inlining in general (@stuartarchibald)
#
# Additional Concepts:
#
# * Reference counting and NRT (@sklam)
# * Testing (Needs first contact/owner)
# * CI:
# - public CI (azure) (Needs first contact/owner)
# - Numba build farm (@esc)
# * Integration testing (https://github.com/numba/numba-integration-testing)
# (@esc)
# * ASV profiling (@esc)
# * Type Annotations (@luk-f-a and @EPronovost)
# * Ufunc/GUfunc (Needs first contact/owner)
# * Profiling (Needs first contact/owner (and code!))
# * Debugging:
# - DWARF (@sklam)
# - gdb support (@stuartarchibald)
# * Hardware targets:
# - The CUDA target (@gmarkall)
# - The ROCm target (@stuartarchibald)
# - ARM* (@stuartarchibald)
# - POWER (Needs first contact/owner)
# - X86* (Needs first contact/owner)
# * OS:
# - Linux (@stuartarchibald)
# - OSX
# - Windows
# - BSD (@stuartarchibald)
#
# Anything not covered by someone else... ping @sklam and @stuartarchibald