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

Call for ideas on how we could improve the maintainer experience #2168

Open
baltpeter opened this issue Mar 23, 2023 · 7 comments
Open

Call for ideas on how we could improve the maintainer experience #2168

baltpeter opened this issue Mar 23, 2023 · 7 comments

Comments

@baltpeter
Copy link
Member

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

@baltpeter
Copy link
Member Author

As a first step I have suggested #2165 and #2166.

@baltpeter
Copy link
Member Author

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.

@mal-tee
Copy link
Member

mal-tee commented Mar 23, 2023

  • the site switches between GitHub and the generator and inside GitHub are annoying
  • this is my current workflow:
    1. github: find PR
    2. open generator via cool edit link, fix stuff
    3. press copy
    4. github: click edit, paste, commit
    5. refresh site
    6. approve
    7. switch to overview to merge
    8. edit message
    9. actually merge
    10. delete branch (can be handled by RefinedGithub iirc)

we can't change 4-7, but is there a way for us to commit directly to the github PR from the generator?

@baltpeter
Copy link
Member Author

baltpeter commented Mar 23, 2023

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.

@mal-tee
Copy link
Member

mal-tee commented Mar 23, 2023

Checking for duplicates.

If a suggestions adds a new company, I usually use datarequests.org to check if it already exists.

@mal-tee
Copy link
Member

mal-tee commented Mar 26, 2023

Formatting an address country-specific.

We could aid this by auto-completions, autoformats, or fuzzy searches on the DB to show other examples?

@mal-tee
Copy link
Member

mal-tee commented Apr 7, 2023

Multiple updates/adds for the same company.

Sometimes we get multiple suggestions for the same company/record.

Ideas:

  • Autoclose exact duplicates
  • Present all suggestions (or even their diffs) at the same time to compare them more efficiently

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

No branches or pull requests

2 participants