Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Choose name #268

Closed
9 tasks done
lrozenblyum opened this issue Jan 7, 2019 · 2 comments · Fixed by #344
Closed
9 tasks done

Choose name #268

lrozenblyum opened this issue Jan 7, 2019 · 2 comments · Fixed by #344
Labels
Milestone

Comments

@lrozenblyum
Copy link
Owner

lrozenblyum commented Jan 7, 2019

During commit the proposed name has established: lrozenblyum-chess 91b7689#diff-aa14599dc3fdfa9cc81a7c3c247b77b9

Previously we used leokomChess.

  • To finalize the decision
  • Update NOTICE if needed
  • Update package names if needed - already good
  • Jar name
  • Log file name - already good
  • Release version name (maybe year.number instead of 0.?) - split to Define release versioning scheme #346
  • Release archive name
  • SonarCloud - split to SonarCloud - investigate url change #347
  • Travis CI - the url depends on github username/repo. Not going to change

! Interesting link: http://webcache.googleusercontent.com/search?q=cache:0p4jnkXY_MMJ:mzchessforum.altervista.org/viewtopic.php%3Ft%3D3654+&cd=12&hl=ru&ct=clnk&gl=ua

! Link#2 http://computer-chess.org/doku.php?id=computer_chess:wiki:lists:chess_engine_list&s[]=leokom

@lrozenblyum
Copy link
Owner Author

Registered on the forum https://mzchessforum.altervista.org, waiting activation

@lrozenblyum
Copy link
Owner Author

Leokom is

  1. easy to pronounce
  2. already indexed and used by multiple web-sites as a reference
  3. not used by any other Chess engines
  4. already used in package name in reverse-domain style.

So I decide that Leokom Chess would be the official name of the engine

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant