Skip to content

Commit bafe07f

Browse files
authored
docs: update CONTRIBUTING guidelines (#3656)
ocs: update CONTRIBUTING guidelines
1 parent dd57ea2 commit bafe07f

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

CONTRIBUTING.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -24,8 +24,8 @@ Please [make the pull request a draft](https://github.blog/2019-02-14-introducin
2424

2525
Currently, we have two regular reviewers of pull requests:
2626

27-
* Jim Pivarski ([jpivarski](https://github.com/jpivarski))
28-
* Topher Cawlfield ([tcawlfield](https://github.com/tcawlfield))
27+
* Ianna Osborne ([ianna](https://github.com/ianna))
28+
* Peter Fackeldey ([pfackeldey](https://github.com/pfackeldey))
2929

3030
You can request a review from one of us or just comment in GitHub that you want a review and we'll see it. Only one review is required to be allowed to merge a pull request. We'll work with you to get it into shape.
3131

@@ -39,7 +39,7 @@ If you want to contribute frequently, we'll grant you write access to the `sciki
3939

4040
Unless you ask us not to, we might commit directly to your pull request as a way of communicating what needs to be changed. That said, most of the commits on a pull request are from a single author: corrections and suggestions are exceptions.
4141

42-
Therefore, we prefer git branches to be named with your GitHub userid, such as `jpivarski/write-contributing-md`.
42+
Therefore, we prefer git branches to be named with your GitHub userid, such as `ianna/write-contributing-md`.
4343

4444
The titles of pull requests (and therefore the merge commit messages) should follow [these conventions](https://www.conventionalcommits.org/en/v1.0.0/#summary). Mostly, this means prefixing the title with one of these words and a colon:
4545

@@ -284,7 +284,7 @@ The `main-v1` branch was split from `main` just before Awkward 1.x code was remo
284284

285285
Currently, only one person can deploy releases:
286286

287-
* Jim Pivarski ([jpivarski](https://github.com/jpivarski))
287+
* Ianna Osborne ([ianna](https://github.com/ianna))
288288

289289
There are two kinds of releases: (1) `awkward-cpp` updates, which only occur when the C++ is updated (rare) and involves compilation on many platforms (takes hours), and (2) `awkward` updates, which can happen with any bug-fix. The [releases listed in GitHub](https://github.com/scikit-hep/awkward/releases) are `awkward` releases, not `awkward-cpp`.
290290

0 commit comments

Comments
 (0)