Browse Source

fixed bug reporting url to point to github (#7968)

* fixed bug reporting url to point to github

Change-Id: I10ea635a3ee1f63ed16347b1da697b2800a31501
tags/8.0.0.alpha10
Matti Tahvonen 7 years ago
parent
commit
110c77d504
1 changed files with 2 additions and 2 deletions
  1. 2
    2
      CONTRIBUTING.md

+ 2
- 2
CONTRIBUTING.md View File

@@ -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:


Loading…
Cancel
Save