diff options
| author | Matti Tahvonen <matti@vaadin.com> | 2016-12-14 11:59:31 +0200 |
|---|---|---|
| committer | Pekka Hyvönen <pekka@vaadin.com> | 2016-12-14 11:59:31 +0200 |
| commit | 110c77d504d0206d5e5a9ff2c541b4f8369fab3f (patch) | |
| tree | c5bcaefd7168663b651c015f22ca426a1a08b007 | |
| parent | 189667e0e19abe02e97f975252e781c2db4d3e27 (diff) | |
| download | vaadin-framework-110c77d504d0206d5e5a9ff2c541b4f8369fab3f.tar.gz vaadin-framework-110c77d504d0206d5e5a9ff2c541b4f8369fab3f.zip | |
fixed bug reporting url to point to github (#7968)
* fixed bug reporting url to point to github
Change-Id: I10ea635a3ee1f63ed16347b1da697b2800a31501
| -rw-r--r-- | CONTRIBUTING.md | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 13f6ca4553..22c201df11 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -1,10 +1,10 @@ # Contributing to Vaadin Framework -*There are many ways to participate to the Vaadin project. You can ask questions and participate to discussion in the [forum](https://vaadin.com/forum), [fill bug reports](https://dev.vaadin.com/) and enhancement suggestion, [create add-ons](https://vaadin.com/directory) and contribute code. These instructions are for contributing code the the core framework.* +*There are many ways to participate to the Vaadin project. You can ask questions and participate to discussion in the [forum](https://vaadin.com/forum), [fill bug reports](https://github.com/vaadin/framework/issues) and enhancement suggestion, [create add-ons](https://vaadin.com/directory) and contribute code. These instructions are for contributing code the the core framework.* # Summary -We like quality patches that solve problems. A quality patch follows good coding practices - it’s easy to read and understand. For more complicated fixes or features, the change should be broken down into several smaller easy to understand patches. Most of this is really just what we consider to be common sense and best development practices. +We like quality patches that solve problems. A quality patch follows good coding practices - it’s easy to read and understand. For more complicated fixes or features, the change should be broken down into several smaller easy to understand patches. Most of this is really just what we consider to be common sense and best development practices. In other words: |