ieeecs-vit/gpl

graVITas Premier League

gpl's Issues

Pipelines

To make seamless transitions from dev staging to production, separate apps can be dropped in favour of Heroku pipelines.

Dashboard

The current team UI is a bit too plain, and needs serious refurbishment.

Leaderboard Route

Now that you have completed the algorithm please implement the following route.

1. /leaderboard

I'm assigning this to you, please get back to me for updates.
@kunagpal

Feel free to get back to @kashishbest or me, @aneesh-neelam, if you have any issues going ahead with the implementation

Cookies

Frequently accessed data like the leader board and user statistics can be cookied in order to inject significant amounts of impetus into application performance, with conditional checks to ensure that the versions of the cookie contents and the matchday value (process.env.DAY) on the server match.

Node.js 0.12.x/io.js 1.x

Switch to the latest io.js. To enable on Heroku, follow the instructions here.

Check here for more information.

Match Schedule

What's the status on this? Also, have you tested this yet? @kashishbest

Social login

Modules need to be created for social login into GPL (Facebook, Twitter, Google, and GitHub)

Create tickets all possible tasks pending in GPL

Create tickets for all possible tasks in GPL and assign them to everybody.

Invite Every Developer to the Meeting

Add everyone to the calendar invite and drop in a message at the whatsapp group to ask people to join the meeting if possible

Game format overhaul

For next year. If accomplished on time, invalidates and nullifies #57

Feature request

A feature request page will have to be added, where people can request improvements / report bugs.

Auto team creator (post register)

Image slideshow

The current image slideshow on the countdown splash page is okay, but can be made better, with regard to the inter image transition flashes, and the awkward aspect ratio.

MatchDay View

Please get in touch with Ayush/Shivam and get your EJS concepts clear and implement the front-end for @sukriti27's assigned Backend route.

I'm assigning this to you, please get back to @kashishbest or me, @aneesh-neelam for updates.
@somya777

Statistic display overhaul

Placeholders and layout will have to be made for:
-Individual player statistics
-Overall event stats (total runs scored by all teams, total wickets taken by all teams, orange cap, purple cap)

Dependency Issue?

What do you mean dependency issue? @kashishbest

Redundant views

Quite a few of the existing views are redundant, and must be deleted.

Admin panel

At present, the matches are simulated via the Heroku panel. A proper administrator interface with features like team count, match simulation buttons, and daily report divisions is needed.

Compute the space requirement.

As per last year's stats, a single matchday collection took up 60 MB of data, please verify that.

Home Page Display Details

Show playing 11 and squad seperate, will give a better look. There is no place where the user can see his current playing 11.

Identify the Hosting Parameters for GPL-2015

DB Hosting for GPL-2014 was on borders, so identify the hosting parameters and revert back

Privacy policy

A separate privacy policy page will have to be created.

Cloudinary

At present, all images are being stored as static assets within the code repository. They will have to be shifted to the aforementioned image hosting platform.

NPM postinstall script fails on Microsoft Windows

The npm postinstall script is defined for Unix-based systems. The path separator used is incompatible with Windows systems. But Windows' path separator is incompatible with Unix systems.

Heroku's default Node.js buildpack only runs:

$ npm install 

Therefore the postinstall script is required to obtain bower components on Heroku, which runs Ubuntu Linux.

On Windows systems, run:

$ npm install
# npm -g install bower
$ bower install

Ignore the npm errors that may occur.

Squad & Team Routes

@amolgautam25 will be implementing, the following two routes.

1. /squad
2. /team

I have already explained to you, how you should go about it.

I'm assigning this to you, please get back to @kashishbest or me, @aneesh-neelam for updates.
@amolgautam25

New Favicion

The one in '/public/images' is taken from here.

We need to make our own favicon.

@kashishbest , @BurnUalive , @kunagpal , @sukriti27 , @amolgautam25 Please look into that.

Developers timeline

