Let's Go!

image/svg+xml

Close/Merge as many issues and PR as possible during the month of November

1074 / 11510

Perfection is achieved, not when there is nothing more to add, but when there is nothing left to take away.

― Antoine de Saint-Exupéry,

1074 issues and pull-requests closed (or merged) so far! We need your help with the 11510 that need to go...

Start Closing Issues

Why Closember ?

Closember aims to increase awareness about Open Source maintainer burnout and promote practices to make maintaining open-source less stressful and more enjoyable for everyone. more…


Did you know ?


You can go to https://github.com/issues and https://github.com/pulls to see all the issues/pull-requests you opened. Are those still relevant ? Maybe close a few if not.


Closeboard

# Repository Closed Issues Closed/Merged PRs
1 datalad/datalad 251 19
2 scipy/scipy 98 91
3 spyder-ide/spyder 75 12
4 vispy/vispy 82 2
5 thanos-io/thanos 35 34
6 PyCQA/pylint 55 8
7 arviz-devs/arviz 29 23
8 astropy/astroquery 32 8
9 ipython/ipython 22 17
10 poliastro/poliastro 18 9
11 spyder-ide/qtpy 12 2
12 radis/radis 9 5
13 pytroll/satpy 8 5
14 ipython/ipykernel 8 3
15 pymc-devs/pymc-examples 3 7
16 pygfx/pygfx 6 4
17 PyCQA/astroid 6 4
18 jupyter/notebook 6 3
19 tqdm/tqdm 6 2
20 physiopy/phys2bids 5 2
21 icesat2py/icepyx 2 3
22 getpelican/pelican 2 3
23 FCP-INDI/C-PAC 1 4
24 pygfx/wgpu-py 3 1
25 spyder-ide/qtawesome 2 1
26 pytroll/pyresample 3 0
27 pytroll/pyorbital 1 2
28 FCP-INDI/fcp-indi.github.io 0 3
29 rse-asia/OLS-4 2 0
30 pytroll/pyspectral 1 1
31 bacloud22/so-cards 2 0
32 P403n1x87/austin-vscode 1 1
33 FCP-INDI/C-PAC_GUI 1 1
34 FCP-INDI/.github 0 2
35 timofurrer/awesome-asyncio 0 1
36 physiopy/phys2denoise 0 1
37 openteamsinc/closember 1 0
38 jupyter/papyri 1 0
39 codezonediitj/pydatastructs 1 0
40 ipython/traitlets 0 0
41 ayan-biswas0412/AlgoDocs 0 0
42 MeeseeksBox/MeeseeksDev 0 0
43 FCP-INDI/cpac 0 0
44 FCP-INDI/app-C-PAC-brainlife.io 0 0
Add Your Repositories

Remember remember to close a PR in November.

― A Maintainer,

This table tracks the number of Issues and Pull requests that have been closed(or merged) in each of projects during the month of Closember. Issues opened in Closember do not count in an effort to encourage the closing of older issues.

Total Open

