Public completion certificates

Open
#423 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
30/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
ruby
Domain
backend

Research direction

The issue names no files, tests, or entry points. Start by locating the certificate creation and viewing code, then determine how public links and visibility are currently handled. Done means certificates can be linked and viewed publicly, with a decided default or opt-in policy and authenticity verification.

Written by the indexing model from the issue text.

Description

easy enhancement

Make certificates easily linkable and publically viewable, so others an verify their authenticity.

Consider if certificates should be public by default or whether this should be opt-in.

Dominant language
Ruby
Stars
51
Forks
42
Avg merge
1h 27m
Merged PRs (30d)
1

Contributor guide

Open the contributing guide

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 testmycode/tmc-server

All issues in testmycode/tmc-server

Similar issues

More Ruby issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.