Project Idea: DepHub

Transcript

1. Project Idea: by Thomas Gossmann github.com/gossi gos.si

2. Goals • Organize Projects • Manage Dependencies • Metrics •

   Analysis

3. Organize Projects • Keep Metadata in sync with your primary

   package manager file (bower.json, composer.json, etc) • Make Metadata searchable for end-users

4. Manage Dependencies • Deploy your project to various dependency managers

   – Bower – Volo – Npm – Composer – Rails – etc.

5. Manage Dependencies • Remove the burden of manually publishing you

   package to package managers (you will miss some) • Of course... automatically (e.g. github service hooks) • Makes them consumable as if you published them to package managers on your own

6. Manage Dependencies • Goal #1: Write once, publish everywhere •

   Goal #2: Let people stay with their ONE favorite package manager The main idea behind DepHub

7. Metrics • Consume Metrics from various package managers and display

   them per project • Example: Downloads – Composer: 235 – Bower: 3143 – Volo: 34 – Total: 3412 • Weekly metrics to see trends

8. Metrics • Gather statistics around projects, examples: – Project-Level: KNP

   Bundles http://knpbundles.com/about/faq-scoring – Language-Level: Scrutinizer https://scrutinizer-ci.com/ – Package-Manager-Level: SensioLabsInsight https://insight.sensiolabs.com/ • Gather and integrate online sources: ohloh, coveralls, github-stars, ...

9. Metrics • Goal: Create metrics around projects to help people

   make decisions on which package/library they want to use

10. Analytics • Analyze your projects: – Check wether your dependencies

    are up-to-date – Run security checks

11. Project Idea: by Thomas Gossmann github.com/gossi gos.si