OpenSeaMap-dev:GitHub: Unterschied zwischen den Versionen

Aus OpenSeaMap-dev
Wechseln zu: Navigation, Suche
K (Edditing code: typo)
(Rules)
 
(4 dazwischenliegende Versionen von 2 Benutzern werden nicht angezeigt)
Zeile 2: Zeile 2:
  
 
== Rules ==
 
== Rules ==
# every theme has his own repository
+
# every theme/topic has its own repository
# every repository has his own repository-team
+
# every repository has its own repository-team
# repoository-team members have write permission
+
# members of a repository-team have write permission
# in repository "general" all OpenSeaMap-devs have write permission
+
# in repository "[https://github.com/OpenSeaMap/general general]" all OpenSeaMap-devs have write permission, currently the repository itself is empty and only the issue tracker is used
# every repository has a maintainer who is responsible for the commitments
+
# by default all OpenSeaMap-devs are member of the "general" team and receive notifications when new issues are created
 +
# every repository has a maintainer who should take care of commits, branches, pull requests, etc.
  
 
If you like to become member of a team, or if you need a new repository:
 
If you like to become member of a team, or if you need a new repository:
* '''Please ask at the [https://lists.sourceforge.net/lists/listinfo/openseamap-develop developers mailing list].'''
+
* '''Please ask at [http://openseamap.org/index.php?id=kontakt&L=1 Contact].'''
 +
 
 +
== How to contribute ==
 +
* Grant repository access only to very few people. <br>If anyone can push changes, there will be a mess and the quality will decrease.
 +
* People who like to support the project should fork the repository, <br>[https://help.github.com/articles/using-pull-requests create a clean commit] (with a reference to the issue in its description) <br> and then [https://help.github.com/articles/creating-a-pull-request create a pull request].
 +
* Pull requests allow the maintainer of the repository to do a review and comment unclear things.
 +
* Bugs and features have to be added to the issue list in the corresponding repository.
  
 
== Editing code ==
 
== Editing code ==
...
+
* [http://sethrobertson.github.io/GitBestPractices/ Git Best Practices]
 +
* [http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html A Note About Git Commit Messages]
 +
* [http://stackoverflow.com/questions/2290016/git-commit-messages-50-72-formatting Commit Messages : 50/72 Formatting]
 +
* [http://stackoverflow.com/questions/1480723/dvcs-how-often-and-when-to-commit-changes How often and when to commit changes]
 +
* [http://nvie.com/posts/a-successful-git-branching-model/ A successful Git branching model]
  
 
== Patches ==
 
== Patches ==
Zeile 44: Zeile 55:
 
| 9 || [https://github.com/OpenSeaMap/gauges gauges] ||  ||  
 
| 9 || [https://github.com/OpenSeaMap/gauges gauges] ||  ||  
 
|-
 
|-
| 10 || [https://github.com/OpenSeaMap/general general] || all together ||  
+
| 10 || [https://github.com/OpenSeaMap/general general] || all together || Currently only the [https://github.com/OpenSeaMap/general/issues issue tracker] is used.
 
|-
 
|-
 
| 11 || [https://github.com/OpenSeaMap/harbour-database harbour-database] ||  ||  
 
| 11 || [https://github.com/OpenSeaMap/harbour-database harbour-database] ||  ||  

Aktuelle Version vom 5. Februar 2021, 11:25 Uhr

OpenSeaMap-code is admistered at https://github.com/OpenSeaMap.

Rules

  1. every theme/topic has its own repository
  2. every repository has its own repository-team
  3. members of a repository-team have write permission
  4. in repository "general" all OpenSeaMap-devs have write permission, currently the repository itself is empty and only the issue tracker is used
  5. by default all OpenSeaMap-devs are member of the "general" team and receive notifications when new issues are created
  6. every repository has a maintainer who should take care of commits, branches, pull requests, etc.

If you like to become member of a team, or if you need a new repository:

How to contribute

  • Grant repository access only to very few people.
    If anyone can push changes, there will be a mess and the quality will decrease.
  • People who like to support the project should fork the repository,
    create a clean commit (with a reference to the issue in its description)
    and then create a pull request.
  • Pull requests allow the maintainer of the repository to do a review and comment unclear things.
  • Bugs and features have to be added to the issue list in the corresponding repository.

Editing code

Patches

...

Commitments

...

Maintainers

Every repository has a maintainer:

No Repository Maintainer Remarks
1 android-ais-openseamap-plotter Victor
2 android-app-openseamapviewer Victor
3 android-app-osmand
4 at5-chart Alexej
5 chart-designer Alexej
6 depth_api Jens
7 depth_webfrontend Jens
8 garmin Alexej
9 gauges
10 general all together Currently only the issue tracker is used.
11 harbour-database
12 ios-app-openseamap Helge Repo is empty...
13 josm Malcolm
14 logger-oseam-0183 Wilfried
15 logger-tplink-0183 Victor Repo is empty...
16 online_chart Dominik
17 renderer Malcolm
18 tidal-scale
19 tide-prediction Alexej
20 website Maintainer for content: Markus
.. [ ]