Comments (7)
Have a look at git://git.lwn.net/gitdm.git
@ditzlike is currently also trying to find out how it's exactly generating graphs.
from pasta.
You should look at the bitergia / patchwork stuff. There might already be some preexisting work.
from pasta.
Oh. I kind of expected this though, will check it out
from pasta.
We are already considering this for a while. The appropriate time scale is probably every full release cycle, because the differences per week are mainly dependent where we are in the release cycle. Further, patches accepted/rejected/ignored can only be determined after a few weeks/months when they show up in the git repositories.
Now to the specific stats:
- ignored patches: is actually quite stable, and quite independent of subsystem; more dependent on the contributor.
- top patch submitters: doable, very similar to top git authors, though.
- top reviewers: Anmol is actually looking into exactly that at the moment.
- LoC added/deleted: Jonathan Corbet already collects and presents that information.
from pasta.
I consider off-list patches interesting (because they are changing over time and interesting for other reasons). Also, top reviewers is interesting, but the really interesting aspect is to present author-reviewer-file relationships in a comprehensible manner (that is pretty stable over time, though.).
from pasta.
We are already considering this for a while. The appropriate time scale is probably every full release cycle, because the differences per week are mainly dependent where we are in the release cycle.
Makes sense. Anyway the timescale shouldn't reallly have an impact on the implementation.
Further, patches accepted/rejected/ignored can only be determined after a few weeks/months when they show up in the git repositories.
Oh yes. That's something that I missed. Do you have any solution for this as you mentioned ignored patches
in the list of stats.
Also we can report threads that have been most actively discussed by the community.
Applying some NLP methods for sentiment analysis may allow us to discover the most polarising threads.
The stability of various subsystem as a function of bug reports is also going to be an interesting metric.
from pasta.
Any idea how these statistics are currently generated by lwn?
from pasta.
Related Issues (20)
- Combine PaStA with the cregit tool
- Compute relation between patch series HOT 8
- Collect user feedback on relating patches in patchwork tool to improve Pasta
- Determine the relevant entries and maintainers for a provided list of files
- [GSOC] Add a requirements.txt to make setup easier HOT 6
- Fix erroneous behaviour in LinuxMaintainers HOT 8
- Analysis jailhouse repo with PaSta HOT 19
- Readme mentions 4 steps but only 3 are explicitly mentioned HOT 5
- Running "pasta analyse succ" in mbox mode doesnt show appropriate error message HOT 5
- Patch groups file is not created HOT 6
- Support identification of kernel developers for improving the precision of analysis HOT 3
- Update Readme for Getting PaStA HOT 5
- Create a ML model for the patch recipients based on the recipients of sent patches HOT 9
- Derive a rule set for the patch recipients based on the existing email data
- Introduce Redis to handle resources HOT 3
- `git -C resources submodule update` is taking a huge amount of time HOT 6
- set_config shows invalid literal for int with base 10 HOT 11
- git and MAINTAINERS only: plot mailing lists over time HOT 1
- Have an option to only run representative analyses (No repository required) HOT 9
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from pasta.