# Repository Open Issues Open PRs
1 FCP-INDI/.github 0 0
2 P403n1x87/austin-vscode 3 0
3 bacloud22/so-cards 4 0
4 openteamsinc/closember 4 0
5 rse-asia/OLS-4 5 0
6 FCP-INDI/app-C-PAC-brainlife.io 7 0
7 FCP-INDI/cpac 8 2
8 pygfx/wgpu-py 9 1
9 pytroll/pyspectral 13 3
10 spyder-ide/qtawesome 15 1
11 jupyter/papyri 17 0
12 ayan-biswas0412/AlgoDocs 13 6
13 pytroll/pyorbital 13 6
14 spyder-ide/qtpy 16 5
15 physiopy/phys2denoise 16 6
16 timofurrer/awesome-asyncio 0 28
17 MeeseeksBox/MeeseeksDev 28 4
18 FCP-INDI/C-PAC_GUI 32 2
19 radis/radis 36 0
20 icesat2py/icepyx 34 11
21 physiopy/phys2bids 43 6
22 pygfx/pygfx 48 2
23 codezonediitj/pydatastructs 55 10
24 FCP-INDI/fcp-indi.github.io 64 2
25 getpelican/pelican 43 28
26 pytroll/pyresample 66 7
27 ipython/traitlets 78 9
28 poliastro/poliastro 95 11
29 pymc-devs/pymc-examples 120 11
30 arviz-devs/arviz 136 11
31 PyCQA/astroid 151 25
32 ipython/ipykernel 191 16
33 thanos-io/thanos 188 32
34 vispy/vispy 260 25
35 tqdm/tqdm 269 64
36 FCP-INDI/C-PAC 331 9
37 pytroll/satpy 290 88
38 astropy/astroquery 402 73
39 datalad/datalad 482 16
40 PyCQA/pylint 728 39
41 spyder-ide/spyder 1103 76
42 ipython/ipython 1492 73
43 scipy/scipy 1485 346
44 jupyter/notebook 2017 46
Add Your Repositories

There is no perfect metric, and we sometimes f et that issues are forgotten on the last page of the issue list. Here is a leader board of who has closed the oldest issues during the month.

Longest open issue

This shows the longest opened issue closed during Closember.

(Note: there is not longest open PR because of GitHub API. Unless you find a way to do it)

# Repository Closed After Oldest issue closed
1 ipython/ipython 10 years ipython/ipython#894
2 scipy/scipy 8 years scipy/scipy#1953
3 PyCQA/pylint 8 years PyCQA/pylint#85
4 astropy/astroquery 8 years astropy/astroquery#222
5 datalad/datalad 7 years datalad/datalad#3
6 vispy/vispy 7 years vispy/vispy#379
7 spyder-ide/spyder 6 years spyder-ide/spyder#1922
8 getpelican/pelican 5 years getpelican/pelican#1162
9 spyder-ide/qtpy 5 years spyder-ide/qtpy#62
10 jupyter/notebook 5 years jupyter/notebook#1684
11 tqdm/tqdm 4 years tqdm/tqdm#461
12 poliastro/poliastro 3 years poliastro/poliastro#365
13 arviz-devs/arviz 3 years arviz-devs/arviz#313
14 pytroll/satpy 2 years pytroll/satpy#583
15 ipython/ipykernel 2 years ipython/ipykernel#398
16 thanos-io/thanos 2 years thanos-io/thanos#1375
17 pytroll/pyresample 2 years pytroll/pyresample#231
18 PyCQA/astroid 1 year, 11 months PyCQA/astroid#748
19 physiopy/phys2bids 1 year, 7 months physiopy/phys2bids#211
20 icesat2py/icepyx 1 year, 3 months icesat2py/icepyx#106
21 pygfx/pygfx 1 year, 1 month pygfx/pygfx#73
22 pygfx/wgpu-py 8 months pygfx/wgpu-py#142
23 radis/radis 7 months radis/radis#222
24 pytroll/pyorbital 7 months pytroll/pyorbital#79
25 FCP-INDI/C-PAC 4 months FCP-INDI/C-PAC#1548
26 pymc-devs/pymc-examples 3 months pymc-devs/pymc-examples#198
27 FCP-INDI/C-PAC_GUI 2 months FCP-INDI/C-PAC_GUI#114
28 pytroll/pyspectral 2 months pytroll/pyspectral#132
29 codezonediitj/pydatastructs a month codezonediitj/pydatastructs#421
30 bacloud22/so-cards a month bacloud22/so-cards#6
31 spyder-ide/qtawesome a month spyder-ide/qtawesome#178
32 openteamsinc/closember 24 days openteamsinc/closember#7
33 rse-asia/OLS-4 19 days rse-asia/OLS-4#1
34 jupyter/papyri 18 days jupyter/papyri#17
35 P403n1x87/austin-vscode 15 days P403n1x87/austin-vscode#19
36 MeeseeksBox/MeeseeksDev 10 days MeeseeksBox/MeeseeksDev#55

