https://github.com/andrew/rubygems

Library packaging and distribution for Ruby.

https://github.com/andrew/rubygems

Science Score: 10.0%

This score indicates how likely this project is to be science-related based on various indicators:

  • CITATION.cff file
  • codemeta.json file
  • .zenodo.json file
  • DOI references
  • Academic publication links
  • Committers with academic emails
    9 of 1275 committers (0.7%) from academic institutions
  • Institutional organization owner
  • JOSS paper metadata
  • Scientific vocabulary similarity
    Low similarity (14.5%) to scientific vocabulary

Keywords from Contributors

authorization oauth2 oauth2-client oidc oidc-client syntax-highlighting workflow-engine orchestration data-engineering bioinformatics
Last synced: 9 months ago · JSON representation

Repository

Library packaging and distribution for Ruby.

Basic Info
  • Host: GitHub
  • Owner: andrew
  • License: other
  • Language: Ruby
  • Default Branch: master
  • Homepage: https://rubygems.org/
  • Size: 191 MB
Statistics
  • Stars: 0
  • Watchers: 0
  • Forks: 0
  • Open Issues: 0
  • Releases: 0
Fork of rubygems/rubygems
Created over 1 year ago · Last pushed over 1 year ago

https://github.com/andrew/rubygems/blob/master/

# RubyGems [![Maintainability](https://api.codeclimate.com/v1/badges/30f913e9c2dd932132c1/maintainability)](https://codeclimate.com/github/rubygems/rubygems/maintainability)

RubyGems is a package management framework for Ruby.

A package (also known as a library) contains a set of functionality that can be invoked by a Ruby program, such as reading and parsing an XML file.
We call these packages "gems" and RubyGems is a tool to install, create, manage and load these packages in your Ruby environment.

