| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
| |
Bundler has had a code of conduct since before the Contributor Covenant was available as an option. In my (admittedly somewhat vague) memory, we continued to use our own custom CoC based on wanting clear enforcement examples directly in the CoC. The Contributor Covenant now contains enforcement examples as of 2.0, so I am proposing that we migrate Bundler's CoC to CC 2.0.
Additional benefits:
- Merging with RubyGems gets easier, since RubyGems uses CC already (rubygems/rubygems#3157).
- The `bundle gem` template and Bundler itself will now use the same CoC.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
| |
package.community has done a terrific job with their clear explanation
of what enforcing a CoC looks like. Bundler is a better place when
everyone knows what kind of behavior is expected, and what will happen
if those expectations are not met, for whatever reason.
|
| | |
|
| |
|
|
|
| |
Reference:
http://contributor-covenant.org/version/1/2/0/code_of_conduct.md
|
| |
|
| |
See also: http://contributor-covenant.org/version/1/1/0/code_of_conduct.md
|
| |
|
|
| |
[ci skip]
|
|
|
Thanks to @CoralineAda for the inspiration, via @doodzik
[ci skip]
|
