Skip to content

Conversation

repo-mountie[bot]
Copy link
Contributor

@repo-mountie repo-mountie bot commented Aug 10, 2020

Repos in our organization need to be licensed appropriately; you'll need to decide how to licence different components of your project based on what the contents are. Here is the TL;DR version:

  1. Source code created by the BCGov should be Apache (Apache-2.0);
  2. Text created by the BCGov should be Creative Commons International 4.0 (CC BY);
  3. Data created by the BCGov should be Open Government Licence - BC (OGL-BC).

For more information, or for out-of-the-box situations check out the BC Policy Framework for GitHub.

Since most repos are code based I've added the Apache-2.0 license as part of this PR. Please checkout this branch and change the license as needed or merge if if you're happy with my suggestion.

Pro Tip 🤓

  • If you're not sure what to do add a comment with the the command @repo-mountie help in it; a real-live-person will reply back to help you out.

  • Only license content BCGov creates. If it was created by someone else you must include the original license that work was released under.

Commands 🤖

I can update the status of the PIA and STRA for you; you'll just need to merge the PR when I'm done. You can find the available status values in the table above. Below are some commands I understand:

Command Description
@repo-mountie help You're freaking out and want to talk to a person.

Examples

@repo-mountie help

@repo-mountie
Copy link
Contributor Author

repo-mountie bot commented Jan 1, 2021

Hey, its been 90 days since this PR was last updated. I'm sure everyone is busy, however, it would be appreciated if someone from the team puts this issue to bed. Thanks in Advance.

@repo-mountie
Copy link
Contributor Author

repo-mountie bot commented May 10, 2021

Hey, its been 126 days since this PR was last updated. I'm sure everyone is busy, however, it would be appreciated if someone from the team puts this issue to bed. Thanks in Advance.

@repo-mountie
Copy link
Contributor Author

repo-mountie bot commented Sep 8, 2021

Hey, its been 120 days since this PR was last updated. I'm sure everyone is busy, however, it would be appreciated if someone from the team puts this issue to bed. Thanks in Advance.

6 similar comments
@repo-mountie
Copy link
Contributor Author

repo-mountie bot commented Jan 6, 2022

Hey, its been 120 days since this PR was last updated. I'm sure everyone is busy, however, it would be appreciated if someone from the team puts this issue to bed. Thanks in Advance.

@repo-mountie
Copy link
Contributor Author

repo-mountie bot commented May 6, 2022

Hey, its been 120 days since this PR was last updated. I'm sure everyone is busy, however, it would be appreciated if someone from the team puts this issue to bed. Thanks in Advance.

@repo-mountie
Copy link
Contributor Author

repo-mountie bot commented Sep 4, 2022

Hey, its been 120 days since this PR was last updated. I'm sure everyone is busy, however, it would be appreciated if someone from the team puts this issue to bed. Thanks in Advance.

@repo-mountie
Copy link
Contributor Author

repo-mountie bot commented Jan 3, 2023

Hey, its been 120 days since this PR was last updated. I'm sure everyone is busy, however, it would be appreciated if someone from the team puts this issue to bed. Thanks in Advance.

@repo-mountie
Copy link
Contributor Author

repo-mountie bot commented May 4, 2023

Hey, its been 120 days since this PR was last updated. I'm sure everyone is busy, however, it would be appreciated if someone from the team puts this issue to bed. Thanks in Advance.

@repo-mountie
Copy link
Contributor Author

repo-mountie bot commented Sep 1, 2023

Hey, its been 120 days since this PR was last updated. I'm sure everyone is busy, however, it would be appreciated if someone from the team puts this issue to bed. Thanks in Advance.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants