From e45e90bf6672b83d9099e9b6b8d3c616da6d48f8 Mon Sep 17 00:00:00 2001 From: Bakaniko Date: Mon, 17 Sep 2018 16:20:38 +0200 Subject: [PATCH 1/9] #1987 Adding CONTRIBUTING.md https://trac.osgeo.org/osgeolive/ticket/1987 https://lists.osgeo.org/pipermail/osgeolive/2018-September/013566.html --- CONTRIBUTING.md | 125 ++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 125 insertions(+) create mode 100644 CONTRIBUTING.md diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md new file mode 100644 index 0000000000..7282a808d0 --- /dev/null +++ b/CONTRIBUTING.md @@ -0,0 +1,125 @@ +# Contributing + +When contributing to this repository, please first discuss the change you wish to make via [issue on our bug tracker](https://trac.osgeo.org/osgeolive/report/1), +[OSGeoLive mailing list](https://lists.osgeo.org/mailman/listinfo/osgeolive), or any other method with the owners of this repository before making a change. + +By submitting you are agreeing to make your content available via our [open license policy](https://live.osgeo.org/en/copyright.html). + +In the same manner, when translating on Transifex, you are agreeing to make your translations following those licence terms. + +Please note we have a code of conduct, please follow it in all your interactions with the project. + + +## Pull Request Process + +1. TO-DO + +## Translation process +### Join a translation team and translate + +1. Create an account or login on [Transifex](https://www.transifex.com/osgeo/osgeolive/) +2. Request joining a translation team +3. Translate ! +4. Please consider adding your self to our [contributor list](https://github.com/OSGeo/OSGeoLive-doc/blob/master/contributors.csv), if you don't know how to use git, please contact a maintainer. + +### Request a new language + +1. TO-DO + +## Code of Conduct + +**Bakaniko's comment:** This part was part of the template, it can be + +### Our Pledge + +In the interest of fostering an open and welcoming environment, we as +contributors and maintainers pledge to making participation in our project and +our community a harassment-free experience for everyone, regardless of age, body +size, disability, ethnicity, gender identity and expression, level of experience, +nationality, personal appearance, race, religion, or sexual identity and +orientation. + +### Our Standards + +Examples of behavior that contributes to creating a positive environment +include: + +* Using welcoming and inclusive language +* Being respectful of differing viewpoints and experiences +* Gracefully accepting constructive criticism +* Focusing on what is best for the community +* Showing empathy towards other community members + +Examples of unacceptable behavior by participants include: + +* The use of sexualized language or imagery and unwelcome sexual attention or +advances +* Trolling, insulting/derogatory comments, and personal or political attacks +* Public or private harassment +* Publishing others' private information, such as a physical or electronic + address, without explicit permission +* Other conduct which could reasonably be considered inappropriate in a + professional setting + +### Our Responsibilities + +**Bakaniko's comment:** This is the official OSGeo Code of Conduct + +Contributors to OSGeoLive are expected to act respectfully toward others in accordance with the [OSGeo Code of Conduct](https://www.osgeo.org/code_of_conduct/). + +#### Diversity Statement + +OSGeo welcomes and encourages participation by everyone. We are committed to being a community that everyone feels good about joining, and we will always work to treat everyone well. No matter how you identify yourself or how others perceive you: we welcome you. + +#### Specific Guidelines + +We strive to: + +* Be open. + We invite anyone to participate in our community. We preferably use public methods of communication for project-related messages, unless discussing something sensitive. This applies to messages for help or project-related support, too; not only is a public support request much more likely to result in an answer to a question, it also makes sure that any inadvertent mistakes made by people answering will be more easily detected and corrected. + +* Be empathetic, welcoming, friendly, and patient. + We work together to resolve conflict, assume good intentions, and do our best to act in an empathetic fashion. We may all experience some frustration from time to time, but we do not allow frustration to turn into a personal attack. A community where people feel uncomfortable or threatened is not a productive one. Note that we have a multi-cultural, multi-lingual community and some of us are non-native speakers. We should be respectful when dealing with other community members as well as with people outside our community. + +* Be collaborative. + Our work will be used by other people, and in turn we will depend on the work of others. When we make something for the benefit of OSGeo, we are willing to explain to others how it works, so that they can build on the work to make it even better. Any decision we make will affect users and colleagues, and we take those consequences seriously when making decisions. + +* Be inquisitive. + Nobody knows everything! Asking questions early avoids many problems later, so questions are encouraged, though they may be directed to the appropriate forum. Those who are asked should be responsive and helpful, within the context of our shared goal of improving OSGeo. + +* Be careful in the words that we choose. + Whether we are participating as professionals or volunteers, we value professionalism in all interactions, and take responsibility for our own speech. Be kind to others. Do not insult or put down other participants. + +* Be concise + Keep in mind that what you write once will be read by hundreds of persons. Writing a short email means people can understand the conversation as efficiently as possible. Short emails should always strive to be empathetic, welcoming, friendly and patient. When a long explanation is necessary, consider adding a summary. + + Try to bring new ideas to a conversation so that each mail adds something unique to the thread, keeping in mind that the rest of the thread still contains the other messages with arguments that have already been made. + + Try to stay on topic, especially in discussions that are already fairly large. + +* Step down considerately. + Members of every project come and go. When somebody leaves or disengages from the project they should tell people they are leaving and take the proper steps to ensure that others can pick up where they left off. In doing so, they should remain respectful of those who continue to participate in the project and should not misrepresent the project’s goals or achievements. Likewise, community members should respect any individual’s choice to leave the project. + +#### Anti-Harassment + +Harassment and other exclusionary behaviour are not acceptable. This includes, but is not limited to: + + Personal insults or discriminatory jokes and language, especially those using racist or sexist terms. + Offensive comments, excessive or unnecessary profanity. + Intimidation, violent threats or demands. + Sustained disruption of sessions or events. + Stalking, harassing photography or recording. + Unwelcome physical contact or sexual attention. + Repeated harassment of others. In general, if someone asks you to stop, then stop. + Posting (or threatening to post) other people’s personally identifying information (“doxing”). + Sharing private content, such as emails sent privately or non-publicly, or unlogged forums such as IRC channel history. + Advocating for, or encouraging, any of the above behaviour. + +#### Reporting Guidelines + +If you believe someone is breaking this code of conduct, you may reply to them, and point to this code of conduct. Such messages may be in public or in private, whatever is most appropriate. Assume good faith; it is more likely that participants are unaware of their bad behaviour than that they intentionally try to degrade the quality of the discussion. Should there be difficulties in dealing with the situation, you may report your concerns to event staff, a forum leader or the OSGeo Board. Serious or persistent offenders may be expelled from the event or forum by event organizers or forum leaders. + +### Attribution + +This CONTRIBUTING.md is inspired by [PurpleBooth/Good-CONTRIBUTING.md-template.md](https://gist.github.com/PurpleBooth/b24679402957c63ec426) + From 6670ccf94c9bdf5c4982d1b9b8a4095d0b4849aa Mon Sep 17 00:00:00 2001 From: Bakaniko Date: Mon, 1 Oct 2018 20:59:52 +0200 Subject: [PATCH 2/9] Shorter CoC --- CONTRIBUTING.md | 91 ++++--------------------------------------------- 1 file changed, 7 insertions(+), 84 deletions(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 7282a808d0..712ad415c4 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -28,96 +28,19 @@ Please note we have a code of conduct, please follow it in all your interactions ## Code of Conduct -**Bakaniko's comment:** This part was part of the template, it can be - -### Our Pledge - -In the interest of fostering an open and welcoming environment, we as -contributors and maintainers pledge to making participation in our project and -our community a harassment-free experience for everyone, regardless of age, body -size, disability, ethnicity, gender identity and expression, level of experience, -nationality, personal appearance, race, religion, or sexual identity and -orientation. - -### Our Standards - -Examples of behavior that contributes to creating a positive environment -include: - -* Using welcoming and inclusive language -* Being respectful of differing viewpoints and experiences -* Gracefully accepting constructive criticism -* Focusing on what is best for the community -* Showing empathy towards other community members - -Examples of unacceptable behavior by participants include: - -* The use of sexualized language or imagery and unwelcome sexual attention or -advances -* Trolling, insulting/derogatory comments, and personal or political attacks -* Public or private harassment -* Publishing others' private information, such as a physical or electronic - address, without explicit permission -* Other conduct which could reasonably be considered inappropriate in a - professional setting - -### Our Responsibilities - -**Bakaniko's comment:** This is the official OSGeo Code of Conduct - Contributors to OSGeoLive are expected to act respectfully toward others in accordance with the [OSGeo Code of Conduct](https://www.osgeo.org/code_of_conduct/). -#### Diversity Statement - -OSGeo welcomes and encourages participation by everyone. We are committed to being a community that everyone feels good about joining, and we will always work to treat everyone well. No matter how you identify yourself or how others perceive you: we welcome you. - -#### Specific Guidelines - -We strive to: - -* Be open. - We invite anyone to participate in our community. We preferably use public methods of communication for project-related messages, unless discussing something sensitive. This applies to messages for help or project-related support, too; not only is a public support request much more likely to result in an answer to a question, it also makes sure that any inadvertent mistakes made by people answering will be more easily detected and corrected. - -* Be empathetic, welcoming, friendly, and patient. - We work together to resolve conflict, assume good intentions, and do our best to act in an empathetic fashion. We may all experience some frustration from time to time, but we do not allow frustration to turn into a personal attack. A community where people feel uncomfortable or threatened is not a productive one. Note that we have a multi-cultural, multi-lingual community and some of us are non-native speakers. We should be respectful when dealing with other community members as well as with people outside our community. - -* Be collaborative. - Our work will be used by other people, and in turn we will depend on the work of others. When we make something for the benefit of OSGeo, we are willing to explain to others how it works, so that they can build on the work to make it even better. Any decision we make will affect users and colleagues, and we take those consequences seriously when making decisions. - -* Be inquisitive. - Nobody knows everything! Asking questions early avoids many problems later, so questions are encouraged, though they may be directed to the appropriate forum. Those who are asked should be responsive and helpful, within the context of our shared goal of improving OSGeo. - -* Be careful in the words that we choose. - Whether we are participating as professionals or volunteers, we value professionalism in all interactions, and take responsibility for our own speech. Be kind to others. Do not insult or put down other participants. - -* Be concise - Keep in mind that what you write once will be read by hundreds of persons. Writing a short email means people can understand the conversation as efficiently as possible. Short emails should always strive to be empathetic, welcoming, friendly and patient. When a long explanation is necessary, consider adding a summary. - - Try to bring new ideas to a conversation so that each mail adds something unique to the thread, keeping in mind that the rest of the thread still contains the other messages with arguments that have already been made. - - Try to stay on topic, especially in discussions that are already fairly large. - -* Step down considerately. - Members of every project come and go. When somebody leaves or disengages from the project they should tell people they are leaving and take the proper steps to ensure that others can pick up where they left off. In doing so, they should remain respectful of those who continue to participate in the project and should not misrepresent the project’s goals or achievements. Likewise, community members should respect any individual’s choice to leave the project. - -#### Anti-Harassment +By submitting content to this project, you agree to be bound by the OSGeo contributor agreement [OSGeo Code of Conduct](https://www.osgeo.org/code_of_conduct/). -Harassment and other exclusionary behaviour are not acceptable. This includes, but is not limited to: +Please read carefully the [OSGeo Code of Conduct](https://www.osgeo.org/code_of_conduct/) and +note that the OSGeoLive project will follow its **Diversity Statement**, **Specific Guidelines** and +its **Anti-Harassment** and **Reporting Guidelines**. So please be sure to have read those +sections. - Personal insults or discriminatory jokes and language, especially those using racist or sexist terms. - Offensive comments, excessive or unnecessary profanity. - Intimidation, violent threats or demands. - Sustained disruption of sessions or events. - Stalking, harassing photography or recording. - Unwelcome physical contact or sexual attention. - Repeated harassment of others. In general, if someone asks you to stop, then stop. - Posting (or threatening to post) other people’s personally identifying information (“doxing”). - Sharing private content, such as emails sent privately or non-publicly, or unlogged forums such as IRC channel history. - Advocating for, or encouraging, any of the above behaviour. +If you contribution is more than a small fix to an existing file, please send +a signed contributor agreement to the [OSGeoLive mailing list](https://lists.osgeo.org/mailman/listinfo/osgeolive). -#### Reporting Guidelines -If you believe someone is breaking this code of conduct, you may reply to them, and point to this code of conduct. Such messages may be in public or in private, whatever is most appropriate. Assume good faith; it is more likely that participants are unaware of their bad behaviour than that they intentionally try to degrade the quality of the discussion. Should there be difficulties in dealing with the situation, you may report your concerns to event staff, a forum leader or the OSGeo Board. Serious or persistent offenders may be expelled from the event or forum by event organizers or forum leaders. ### Attribution From 9d094ef5b4c2bf3519e50d6e6fe38e57ad8810e3 Mon Sep 17 00:00:00 2001 From: Bakaniko Date: Mon, 1 Oct 2018 21:54:56 +0200 Subject: [PATCH 3/9] Adding CLA and Carto inspired obvious fix rule Follows Jody's recommendations [1] and adding contributor licensing agreement and OBVIOUS FIX rule [1] https://lists.osgeo.org/pipermail/osgeolive/2018-September/013593.html --- CONTRIBUTING.md | 77 +++++++++++++++++++++++++++++++++++++++++++++++-- 1 file changed, 74 insertions(+), 3 deletions(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 712ad415c4..5ee181418c 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -1,6 +1,6 @@ # Contributing -When contributing to this repository, please first discuss the change you wish to make via [issue on our bug tracker](https://trac.osgeo.org/osgeolive/report/1), +When contributing to this repository, read the Pull Request Process section and if necessary,discuss the change you wish to make via [issue on our bug tracker](https://trac.osgeo.org/osgeolive/report/1), [OSGeoLive mailing list](https://lists.osgeo.org/mailman/listinfo/osgeolive), or any other method with the owners of this repository before making a change. By submitting you are agreeing to make your content available via our [open license policy](https://live.osgeo.org/en/copyright.html). @@ -12,7 +12,76 @@ Please note we have a code of conduct, please follow it in all your interactions ## Pull Request Process -1. TO-DO +1. Evaluate the change +2. If necessary, sign the **contributor licensing agreement** +3. For big changes fill, eventually engage discussion in a new issue or in the mailing list. +4. Make the PR + +### Evaluate the change + +In the OSGeoLive, we see 2 type of contribution. + +#### What qualifies as an OBVIOUS FIX? +An obvious fix is a pull request that does not contain creative work. We rely on your judgment to determine what is “obvious”; if you’re not sure, just ask by sending an email to the [OSGeoLive mailing list](https://lists.osgeo.org/mailman/listinfo/osgeolive). + +As a rule of thumb, changes are obvious fixes if they do not introduce any new functionality or creative thinking. As long as the change does not affect functionality, some likely examples include the following: + +* Spelling/grammar fixes; +* Correcting typos; +* Cleaning up comments in the code; +* Changes to white space or formatting; +* Adding logging messages or debugging output; +* Changes to files like Makefile, .gitignore, example configuration files, build scripts, etc.; +* Changes that reflect outside facts, like renaming a build directory or changing a constant; +* Changes in build or installation scripts; +* Re-ordering of objects or subroutines within a source file (such as alphabetizing routines); +* Moving source files from one directory or package to another, with no changes in code; +* Breaking a source file into multiple source files, or consolidating multiple source files into one source file, with no change in code behavior; +* Changes to words or phrases isolated from their context; +* Changes to typeface. + +#### Things that would still require signing a CLA before submitting would likely include stuff like the following: + +* Any of the above actions that result in a change in functionality; +* Adding a new project; +* Adding a new file (Overview, Quickstart); +* Joining a translation team; +* Requesting a new language; +* A new feature in the installation files; +* Extensive or creative comments. + +### CLA +A contributor licensing agreement (CLA) must be filled out by every contributor to OSGeoLive. + +The CLA makes everyone’s rights clear: + +You (or your company) grant copyright license for your contributions to CARTO. +You (or your company) grant patent license for your contributions to CARTO. +The contribution is entirely voluntary. +The work is your original creation. +You (or your company) are not required to provide support for your contributions. +You (or your company) should read and understand the entire CLA before signing it. Our description of it is not legally binding. + +Please send your CLA to the [OSGeoLive mailing list](https://lists.osgeo.org/mailman/listinfo/osgeolive). + +#### OSGeoLive CLA example + +"I want to contribute XXX to OSGeoLive. I acknowledge that my contributions will be in line with OSGeoLive's Open licenses and OSGeo Code of Conduct." + +### How does the OBVIOUS FIX RULE work? + +Any committer may commit fixes without first signing a CLA for obvious typos, grammar mistakes, and formatting problems wherever they may be. + +Whenever you invoke the Obvious Fix Rule, please say so in your commit message. For example: + +> commit 375t3248vkdd912b0cf9c1d1e99b13 + Author: javier + Date: Tue Jul 24 12:15:03 2013 -0500 + Fix typo in install file docs. + Obvious fix. + + + ## Translation process ### Join a translation team and translate @@ -44,5 +113,7 @@ a signed contributor agreement to the [OSGeoLive mailing list](https://lists.osg ### Attribution -This CONTRIBUTING.md is inspired by [PurpleBooth/Good-CONTRIBUTING.md-template.md](https://gist.github.com/PurpleBooth/b24679402957c63ec426) +This CONTRIBUTING.md is inspired by [PurpleBooth/Good-CONTRIBUTING.md-template.md](https://gist.github.com/PurpleBooth/b24679402957c63ec426). + +Contributions policy is also based on [Carto CLA's and "Obvious fix" rule](https://carto.com/contributions/). From d9d512cbba137899df7379389c4dc7f732328ff6 Mon Sep 17 00:00:00 2001 From: Bakaniko Date: Mon, 1 Oct 2018 22:28:27 +0200 Subject: [PATCH 4/9] Fix forgotten CARTO mention to OSGeoLive --- CONTRIBUTING.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 5ee181418c..8135589e08 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -55,8 +55,8 @@ A contributor licensing agreement (CLA) must be filled out by every contributor The CLA makes everyone’s rights clear: -You (or your company) grant copyright license for your contributions to CARTO. -You (or your company) grant patent license for your contributions to CARTO. +You (or your company) grant copyright license for your contributions to OSGeoLive. +You (or your company) grant patent license for your contributions to OSGeoLive. The contribution is entirely voluntary. The work is your original creation. You (or your company) are not required to provide support for your contributions. From 353f70d1721ba5483dc1c16bf5a437891146065e Mon Sep 17 00:00:00 2001 From: Nicolas Roelandt Date: Tue, 17 Sep 2019 21:53:07 +0200 Subject: [PATCH 5/9] Remove misplaced line about CLA --- CONTRIBUTING.md | 7 ------- 1 file changed, 7 deletions(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 8135589e08..bb1ff72be0 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -80,9 +80,6 @@ Whenever you invoke the Obvious Fix Rule, please say so in your commit message. Fix typo in install file docs. Obvious fix. - - - ## Translation process ### Join a translation team and translate @@ -106,10 +103,6 @@ note that the OSGeoLive project will follow its **Diversity Statement**, **Speci its **Anti-Harassment** and **Reporting Guidelines**. So please be sure to have read those sections. -If you contribution is more than a small fix to an existing file, please send -a signed contributor agreement to the [OSGeoLive mailing list](https://lists.osgeo.org/mailman/listinfo/osgeolive). - - ### Attribution From 3b658c3429e4f92d0f6d57df72f905bffa235d66 Mon Sep 17 00:00:00 2001 From: Nicolas Roelandt Date: Tue, 17 Sep 2019 21:55:40 +0200 Subject: [PATCH 6/9] Adding Reporting guidelines --- CONTRIBUTING.md | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index bb1ff72be0..be76ef53ad 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -103,6 +103,11 @@ note that the OSGeoLive project will follow its **Diversity Statement**, **Speci its **Anti-Harassment** and **Reporting Guidelines**. So please be sure to have read those sections. +### Reporting Guidelines + +If you believe someone behaving inappropriately with respect to a code of conduct, you may reply to them, and point to this code of conduct. Such messages may be in public or in private, whatever is most appropriate. Assume good faith; it is more likely that participants are unaware of their bad behaviour than that they intentionally try to degrade the quality of the discussion. Should there be difficulties in dealing with the situation, you may report your concerns to event staff, a forum leader or any OSGeo Board member or officer. Serious or persistent offenders may be expelled from the event or forum by event organizers or forum leaders. + +To privately email the code of conduct committee leadership use coc@osgeo.org. ### Attribution From 6373141cca3a3d941adfc9e6e7a5ee8ff79a6409 Mon Sep 17 00:00:00 2001 From: Nicolas Roelandt Date: Tue, 17 Sep 2019 21:59:40 +0200 Subject: [PATCH 7/9] Add contacting PSC members to report --- CONTRIBUTING.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index be76ef53ad..5bc3ae12ac 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -107,7 +107,7 @@ sections. If you believe someone behaving inappropriately with respect to a code of conduct, you may reply to them, and point to this code of conduct. Such messages may be in public or in private, whatever is most appropriate. Assume good faith; it is more likely that participants are unaware of their bad behaviour than that they intentionally try to degrade the quality of the discussion. Should there be difficulties in dealing with the situation, you may report your concerns to event staff, a forum leader or any OSGeo Board member or officer. Serious or persistent offenders may be expelled from the event or forum by event organizers or forum leaders. -To privately email the code of conduct committee leadership use coc@osgeo.org. +You can contact any [OSGeoLive PSC member](https://wiki.osgeo.org/wiki/OSGeoLive_PSC) or privately email the code of conduct committee leadership using this mail adress : coc@osgeo.org. ### Attribution From 511aedce272a16cc69bf4b480a6802372ae8b79b Mon Sep 17 00:00:00 2001 From: Markus Neteler Date: Sat, 3 Dec 2022 11:46:26 +0100 Subject: [PATCH 8/9] Apply suggestions from code review --- CONTRIBUTING.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 5bc3ae12ac..5acd69994d 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -1,6 +1,6 @@ # Contributing -When contributing to this repository, read the Pull Request Process section and if necessary,discuss the change you wish to make via [issue on our bug tracker](https://trac.osgeo.org/osgeolive/report/1), +When contributing to this repository, read the Pull Request Process section and if necessary, discuss the change you wish to make via [issue on our bug tracker](https://trac.osgeo.org/osgeolive/report/1), [OSGeoLive mailing list](https://lists.osgeo.org/mailman/listinfo/osgeolive), or any other method with the owners of this repository before making a change. By submitting you are agreeing to make your content available via our [open license policy](https://live.osgeo.org/en/copyright.html). @@ -19,7 +19,7 @@ Please note we have a code of conduct, please follow it in all your interactions ### Evaluate the change -In the OSGeoLive, we see 2 type of contribution. +In the OSGeoLive, we see two types of contribution. #### What qualifies as an OBVIOUS FIX? An obvious fix is a pull request that does not contain creative work. We rely on your judgment to determine what is “obvious”; if you’re not sure, just ask by sending an email to the [OSGeoLive mailing list](https://lists.osgeo.org/mailman/listinfo/osgeolive). @@ -86,7 +86,7 @@ Whenever you invoke the Obvious Fix Rule, please say so in your commit message. 1. Create an account or login on [Transifex](https://www.transifex.com/osgeo/osgeolive/) 2. Request joining a translation team 3. Translate ! -4. Please consider adding your self to our [contributor list](https://github.com/OSGeo/OSGeoLive-doc/blob/master/contributors.csv), if you don't know how to use git, please contact a maintainer. +4. Please consider adding yourself to our [contributor list](https://github.com/OSGeo/OSGeoLive-doc/blob/master/contributors.csv), if you don't know how to use git, please contact a maintainer. ### Request a new language From b63ea3bb75704d3051e10083b353e26a3cc8294d Mon Sep 17 00:00:00 2001 From: Markus Neteler Date: Sat, 3 Dec 2022 11:48:39 +0100 Subject: [PATCH 9/9] add https://explore.transifex.com/osgeo/osgeolive/ --- CONTRIBUTING.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 5acd69994d..09c63b2288 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -5,7 +5,7 @@ When contributing to this repository, read the Pull Request Process section and By submitting you are agreeing to make your content available via our [open license policy](https://live.osgeo.org/en/copyright.html). -In the same manner, when translating on Transifex, you are agreeing to make your translations following those licence terms. +In the same manner, when translating on [Transifex](https://explore.transifex.com/osgeo/osgeolive/), you are agreeing to make your translations following those licence terms. Please note we have a code of conduct, please follow it in all your interactions with the project.