librariesio / libraries.io Goto Github PK

Default to the github owner avatar

Where available, check atom feed/scrape a webpage/follow twitter feed to find new releases on registries without having to download the whole archive.

This should mean that we're more up to date, more often.

Rather than comma seperated strings

People change their github user names, repo names and transfer repo ownership, we should record the github id for users, orgs and repos and then keep the names up to date.

Group related repos together, i.e. nodebots, not really sure how to do this automatically, most likely community curated.

Useful links to things related to a project:

• books
• screencasts
• tutorials
• slide decks and talks
• stack overflow
• searchcode
• podcasts

Community organised categorization of projects, similar to https://www.ruby-toolbox.com/

Company pages, grouping projects and members belonging to orgs from github or bitbucket.

Dependent on #1040

Omniauth provider for twitter: https://github.com/arunagw/omniauth-twitter

Dependent on #1040

Omniauth plugin for bitbucket: https://github.com/sishen/omniauth-bitbucket

{"type"=>"MIT"} should be MIT

e.g. http://libraries.io/projects/127377-amber

Show install instructions for relevant package manager

Allow logged in users to correct or fill in missing details we've gathered on project pages (with some form of moderation).

http://libraries.io/projects/112830-twitter-bootstrap

Pages for each language with popular, trending and new projects and biggest users

On a project page you should be able to see projects that are similar to the one you're looking at, with the aim of that wikipedia-style discovery mechanism of bouncing between related things.

Most likely based on matches from title, description, keywords, rather than language and platform.

Use elasticsearch more like this to begin with.

Potential schema:

dependency_id: integer (project that it depends on)
requirements: string (versions allowed, optional)
version_id: integer (version of project)
project_id: integer (prefer versions but some registries might need this)

Faye is available via npm and rubygems:

https://github.com/faye/faye
https://rubygems.org/gems/faye
https://www.npmjs.com/package/faye/

Once dependencies are being stored we can show projects that depend on a given project.

This is another way of exploring related projects and also highlighting the most depended on projects as a sign of popularity.

On the project page, show the highest voted questions where the question or answer has one of the project urls in it.

Message boards and other features to bring communities together

• irc
• slack
• gitter
• other

Show the changes in each release, either via a changelog file or pulling commits from the repo.

Depends on #35

I think it's related to the persistant http class

Show warnings about:

• lack of license
• conflicting licenses between package and source
• unknown license
• conflicting dependency licenses

• rest
• webhooks
• rss/atom
• stream

git://github.com/amber-smalltalk/amber.git#0.14.1 should be https://github.com/amber-smalltalk/amber

Keep a copy of the source code of every version of every project.

Also make it available for download in case the registry goes down or away.

Dependent on #46

Show ways to improve your projects like:

• add a license
• add a homepage link
• fix warnings about deprecated/unmaintained/removed/conflicting dependencies

Trawl through all the forks on a project and highlight interesting divergent forks.

Newsfeeds for every project, highlighting new releases, maintainer changes and github activity.

Quite adventurous but very useful for people working in tightly controlled environments.

For a particular version, take the tarball provided by the registry and compare/diff it to the tagged release in the source control.

The idea being to highlight if there are any differences between the public source and the released package, i.e. sneaky code or undocumented features.

Depends on #35

For registries that don't have versions, it would be good to show git tags instead.

Suggest repos to people based on github stars or projects contributed to.

Potential option: https://github.com/PredictionIO/PredictionIO

For projects that aren't on github, download the source and work it out using https://github.com/github/linguist

Some repos keep them separately, try to get an email address so we can tie it to a user record and avatar.

Proper full text search with the following

• Language facet/filter (Ruby, Elixir etc)
• License facet/filter (MIT, GPL etc)
• Platform facet/filter (npm, Hex etc)
• Sort by stars
• Sort by updated
• Sort by created
• Exact match support
• Facet filters to allow for drill down filtering

Likely using https://github.com/benbalter/licensee or https://github.com/pivotal/LicenseFinder