RubyGems is also a client for [RubyGems.org](https://rubygems.org), a public repository of Gems that allows you to publish a Gem
that can be shared and used by other developers. See our guide on publishing a Gem at [guides.rubygems.org](https://guides.rubygems.org/publishing/)

## Getting Started

Installing and managing a Gem is done through the `gem` command. To install a Gem such as [Nokogiri](https://github.com/sparklemotion/nokogiri) which lets
you read and parse XML in Ruby:

    $ gem install nokogiri

RubyGems will download the Nokogiri Gem from RubyGems.org and install it into your Ruby environment.

Finally, inside your Ruby program, load the Nokogiri gem and start parsing your XML:

    require 'nokogiri'

    Nokogiri.XML('

Hello World

') For more information about how to use RubyGems, see our RubyGems basics guide at [guides.rubygems.org](https://guides.rubygems.org/rubygems-basics/) ## Requirements * RubyGems supports Ruby 3.0 or later. ## Installation RubyGems is already installed in your Ruby environment, you can check the version you have installed by running `gem --version` in your terminal emulator. In some cases Ruby & RubyGems may be provided as OS packages. This is not a recommended way to use Ruby & RubyGems. It's better to use a Ruby Version Manager, such as [rbenv](https://github.com/rbenv/rbenv) or [chruby](https://github.com/postmodern/chruby). If you still want to use the version provided by your OS package manager, please also use your OS package manager to upgrade rubygems, and disregard any other installation instructions given below. If you would like to manually install RubyGems: * Download from https://rubygems.org/pages/download, unpack, and `cd` into RubyGems' src * OR clone this repository and `cd` into the repository Install RubyGems by running: $ ruby setup.rb For more details and other options, see: $ ruby setup.rb --help ## Upgrading RubyGems To upgrade to the latest RubyGems, run: $ gem update --system See [UPGRADING](doc/bundler/UPGRADING.md) for more details and alternative instructions. ## Release policy RubyGems and Bundler are released in sync, although they do not share their major version number. It is planned that also their major version numbers will be sync'ed in the future. The release policy is somewhat similar to the release policy of Ruby itself: * Frequent patch releases (every 2-4 weeks) including bug fixes, minor enhancements, small features, or even medium sized features declared as experimental for battle testing. * Yearly minor releases including bigger features, and minor breaking changes (affecting only edge cases and a very small set of users). * Occasional major releases (replacing yearly minors) including major breaking changes. ## Documentation RubyGems uses [rdoc](https://github.com/rdoc/rdoc) for documentation. A compiled set of the docs can be viewed online at [rubydoc](https://www.rubydoc.info/github/rubygems/rubygems). RubyGems also provides a comprehensive set of guides which covers numerous topics such as creating a new gem, security practices and other resources at https://guides.rubygems.org ## Getting Help ### Filing Tickets Got a bug and you're not sure? You're sure you have a bug, but don't know what to do next? In any case, let us know about it! The best place for letting the RubyGems team know about bugs or problems you're having is [on the RubyGems issues page at GitHub](https://github.com/rubygems/rubygems/issues). ### Bundler Compatibility See https://bundler.io/compatibility for known issues. ### Supporting RubyGems is managed by [Ruby Central](https://rubycentral.org), a non-profit organization that supports the Ruby community through projects like this one, as well as [RubyConf](https://rubyconf.org), [RailsConf](https://railsconf.org), and [RubyGems.org](https://rubygems.org). You can support Ruby Central by attending or [sponsoring](sponsors@rubycentral.org) a conference, or by [joining as a supporting member](https://rubycentral.org/#/portal/signup). ### Contributing If you'd like to contribute to RubyGems, that's awesome, and we <3 you. Check out our [guide to contributing](doc/rubygems/CONTRIBUTING.md) for more information. ### Code of Conduct Everyone interacting in the RubyGems projects codebases, issue trackers, chat rooms, and mailing lists is expected to follow the [contributor code of conduct](https://github.com/rubygems/rubygems/blob/master/CODE_OF_CONDUCT.md).

Owner

  • Name: Andrew Nesbitt
  • Login: andrew
  • Kind: user
  • Location: Bristol, UK
  • Company: @ecosyste-ms and @octobox

Working on mapping the world of open source software @ecosyste-ms and empowering developers with @octobox

GitHub Events

Total
  • Push event: 19
Last Year
  • Push event: 19

Committers

Last synced: 9 months ago

All Time
  • Total Commits: 23,513
  • Total Committers: 1,275
  • Avg Commits per committer: 18.442
  • Development Distribution Score (DDS): 0.797
Past Year
  • Commits: 259
  • Committers: 20
  • Avg Commits per committer: 12.95
  • Development Distribution Score (DDS): 0.34
Top Committers
Name Email Commits
David Rodríguez d****z@r****t 4,772
Eric Hodel d****n@s****t 3,076
Andre Arko a****e@a****t 2,175
Samuel Giddins s****s@s****e 1,590
Hiroshi SHIBATA h****t@r****g 1,226
Jim Weirich j****h@g****m 592
Ryan Davis r****y@z****m 427
The Bundler Bot b****t@b****o 409
Terence Lee h****2@g****m 392
José Valim j****m@g****m 369
Carl Lerche c****e@m****m 299
Chad Fowler c****d@c****m 278
dependabot[bot] 4****]@u****m 277
bronzdoc l****0@g****m 272
Aaron Patterson a****n@g****m 211
Nobuyoshi Nakada n****u@r****g 180
Carlhuda c****a@e****m 174
Colby Swandale c****y@t****m 137
Evan Phoenix e****n@f****t 134
Richard Kilmer r****h@i****m 127
Asutosh Palai a****i@g****m 123
Colby Swandale me@c****i 120
Daniel Berger d****6@g****m 120
James Wen j****5@c****u 115
Ellen Marie Dash me@d****o 104
Erik Hollensbe e****k@h****g 104
wycats w****s@g****m 103
Smit Shah w****8@g****m 101
Ian Ker-Seymer i****r@g****m 101
Evan Phoenix e****n@p****o 92
and 1,245 more...