SSH is a little bit tough for a beginner. Wouldn't it be better if we'd recommend HTTPS in windows setup tutorial?

Create game_createGame() and game_deleteGame().

There are some tests that dynamically alocate memory and don't free it.

Write a function to determine the winner of a hand

./run-test.sh

** (cutter:34966): WARNING **: can't load a shared object for test case: ./.libs/test_team.so: dlopen(./.libs/test_team.so, 1): Library not loaded: /usr/local/lib/libdeck.0.dylib
Referenced from: /Volumes/SoftwareDocumentation/Projects/CruceGame/test/.libs/test_team.so
Reason: image not found

** (cutter:34966): WARNING **: can't load a shared object for test case: ./.libs/test_round.so: dlopen(./.libs/test_round.so, 1): Library not loaded: /usr/local/lib/libdeck.0.dylib
Referenced from: /Volumes/SoftwareDocumentation/Projects/CruceGame/test/.libs/test_round.so
Reason: image not found

** (cutter:34966): WARNING **: can't load a shared object for test case: ./.libs/test_deck.so: dlopen(./.libs/test_deck.so, 1): Library not loaded: /usr/local/lib/libdeck.0.dylib
Referenced from: /Volumes/SoftwareDocumentation/Projects/CruceGame/test/.libs/test_deck.so
Reason: image not found

Finished in 0.000056 seconds (total: 0.000000 seconds)

0 test(s), 0 assertion(s), 0 failure(s), 0 error(s), 0 pending(s), 0 omission(s), 0 notification(s)
0% passed

Document how to close an issue and how to reference issues in commit names. The issues should be closed at merge.

At the top of the document, there is some text written in italic. This should be integrated into the document to form a cohesive documentation and the italic text should be removed.

Add function to create the teams in the Game based on user input, after the players were added to the Game.

Will unicode string be supported?
If so, which encoding will be used?

Fix formatting of docs/hacking.md

Write a function for card comparison. Take into account the trump.

The steps needed to test the code should be documented, together with a short introduction about the test framework

The name libAsciiGui is no longer relavent because

• The project is no longer a library, it's a normal executable
• It uses UTF-8 & curses for displaying the cards

You should document "good techniques and advices" to reduce merge conflicts and CS violations (like line endings).

Any other git-related advices are also welcome.

Create a function that randomly distributes cards to players from a hand, using a Deck.

Analyze the features and the requirements and create a roadmap for the five milestones: 0.2.0, 0.4.0, 0.6.0, 0.8.0, 1.0.0.

Since you're currently working on 0.2.0, try to create a finer-grained task list (or better yet, a tree of tasks with depencies as children) for this milestone.

An inclusion guard should have the same name as the module. Take a look at deck.h.

Create game_addPlayer(), game_addTeam() - it should take 2 player id's and create a team with them, game_removePlayer(), game_removeTeam().

Find a way to avoid the use of static variables in createPlayer and createTeam, if possible.

Which of the two should be used in the project?
It all comes down to having to write "struct" everytime the structure is referenced, or not.

Write functions to display cards (a deck, as well as cards from a player's hand or in a game hand). Translate card score to card face.

In case of game rules, romanian version:

"Sa zicem ca ne continuam jocul in 4 lasat la scorul de 2 - 9 si acelasi jucator al primei echipe castiga licitatia cu doua. La finalul turei, se numara punctele si prima echipa a acumulat 102 puncte, iar cea de-a doua 18. Scorul va fi 5 - 9 (A se observa diferenta fata de whist unde daca nu faci exact cat ai licitat, iei minus, si toti jucatorii au pariurile lor, neexistand un singur pariu pentru fiecare tura)."

I think the final score should be 4-9, instead of 5-9. Because the bid made by first team player was of two. As It's written there that they scored 109 points too, So does it make the increment of 3?

Does the point matters or the bidding matters? In my opinion, it should be bidding, so the final score must be 4-9 instead of 5-9.

Add instructions to install curses on Windows.

Use dynamic allocation for cards. Complete deck_createDeck() and tests.

Somewere in documentation it is stated that we are going to use make.
Replace that with autotools.

Fix indenting in team.c

Using lib in the name of a header is not common. It would be better called cruceGame.h

Add function to team module to compute the score of a team by adding the score of the members.

Implement data structures documented in docs/data-structures.md, as well as some helper functions (like addPlayer to a team). That is just a reference, feel free to add/remove from it.
Comment often, use IRC to let other know what are you doing/what have you done. Work as a team.

Currently, test function have the name test_MODULE_test_functionName. Replace them with test_MODULE_functionName

Getting below warning on build process, that needs attention.

configure.ac:8: warning: AM_INIT_AUTOMAKE: two- and three-arguments forms are deprecated.

test/Makefile.am:1: warning: 'INCLUDES' is the old name for 'AM_CPPFLAGS' (or '*_CPPFLAGS')

Create functions to add a card to a player and rename round_giveCard to round_putCard

As C does not allow namespaces, I suggest using modulename_function_name or modulename_functionName as a convention for function names.

At commit d85d24b, entering ./autogen.sh says

aclocal: error: 'configure.ac' is required
Failed aclocal

The documentation is completely missing on how to get this rolling.

I've noticed from the tests that each .c file is compiled to a different library.
They should all be part of a single game-logic library.

Add inclusion guard for error codes

Implement a game structure to keep track of all players, current round and teams. It should also contain the deck and a player count.
Create it in a new module, called game.

A lot of comments use very poor English and are hard to understand

Many of the structures need to be dynamically allocated (all, except Card). Please write functions to initialize them (allocate memory and initialize members) and to free them.

Use pointers to constants as function parameters, to avoid changing values by mistake.

Add function to get input from user and create a Player.

Reduce the number of assertions in test_deck_test_newDeck function from test-deck.c

There is a formatting mistake in docs/hacking.md

Document (in this order):

• requirements (from the perspective of the user) - what will the user be able to do with your product (WHAT, not HOW)
• requirements - what operating systems will it run on? Which compilers and build infrastructure will you use?
• features - based on the requirements: what you will use to meet those requirements. Which testing framework will you use, will it be multithreaded, which networking techniques will you use (supposing "networking" is among the requirements), which UIs will be available, how will AIs be plugged into the game (supposing AI is a requirement)? "Features" should contain more technical details about how you meet the requirements, but without going into the details of "how"
• features - will there be a library which I can embed in my own UI? Is it going to be thread-safe?

• How will you communicate within the team?
• How will the client communicate with you?

Where is the mailing list? How to subscribe to it? Document it.

Rename MAX_PLAYERS to MAX_PLAYERS_IN_TEAM to remove ambiguity

Is your code following a coding standard? Is it documented? Is doxygen used or any other tool?

Describe such things in hacking.md

Create functions for adding and removing players to/from a team.