In order to better represent the identities of the people involved in the project, a developer timeline has to be made.

Error messages

Incorrect credentials, invalid password reset links, invalid teams, passwords not matching, etc., may be conveyed to the user(s) via this library.

Option to create multiple teams from one registration instance

For next year. This also involves separating registration from team creation, thereby having _id as the email address. Team numbers can be stored as an array, with team details in a different collection altogether.

Mobile Website

The website must be adapted for mobile form factors. Please research on a good and easy way to adapt the current website for phone and tablet screen sizes.

The current website is deployed here, check it out.

I'm assigning this to the three of you, please work together on this. Get back to me for updates.

@MUDITSARAF, @diksha-jain, @tannika

If you have any issues, please contact either @kashishbest or me, @aneesh-neelam

Check master branch commits

@kashishbest, I may have inadvertently deleted your contributions made on August 3rd, 2014.

Please check the master branch if they are present. If not, then please push your local repository to a separate branch and then issue a pull request.

I'm sorry for this, I made a mistake while merging branches and cleaning up the repository.

Game sharing integration options.

For next year.

Like, follow buttons

The aforementioned items need to be added to every page of the website.

Process management

Using process management libraries like this one can enable better control over application performance in production environments.

Countdown

The countdown remains buggy at the moment.

Dynamic team name availability

As is the case with username selection for most account based web services, the team name selection must be improved to include 'on the fly' checks for team name availability.

Emails

The backend code for sending emails for various tasks like password resets, welcome emails, as well as post match emails is ready, but the emails are just boring plain text. They will need to be stylized as well.

Stop Pushing to GPL

There is a separate repository for RPL for a reason.

Matchday Route

@sukriti27 will be implementing, the following routes.

1. /matchday

I have already explained to you, how you should go about it.

I'm assigning this to you, please get back to @kashishbest or me, @aneesh-neelam for updates.
@sukriti27

Process environment variables.

https://github.com/motdotla/dotenv may be used in order to relegate all process.env related tasks to a .env file, thereby avoiding the pain of manually creating process.env variables, albeit once.

Login IDs to be made case insensitive

Logs

Wherever you need to log something, use Logentries for it.

Add the following at the start of every Node.js file you're going to be logging:

var log;
if (process.env.LOGENTRIES_TOKEN)
{
    var logentries = require('node-logentries');
    log = logentries.logger({
        token: process.env.LOGENTRIES_TOKEN
    });
}

Then use the following syntax to log things:

if (log) log.log('debug', {Error: err, Message: err.message});

Check out the Logentries Documentation for more information.

2 factor authentication

Session undefined.

Aneesh/Kunal kindly help me out with the issue

Session in the request is undefined, kindly let me know where I am going wrong.

@aneesh-neelam @kunagpal

Mocha

It's about time GPL had tests. Check out https://mochajs.org/

Stats to be updated

The player statistical indices are out of date, and need to be updated.

Matches Simulation

What's the status on the match simulation? @kashishbest, @kunagpal

Also, do not insert formatted commentary into the database, the frontend must do the formatting based on the screen width. HTML web pages don't work the same as C/C++.

And @kunagpal, our work would get done faster if you had written the Node.js code properly. The input data to the simulation code is present in the database, its not as if you could simply sit and write it in C/C++.

All match details need to be displayed

At present, only the current match and the next opponent are shown, this has to be expanded to show all matches.

Pipelines

In order to make seamless shifts from dev staging to production, separate apps for production and testing can be dropped in favour of one cumulative Heroku pipeline.

https://devcenter.heroku.com/articles/pipelines

Logo

We need a modified Logo for GraVITas Premier League. The current logo doesn't match well with the rest of the background. Check out the logo on the current website here

Please tweak the existing logo, make it more visually appealing.

I'm assigning this to you, please get back to me for updates.
@Vikhyati

If you have any issues or need any help, contact either @kashishbest or me, @aneesh-neelam