Revise and define flexible and great paste visibility strategies

Open
#202 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Domain
authorization, security

Research direction

No files, tests, or entry points are identified. Start by locating the two existing paste visibility strategies, then research and compare candidate strategies against usability, user experience, and peer support; done means a specific strategy is selected and its requirements are clearly defined.

Written by the indexing model from the issue text.

Description

easy enhancement important

Currently we have only two pastebin visibility strategies, neither one is really good.

Investigate new relevant strategies, based on research interests, usability and user experience, and best possible peer support (students helping each other).

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.