-
-
Notifications
You must be signed in to change notification settings - Fork 90
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
Call for ideas on how we could improve the maintainer experience #2168
Comments
I'm also consider whether we can even implement an "ideal" review experience for our particular use case in GitHub. Maybe we need our on frontend? I might try and implement a prototype for that. I'm very interested in any ideas you might have for such a frontend. |
we can't change 4-7, but is there a way for us to commit directly to the github PR from the generator? |
That's what I was thinking as well. Most of the GitHub API endpoints are CORS-enabled. We should be able to build our own little GitHub "client" in a static site. |
Checking for duplicates. If a suggestions adds a new company, I usually use datarequests.org to check if it already exists. |
Formatting an address country-specific. We could aid this by auto-completions, autoformats, or fuzzy searches on the DB to show other examples? |
Multiple updates/adds for the same company. Sometimes we get multiple suggestions for the same company/record. Ideas:
|
We are unfortunately quite behind on reviewing company suggestions and, at least personally, I'm quite overwhelmed by the huge work load. I also feel like our review process is currently quite inefficient and has a fair amount of rough edges that make the situation worse.
I'm quite motivated to work on fixing those, but I'm lacking ideas. So, here's my call to everyone who helps with maintaining the company database (or has helped in the past): Which parts of the process annoy you, what slows you down when going through suggestions? Do you have any ideas on what we could improve?
Let's dream big. I can't promise that we'll be able to implement/fix everything, but we can try. :D
The text was updated successfully, but these errors were encountered: