TL;DR

Topics greatly improve the discoverability of repos; please add the short code from the table below to the topics of your repo so that ministries can use GitHub's search to find out what repos belong to them and other visitors can find useful content (and reuse it!).

Why Topic

In short order we'll add our 800th repo. This large number clearly demonstrates the success of using GitHub and our Open Source initiative. This huge success means its critical that we work to make our content as discoverable as possible; Through discoverability, we promote code reuse across a large decentralized organization like the Government of British Columbia as well as allow ministries to find the repos they own.

What to do

Below is a table of abbreviation a.k.a short codes for each ministry; they're the ones used in all @gov.bc.ca email addresses. Please add the short codes of the ministry or organization that "owns" this repo as a topic.

That's in, you're done!!!

How to use

Once topics are added, you can use them in GitHub's search. For example, enter something like org:bcgov topic:citz to find all the repos that belong to Citizens' Services. You can refine this search by adding key words specific to a subject you're interested in. To learn more about searching through repos check out GitHub's doc on searching.

Pro Tip 🤓

• If your org is not in the list below, or the table contains errors, please create an issue here.

• While you're doing this, add additional topics that would help someone searching for "something". These can be the language used javascript or R; something like opendata or data for data only repos; or any other key words that are useful.

• Add a meaningful description to your repo. This is hugely valuable to people looking through our repositories.

• If your application is live, add the production URL.

Ministry Short Codes

NOTE See an error or omission? Please create an issue here to get it remedied.

Trying to view the guide, the link in the description leads to this page.

This issue is a kind reminder that your repository has been inactive for 608.07 days. Some repositories are maintained in accordance with business requirements that infrequently change thus appearing inactive, and some repositories are inactive because they are unmaintained.

To help differentiate products that are unmaintained from products that do not require frequent maintenance, repomountie will open an issue whenever a repository has not been updated in 608.07 days.

If this product is being actively maintained, please close this issue.
If this repository isn't being actively maintained anymore, please archive this repository.

Thank you for your help ensuring effective governance of our open-source ecosystem!

Section 2: Resources:
I want to good content for the Web

This issue is a kind reminder that your repository has been inactive for 609 days. Some repositories are maintained in accordance with business requirements that infrequently change thus appearing inactive, and some repositories are inactive because they are unmaintained.

To help differentiate products that are unmaintained from products that do not require frequent maintenance, repomountie will open an issue whenever a repository has not been updated in 180 days.

• If this product is being actively maintained, please close this issue.
• If this repository isn't being actively maintained anymore, please archive this repository. Also, for bonus points, please add a dormant or retired life cycle badge.

Thank you for your help ensuring effective governance of our open-source ecosystem!

Guide of Guides is the only one with the BCGov CSS applied. Need to do all guides and template.

This issue is a kind reminder that your repository has been inactive for 610 days. Some repositories are maintained in accordance with business requirements that infrequently change thus appearing inactive, and some repositories are inactive because they are unmaintained.

To help differentiate products that are unmaintained from products that do not require frequent maintenance, repomountie will open an issue whenever a repository has not been updated in 180 days.

• If this product is being actively maintained, please close this issue.
• If this repository isn't being actively maintained anymore, please archive this repository. Also, for bonus points, please add a dormant or retired life cycle badge.

Thank you for your help ensuring effective governance of our open-source ecosystem!

Value: $9,000.00Closes: Thursday, February 8, 2018Location: Victoria Some in-person work required

Opportunity Description

As the Government of British Columbia increases delivery of digital services, there is a need to help all stakeholders understand what “digital” means.   At the same time, there is a subset of stakeholders that will need to know what tools, techniques, and methodologies are recommended for their use to design and build digital services.  The website described by the GitHub repositories in the next paragraph is a first iteration, a prototype, of a “Digital Guide” for the Government of British Columbia.

