All times are in IST
messaged on August 3 at 5:10 pm

This is important! All Teams, Please commit your final code to Git ASAP
messaged on August 3 at 3:06 pm

Clarification on github questions teams have asked individually: Overall we want to look at only 1 repository. You can keep separate branches for code with zero compile dependency - Like Andriod App, iOS app, Backend etc. However make sure code all contributors working per branch is merged. No open changes when you get to evaluation stage
messaged on August 2 at 7:34 pm

We have compiled some beautiful speeches/stories of world leaders, do watch them today 8pm at below link:
messaged on August 2 at 6:57 pm

Students, a small presentation by the students, hope you will like it. Kindly join at 7:30pm today at below link:
messaged on August 2 at 5:36 pm

Hope we all are on same page to the above statements.
messaged on August 2 at 5:24 pm

Dear Students.. Demo well.. Have pride in your product..:+1:
messaged on August 2 at 5:22 pm

Respected evaluators, Please note the same
messaged on August 2 at 5:22 pm

Message from <@U018673QB3N> :Dear All, Feel free to show a slide or flowchart provided it helps you explain your demo. No separate time for slides/ flowcharts Marks will be given on basis of demo...
messaged on August 2 at 10:49 am

Dear students, Make the most of the mentoring sessions. Mentors are experts in their areas and have kindly taken time to make your work better. Take their advice and improve your chance of standing out in the hackathon.
messaged on August 1 at 11:16 pm

Hello Teams, Here is a Reminder for you A) ALL Team members HAVE TO commit to Git ( not only 1 person) B) ALL Teams must have COMMITS happening with higher frequency C) ALL commits have to be significant commits and not just for the sake of doing them All these points matter for evaluation. We are checking Git commits for all above aspects Usage of Git will improve your feature delivery and is highly recommended.
messaged on August 1 at 9:54 pm

Hello Teams.. Please make frequent commits to git. Dont take risk on code.. Keep it safe in git every 2 to 3 hours. Each one of you commit individual code..
messaged on August 1 at 5:46 pm

All teams, Believe in your self and give your best.
messaged on August 1 at 4:52 pm

Check this link for Hon. PM Address
messaged on August 1 at 1:27 pm

SIH 2020|| LEISURE ACTIVITY BREAK ||1ST AUGUST 2020 3:30 - 4:00 PM || NODAL CENTER - GRAPHIC ERA
messaged on August 1 at 12:40 pm

Reminder to All Teams, Please make sure that your team has only one repository. Follow Repository name format as below 'NC_GEU_<problem statement>_<team name>' If you have already Created it ask admin to Go to 'repository'-> 'settings' and you can rename
messaged on August 1 at 12:37 pm

Teams, Mostly you will be going to use synchronize Changes commands, if you do it couple of times you will feel comfortable with GitHub.
messaged on August 1 at 12:25 pm

All Teams, Here is a cheat sheet for you, hope this is helpful.
messaged on August 1 at 10:30 am

Hello Teams, Git Usage Tips (Do's and Don'ts) 1. Avoid Committing Zip File to repository 2. Avoid Committing compilation output files (eg .exe, .jar,.dll etc) 3. Avoid Committing without log messages (it answers “Why?” part of commit) 4. Avoid Creating version control inside version control (e.g. File1.docx, file_final.docx, file_really_final.docx) 5. DO NOT Use File system copy , move, delete, rename. Always use ‘git move’ to rename/move files. 6. Avoid committing 'videos' and other large sized test data used in AI/ML in your git repository. To share the videos and test data amongst the team members use services like Google drive, Dropbox or OneDrive 7. Do Small commits. Commit small logical changes. It is ok to commit 1 line change. 8. Frequent ‘push’. During hackathon ‘commit/push’ at least once every hour 9. Frequent ‘pull’. Pull every hour. Pull before every push 10. Make sure everything works on everyone’s machine. Test everything on every machine 11. Commit configuration and test data (small size) in the repo. 12. Everyone should commit to same repository. Do not create multiple repositories for one project. 13. All team members should commit to this one repository. Only team leader (or just one person) committing to this repository is NOT recommended.
messaged on August 1 at 10:14 am

All Teams, Please make sure that your team has only one repository. Follow Repository name format as below 'NC_GEU_<problem statement>_<team name>'
messaged on August 1 at 10:05 am

GITHUB Instructions for Nodal Centers and Participants. (FAQ) 1. All hackathon team members have to register on  2. Only team leader will create one repository on github. This will be a private repository. 3. One repository per Team. Multiple repositories per team are NOT allowed. 4. Repository name should be in the format 'NC_GEU_<problem statement>_<team name>' 5. Team leader has to add all his/her team members to this repository as 'collaborators'. 6. Team leader has to add github user named 'sih2020admin' in the repository as 'collaborator' 7. To add collaborator to 'Settings/manage access'. Use "invite collaborator" button to add the collaborator. 8. Team leader has to add two vigilance officers to the repository as 'collaborator' in the same way. ajay-gandhe and amit-parshetti 9. Nodal Center is not expected to create any github repositories. 10. Nodal Center has to create an excel with 'team name' and URL of the repository. The url will be in the format '/<team leader userid>/<problem statement>_<team name>'.  Nodal center has to share this excel with AICTE SPOC for that Nodal Center.