Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Mechanism for collecting feedback #371

Open
nsheff opened this issue Aug 14, 2024 · 4 comments
Open

Mechanism for collecting feedback #371

nsheff opened this issue Aug 14, 2024 · 4 comments

Comments

@nsheff
Copy link
Contributor

nsheff commented Aug 14, 2024

I would like to add a simple "Help/Feedback" tool to collect feedback from our users.

It would be nice if there was an easy way for them to notify us if something is not working or to ask a question, right from within PEPhub, since they're logged in, we could just make it a simple web form, since it would be unlikely to be abused.

@nleroy917
Copy link
Member

nleroy917 commented Aug 14, 2024

I think soliciting feedback would be useful. My initial thought is: Isn't that what GitHub issue are for? However, the barrier to entry there is a bit higher since you need to know about GitHub, navigate there and open an issue. If it was embedded into the app, its easier to collect that feedback directly.

Alternatively, we could let people into the discord (getting access to only a few channels) and make the conversation synchronous...

@nleroy917
Copy link
Member

nleroy917 commented Aug 20, 2024

A simple form popup in the app is simple to develop and low barrier to entry. We could insert into a table in the database called feedback with the text and then a simple timestamp.

One problem is that we'd need an API endpoint for this, and obviously we need to protect that so people don't start spamming the database feedback table (with a python script)

@sanghoonio
Copy link
Member

sanghoonio commented Aug 27, 2024

I think soliciting feedback would be useful. My initial thought is: Isn't that what GitHub issue are for? However, the barrier to entry there is a bit higher since you need to know about GitHub, navigate there and open an issue. If it was embedded into the app, its easier to collect that feedback directly.

I think you are right. Anyone who uses PEPhub for more than just browsing public PEPs will need a GitHub account. They may not know about the issues or discussions features of GitHub, maybe adding direct links to the issues and discussions tabs of our repo would help?

image

'Give Feedback' would link to https://github.com/pepkit/pephub/discussions
'Report a Bug' would link to https://github.com/pepkit/pephub/issues

This means casual visitors to PEPhub need a GitHub to provide feedback, but I think you would need to log in to encounter a potential bug in the first place.

@nsheff
Copy link
Contributor Author

nsheff commented Aug 27, 2024

Ok, let's go with that. I like it.

sanghoonio added a commit that referenced this issue Aug 28, 2024
…use making ph_id read only makes it impossible to overwrite if pasting a larger table
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants