-
Notifications
You must be signed in to change notification settings - Fork 28
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge branch 'dev-3.6' into master-3.6
# Conflicts: # dbmodel
- Loading branch information
Showing
66 changed files
with
12,499 additions
and
9,730 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -9,12 +9,14 @@ You can find more information about our code of conduct on: https://github.com/G | |
As well as Giswater is developed in Python (qgis plugin) and PL/SQL(PostgreSQL database) there are three main repositories to manage it (QGIS-PLUGIN, DB-MODEL and DOCS). Right now this is the repository for the QGIS-PLUGIN. | ||
|
||
## TABLE OF CONTENTS | ||
|
||
1- Bug report.<br> | ||
2- Working with issues.<br> | ||
3- Make new code contribution.<br> | ||
4- Contributors list.<br> | ||
|
||
## BUG REPORT | ||
|
||
If you’re experiencing a problem while working with Giswater, please, report it so our developers can revise and fix it, by submitting the following information and sending an e-mail to [email protected] | ||
|
||
1. Contact Information: name and e-mail address.<br> | ||
|
@@ -27,33 +29,38 @@ This report is generated by clicking on the button ‘Check project' on utilitie | |
After a few seconds an extensive report for project status is generated within a dialog. Screenshot of this dialog should be sent such that (at least errors & warnings).<br> | ||
More information: https://www.giswater.org/bug-report<br> | ||
|
||
|
||
## WORKING WITH ISSUES | ||
|
||
### Create a new issue: | ||
|
||
If you spot a problem with the docs, search if an issue already exists. If a related issue doesn't exist, you can open a new issue using a relevant issue form.<br> | ||
|
||
### Solve an issue: | ||
|
||
Scan through our existing issues to find one that interests you. You can narrow down the search using labels as filters. See Labels for more information. As a general rule, we don’t assign issues to anyone. If you find an issue to work on, you are welcome to open a PR with a fix.<br> | ||
|
||
## MAKE NEW CODE CONTRIBUTION | ||
|
||
To get an overview of the project, read the README. Here are some resources to help you get started with open source contributions.<br> | ||
|
||
### Finding ways to contribute with project: | ||
|
||
- Set up Git.<br> | ||
- GitHub flow.<br> | ||
- Collaborating with pull requests.<br> | ||
- Getting started.<br> | ||
- To navigate our codebase with confidence, see the introduction to working in the docs repository.<br> | ||
|
||
### Choose te repo: | ||
|
||
To make new code you need to choose what repo are you looking for:<br> | ||
Use the https://github.com/Giswater/docs repository to work with DOCS<br> | ||
Use the https://github.com/Giswater/giswater_qgis_plugin repository to work with PYTHON QGIS PLUGIN.<br> | ||
Use the https://github.com/Giswater/giswater_dbmodel repository to work with DATABASE MODEL.<br> | ||
Rest of repositories are no significant. Some of them they are deprecated or some of them are not used yet. | ||
|
||
|
||
### Make changes locally: | ||
|
||
1- Install Git LFS.<br> | ||
2- Fork the repository.<br> | ||
3- Using GitHub Desktop.<br> | ||
|
@@ -66,13 +73,15 @@ Rest of repositories are no significant. Some of them they are deprecated or som | |
10- Once your changes are ready, don't forget to self-review to speed up the review process.<br> | ||
|
||
### Create Pull Request: | ||
|
||
When you're finished with the changes, create a pull request, also known as a PR.<br> | ||
Fill the "Ready for review" template so that we can review your PR. This template helps reviewers understand your changes as well as the purpose of your pull request. Don't forget to link PR to issue if you are solving one.<br> | ||
Enable the checkbox to allow maintainer edits so the branch can be updated for a merge. Once you submit your PR, a team member will review your proposal. We may ask questions or request for additional information.<br> | ||
We may ask for changes to be made before a PR can be merged, either using suggested changes or pull request comments.<br> | ||
As you update your PR and apply changes, mark each conversation as resolved. Once your PR is merged, your contributions will be publicly visible on the GitHub.<br> | ||
|
||
## CONTRIBUTORS LIST | ||
|
||
Nicole Aguiar, Frelance GIS consultant.<br> | ||
Jordi Blanch, Stagier on BGEO OPEN GIS.<br> | ||
Guillem Esteve, Stagier on BGEO OPEN GIS.<br> | ||
|
@@ -94,4 +103,5 @@ Edgar Fuste, GIS developer on BGEO OPEN GIS.<br> | |
Albert Bofill, GIS analyst on BGEO OPEN GIS.<br> | ||
Barbara Rzepka, GIS analyst on BGEO OPEN GIS.<br> | ||
Xavier Torret, GIS analyst on BGEO OPEN GIS.<br> | ||
|
||
Daniel Marín, Backend on BGEO OPEN GIS.<br> | ||
Ferran Martínez, Frontend on BGEO OPEN GIS.<br> |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.