Skip to content

Latest commit

 

History

History
71 lines (58 loc) · 2.59 KB

automate-dependency-repology.md

File metadata and controls

71 lines (58 loc) · 2.59 KB
collaborating_projects desc difficulty initiatives issues markdown mentors name requirements status tags
repology
coala
Improve coala's dependency installation and management, by automating using data from repology.
medium
GSoC18
RGSoC
automate-dependency-repology.md
waldyrious
fexpr
underyx
Automation of Dependency Management using Repology
At least one patch to the coala core should be accepted and merged.
The proposal needs to show some familiarity with coala's dependency management implementation.
disabled
Automation
Installation
Dependency
Web

coala-bears are of two types, Native Bears which implement all the buisness logic themselves and Linter Bears which wrap existing linters and checkers.

These Linter Bears have dependencies which need to be installed before they can be executed. In this project, you're to improve on the current strategies of installing these dependencies.

Repology is a packaging hub. It analyzes a lot of package repositories and other sources, comparing packages versions across them and gatherinng relevant information. It shows you in which repositories a given project is packaged, which version is the latest and which needs updating, who maintains the package, and other related information. The student has to use this information and implement improvments to the automated management of dependencies.

The scope of a complete soultion is too large. The student should come up with suitable scope and make a proposal accordingly.

Milestones

PREPARATION/BONDING
  • The applicant has identified most of the related problems.
  • The applicant has came up with a complete workflow of how dependencies would be managed across multiple operating systems and package managers.
  • The Student has at least one Linter Bear connected with Repology ID.
CODING PHASE 1
  • All the existing LinterBears and Package Manager classes are connected with their respective Repology IDs.
  • Documentation added on how to do the same for new Linter Bears to Writing Linter Bears
CODING PHASE 2
  • The applicant has implemented a system for fetching data from Repology.
  • The applicant has wrote sufficent tests and documentation for the same.
  • At least part of the scope has been implemented and tested.
CODING PHASE 3
  • The proposed scope is completly implemented and tested.