Beginning a journey towards a “BC Digital Guide,” this site is the first step.  Modelled after 18F in the U.S. and UK Government Digital Service, the government reference in this repository, supported by the guides found through this repository  is organized like this (from the FAQ):  “You’ll find three layers to the toolkit: (i) a front page describing basic steps and principles, (ii), a set of high level guides that further define those steps and principles, and (iii) detailed guides providing a deeper level of information and instruction with those responsible for designing and delivering simple, streamlined, modern services.” 

This iteration intends to build out content, to fill in the blanks, as it were, to take the collection of guides to a first official release.  Most of this work is focused on updating the detailed guides, adding new guides, and providing links to other good related government references.

Phase 1

Propose a methodology or mechanism to facilitate contribution from anyone across government

Propose a method of measuring, collecting, and analysing visitor behaviour so that the content, navigation, and overall service can be improved.

Implement both of these methods.

Phase 2

Fix navigation so that it works as expected, forward and back.

Provide a Search function on the home page so that content on that page is easier to find.

Correct feedback and email links to proper endpoints (to be provided.)

Include new and updated content (to be provided.)

Include a section for “Corporate Enablers”, and a one-page description of what each is, and how to consume them (content to be provided).

Include an expanded collection of links for DataBC (links to be provided).

Acceptance Criteria

• Work with our Agile/Scrum team (4000 Seymour Place in Victoria, BC):
• The DigitalToolkit team works in 1-week sprints. You will attend in-person planning (2 hours) and review (3 hours) meetings for each sprint.
• You will track your work with the team on our DigitalToolkit Trello board
• Completion of Phase 1  $4,000
• Completion of Phase 2  $5,000

How to Apply

Go to the Opportunity Page, click the Apply button above and submit your proposal by 16:00 PST on Thursday, February 8, 2018.

We plan to assign this opportunity by Saturday, February 10, 2018 with work to start on Wednesday, February 14, 2018.

Proposal Evaluation Criteria

1. Your confirmation of being able to commit the time to meet all of the Acceptance Criteria by Wednesday, February 7, 2018.
2. A short (200 words or less) summary of your experience working with agile projects (40 points).
3. References to your relevant experience and demonstrated ability to do the work (60 points). For example, a link to your GitHub projects

Hi, could you please add a LICENSE file to your repo. All repositories in the BCGOV ORG are required to have a LICENSE file. Reference: https://github.com/bcgov/BC-Policy-Framework-For-GitHub/tree/master/BC-Gov-Org-HowTo and https://github.com/bcgov/BC-Policy-Framework-For-GitHub/blob/master/BC-Gov-Org-HowTo/Cheatsheet.md. Thank you.

The application currently uses ruby-webrick (https://github.com/ruby/webrick) which intended for low-traffic non production sites.
Suggest to research of other webservers (caddy, ruby-unicorn, ruby-thin, etc) which are more appropriate for a production site.

This issue is a kind reminder that your repository has been inactive for 611 days. Some repositories are maintained in accordance with business requirements that infrequently change thus appearing inactive, and some repositories are inactive because they are unmaintained.

To help differentiate products that are unmaintained from products that do not require frequent maintenance, repomountie will open an issue whenever a repository has not been updated in 180 days.

• If this product is being actively maintained, please close this issue.
• If this repository isn't being actively maintained anymore, please archive this repository. Also, for bonus points, please add a dormant or retired life cycle badge.

Thank you for your help ensuring effective governance of our open-source ecosystem!

The innovation toolkit proof of concept needs to be showed around gov to help raise awareness of the team and technology learnings

No Project Lifecycle Badge found in your readme!

Hello! I scanned your readme and could not find a project lifecycle badge. A project lifecycle badge will provide contributors to your project as well as other stakeholders (platform services, executive) insight into the lifecycle of your repository.

What is a Project Lifecycle Badge?

It is a simple image that neatly describes your project's stage in its lifecycle. More information can be found in the project lifecycle badges documentation.

What do I need to do?

I suggest you make a PR into your README.md and add a project lifecycle badge near the top where it is easy for your users to pick it up :). Once it is merged feel free to close this issue. I will not open up a new one :)

1. Address legislation, privacy and security by design
2. Leverage flexible deployment
3. Achieve continuous improvement