Identification of statistical metric(s) to determine anchor packages for Maven ecosystem

abs51295 commented 7 years ago

Epic: #1250

User Story

As an OSIO developer, I will be able to get better outlier recommendations for Maven ecosystem so that I can refine my chosen Maven stack.

Description

After the identification of sub-ecosystems ( #1291 ) we need to determine the set of metrics with which to identify anchor packages.

Acceptance Criteria

System should be able to provide a list of all anchor packages for Maven ecosystem.

Task list

[x] Identify a set of statistical metric(s).
[x] Test if the identified statistical metric(s) are generalized enough to work for every identified subgroup.
[x] If the above task fails, then go back to task 1 and repeat the process.

miteshvp commented 6 years ago

@abs51295 - you can assign yourself when you actually start working on it. Till then no assignment

abs51295 commented 6 years ago

@miteshvp I think the problem was trivially solved since we decided to move with mvn repository's download statistics. Assigning it to me and taking this is in current sprint goals.

abs51295 commented 6 years ago

Top 30% packages for identified sub-ecosystems [ #1291 ] were chosen as anchor packages. Artifact usages from mvnrepository were taken as the primary metric to identify top 30% packages for the sub-ecosystems.

openshiftio / openshift.io