+# Contributing
+
* https://www.ruby-lang.org/ - The homepage of Ruby which has more links and some great tutorials.
* https://rubyonrails.org/ - The homepage of Rails, also has links and tutorials.
+## Assigning Issues
+
+We don't assign issues to individual contributors. You are welcome to work on any
+issue, and there's no need to ask first.
+
+For more details see [our FAQ](FAQ.md)]
+
## Coding style
We use [Rubocop](https://github.com/rubocop-hq/rubocop) (for ruby files)
```
bundle exec rubocop
bundle exec rails eslint
-bundle exec erblint .
+bundle exec erb_lint .
```
You can also install hooks to have git run checks automatically when
bundle exec rails test:all
```
+You can run javascript tests with:
+
+```
+bundle exec teaspoon
+```
+
You can view test coverage statistics by browsing the `coverage` directory.
The tests are automatically run on Pull Requests and other commits via github
## i18n
-If you make a change that involve the locale files (in `config/locales`) then please
+If you make a change that involves the locale files (in `config/locales`) then please
only submit changes to the `en.yml` file. The other files are updated via
[Translatewiki](https://translatewiki.net/wiki/Translating:OpenStreetMap) and should
not be included in your pull request.
-### Nominatim prefixes
-
-I18n keys under the `geocoder.search_osm_nominatim` keyspace are managed by the
-Nominatim maintainers. From time to time they run stats over the Nominatim
-database, and update the list of available keys manually.
-
-Adding or removing keys to this list is therefore discouraged, but contributions
-to the descriptive texts are welcome.
-
### Copyright attribution
The list of attributions on the /copyright page is managed by the [OSMF Licensing
large to review in one sitting, or if changes are requested, then the
maintainer needs to repeatedly re-read code that has already been considered.
* The commit history is important. This is a large codebase, developed over many
- years by many developers. We frequently need to read the commit history (e.g.
+ years by many developers. We frequently need to read the commit history (for example
using `git blame`) to figure out what is going on. So small, understandable,
and relevant commits are important for other developers looking back at your
work in future.