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

Discuss users UX #3

Open
chshersh opened this issue May 31, 2018 · 3 comments
Open

Discuss users UX #3

chshersh opened this issue May 31, 2018 · 3 comments
Labels
question Further information is requested UX Usability issues

Comments

@chshersh
Copy link
Contributor

I would like to have an ability for users to see their achievements depending on their open-source contribution. This is the biggest motivation for people to do something. So we should have an ability to login into our application through GitHub (in perfect case).

Also, I'm not sure that we should synchronise contributors past... Let's track everything starting from server start.

So I propose the following sync scheme:

  • Sync all activity for user starting from server start and calculate all achivements
  • Sync all achievements for users no often than in 4 hours (?) (or smarter strategy, depending on user activity?...)
  • If user doesn't do anything for 30 days, stop syncing him (to not waste our resources)
  • Have force sync button in API

We should also assign points to every achievement and have ranking table...

@chshersh chshersh added the UX Usability issues label May 31, 2018
@chshersh
Copy link
Contributor Author

chshersh commented Jun 10, 2018

Tags to consider:

good first issue help wanted wanted up-for-grabs beginner-friendly easy difficulty:easy your first pull request low-hanging-fruit newbie-friendly

@chshersh chshersh added the question Further information is requested label Sep 11, 2018
@rashadg1030
Copy link
Collaborator

@chshersh I think the idea of an achievement board is cool. It's a good motivator. Along with all the tags @chshersh mentioned I think we should also include issues with docs or any other doc related tags to the list. It's not really programming, but fixing docs is a good way for programmers to get introduced to a codebase. I think the sync strategy that @chshersh proposed is good. By "server start" do you mean when they use issue-wanted for the first time they start off fresh? I think that's fine.

@chshersh
Copy link
Contributor Author

By "server start" do you mean when they use issue-wanted for the first time they start off fresh?

Yes, I meant that some hardcoded timestamp of the project start. However, I think it shouldn't be that difficult to fetch all user information (I hope).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested UX Usability issues
Projects
None yet
Development

No branches or pull requests

2 participants