Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

From GIS CoP

Open
#12 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Documentation
Clarity
Needs clarification
Activity status
Stale
Domain
api, documentation

Research direction

No implementation file or test is named. Start by reviewing the existing API Guidelines and the questions about cataloguing, documentation, API keys, and authentication; done means turning an agreed scope into guidance or clearly recording where consumers find these resources.

Written by the indexing model from the issue text.

Description

feedback

Feedback sent via API Guidelines from Yammer (GIS CoP):
William Burt (FLNRORD, Regional Geomatics Specialist, Kootenay Boundary Region)
–
This guidance looks great. Likely I won't be developing an api anytime soon but perhaps I would be a consumer. Many of bcgov api are purpose built for and limited to one application. To animate the new data story line that is being presented access needs to be open to other consumers with un-forcasted use cases.
Here are some questions I expect this COP would have:- Are our APIs catalogued and documented like data? If I need documentation, an api key or authentication where would someone go?

Dominant language
No language data
Stars
34
Forks
10
PR merge metrics
No merged PRs in 30d

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from bcgov/api-guidelines

All issues in bcgov/api-guidelines

Similar issues

More Backend & API Design issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.