PGN Chess for PHP

in #utopian-io6 years ago

Repository

https://github.com/programarivm/pgn-chess

New Projects

  • What is the project about?

PGN Chess for PHP is a friendly and powerful PGN (Portable Game Notation) library for running chess games from within PHP apps. This is a chess board representation available for PHP! Hopefully at some point it could be used to play against the computer, and for many other purposes also: learn chess, chess-move.jpgetc.

PGN Chess internally replicates the games being played on the board, which means they are actually run in the computer's memory.

  • Technology Stack

PHP

  • Roadmap

At this moment, the library is been tested already to only be aware of games being played on the board -- you can play with a friend -- but it does not have any intelligence at all yet -- you cannot play against the computer.

  • How to contribute?

Would you help make this library better? Contributions are welcome.

  • Feel free to send a pull request
  • Drop an email at [email protected] with the subject "PGN Chess Contributions"
  • Leave me a comment on Twitter
  • Say hello on Google+

GitHub Account

https://github.com/programarivm

Sort:  

Hi @programarivm, welcome to Utopian! It looks like a cool project - however there are some things I should note about our guidelines, specifically those for the development category.

Currently we only consider commits made in the last 14 days for development contributions when determining its score, so that means that in your case there aren't any "eligible" commits.

What we normally expect to see in a contribution is for example a newly added feature(s) with all the relevant commits or PRs linked within the body of the post.

Since you want to introduce your project I think the blog category would be a better fit for now, since they are specifically looking for posts that include a project's introduction. If this sounds of something of interest to you then I'd recommend contacting the blog community manager @roj on Discord (roj#7486), as he should be able to help you out more than I can in that regard.

Once you have added e.g. a feature in the last 14 days you can create a development contribution about it of course (I would definitely recommend reading this amazing guide made by one of our moderators before doing so).

Good luck with your future contributions and I hope to see you back in the development category soon!


Need help? Write a ticket on https://support.utopian.io/.
Chat with us on Discord.
[utopian-moderator]

Thank you for your review, @amosbastian!

So far this week you've reviewed 14 contributions. Keep up the good work!

Thank you @amosbastian for the prompt response!

Mmmm. Not very clear about this: "Currently we only consider commits made in the last 14 days for development contributions when determining its score."

In fact, I'd like to add a new feature actually :) Could I create a new branch describing the new feature to be implemented?

If I understand okay, some first commits on the new feature must be pushed for the project to be eligible? If so, how many?

Kind regards,

There isn't really a number of commits that need to be pushed to be eligible, but the more work done, the higher the score and thus your reward! Once you have implemented the feature you can merge it into the main branch for example, create a contribution about it and link to it in the body of your post. If something isn't clear and you have any further questions don't be afraid to ask (either here or on our Discord server - I'm here to help!).

Thank you @amosbastian

I'd like to start writing a PGN Chess command line interface. The first command is about inserting valid pgn games into a database for further processing -- which is a very cool feature that hopefully will attract contributors at some point I guess.

I am clear that I have to checkout -b feature/pgntosql and start writing :)

However, atm I am not very clear on when I should post the feature on steemit for evaluation: 10 commits, 20 commits, ... or when the feature is ready to be merged?

Whenever you feel the feature is done - so whenever the feature is ready to be merged. Once it is merged you will have 14 days to submit a contribution about it (in the future we will more than likely change this to 28 days). I look forward to seeing your next contribution!