Open Source 4 Player Chess

Dear Chess.com Team,

Did you consider making the 4 Player Chess an open source project? There are lots of Java Script developers (as long as HTML and CSS developers and designers) in chess.com community. We could contribute! This way you'd become this project alive again.

Some bugs can be fixed by changing 1 to 5 lines of code (CSS, HTML or Java Script). For example, a bug with long player names, a bug with 2 teammates appearing in different teams, a bug when the same player appears in 2 teams and should play against himself, a bug of the rating range selector, a bug of left arrow key in chat rewinding game moves and so on. The community could fix it fast. The paid engineers could not fix it from 10th of November.

Let the paid engineers to make core things and the server side things like "the server can handle a million of players now", but UI things and related bugs can be fixed and changed by the community.

@BabYagun Do you mean like actually fixing it in the system or fixing it in a remote manner and submitting it for the Chess.com team to test before implementing (assuming it worked as intended).

I'm curious as to how much access then volunteer programmers would have to the site....

Sourceforge has gotten a lot of projects done via open source and volunteers. I wish I knew how to  do that stuff, I'd volunteer in a heart beat.

It is an excellent idea! I am surprised it hasn't been broached previously.

Seems like a good idea even though I'm no developer

Better program -> Sounds good.

it sounds good, but to make some of these things might take lines on lines of code to make, and to change it would take more lines

@RG-2HI4U, now people use GitHub (github.com) instead of Sourceforge, it is much more popular. It works this way (a little simplified):

1. Chess.com publishes the source code (or its part, for example, only the client side part) at GitHub.

2. Chess.com gives Administrator permissions to a couple of developers from Chess.com team.

3. Both the administrators and volunteers make their changes in the code.

4. The administrators test the code of the volunteers and accept the changes if they do fix the issues.

5. Everyone becomes happy.

@BabYagun,

The open source model works well for distributed software, but are there any working examples of open-source development of client-side components of centrally-hosted web content?  

Also, your proposal assumes that the 4pc client-side component is already coded in such a way that it can be distributed, compiled and hosted by an external web server.  After all, I'm not going to touch the source code unless I can compile & host it on a personal server for unit-test purposes.  Yes, I would *hope* this to already be the case, but in reality, in-house application development is not always cleanly modular.  Is the game-play source code packaged with the leader-board code that queries a centralized database using hard-coded application credentials?  Hopefully not [!], but I wouldn't be surprised if there were at least some amount of code refactoring necessary before going open-source with the client-side module.  And that may be a tall order for a project that's been (seemingly) deprioritized to the point that even simple bug fixes are not addressed.

Kevin is a real pump. Dude just roasted chess.com 

Much respect dawg

#kevinkirkpatisathug

Get It trending boyz

The grates example is Wikipedia.