Should be ordered by each number in turn, maybe use https://github.com/dazuma/versionomy

• Help wanted
• Maintainers wanted

Ensure no duplications with validations

Links to download the raw package tarball for each package manager

Allow people to leave reviews or star ratings on projects, mostly to highlight poor quality projects.

Prove you are this person, also store oauth token for pulling data from the github api

Show security advisories against insecure versions.

Sources:

• https://github.com/FriendsOfPHP/security-advisories
• https://github.com/rubysec/ruby-advisory-db
• http://www.cvedetails.com
• https://nodesecurity.io/advisories
• https://github.com/requires/monitoring
• https://github.com/bekk/retire.js
• https://github.com/presidentbeef/brakeman

Pull in docs folders or generated docs like yard for each version.

Depends on #35

Trying to be as similar as the Github repos for now, using the api: https://confluence.atlassian.com/display/BITBUCKET/Use+the+Bitbucket+REST+APIs

Active/inactive based on version releases and commits on repo

Supported

• Hex
  • include dependencies
• Dub
  • include dependencies
• NPM
  • include dependencies
• Packagist
  • include dependencies
• Cargo
  • include dependencies
• Rubygems
  • include dependencies
• CRAN http://cran.r-project.org/web/packages/available_packages_by_name.html
  • include dependencies
• Elm http://package.elm-lang.org/packages
  • include dependencies
• CPAN http://www.cpan.org/modules/01modules.index.html https://github.com/CPAN-API/cpan-api
  • include dependencies
• Atom https://atom.io/packages/list
  • include dependencies
• Nuget
  • include dependencies
• Maven
  • include dependencies
• Wordpress http://codex.wordpress.org/WordPress.org_API
  • include dependencies
• Go http://go-search.org/api?action=packages
  • include dependencies
• Meteor https://atmospherejs.com/packages/recent
  • include dependencies
• Clojure https://github.com/ato/clojars-web/wiki/Data
  • include dependencies
• Cocoapods https://github.com/CocoaPods/Specs/tree/master/Specs
  • include dependencies
• Julia https://github.com/JuliaLang/METADATA.jl
  • include dependencies
• Homebrew http://brewformulas.org/
  • include dependencies
• Nimble
  • include dependencies
• PyPi
  • include dependencies
• Bower
  • include dependencies
• Hackage
  • include dependencies

Unsupported

• CTAN http://www.ctan.org/pkg
  • include dependencies
• Vim http://www.vim.org/scripts/script_search_results.php?order_by=creation_date&direction=descending
  • include dependencies
• Smalltalk http://smalltalkhub.com/
  • include dependencies
• Opam https://github.com/ocaml/opam-repository
  • include dependencies
• Lua rocks http://rocks.moonscript.org/manifest
  • include dependencies
• Pascal http://wiki.freepascal.org/fppkg
  • include dependencies
• Common Lisp http://www.quicklisp.org/beta/releases.html
  • include dependencies
• Erlang rebar https://github.com/rebar/rebar
  • include dependencies
• C https://github.com/clibs/clib/wiki/Packages
  • include dependencies
• Bash http://www.bpkg.io/packages/name/ http://modulereg.vertx.io/
  • include dependencies
• Puppet https://forge.puppetlabs.com/modules?utf-8=%E2%9C%93
  • include dependencies
• Ansible https://galaxy.ansible.com/
  • include dependencies
• Chef https://supermarket.chef.io/
  • include dependencies
• Nix http://nixos.org/nixpkgs/
  • include dependencies
• Titanium http://gitt.io/
  • include dependencies
• Phonegap http://plugreg.com/
  • include dependencies
• Conda https://github.com/conda/conda-recipes
  • include dependencies
• Erlang https://github.com/ninenines/erlang.mk/blob/master/packages.v2.tsv
  • include dependencies
• Emacs, gnu default db, marmalade, melpa
  • include dependencies

People write their licenses in all kinds of weird ways, we should try to match the license name with one from http://spdx.org/licenses/, otherwise group it into "other".