From 244ee76c732f86776d6a5f500d1aa428e2a5f734 Mon Sep 17 00:00:00 2001 From: Annika <32690119+annikaLiving@users.noreply.github.com> Date: Tue, 2 Jul 2024 08:38:48 -0700 Subject: [PATCH 1/5] Create CODE_OF_CONDUCT.md --- CODE_OF_CONDUCT.md | 74 ++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 74 insertions(+) create mode 100644 CODE_OF_CONDUCT.md diff --git a/CODE_OF_CONDUCT.md b/CODE_OF_CONDUCT.md new file mode 100644 index 0000000..453361d --- /dev/null +++ b/CODE_OF_CONDUCT.md @@ -0,0 +1,74 @@ +## Contributor Covenant Code of Conduct + +## 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 + +Project maintainers are responsible for clarifying the standards of acceptable +behavior and are expected to take appropriate and fair corrective action in +response to any instances of unacceptable behavior. + +Project maintainers have the right and responsibility to remove, edit, or +reject comments, commits, code, wiki edits, issues, and other contributions +that are not aligned to this Code of Conduct, or to ban temporarily or +permanently any contributor for other behaviors that they deem inappropriate, +threatening, offensive, or harmful. + +## Scope + +This Code of Conduct applies both within project spaces and in public spaces +when an individual is representing the project or its community. Examples of +representing a project or community include using an official project e-mail +address, posting via an official social media account, or acting as an appointed +representative at an online or offline event. Representation of a project may be +further defined and clarified by project maintainers. + +## Enforcement + +Instances of abusive, harassing, or otherwise unacceptable behavior may be +reported by contacting the project team at [INSERT EMAIL ADDRESS]. All +complaints will be reviewed and investigated and will result in a response that +is deemed necessary and appropriate to the circumstances. The project team is +obligated to maintain confidentiality with regard to the reporter of an incident. +Further details of specific enforcement policies may be posted separately. + +Project maintainers who do not follow or enforce the Code of Conduct in good +faith may face temporary or permanent repercussions as determined by other +members of the project's leadership. + +## Attribution + +This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4, +available at [http://contributor-covenant.org/version/1/4][version] + +[homepage]: http://contributor-covenant.org +[version]: http://contributor-covenant.org/version/1/4/ From 8b188bec7ba38559a6038599545ecfe75ba4347e Mon Sep 17 00:00:00 2001 From: Annika <32690119+annikaLiving@users.noreply.github.com> Date: Tue, 2 Jul 2024 08:39:18 -0700 Subject: [PATCH 2/5] Create CONTRIBUTING --- CONTRIBUTING | 8 ++++++++ 1 file changed, 8 insertions(+) create mode 100644 CONTRIBUTING diff --git a/CONTRIBUTING b/CONTRIBUTING new file mode 100644 index 0000000..018f460 --- /dev/null +++ b/CONTRIBUTING @@ -0,0 +1,8 @@ +## How to contribute +Government employees, public and members of the private sector are encouraged to contribute to the repository by **forking and submitting a pull request**. + +(If you are new to GitHub, you might start with a [basic tutorial](https://help.github.com/articles/set-up-git) and check out a more detailed guide to [pull requests](https://help.github.com/articles/using-pull-requests/).) + +Pull requests will be evaluated by the repository guardians on a schedule and if deemed beneficial will be committed to the master. + +All contributors retain the original copyright to their stuff, but by contributing to this project, you grant a world-wide, royalty-free, perpetual, irrevocable, non-exclusive, transferable license to all users **under the terms of the license under which this project is distributed.** From 3b6190c32200b8a24f49b2b9c74311d29654a390 Mon Sep 17 00:00:00 2001 From: Annika <32690119+annikaLiving@users.noreply.github.com> Date: Tue, 2 Jul 2024 08:41:01 -0700 Subject: [PATCH 3/5] Update README.md --- README.md | 19 ++++++++++++++++++- 1 file changed, 18 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index 53dffd2..cd48d11 100644 --- a/README.md +++ b/README.md @@ -1,7 +1,24 @@ # Publishing to the DataBC Program -Standards, tips, and tricks to help you on your way. +Standards, tips, and tricks to help you on your way to publishing data and metadata to the BC Geographic Warehous, BC Data Catalogue and BC's MapHub and how to leverage these services and more. See Documentation - [https://bcgov.github.io/data-publication](https://bcgov.github.io/data-publication) [![img](https://img.shields.io/badge/Lifecycle-Maturing-007EC6)](https://github.com/bcgov/repomountie/blob/master/doc/lifecycle-badges.md) [![img](https://img.shields.io/badge/Lifecycle-Stable-97ca00)](https://github.com/bcgov/repomountie/blob/master/doc/lifecycle-badges.md) + +## How to Contribute + +Review the [Contributing Guidelines](CONTRIBUTING.md) and the [Contributor Covenant Code of Conduct](CODE_OF_CONDUCT.md). By participating in this project you agree to abide by its terms. + +## License + + Copyright 2019 Province of British Columbia + + Licensed under the Apache License, Version 2.0 (the "License"); + you may not use this file except in compliance with the License. + You may obtain a copy of the License at + + http://www.apache.org/licenses/LICENSE-2.0 + + Unless required by applicable law or agreed to in writing, software + distributed under the License is distributed on an "AS IS" BASIS, From 85a32065bfced0629534193a193138cf07944577 Mon Sep 17 00:00:00 2001 From: Annika <32690119+annikaLiving@users.noreply.github.com> Date: Tue, 2 Jul 2024 08:46:27 -0700 Subject: [PATCH 4/5] Update README.md --- README.md | 12 +++++++++++- 1 file changed, 11 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index cd48d11..6ab7291 100644 --- a/README.md +++ b/README.md @@ -1,5 +1,15 @@ # Publishing to the DataBC Program -Standards, tips, and tricks to help you on your way to publishing data and metadata to the BC Geographic Warehous, BC Data Catalogue and BC's MapHub and how to leverage these services and more. + +1. Standards, tips, and tricks to help you on your way to publishing data and metadata to the: + * BC Geographic Warehouse + * BC Data Catalogue + * BC's MapHub +1. Leveraging and using: + * WMS/WFS + * BC Data Catalogue API + * Creating useful data + * Naming standards +1. Publishing data under the Open Government Licence - British Columbia See Documentation - [https://bcgov.github.io/data-publication](https://bcgov.github.io/data-publication) From c986d7d63c4c58216cc4e820ada5d0f0de56c3d2 Mon Sep 17 00:00:00 2001 From: Annika <32690119+annikaLiving@users.noreply.github.com> Date: Tue, 2 Jul 2024 08:47:15 -0700 Subject: [PATCH 5/5] Rename CONTRIBUTING to CONTRIBUTING.md --- CONTRIBUTING => CONTRIBUTING.md | 0 1 file changed, 0 insertions(+), 0 deletions(-) rename CONTRIBUTING => CONTRIBUTING.md (100%) diff --git a/CONTRIBUTING b/CONTRIBUTING.md similarity index 100% rename from CONTRIBUTING rename to CONTRIBUTING.md