RFC: Graph-Based Popularity Metric for Packages (Issue #833)#834
Open
mohityadav8 wants to merge 1 commit intoaboutcode-org:mainfrom
Open
RFC: Graph-Based Popularity Metric for Packages (Issue #833)#834mohityadav8 wants to merge 1 commit intoaboutcode-org:mainfrom
mohityadav8 wants to merge 1 commit intoaboutcode-org:mainfrom
Conversation
Signed-off-by: Mohit <mohityadav8@users.noreply.github.com>
9f06a87 to
75bd1a9
Compare
Author
|
@pombredanne @pombredanne @AyanSinhaMahapatra can u merge this |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR introduces a structured RFC proposing a graph-based popularity metric for packages in PurlDB.
The proposal is based on local exploration of the data model, particularly the Package and DependentPackage models, and outlines a dependency-graph-based approach to computing popularity.
The goal is to align on architectural direction before moving to implementation.
Feedback from maintainers would be greatly appreciated.
Related to #833.