https://github.com/henrahmagix/anony

Anonymous feedback system
https://github.com/henrahmagix/anony

Last synced: 9 days ago
JSON representation

Anonymous feedback system

• Host: GitHub
• URL: https://github.com/henrahmagix/anony
• Owner: henrahmagix
• License: mit
• Created: 2017-07-07T11:51:03.000Z (over 7 years ago)
• Default Branch: master
• Last Pushed: 2017-07-07T12:36:40.000Z (over 7 years ago)
• Last Synced: 2024-12-11T20:06:02.266Z (about 1 month ago)
• Size: 1.95 KB
• Stars: 0
• Watchers: 2
• Forks: 0
• Open Issues: 0
• Metadata Files:
  • Readme: README.md
  • License: LICENSE

Awesome Lists containing this project

README

        
# anony

Anonymous feedback system

## Goal

To provide a system for anonymous authors to submit issues to named recipients and receive feedback, including issue status.

The system will provide a unique login method to users through a sign-up form that requires no input.

Each item in the system will be an "issue". Each issue can be submitted to any number of named recipients at any time.

The status of an issue can be set by the author or the recipient, but the author must accept any changes to status by the recipient. For example: the recipient may mark an issue as resolved, but the author may decline this status to ensure the issue stays open until the author is satisfied.

Statuses include:

- received

- accepted

- awaiting response

- closed as actioned

- denied/closed (requires reason)

The author can make themselves known at any time and move discussion to a different medium, but is not required to do so.

Named recipients will be sent an invite to sign-up with user information (different to anonymous authors). 

## Sign-up and Login

An anonymous author will be able to ask for a random sign-in, and the system will respond with a unique ID. The author must remember or otherwise save this ID: it is the only thing that gives them access to their feedback submissions.

Alternatively, an anonymous author may author a submission and receive a unique ID upon submission, such that every issue they make may be separated.

## Storage

The storage method will be assigned when this system is deployed by the deployer(s).

This system may offer built-in methods but primarily it will be up to the initiator to attach a backend and determine it satisfies the requirements for anonymity.

## Anonymity requirements

For the chosen storage method, answer the questions below. A "yes" is 👍, a "no" is 👎. The more 👍 the better.

It is up to the deployer(s) (ideally the future authors) to seek changes to produce what they would accept as an anonymous system. The questions below are provided as best practices: it is up to you to decide how many must be 👍.

- Can an issue be viewed by anyone without the author inviting them to do so?

- [More to come]