ghuls-apps / ghuls-deprecated Goto Github PK

There should be an option, in both CLI and the web app, to get a random user's data.

In CLI, it should be a new option called -r, with no parameters (like -h).
In web, it should just be a button at the bottom of each page.

http://ghuls.herokuapp.com/analyze?user=zeke spins for a while, then:

Would love to see the results. Let me know how I can help.

I should rewrite the entire thing as Ruby code. This would involve creating a Ruby on Rails application, and a command line application.

http://ghuls.herokuapp.com/analyze

I have no idea what it analyzes, but... I guess it shouldn't, because no username is passed.

• Separate auth/login window
  • Asks if you want to login or use an auth code. Then the window will change to have according text and fields.
• Username search box
• pie chart

Allow auth codes to be used for the API authorization.

Since I'm not packaging my secure.txt file with the app, I need to have the user log into the GitHub API first and use their credentials to get more possible API requests. I should also allow them to use an auth code instead.

Once the program is run once, it cannot be restarted.

http://ghuls.herokuapp.com/analyze?user=ProgramFOX says:

Unfortunately, ProgramFOX has not contributed to any organizations :(.

But that's not correct (unless I'm misunderstanding "contributed" here), because I have contributed to open-source projects of organizations I'm in.

Write a Makefile.PL file that automatically downloads necessary dependencies. See Stack Overflow

I was wondering what you thought about separating the bulk of the code off into a separate gem, say ghuls-lib and thus people could use it as a library of it's own?

The chart errors occasionally with "a is null" or "null is not an object" errors. My guess is that this would be related to users having repositories that do not have languages defined by linguist. The two users I have seen this happen for are: ProgramFOX and Strikingwolf. It might also be because these users are too pro for GHULS.

Handle incorrect username/password/auth code errors

The web app is disgustingly hideous on mobile. I should create a mobile version of the app that uses custom CSS for mobile.

JSONs stick around endlessly. They should be deleted as soon as the GUI gets the data and pies it.

The user should be able to select Organizations to include in the calculation.

It looks in the wrong directory for the utilities module. This should be a pretty easy fix. The problem is that it looks in the current working directory, so it only works if you are in the GHULS dir. It should look relatively to the gem directory, rather than relatively to the current directory.

To let the user know that it is actually working, there should be a progress bar. I believe I would have to use JavaScript for the web application's progress bar, which is a bummer, but I know there are CLI progress bar gems.

• CLI
• Web

Something I've noticed while looking at some different analyzations is that code bloat from languages such as Java (where LOC per action is higher than say Ruby or something else) cause the graph to be skewed in their favor. I would propose having a weighted graph along with the non-weighted one which balances out the languages using some "expressivity factor", I'm not sure if you would have to come up with these yourself or if there may be some real comparison site you can use, but it would be a nice feature to add.

I am particularly interested in helping to get a web app up and running, if you are open to it.

This issue serves the purpose of a basic list for things that need to get done in order to get the data I need. I will continue to add things to this list as I find them, then eventually turn it into a checklist.

1. Use the GitHub search API to get all repositories from that user. Unfortunately this is the only way to get the most general information, but will exclude all repositories that the user contributes to that are NOT under their username. It also excludes their organizations. I'm sure there's something that can be done to avoid this, but I still have a lot of research to do in the GH API.
2. Get info from the Repos API, using repos/username/repositoryname/languages. This will give the number of bytes per language that that repo uses. Do this for all repositories that the user has.

Use Net::GitHub::V3 (Net::GitHub::V3::Users)(Net::GitHub::V3::Repos) instead of the web interface for the API.

Checklist:

• Get repo list
• Get language data for each repo
• Option to ignore forks --- (Probably) temp removed.
• Calculate data into totals
• Calculate data into percentages