From 475a0f887ce4087443fdf7c5f3f066c90fb00126 Mon Sep 17 00:00:00 2001 From: Xavier Noria Date: Sun, 17 Dec 2017 14:14:40 +0100 Subject: emphasize working on existing issues/patches for newcomers [ci skip] Thanks to @Datasnuten for the suggestion. --- guides/source/contributing_to_ruby_on_rails.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) (limited to 'guides/source/contributing_to_ruby_on_rails.md') diff --git a/guides/source/contributing_to_ruby_on_rails.md b/guides/source/contributing_to_ruby_on_rails.md index 7424818757..967c992c05 100644 --- a/guides/source/contributing_to_ruby_on_rails.md +++ b/guides/source/contributing_to_ruby_on_rails.md @@ -84,7 +84,9 @@ discussions new features require. Helping to Resolve Existing Issues ---------------------------------- -As a next step beyond reporting issues, you can help the core team resolve existing issues. If you check the [issues list](https://github.com/rails/rails/issues) in GitHub Issues, you'll find lots of issues already requiring attention. What can you do for these? Quite a bit, actually: +As a next step beyond reporting issues, you can help the core team resolve existing ones by providing feedback about them. If you are new to Rails core development, that might be a great way to walk your first steps, you'll get familiar with the code base and the processes. + +If you check the [issues list](https://github.com/rails/rails/issues) in GitHub Issues, you'll find lots of issues already requiring attention. What can you do for these? Quite a bit, actually: ### Verifying Bug Reports -- cgit v1.2.3