One issue I found was that there seemed to be no module named "mpld3".

I downloaded all the content from eloc. Then in the server.py, it said that it was missing a module called "mpld3". I downloaded mpld3 from github, and it sensed the file, but still said "No module named mpld3". I looked for a pip install, and installed it, but it still said "No module named mpld3".

I think that GCI should put where to get these modules from, and the Readme.md didn't have any proper information. It was also missing some important files like config files.

The local server of eloc does not startup due to matplotlib.pyplot being imported as mpld3. Initially, I thought I could come overcome this by looking around but then I noticed that mpld3 is redundant as it was not being used anywhere inside plotSpec.py.

So I removed mpld3 and rebuilt. This time, a local instance of eloc spun up smoothly. I recreated the exact error and took a screenshot for more clarity.

Find this task on my website: http://itsrohan.com/gci/gcitasks

Add a list of dependencies needed to run the program. This will allow people to run the program as it is intended to be run: not with errors about missing modules.

Some of the Important Files that must be included in an Open Source Project are missing

Contributor Documentation
Issue Template
Pull Request Template
Proper Readme File
Build Testings Used
Config Files
Updated License
Updated Documentation

=> Dismiss stale pull request approvals when new commits are pushed is active
=>Require status checks to pass before merging is active
=>Readme files should be more descriptive and instructions should be clear
=>Sometimes the app crashes due to mpld3
=>many syntax errors in js,css files

A README file must contain information about other files in a directory or archive of computer software.

The program doesn't support Python 3. Since it's been a long time since Python 3's launch 98% people has switched to Python 3. Also all the New comers will have learnt Python 3. So it's best that the program is written in Python 3.

This project's README.md is not explained well enough about the project itself. A few pros about the project, explaining what the project actually does and stating methods of using it would be really helpful.

It can rather start as....

"This project is used to locate the geographical locations of elephants. ELOC can be setup by doing the following steps.... etc.

Making it more descriptive would surely help people understand it much better, including newbies.

Issue 1:

There should be a proper guide on how to set up a development environment, or how the users going to use it.
How the users are supposed to know how the program works.

Possible Fix: Add Proper Guide

Issue 2:

There must be a requirements.txt file on each folder which contains libraries other than the Standard Libraries.
eloc_node, eloc_server folders must have requirements.txt file on each folder.

Possible Fix: Add requirements.txt file on above-mentioned folders

Issue 3:

As the life of Python 2.7 is about to end, it would be better to use Python 3 instead.

Possible Fix :

• Rewrite in Python 3 or make it Python 3 compatible
• use 2to3 tool

Issue 4:

eloc_node/readData.py file has inconsistent use of tabs and spaces in indentation.

Possible Fix: Use 4 soft spaces instead of tabs

The new contributors will get the idea of the project after reading the readme file. But here the only thing that consist in the readme file is "eloc". So I suggest to add details to the README file

There should be a CONTRIBUTORS.md page in the repository to guide the developers.So please add it.

Expected Behavior

There should be Travis CI Integration In Project Which runs tests every time Anyone commits to Repository.

Current Behavior

There is no Travis CI Integration Available

Possible Solution

All the commands/Documentation that are required To integrate Travis CI are present Here

Follow-up

Update the README.md accordingly.

THIS IS A NOT A REAL ISSUE BUT A PLACEHOLDER.

All the practising PRs for Google Code-In 2017 should refer this issue. PRs referring this issue will be closed without merging. Do not refer this issue if you are NOT submitting a practice PR and need your work merged.

The project is missing following files needed for a open source development workflow:

Contributor Documentation
Issue Template
Pull Request Template

The "About" link on the initial pointing to pages/about.html and "Home" link pointing to pages/dashBoard.html are not loading the respective pages and show endless loading animation

I opened two files which were present in another sub-folder of the Main Zip file. They were containing information but no design...

1. Batch should be made with a inbuilt environment installed especially for Python GUI Bash
2. There should options for several Languages other than English.
3. There should be some kind of Page build up for Tabs like FAQ's and tab to ask Questions to people.
4. At line 13, SYSTEM_RATE can be increased to '800' to get a better connectivity with the apparent IP
   Address.
5. Also, Font Style tab may be added for more fancy touch to the Python Bash GUI.

There are several directories where readme update is neessary like eloc_node,eloc_server only python script is provided respective README.md is blank.

There is very less info in README and no proper ISSUE SUBMITTING TEMPLATE is there.

• There should be a proper guide on how to set up a development environment, or how the users going to use it.

• There must be a requirements.txt file on each folder which contains libraries other than the Standard Libraries.

• The program doesn't support Python 3. Since it's been a long time since Python 3's launch 98% people has switched to Python 3.

readData.py found under eloc_node file:

Inconsistent use of tabs and spaces in indentation

Eloc_data should have more descriptive inside catalogs names, because now we have weird naming, and don't know how this data is relevant to project.

I wasn't able to install it because there's lack of information on the README.md in such a way that you don't know what this thing does or how to install it. It needs improvement :D

the README.md file should contain images of the project and installation process, images play a very important roll in an Open-Source project not only because it shows you some ui components for example, and you can get feedback to improve your project UI without needing to install, or sometimes images help a lot when someone has problems installing for example terminal output screenshots.
Hope this helped :D

README.md file should explain how to set up the project locally, on the user's own environment. We should describe how the installation process will look on Linux (Ubuntu etc.), Mac and Windows.

This process is for sure easy and fast, but some people coming from another environment or those who are not very familiar with git itself wouldn't be able to set up eloc.

This Issue is connected with #5 as this file has no description AT ALL 😞

The local server of eloc crashes due to mpld3.
the README file should be more descriptive for the user in order to follow instructions
And important files such as ,contributor documents and config files are missing.