sanitize_email 2.0.10 → 2.0.12
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- checksums.yaml +4 -4
- checksums.yaml.gz.sig +0 -0
- data/CHANGELOG.md +189 -44
- data/CITATION.cff +20 -0
- data/CODE_OF_CONDUCT.md +79 -29
- data/CONTRIBUTING.md +249 -46
- data/FUNDING.md +74 -0
- data/LICENSE.md +22 -0
- data/README.md +404 -596
- data/RUBOCOP.md +71 -0
- data/SECURITY.md +15 -9
- data/certs/pboling.pem +27 -0
- data/lib/sanitize_email/bleach.rb +3 -1
- data/lib/sanitize_email/config.rb +51 -34
- data/lib/sanitize_email/deprecation.rb +9 -1
- data/lib/sanitize_email/mail_ext.rb +8 -6
- data/lib/sanitize_email/mail_header_tools.rb +64 -61
- data/lib/sanitize_email/version.rb +2 -4
- data/lib/sanitize_email.rb +25 -5
- data/sig/sanitize_email/version.rbs +6 -0
- data.tar.gz.sig +0 -0
- metadata +242 -52
- metadata.gz.sig +0 -0
- data/LICENSE.txt +0 -21
checksums.yaml
CHANGED
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
---
|
|
2
2
|
SHA256:
|
|
3
|
-
metadata.gz:
|
|
4
|
-
data.tar.gz:
|
|
3
|
+
metadata.gz: 9307cb56be3bde5294d38c2c1fb823458f458ea1db6e0868c55638b4b3126089
|
|
4
|
+
data.tar.gz: 9d9d4aa8f7e9d95c0b972cae2fa82037af0ee1f0cf55b9240f65028069b2fa99
|
|
5
5
|
SHA512:
|
|
6
|
-
metadata.gz:
|
|
7
|
-
data.tar.gz:
|
|
6
|
+
metadata.gz: 0521e2513ab55d62be47c2957f88509a5ca299bdf11875f7d75b1cddfe52ccbef04e96becafa684c4bf41ad8ee94155eb99217a72178dbc1f9d6613295a6ce39
|
|
7
|
+
data.tar.gz: b68b04b772ff25d83d095365ad357a809aa530832626a19d0296c38517834c7f3e4748c379ecd400683ad64b8fce6b42a3d6aff26674ebcbcd25283723dfe884
|
checksums.yaml.gz.sig
CHANGED
|
Binary file
|
data/CHANGELOG.md
CHANGED
|
@@ -1,46 +1,137 @@
|
|
|
1
1
|
# Changelog
|
|
2
|
+
|
|
3
|
+
[![SemVer 2.0.0][📌semver-img]][📌semver] [![Keep-A-Changelog 1.0.0][📗keep-changelog-img]][📗keep-changelog]
|
|
4
|
+
|
|
2
5
|
All notable changes to this project will be documented in this file.
|
|
3
6
|
|
|
4
|
-
|
|
5
|
-
and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html)
|
|
7
|
+
The format is based on [Keep a Changelog][📗keep-changelog],
|
|
8
|
+
and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html),
|
|
9
|
+
and [yes][📌major-versions-not-sacred], platform and engine support are part of the [public API][📌semver-breaking].
|
|
10
|
+
Please file a bug if you notice a violation of semantic versioning.
|
|
11
|
+
|
|
12
|
+
[📌semver]: https://semver.org/spec/v2.0.0.html
|
|
13
|
+
[📌semver-img]: https://img.shields.io/badge/semver-2.0.0-FFDD67.svg?style=flat
|
|
14
|
+
[📌semver-breaking]: https://github.com/semver/semver/issues/716#issuecomment-869336139
|
|
15
|
+
[📌major-versions-not-sacred]: https://tom.preston-werner.com/2022/05/23/major-version-numbers-are-not-sacred.html
|
|
16
|
+
[📗keep-changelog]: https://keepachangelog.com/en/1.0.0/
|
|
17
|
+
[📗keep-changelog-img]: https://img.shields.io/badge/keep--a--changelog-1.0.0-FFDD67.svg?style=flat
|
|
6
18
|
|
|
7
19
|
## [Unreleased]
|
|
20
|
+
|
|
8
21
|
### Added
|
|
22
|
+
|
|
9
23
|
### Changed
|
|
10
|
-
|
|
24
|
+
|
|
25
|
+
### Deprecated
|
|
26
|
+
|
|
11
27
|
### Removed
|
|
12
28
|
|
|
13
|
-
|
|
29
|
+
### Fixed
|
|
30
|
+
|
|
31
|
+
### Security
|
|
32
|
+
|
|
33
|
+
## [2.0.12] - 2026-06-14
|
|
34
|
+
|
|
35
|
+
- TAG: [v2.0.12][2.0.12t]
|
|
36
|
+
- COVERAGE: 94.87% -- 259/273 lines in 7 files
|
|
37
|
+
- BRANCH COVERAGE: 81.19% -- 82/101 branches in 7 files
|
|
38
|
+
- 51.14% documented
|
|
39
|
+
|
|
40
|
+
### Changed
|
|
41
|
+
|
|
42
|
+
- Refreshed generated project metadata, support documentation and README
|
|
43
|
+
badges, funding metadata, documentation URLs, CI workflow pins and matrices,
|
|
44
|
+
`docs/CNAME`, and development dependency floors from the latest `kettle-jem`
|
|
45
|
+
template.
|
|
46
|
+
|
|
47
|
+
### Fixed
|
|
48
|
+
|
|
49
|
+
- Honored explicit per-call `activation_proc` and `engage` options in `SanitizeEmail.sanitary`, and restored temporary sanitization state when a delivery raises.
|
|
50
|
+
- Preserved the Rails environment activation override in sanitizer specs so
|
|
51
|
+
test setup matches configured activation behavior.
|
|
52
|
+
|
|
53
|
+
## [2.0.11] - 2026-05-28
|
|
54
|
+
|
|
55
|
+
- TAG: [v2.0.11][2.0.11t]
|
|
56
|
+
- COVERAGE: 94.93% -- 262/276 lines in 8 files
|
|
57
|
+
- BRANCH COVERAGE: 80.81% -- 80/99 branches in 8 files
|
|
58
|
+
- 52.27% documented
|
|
59
|
+
|
|
60
|
+
### Added
|
|
61
|
+
|
|
62
|
+
- Published generated API documentation
|
|
63
|
+
- refreshed README Ruby & Rails compatibility guidance
|
|
64
|
+
|
|
65
|
+
### Changed
|
|
66
|
+
|
|
67
|
+
- Refreshed package metadata, support links, and documentation links for the
|
|
68
|
+
current `galtzo-floss/sanitize_email` project home.
|
|
69
|
+
|
|
70
|
+
### Fixed
|
|
71
|
+
|
|
72
|
+
- Fixed sanitization of SendGrid ActionMailer `personalizations` headers so the
|
|
73
|
+
overridden recipient data is written back to the message.
|
|
74
|
+
- Made global sanitization/configuration state updates safer under concurrent
|
|
75
|
+
access by synchronizing `force_sanitize`, configuration, and deprecation
|
|
76
|
+
silence state.
|
|
77
|
+
|
|
78
|
+
## [2.0.10] - 2024-11-09
|
|
79
|
+
|
|
80
|
+
- TAG: [v2.0.10][2.0.10t]
|
|
81
|
+
|
|
14
82
|
- COVERAGE: 90.15% -- 247/274 lines in 8 files
|
|
15
83
|
- BRANCH COVERAGE: 71.68% -- 81/113 branches in 8 files
|
|
16
84
|
- 61.73% documented
|
|
85
|
+
|
|
17
86
|
### Fixed
|
|
87
|
+
|
|
18
88
|
* Prefer `require_relative` > `require` internally
|
|
19
89
|
* Better performance, portability, and consistency
|
|
20
90
|
* See: https://github.com/rubocop/rubocop/issues/8748
|
|
21
91
|
|
|
22
|
-
## [2.0.9] - 2024-11-09
|
|
92
|
+
## [2.0.9] - 2024-11-09
|
|
93
|
+
|
|
94
|
+
- TAG: [v2.0.9][2.0.9t]
|
|
95
|
+
|
|
23
96
|
- COVERAGE: 90.15% -- 247/274 lines in 8 files
|
|
24
97
|
- BRANCH COVERAGE: 71.68% -- 81/113 branches in 8 files
|
|
25
98
|
- 61.73% documented
|
|
99
|
+
|
|
26
100
|
### Added
|
|
101
|
+
|
|
27
102
|
* More & better documentation
|
|
28
103
|
* Rails 8.0 to CI
|
|
29
104
|
|
|
30
|
-
## [2.0.8] - 2024-06-11
|
|
105
|
+
## [2.0.8] - 2024-06-11
|
|
106
|
+
|
|
107
|
+
- TAG: [v2.0.8][2.0.8t]
|
|
108
|
+
|
|
31
109
|
### Fixed
|
|
32
|
-
* [#110](https://github.com/pboling/sanitize_email/issues/110) - interceptor not working via Rails 6+ engine (actual fix!)
|
|
33
110
|
|
|
34
|
-
|
|
111
|
+
* [#110](https://github.com/galtzo-floss/sanitize_email/issues/110) - interceptor not working via Rails 6+ engine (actual fix!)
|
|
112
|
+
|
|
113
|
+
## [2.0.7] - 2024-04-25
|
|
114
|
+
|
|
115
|
+
- TAG: [v2.0.7][2.0.7t]
|
|
116
|
+
|
|
35
117
|
### Added
|
|
118
|
+
|
|
36
119
|
* More documentation
|
|
120
|
+
|
|
37
121
|
### Changed
|
|
122
|
+
|
|
38
123
|
* Documentation is now via yard instead of rdoc
|
|
124
|
+
|
|
39
125
|
### Fixed
|
|
40
|
-
* [#110](https://github.com/pboling/sanitize_email/issues/110) - interceptor not working via Rails 6+ engine
|
|
41
126
|
|
|
42
|
-
|
|
127
|
+
* [#110](https://github.com/galtzo-floss/sanitize_email/issues/110) - interceptor not working via Rails 6+ engine
|
|
128
|
+
|
|
129
|
+
## [2.0.6] - 2024-04-25
|
|
130
|
+
|
|
131
|
+
- TAG: [v2.0.6][2.0.6t]
|
|
132
|
+
|
|
43
133
|
### Added
|
|
134
|
+
|
|
44
135
|
* Appraisals & Combustion for comprehensive testing across versions of Rails (@pboling)
|
|
45
136
|
* Rails 3.0 to Test Matrix (@pboling)
|
|
46
137
|
* Rails 3.1 to Test Matrix (@pboling)
|
|
@@ -51,12 +142,18 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
|
|
|
51
142
|
* Rails 5.0 to Test Matrix (@pboling)
|
|
52
143
|
* Rails 5.1 to Test Matrix (@pboling)
|
|
53
144
|
* More Documentation (@pboling)
|
|
145
|
+
|
|
54
146
|
### Fixed
|
|
147
|
+
|
|
55
148
|
* Compatibility with Rails 3.0, 3.1, 3.2 (@pboling)
|
|
56
149
|
* Compatibility with Rails 6.0, 6.1, 7.0, 7.1 (@pboling)
|
|
57
150
|
|
|
58
|
-
## [2.0.5] - 2024-04-18
|
|
151
|
+
## [2.0.5] - 2024-04-18
|
|
152
|
+
|
|
153
|
+
- TAG: [v2.0.5][2.0.5t]
|
|
154
|
+
|
|
59
155
|
### Added
|
|
156
|
+
|
|
60
157
|
* New RSpec matcher (@pboling)
|
|
61
158
|
* `have_bcc_username`
|
|
62
159
|
* Feature #21 - environment configuration option can now be set to proc / lambda / #call (@pboling)
|
|
@@ -64,14 +161,22 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
|
|
|
64
161
|
* Many more tests
|
|
65
162
|
* Confirmed compatibility with [`sendgrid-actionmailer`](https://github.com/eddiezane/sendgrid-actionmailer)
|
|
66
163
|
* Code coverage up to 90%
|
|
164
|
+
|
|
67
165
|
### Changed
|
|
166
|
+
|
|
68
167
|
* Averted deprecation warnings when using Rails 6 (@pboling)
|
|
168
|
+
|
|
69
169
|
## Fixed
|
|
170
|
+
|
|
70
171
|
* Bug #37 - Unable to send email when only CC or BCC present
|
|
71
172
|
|
|
72
|
-
## [2.0.4] - 2024-03-22
|
|
173
|
+
## [2.0.4] - 2024-03-22
|
|
174
|
+
|
|
175
|
+
- TAG: [v2.0.4][2.0.4t]
|
|
176
|
+
|
|
73
177
|
### Added
|
|
74
|
-
|
|
178
|
+
|
|
179
|
+
* [#74](https://github.com/galtzo-floss/sanitize_email/pull/74) Support sanitizing SendGrid personalization fields (@joeyparis)
|
|
75
180
|
* mail gem dependency (@pboling)
|
|
76
181
|
* version_gem dependency (@pboling)
|
|
77
182
|
* new RSpec Matchers (@pboling)
|
|
@@ -80,48 +185,84 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
|
|
|
80
185
|
* Contributor [CODE_OF_CONDUCT.md](CODE_OF_CONDUCT.md) (@pboling)
|
|
81
186
|
* Security Policy in [SECURITY.md](SECURITY.md) (@pboling)
|
|
82
187
|
* More documentation (@pboling)
|
|
188
|
+
|
|
83
189
|
### Changed
|
|
190
|
+
|
|
84
191
|
* Switched from Travis-CI to GitHub Actions
|
|
85
192
|
* Testing for
|
|
193
|
+
|
|
86
194
|
### Fixed
|
|
87
|
-
|
|
195
|
+
|
|
196
|
+
* [#64](https://github.com/galtzo-floss/sanitize_email/issues/64) Automatically dedup recipients in cascading fashion: To > CC > BCC (@pboling)
|
|
88
197
|
* Set sanitized email headers with decoded values from Mail gem
|
|
198
|
+
|
|
89
199
|
### Removed
|
|
200
|
+
|
|
90
201
|
* Dependency on git in gemspec (@pboling)
|
|
91
202
|
* Coveralls development gem dependecy
|
|
92
203
|
|
|
93
|
-
## [2.0.3] - 2018-09-08
|
|
204
|
+
## [2.0.3] - 2018-09-08
|
|
205
|
+
|
|
206
|
+
- TAG: [v2.0.3][2.0.3t]
|
|
207
|
+
|
|
94
208
|
### Changed
|
|
209
|
+
|
|
95
210
|
* Nothing
|
|
96
211
|
|
|
97
|
-
## [2.0.2] - 2018-09-08
|
|
212
|
+
## [2.0.2] - 2018-09-08
|
|
213
|
+
|
|
214
|
+
- TAG: [v2.0.2][2.0.2t]
|
|
215
|
+
|
|
98
216
|
### Added
|
|
217
|
+
|
|
99
218
|
* More and fixed badges (@pboling)
|
|
100
219
|
* Code Coverage reporting (@pboling)
|
|
220
|
+
|
|
101
221
|
### Changed
|
|
222
|
+
|
|
102
223
|
* begin following SemVer for dependency requirements (@pboling)
|
|
224
|
+
|
|
103
225
|
### Fixed
|
|
104
|
-
|
|
226
|
+
|
|
227
|
+
* [#47](https://github.com/galtzo-floss/sanitize_email/pull/47) Don't use #prepend on subject (@mslade-fairfax)
|
|
228
|
+
|
|
105
229
|
### Removed
|
|
230
|
+
|
|
106
231
|
* Ability to install on Ruby 2.2 (@pboling)
|
|
107
232
|
|
|
108
|
-
## [2.0.1] - 2018-03-07
|
|
233
|
+
## [2.0.1] - 2018-03-07
|
|
234
|
+
|
|
235
|
+
- TAG: [v2.0.1][2.0.1t]
|
|
236
|
+
|
|
109
237
|
### Fixed
|
|
110
|
-
|
|
238
|
+
|
|
239
|
+
* [#32](https://github.com/galtzo-floss/sanitize_email/pull/32) A better fix for the frozen subject bug (@pboling)
|
|
240
|
+
|
|
111
241
|
### Removed
|
|
242
|
+
|
|
112
243
|
* Ruby 2.2 is really no longer supported (@pboling)
|
|
113
244
|
|
|
114
|
-
## [2.0.0] - 2018-03-07
|
|
245
|
+
## [2.0.0] - 2018-03-07
|
|
246
|
+
|
|
247
|
+
- TAG: [v2.0.0][2.0.0t]
|
|
248
|
+
|
|
115
249
|
### Added
|
|
250
|
+
|
|
116
251
|
* Add testing for Rails 5.1 and 5.2 (@pboling)
|
|
117
252
|
* More and fixed badges (@pboling)
|
|
253
|
+
|
|
118
254
|
### Changed
|
|
255
|
+
|
|
119
256
|
* Drop support for MRI Ruby 1.9, 2.0, 2.1, and 2.2 (@pboling)
|
|
120
257
|
* Drop support for JRuby 1.7 and 9.0, while still supporting 9.1 (@pboling)
|
|
121
258
|
* Drop support for Rails 3.0, 3.1, 3.2, 4.0, 4.1, while still supporting 4.2 (@pboling)
|
|
259
|
+
|
|
122
260
|
### Fixed
|
|
261
|
+
|
|
123
262
|
* Frozen subject bug (@pboling)
|
|
263
|
+
|
|
124
264
|
### Removed
|
|
265
|
+
|
|
125
266
|
* Ruby 2.2 is no longer supported (@pboling)
|
|
126
267
|
|
|
127
268
|
Version 1.2.2 - FEB.20.2017
|
|
@@ -274,7 +415,7 @@ Version 1.0.0.rc3 - AUG.08.2012
|
|
|
274
415
|
Version 1.0.0.rc2 - AUG.08.2012 - botched
|
|
275
416
|
|
|
276
417
|
* Bug: loading the gem in a rails app broke mailer specs in the app - Fixed
|
|
277
|
-
* https://github.com/
|
|
418
|
+
* https://github.com/galtzo-floss/sanitize_email/issues/4
|
|
278
419
|
* Moved MIT-LICENSE to LICENSE, updated years
|
|
279
420
|
* Added Travis-CI for... CI.
|
|
280
421
|
|
|
@@ -320,26 +461,30 @@ Old version?
|
|
|
320
461
|
* Fixed require paths
|
|
321
462
|
* added about.yml and this CHANGELOG
|
|
322
463
|
|
|
323
|
-
[Unreleased]: https://github.com/
|
|
324
|
-
[2.0.
|
|
325
|
-
[2.0.
|
|
326
|
-
[2.0.
|
|
327
|
-
[2.0.
|
|
328
|
-
[2.0.
|
|
329
|
-
[2.0.
|
|
330
|
-
[2.0.
|
|
331
|
-
[2.0.
|
|
332
|
-
[2.0.
|
|
333
|
-
[2.0.
|
|
334
|
-
[2.0.
|
|
335
|
-
[2.0.
|
|
336
|
-
[2.0.
|
|
337
|
-
[2.0.
|
|
338
|
-
[2.0.
|
|
339
|
-
[2.0.
|
|
340
|
-
[2.0.
|
|
341
|
-
[2.0.
|
|
342
|
-
[2.0.
|
|
343
|
-
[2.0.
|
|
344
|
-
[2.0.
|
|
345
|
-
[2.0.
|
|
464
|
+
[Unreleased]: https://github.com/galtzo-floss/sanitize_email/compare/v2.0.12...HEAD
|
|
465
|
+
[2.0.12]: https://github.com/galtzo-floss/sanitize_email/compare/v2.0.11...v2.0.12
|
|
466
|
+
[2.0.12t]: https://github.com/galtzo-floss/sanitize_email/releases/tag/v2.0.12
|
|
467
|
+
[2.0.11]: https://github.com/galtzo-floss/sanitize_email/compare/v2.0.10...v2.0.11
|
|
468
|
+
[2.0.11t]: https://github.com/galtzo-floss/sanitize_email/releases/tag/v2.0.11
|
|
469
|
+
[2.0.10]: https://github.com/galtzo-floss/sanitize_email/compare/v2.0.9...v2.0.10
|
|
470
|
+
[2.0.10t]: https://github.com/galtzo-floss/sanitize_email/tags/v2.0.10
|
|
471
|
+
[2.0.9]: https://github.com/galtzo-floss/sanitize_email/compare/v2.0.8...v2.0.9
|
|
472
|
+
[2.0.9t]: https://github.com/galtzo-floss/sanitize_email/tags/v2.0.9
|
|
473
|
+
[2.0.8]: https://github.com/galtzo-floss/sanitize_email/compare/v2.0.7...v2.0.8
|
|
474
|
+
[2.0.8t]: https://github.com/galtzo-floss/sanitize_email/tags/v2.0.8
|
|
475
|
+
[2.0.7]: https://github.com/galtzo-floss/sanitize_email/compare/v2.0.6...v2.0.7
|
|
476
|
+
[2.0.7t]: https://github.com/galtzo-floss/sanitize_email/tags/v2.0.7
|
|
477
|
+
[2.0.6]: https://github.com/galtzo-floss/sanitize_email/compare/v2.0.5...v2.0.6
|
|
478
|
+
[2.0.6t]: https://github.com/galtzo-floss/sanitize_email/tags/v2.0.6
|
|
479
|
+
[2.0.5]: https://github.com/galtzo-floss/sanitize_email/compare/v2.0.4...v2.0.5
|
|
480
|
+
[2.0.5t]: https://github.com/galtzo-floss/sanitize_email/tags/v2.0.5
|
|
481
|
+
[2.0.4]: https://github.com/galtzo-floss/sanitize_email/compare/v2.0.3...v2.0.4
|
|
482
|
+
[2.0.4t]: https://github.com/galtzo-floss/sanitize_email/tags/v2.0.4
|
|
483
|
+
[2.0.3]: https://github.com/galtzo-floss/sanitize_email/compare/v2.0.2...v2.0.3
|
|
484
|
+
[2.0.3t]: https://github.com/galtzo-floss/sanitize_email/tags/v2.0.3
|
|
485
|
+
[2.0.2]: https://github.com/galtzo-floss/sanitize_email/compare/v2.0.1...v2.0.2
|
|
486
|
+
[2.0.2t]: https://github.com/galtzo-floss/sanitize_email/tags/v2.0.2
|
|
487
|
+
[2.0.1]: https://github.com/galtzo-floss/sanitize_email/compare/v2.0.0...v2.0.1
|
|
488
|
+
[2.0.1t]: https://github.com/galtzo-floss/sanitize_email/tags/v2.0.1
|
|
489
|
+
[2.0.0]: https://github.com/galtzo-floss/sanitize_email/compare/v1.2.2...v2.0.0
|
|
490
|
+
[2.0.0t]: https://github.com/galtzo-floss/sanitize_email/tags/v2.0.0
|
data/CITATION.cff
ADDED
|
@@ -0,0 +1,20 @@
|
|
|
1
|
+
cff-version: 1.2.0
|
|
2
|
+
title: "sanitize_email"
|
|
3
|
+
message: >-
|
|
4
|
+
If you use this work and you want to cite it,
|
|
5
|
+
then you can use the metadata from this file.
|
|
6
|
+
type: software
|
|
7
|
+
authors:
|
|
8
|
+
- given-names: "Peter H."
|
|
9
|
+
family-names: "Boling"
|
|
10
|
+
email: "floss@galtzo.com"
|
|
11
|
+
affiliation: "galtzo.com"
|
|
12
|
+
orcid: 'https://orcid.org/0009-0008-8519-441X'
|
|
13
|
+
identifiers:
|
|
14
|
+
- type: url
|
|
15
|
+
value: 'https://github.com/galtzo-floss/sanitize_email'
|
|
16
|
+
description: "sanitize_email"
|
|
17
|
+
repository-code: 'https://github.com/galtzo-floss/sanitize_email'
|
|
18
|
+
abstract: >-
|
|
19
|
+
sanitize_email
|
|
20
|
+
license: See license file
|
data/CODE_OF_CONDUCT.md
CHANGED
|
@@ -2,83 +2,133 @@
|
|
|
2
2
|
|
|
3
3
|
## Our Pledge
|
|
4
4
|
|
|
5
|
-
We as members, contributors, and leaders pledge to make participation in our
|
|
5
|
+
We as members, contributors, and leaders pledge to make participation in our
|
|
6
|
+
community a harassment-free experience for everyone, regardless of age, body
|
|
7
|
+
size, visible or invisible disability, ethnicity, sex characteristics, gender
|
|
8
|
+
identity and expression, level of experience, education, socio-economic status,
|
|
9
|
+
nationality, personal appearance, race, caste, color, religion, or sexual
|
|
10
|
+
identity and orientation.
|
|
6
11
|
|
|
7
|
-
We pledge to act and interact in ways that contribute to an open, welcoming,
|
|
12
|
+
We pledge to act and interact in ways that contribute to an open, welcoming,
|
|
13
|
+
diverse, inclusive, and healthy community.
|
|
8
14
|
|
|
9
15
|
## Our Standards
|
|
10
16
|
|
|
11
|
-
Examples of behavior that contributes to a positive environment for our
|
|
17
|
+
Examples of behavior that contributes to a positive environment for our
|
|
18
|
+
community include:
|
|
12
19
|
|
|
13
20
|
* Demonstrating empathy and kindness toward other people
|
|
14
21
|
* Being respectful of differing opinions, viewpoints, and experiences
|
|
15
22
|
* Giving and gracefully accepting constructive feedback
|
|
16
|
-
* Accepting responsibility and apologizing to those affected by our mistakes,
|
|
17
|
-
|
|
23
|
+
* Accepting responsibility and apologizing to those affected by our mistakes,
|
|
24
|
+
and learning from the experience
|
|
25
|
+
* Focusing on what is best not just for us as individuals, but for the overall
|
|
26
|
+
community
|
|
18
27
|
|
|
19
28
|
Examples of unacceptable behavior include:
|
|
20
29
|
|
|
21
|
-
* The use of sexualized language or imagery, and sexual attention or
|
|
22
|
-
|
|
30
|
+
* The use of sexualized language or imagery, and sexual attention or advances of
|
|
31
|
+
any kind
|
|
23
32
|
* Trolling, insulting or derogatory comments, and personal or political attacks
|
|
24
33
|
* Public or private harassment
|
|
25
|
-
* Publishing others' private information, such as a physical or email
|
|
26
|
-
|
|
34
|
+
* Publishing others' private information, such as a physical or email address,
|
|
35
|
+
without their explicit permission
|
|
27
36
|
* Other conduct which could reasonably be considered inappropriate in a
|
|
28
37
|
professional setting
|
|
29
38
|
|
|
30
39
|
## Enforcement Responsibilities
|
|
31
40
|
|
|
32
|
-
Community leaders are responsible for clarifying and enforcing our standards of
|
|
41
|
+
Community leaders are responsible for clarifying and enforcing our standards of
|
|
42
|
+
acceptable behavior and will take appropriate and fair corrective action in
|
|
43
|
+
response to any behavior that they deem inappropriate, threatening, offensive,
|
|
44
|
+
or harmful.
|
|
33
45
|
|
|
34
|
-
Community leaders have the right and responsibility to remove, edit, or reject
|
|
46
|
+
Community leaders have the right and responsibility to remove, edit, or reject
|
|
47
|
+
comments, commits, code, wiki edits, issues, and other contributions that are
|
|
48
|
+
not aligned to this Code of Conduct, and will communicate reasons for moderation
|
|
49
|
+
decisions when appropriate.
|
|
35
50
|
|
|
36
51
|
## Scope
|
|
37
52
|
|
|
38
|
-
This Code of Conduct applies within all community spaces, and also applies when
|
|
53
|
+
This Code of Conduct applies within all community spaces, and also applies when
|
|
54
|
+
an individual is officially representing the community in public spaces.
|
|
55
|
+
Examples of representing our community include using an official email address,
|
|
56
|
+
posting via an official social media account, or acting as an appointed
|
|
57
|
+
representative at an online or offline event.
|
|
39
58
|
|
|
40
59
|
## Enforcement
|
|
41
60
|
|
|
42
|
-
Instances of abusive, harassing, or otherwise unacceptable behavior may be
|
|
61
|
+
Instances of abusive, harassing, or otherwise unacceptable behavior may be
|
|
62
|
+
reported to the community leaders responsible for enforcement at
|
|
63
|
+
[![Contact Maintainer][🚂maint-contact-img]][🚂maint-contact].
|
|
64
|
+
All complaints will be reviewed and investigated promptly and fairly.
|
|
43
65
|
|
|
44
|
-
All community leaders are obligated to respect the privacy and security of the
|
|
66
|
+
All community leaders are obligated to respect the privacy and security of the
|
|
67
|
+
reporter of any incident.
|
|
45
68
|
|
|
46
69
|
## Enforcement Guidelines
|
|
47
70
|
|
|
48
|
-
Community leaders will follow these Community Impact Guidelines in determining
|
|
71
|
+
Community leaders will follow these Community Impact Guidelines in determining
|
|
72
|
+
the consequences for any action they deem in violation of this Code of Conduct:
|
|
49
73
|
|
|
50
74
|
### 1. Correction
|
|
51
75
|
|
|
52
|
-
**Community Impact**: Use of inappropriate language or other behavior deemed
|
|
76
|
+
**Community Impact**: Use of inappropriate language or other behavior deemed
|
|
77
|
+
unprofessional or unwelcome in the community.
|
|
53
78
|
|
|
54
|
-
**Consequence**: A private, written warning from community leaders, providing
|
|
79
|
+
**Consequence**: A private, written warning from community leaders, providing
|
|
80
|
+
clarity around the nature of the violation and an explanation of why the
|
|
81
|
+
behavior was inappropriate. A public apology may be requested.
|
|
55
82
|
|
|
56
83
|
### 2. Warning
|
|
57
84
|
|
|
58
|
-
**Community Impact**: A violation through a single incident or series of
|
|
85
|
+
**Community Impact**: A violation through a single incident or series of
|
|
86
|
+
actions.
|
|
59
87
|
|
|
60
|
-
**Consequence**: A warning with consequences for continued behavior. No
|
|
88
|
+
**Consequence**: A warning with consequences for continued behavior. No
|
|
89
|
+
interaction with the people involved, including unsolicited interaction with
|
|
90
|
+
those enforcing the Code of Conduct, for a specified period of time. This
|
|
91
|
+
includes avoiding interactions in community spaces as well as external channels
|
|
92
|
+
like social media. Violating these terms may lead to a temporary or permanent
|
|
93
|
+
ban.
|
|
61
94
|
|
|
62
95
|
### 3. Temporary Ban
|
|
63
96
|
|
|
64
|
-
**Community Impact**: A serious violation of community standards, including
|
|
97
|
+
**Community Impact**: A serious violation of community standards, including
|
|
98
|
+
sustained inappropriate behavior.
|
|
65
99
|
|
|
66
|
-
**Consequence**: A temporary ban from any sort of interaction or public
|
|
100
|
+
**Consequence**: A temporary ban from any sort of interaction or public
|
|
101
|
+
communication with the community for a specified period of time. No public or
|
|
102
|
+
private interaction with the people involved, including unsolicited interaction
|
|
103
|
+
with those enforcing the Code of Conduct, is allowed during this period.
|
|
104
|
+
Violating these terms may lead to a permanent ban.
|
|
67
105
|
|
|
68
106
|
### 4. Permanent Ban
|
|
69
107
|
|
|
70
|
-
**Community Impact**: Demonstrating a pattern of violation of community
|
|
108
|
+
**Community Impact**: Demonstrating a pattern of violation of community
|
|
109
|
+
standards, including sustained inappropriate behavior, harassment of an
|
|
110
|
+
individual, or aggression toward or disparagement of classes of individuals.
|
|
71
111
|
|
|
72
|
-
**Consequence**: A permanent ban from any sort of public interaction within the
|
|
112
|
+
**Consequence**: A permanent ban from any sort of public interaction within the
|
|
113
|
+
community.
|
|
73
114
|
|
|
74
115
|
## Attribution
|
|
75
116
|
|
|
76
|
-
This Code of Conduct is adapted from the [Contributor Covenant][homepage],
|
|
77
|
-
available at
|
|
117
|
+
This Code of Conduct is adapted from the [Contributor Covenant][homepage],
|
|
118
|
+
version 2.1, available at
|
|
119
|
+
[https://www.contributor-covenant.org/version/2/1/code_of_conduct.html][v2.1].
|
|
78
120
|
|
|
79
|
-
Community Impact Guidelines were inspired by
|
|
80
|
-
|
|
81
|
-
[homepage]: https://www.contributor-covenant.org
|
|
121
|
+
Community Impact Guidelines were inspired by
|
|
122
|
+
[Mozilla's code of conduct enforcement ladder][Mozilla CoC].
|
|
82
123
|
|
|
83
124
|
For answers to common questions about this code of conduct, see the FAQ at
|
|
84
|
-
https://www.contributor-covenant.org/faq. Translations are available at
|
|
125
|
+
[https://www.contributor-covenant.org/faq][FAQ]. Translations are available at
|
|
126
|
+
[https://www.contributor-covenant.org/translations][translations].
|
|
127
|
+
|
|
128
|
+
[homepage]: https://www.contributor-covenant.org
|
|
129
|
+
[v2.1]: https://www.contributor-covenant.org/version/2/1/code_of_conduct.html
|
|
130
|
+
[Mozilla CoC]: https://github.com/mozilla/diversity
|
|
131
|
+
[FAQ]: https://www.contributor-covenant.org/faq
|
|
132
|
+
[translations]: https://www.contributor-covenant.org/translations
|
|
133
|
+
[🚂maint-contact]: http://www.railsbling.com/contact
|
|
134
|
+
[🚂maint-contact-img]: https://img.shields.io/badge/Contact-Maintainer-0093D0.svg?style=flat&logo=rubyonrails&logoColor=red
|