JezK
Edit File: page-CONTRIBUTING_rdoc.ri
U:RDoc::TopLevel[ i I"CONTRIBUTING.rdoc:ETcRDoc::Parser::Simpleo:RDoc::Markup::Document:@parts[:S:RDoc::Markup::Heading: leveli: textI"How to contribute;To:RDoc::Markup::BlankLine o:RDoc::Markup::Paragraph;[I"PCommunity involvement is essential to RubyGems. We want to keep it easy as ;TI"Mpossible to contribute changes. There are a few guidelines that we need ;TI"Qcontributors to follow to reduce the time it takes to get changes merged in.;T@ S; ; i;I"Guidelines;T@ o:RDoc::Markup::List: @type:NUMBER:@items[ o:RDoc::Markup::ListItem:@label0;[o; ;[I"/New features should be coupled with tests.;T@ o;;0;[o; ;[I"1Ensure that your code blends well with ours:;To;;:BULLET;[o;;0;[o; ;[I"No trailing whitespace;To;;0;[o; ;[I"#Match indentation (two spaces);To;;0;[o; ;[I"DMatch coding style (`if`, `elsif`, `when` need trailing `then`);T@ o;;0;[o; ;[I"zIf any new files are added or existing files removed in a commit or PR, please update the `Manifest.txt` accordingly.;T@ o;;0;[o; ;[I"5Don't modify the history file or version number.;T@ o;;0;[o; ;[I"QIf you have any questions, just ask on IRC in #rubygems on Freenode or file ;TI">an issue here: http://github.com/rubygems/rubygems/issues;T@ o; ;[I"TFor more information and ideas on how to contribute to RubyGems ecosystem, see ;TI"3here: http://guides.rubygems.org/contributing/;T@ S; ; i;I"Getting Started;T@ o:RDoc::Markup::Verbatim;[I"$ gem install hoe ;TI"$ rake newb ;T:@format0o; ;[I"6To run commands like `gem install` from the repo:;T@ o;;[I""$ ruby -Ilib bin/gem install ;T;0S; ; i;I"Issues;T@ o; ;[I"URubyGems uses labels to track all issues and pull requests. In order to provide ;TI"Sguidance to the community this is documentation of how labels are used in the ;TI"rubygems repository.;T@ S; ; i;I" Type;T@ o; ;[I"UMost Issues or pull requests will have one of these labels, which describes the ;TI"'type of the issue or pull request.;T@ o;;;;[ o;;0;[o; ;[I"X<b>bug report</b> - An issue describing a bug in rubygems. This would be something ;TI"8that is broken, confusing, unexpected behavior etc.;To;;0;[o; ;[I"<<b>bugfix</b> - A pull request that fixes a bug report.;To;;0;[o; ;[I"Q<b>feature request</b> - An issue describing a request for a new feature or ;TI"enhancement.;To;;0;[o; ;[I"S<b>feature implementation</b> - A pull request implementing a feature request.;To;;0;[o; ;[I"V<b>question</b> - An issue that is a more of a question than a call for specific ;TI"changes in the codebase.;To;;0;[o; ;[I"W<b>cleanup</b> - Generally for a pull request that improves the code base without ;TI",fixing a bug or implementing a feature.;To;;0;[o; ;[I"Q<b>major bump</b> - This issue or pull request requires a major version bump;To;;0;[o; ;[I"U<b>administrative</b> - This issue relates to administrative tasks that need to ;TI")take place as it relates to rubygems;T@ o; ;[I"OBug report and Bugfix have the same color. And feature implementation and ;TI"Gfeature request have the same color since they are related labels.;T@ S; ; i;I" Workflow;T@ o; ;[I"VThese are labels that indicate the state of an issue, where it is in the process ;TI"Qfrom being submitted to being closed. These are listed in rough progression ;TI"$order from submitted to closed.;T@ o;;;;[o;;0;[o; ;[I"P<b>triage</b> - This is an issue or pull request that needs to be properly ;TI" labeled by by a maintainer.;To;;0;[o; ;[I"P<b>accepted</b> - This issue / pull request has been accepted as valid and ;TI""will be worked on by someone.;To;;0;[o; ;[ I"V<b>ready for work</b> - An issue that is available for collaboration. This issue ;TI"Tshould have existing discussion on the problem, and a description of how to go ;TI"Sabout solving it. This label should be removed once someone has said they are ;TI"going to work on it.;To;;0;[o; ;[I"S<b>claimed</b> - An issue that is claimed by a member of the community and is ;TI"Oworking on it. If the member can be assigned to the issue, they should be.;To;;0;[o; ;[I"J<b>feedback</b>- This issue/pull request is waiting on feedback from ;TI"Sone ore more of the folks involved in the issue. Generally their should be an ;TI"H<tt>@username/team</tt> in the issue indicating who should respond.;To;;0;[o; ;[ I"Y<b>blocked</b> - the issue/pull request is currently unable to move forward because ;TI"Nof some specific reason, generally this will be a reason that is outside ;TI"SRubyGems or needs feedback from some specific individual or group, and it may ;TI"0be a while before something it is resolved.;T@ o; ;[I"PFeedback and blocked all have the same color since they are all waiting on ;TI"+someone in particular to do something.;T@ S; ; i;I"Inactive Reason;T@ o; ;[I"SReasons are why an issue / pull request was closed without being worked on or ;TI"Naccepted. There should also be more detailed information in the comments.;T@ o;;;;[ o;;0;[o; ;[I"M*duplicate* - This is a duplicate of an existing bug. The comments must ;TI""reference the existing issue.;To;;0;[o; ;[I"R*abandonded* - This is an issue/pull request that has aged off, is no longer ;TI"applicable or similar.;To;;0;[o; ;[I"R*declined* - An issue that won't be fixed/implemented or a pull request that ;TI"is not accepted.;To;;0;[o; ;[I"Q*deprecated* - An issue/pull request that no longer applies to the actively ;TI"maintained codebase.;T@ o; ;[I"5All the reason labels are the same maroon color.;T@ S; ; i;I"Categories;T@ o; ;[I"OThese are aspects of the codebase, or what general area the issue or pull ;TI"?request pertains too. Not all issues will have a category.;T@ o;;;;[ o;;0;[o; ;[I"=<b>gemspec</b> - related to the gem specification itself;To;;0;[o; ;[I"V<b>API</b> - related to the public supported rubygems API. This is the code api, ;TI"not a network related API.;To;;0;[o; ;[I"D<b>command</b> - related to something in <tt>Gem::Commands</tt>;To;;0;[o; ;[I"2<b>install</b> - related to gem installations;To;;0;[o; ;[I"W<b>documentation</b> - related to updating / fixing / clarifying documentation or ;TI"guides;T@ o; ;[I"1All category labels are the same blue color.;T@ S; ; i;I"Platforms;T@ o; ;[I"TIf an issue or pull request pertains to only one platform, then it should have ;TI"!an appropriate platform tag.;T@ o;;;;[ o;;0;[o; ;[I"*windows*;To;;0;[o; ;[I"*java*;To;;0;[o; ;[I" *osx*;To;;0;[o; ;[I"*linux*;T@ o; ;[I"1All platform tags are the same purple color.;T: @file@:0@omit_headings_from_table_of_contents_below0