It's a wrap for 2021, Prepare for 2022

image/svg+xml

And we are all done for 2021 ! Thanks to all the participants, we are already working on preparing 2022, your help is welcomed ! Please come contribute to the closember repo

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

2459 / 11411

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,

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

Start Closing Issues

Metric collections have stopped since Dec 1st, you can still tag your repo with the closember tag to see how well you did, and get ready for next year.

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

Placeholder values : Will be reset to 0 on Nov 1st when Closember starts.

# Repository Closed Issues Closed/Merged PRs
1 scipy/scipy 357 188
2 datalad/datalad 333 25
3 PyCQA/pylint 301 20
4 spyder-ide/spyder 150 30
5 thanos-io/thanos 104 51
6 ipython/ipython 121 22
7 jupyter/notebook 122 8
8 astropy/astroquery 62 37
9 vispy/vispy 93 4
10 arviz-devs/arviz 42 31
11 pymc-devs/pymc-examples 40 9
12 poliastro/poliastro 36 10
13 pytroll/satpy 23 16
14 FCP-INDI/C-PAC 28 5
15 PyCQA/astroid 23 8
16 spyder-ide/qtpy 17 3
17 pygfx/pygfx 13 5
18 icesat2py/icepyx 13 5
19 tqdm/tqdm 12 4
20 radis/radis 11 5
21 ipython/ipykernel 10 4
22 pytroll/pyresample 5 4
23 physiopy/phys2bids 5 2
24 pytroll/pyorbital 1 3
25 pygfx/wgpu-py 3 1
26 FCP-INDI/fcp-indi.github.io 1 3
27 spyder-ide/qtawesome 2 1
28 ipython/traitlets 3 0
29 FCP-INDI/C-PAC_GUI 1 2
30 timofurrer/awesome-asyncio 0 2
31 rse-asia/OLS-4 2 0
32 pytroll/pyspectral 1 1
33 bacloud22/so-cards 2 0
34 P403n1x87/austin-vscode 1 1
35 MeeseeksBox/MeeseeksDev 0 2
36 FCP-INDI/cpac 1 1
37 FCP-INDI/.github 0 2
38 physiopy/phys2denoise 0 1
39 openteamsinc/closember 1 0
40 jupyter/papyri 1 0
41 codezonediitj/pydatastructs 1 0
42 ayan-biswas0412/AlgoDocs 0 1
43 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

Placeholder values : Will be reset to 0 on Nov 1st when Closember starts.

# Repository Open Issues Open PRs
1 FCP-INDI/.github 0 0
2 openteamsinc/closember 4 0
3 bacloud22/so-cards 5 0
4 rse-asia/OLS-4 5 0
5 FCP-INDI/app-C-PAC-brainlife.io 7 0
6 P403n1x87/austin-vscode 8 0
7 spyder-ide/qtpy 8 2
8 pygfx/wgpu-py 12 1
9 FCP-INDI/cpac 13 1
10 spyder-ide/qtawesome 14 2
11 ayan-biswas0412/AlgoDocs 13 5
12 physiopy/phys2denoise 16 6
13 pytroll/pyspectral 17 5
14 pytroll/pyorbital 16 7
15 timofurrer/awesome-asyncio 0 30
16 MeeseeksBox/MeeseeksDev 31 2
17 FCP-INDI/C-PAC_GUI 32 6
18 icesat2py/icepyx 38 9
19 jupyter/papyri 47 0
20 physiopy/phys2bids 42 7
21 pygfx/pygfx 52 3
22 radis/radis 55 7
23 codezonediitj/pydatastructs 58 13
24 FCP-INDI/fcp-indi.github.io 68 4
25 pytroll/pyresample 76 8
26 ipython/traitlets 89 10
27 poliastro/poliastro 93 23
28 pymc-devs/pymc-examples 100 16
29 PyCQA/astroid 140 22
30 arviz-devs/arviz 156 12
31 thanos-io/thanos 184 39
32 ipython/ipykernel 212 21
33 vispy/vispy 267 29
34 FCP-INDI/C-PAC 330 10
35 tqdm/tqdm 287 80
36 pytroll/satpy 303 84
37 astropy/astroquery 435 55
38 datalad/datalad 528 21
39 PyCQA/pylint 621 37
40 spyder-ide/spyder 1107 63
41 ipython/ipython 1450 78
42 scipy/scipy 1399 322
43 jupyter/notebook 1982 51
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)

Placeholder values : Will be reset to 0 on Nov 1st when Closember starts.

# Repository Closed After Oldest issue closed
1 ipython/ipython 10 years ipython/ipython#894
2 scipy/scipy 8 years scipy/scipy#629
3 astropy/astroquery 8 years astropy/astroquery#222
4 datalad/datalad 7 years datalad/datalad#3
5 vispy/vispy 7 years vispy/vispy#379
6 spyder-ide/spyder 6 years spyder-ide/spyder#1922
7 PyCQA/pylint 6 years PyCQA/pylint#507
8 jupyter/notebook 5 years jupyter/notebook#1150
9 spyder-ide/qtpy 5 years spyder-ide/qtpy#66
10 tqdm/tqdm 4 years tqdm/tqdm#461
11 arviz-devs/arviz 3 years arviz-devs/arviz#2
12 poliastro/poliastro 3 years poliastro/poliastro#365
13 pytroll/satpy 2 years pytroll/satpy#583
14 thanos-io/thanos 2 years thanos-io/thanos#1375
15 physiopy/phys2bids 1 year, 7 months physiopy/phys2bids#211
16 PyCQA/astroid 1 year, 5 months PyCQA/astroid#798
17 pygfx/pygfx 1 year, 5 months pygfx/pygfx#33
18 icesat2py/icepyx 1 year, 3 months icesat2py/icepyx#106
19 ipython/traitlets 9 months ipython/traitlets#490
20 radis/radis 7 months radis/radis#222
21 ipython/ipykernel 5 months ipython/ipykernel#693
22 pymc-devs/pymc-examples 3 months pymc-devs/pymc-examples#198
23 bacloud22/so-cards a month bacloud22/so-cards#6
24 spyder-ide/qtawesome a month spyder-ide/qtawesome#178
25 openteamsinc/closember 24 days openteamsinc/closember#7
26 rse-asia/OLS-4 19 days rse-asia/OLS-4#1
27 jupyter/papyri 18 days jupyter/papyri#17
28 P403n1x87/austin-vscode 12 days P403n1x87/austin-vscode#15
29 pytroll/pyresample 2 days pytroll/pyresample#390
30 codezonediitj/pydatastructs 2 days codezonediitj/pydatastructs#433

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.