Add Your Repositories

Those are suggested metrics, they are of course not absolute. Your community should have its own goal, though be careful about the Normalization of deviance. You can also suggest metrics, send us a PR, or open an issue.

Show your support : 39 Supporters

Star our repository to show your support even if your own organizations or projects don't participate Star


Maintainers in Open Source

The Role of a Maintainer in Open-Source is rarely about simply writing more code or getting more Pull-Requests. It is about properly caring, knowing how to say “No” and thinking about long term sustainability.

Having a well-setup process, not too many tasks running at the same time, can be critical for Maintainers cognitive load, and mental health, as well as provide an easier environment for new contributors.

When projects have fewer open pull requests, and well curated issues that are closed when not relevant it is easier to get timely reviews. As a result maintainers more easily avoid duplicate work, have less risk of code conflicts, and have an easier time finding potential duplicate bugs.

Fewer tasks, and less stress also lead to friendlier interactions.

Therefore, we encourage contributions to Closember. Work with your favorite maintainers, on your favorite repositories to decrease the number of opened issues and pull-requests for a more dynamic, better maintained, cleaner, leaner, environment and ecosystem.

We also encourage you to avoid duplicate work by merging similar projects when relevant.

Join us to close issues and PRs

The tables below tracks multiple metrics to help you achieve goals. There are no good, or bad metrics, but it is fun to be able to compare.

Please be careful about project guidelines and whether an issue should be closed, some projects close issues/PR that have not been commented on in a while, some others only close issues when it is resolved and a release has been made. If you are ever in doubt, ask.

Zeno Paradox

… you keep closing them but new ones keep opening. This is why issues or pull-requests opened during November do not count toward the total. This is not meant to disrupt the normal flow of work, but to encourage you to help maintainers take care of older issues and pull-requests.

What should I do?

This is about you first; you need to be in a good mental state in order to help others. Personally I’ll walk in circles for about 2 hours, tidy my desk, remove extra icons for my desktop, and also try to decrease my amount of unread emails. Like can I get under 1000? Another trick is to find a couple of things and click “unsubscribe”, it can be emails, or slack channels or un-follow people on twitter/facebook/instagram.

Once you feel great about yourself go help others. What you just did for yourself here, you can now do for the maintainers of your favorites projects, and make those project better for everyone.

Maintainers: How to get ready:

How can I help other?

Great question! You often do not need to know how to code to contribute to Closember! For any project you contribute to, make sure to check their guidelines, and avoid eager closing of issues/PRs if that’s not the desire of the maintainers. The following guide is intended to be adapted to your skills and skills that can be of use for projects.

It will be less work for the maintainers, and they’ll close the issue for you.

How to be listed on this leader-board ?

Add the closember topic to your repositories. Next time the site is updated you’ll be listed.

Why is the score not changing ?

GitHub requests are cached for a few minutes, maybe 1 maybe 10, maybe 60, depend on my mood, or how much traffic we get. It should update soon. But please relax. It’s not a sprint, it’s a marathon.

Show me this website code

https://github.com/openteamsinc/closember – please come close issues.

I closed all my issues / I really want to code…

Ok, fine, you want an excuse to write some code. Still you can do things the make maintainer life easier. A couple pet peeves of mine.

I want to lean more about Open-Source

While we haven’t read it yet, we recommend Working in Public: The Making and Maintenance of Open Source Software by Nadia Eghbal

Do I get a Lousy T-Shirt ?

Open-teams, FairOSS and Quansight are working on this, and how we can sponsors this better. Likely not this year, but we’ll see for next. It is also a tough problem as not everyone can close any issue, so come talk to us if you want to find a way for user to claim having helped and maintainers to validate those claims.

Partners

Closember is currently sponsored by Quansight, FairOSS and OpenTeams.

F.A.Q. with creator

Comments

Comments on the Following GitHub Issue will appear below.