Open Exchange Quality Statistics
In my recent post Quality of Open Exchange packages, I tried to raise attention on
Pull Requests and Issues (on GitHub).
I could count the replies on 1 hand. Special Thanks to the French Community!
I see the role of a Pull Request as a proposal to fix a problem in the submitted package.
- If you agree you Merge it
- If you disagree you Close it
Both actions signal to the creator of the PR that you got the message.
Doing Nothing, leaving it Pending is not just an unfriendly act to the creator but
also to anyone.of the community who wants to consume the repo. He is just left in the lurge.
We actually have 848 Applications in OEX. But I see in 117 packages 374 PullRequest pending
.png)
And the affected packages are well known.
I have anonymized them as far as required. So it's no personal finger-pointing.
| PullReq | Packages | Repos |
|---|---|---|
| 143 | 17 | intersystems-community |
| 34 | 2 | * |
| 31 | 5 | * |
| 25 | 8 | * |
| 20 | 4 | intersystems-ib |
| 16 | 8 | intersystems |
| 12 | 6 | * |
| 8 | 8 | intersystems-ru |
| 7 | 2 | * |
| 7 | 5 | * |
| 6 | 1 | * |
| 6 | 4 | * |
| 5 | 1 | * |
| 4 | 3 | * |
| 4 | 4 | * |
| 3 | 1 | * |
| 3 | 2 | * |
| 3 | 2 | * |
| 3 | 2 | * |
| 3 | 3 | * |
| 3 | 3 | * |
| 3 | 3 | * |
| 2 | 1 | * |
| 2 | 1 | * |
| 2 | 2 | * |
| 2 | 2 | * |
| 1 | 1 | * |
| 1 | 1 | * |
| 1 | 1 | * |
| 1 | 1 | * |
| 1 | 1 | * |
| 1 | 1 | * |
| 1 | 1 | * |
| 1 | 1 | * |
| 1 | 1 | * |
| 1 | 1 | * |
| 1 | 1 | * |
| 1 | 1 | * |
| 1 | 1 | * |
| 1 | 1 | * |
| 1 | 1 | * |
| 1 | 1 | * |
| 1 | 1 | * |
43 row(s) affected
The roles of Issues are a bit more complicated.
- It can be a bug, but there is no known solution available.
- It can be a request for enhancement with no code proposal
- Sometimes it is just a comment
So immediate action could be impossible.
Anyhow the general goal is to have as few issues s possible.
Actually I also see in 281 packages 843 Open Issues
.png)
The list is shortened to repos with > 2 issues
| Issues | Packages | Repos |
|---|---|---|
| 178 | 21 | intersystems-community |
| 146 | 9 | intersystems |
| 86 | 15 | intersystems-ru |
| 28 | 3 | * |
| 22 | 2 | * |
| 13 | 1 | * |
| 12 | 2 | * |
| 11 | 2 | * |
| 10 | 3 | * |
| 9 | 1 | * |
| 6 | 1 | * |
| 6 | 1 | * |
| 4 | 1 | * |
| 4 | 1 | * |
| 4 | 1 | * |
| 4 | 1 | * |
| 4 | 1 | * |
| 3 | 1 | * |
| 3 | 1 | * |
| 3 | 1 | * |
| 3 | 1 | * |
| 3 | 1 | * |
| 3 | 1 | * |
| 3 | 1 | * |
24 row(s) affected
I hope you agree that there is room for improvement.
And I also want to remind you that this is not just a matter of statistics
but much more a matter of credibility of OEX which depends on your contributions.
I really count on your help and cooperation
Comments
Hi @Robert Cemper ,
Stats very interesting to know.
I'm glad to read the French Community is reactive 😄.
This weekend I've been working on integrating code from @Theo Stolker and bug fixes about openapi-suite. I was very happy to have a contribution.
I noticed all issues (tasks for improvement in fact) of a project currently in active development were opened, but already done. With Kanban it's not enough to move an issue to "done status", we have to close explicitly. I probably raised your stats with this repository journal-indexer.
Thanks.
This matches my experience. Issues require explicit Close to vanish from main-page counter.
@Robert Cemper - thank you very much for all the ways in which you strive to continue to make out Community better! I am sure this took time to pull together - I hope it gets traction.
Thank you for the motivation!