Planning Issue: Upgrade rails from 3.2 to rails 6

[SidharthBansal]

• Rails upgrade
• Rails 3.2 => Rails 4.0
• Rails 4.0 => Rails 4.1
• Rails 4.1 => Rails 4.2
• Rails 4.2 => Rails 5.0
• Rails 5.0 => Rails 5.1
• Rails 5.1 => Rails 5.2
• Rails 5.2 => Rails 6.0
• UI update and collaborate with others
• Fix existing deprecation warnings
• Write Test Coverage for new Rails 6.0 Unit testing Functional testing
• JS API endpoints of MapKnitter
• write Functional Test
• Karma, Jasmine, Mocha, QUnit. Decide which one??
• Code Clean up after upgrade to Rails 6.0
• Generate Code Coverage Report
• Add git tools
• codeclimate
• codacy
• codecov
  Part of MapKnitter Upgrades planning (overall) #300

[Dhiraj240]

@SidharthBansal @jywarren @gauravano I would like to work on the this from now onwards so that i get familiar with the end parts of the project before GSOC.
So should i start with breaking up the issues and submitting PR ?

[SidharthBansal]

You can try some small issues of mapknitter to become familiar with this repo. Then you can start breaking this and open up a pr for this issue.

[jywarren]

this will be a big project! Noting that #304 -- expanded test coverage -- will be VERY helpful before taking on the upgrades, so we can be sure to know what is broken with each change.

[SidharthBansal]

@Dhiraj240 you can start working on #304 then

[Dhiraj240]

@SidharthBansal @jywarren alright !!

[kaustubh-nair]

I'm interested in this project too!
I'd love to help you guys out in improving test coverage 😃
If there's an issue I can fix please let me know!

[Dhiraj240]

@kaunair You can see the available issues in the repository although one of them is highlighted in the above chat.But were you able to install it ?

[grvsachdeva]

We would also love to have your help @kaunair. But, how about doing the testing part after switch to yarn part, you have claimed? You can start both too, we don't mind that too 😄 . Thank you!