Add communication plan to collaboration/communication.md

[emrebiyik]

• Adds the communication.md file under the /collaboration/ folder.
• Outlines the communication schedule, channels, and availability for the team.
• To define a clear communication structure and ensure team alignment.

[oleksandr-maksymikhin]

Clear description

The merge-base changed after approval.

[oleksandr-maksymikhin]

Clear description

The merge-base changed after approval.

The merge-base changed after approval.

[oleksandr-maksymikhin]

Communication plan is completed

The merge-base changed after approval.

[NimahMasuud]

good documentation and description

The merge-base changed after approval.

[NimahMasuud]

you should firstly delete constraints and learning_goals files. and then everythings is ok.

[NimahMasuud]

thanks

The merge-base changed after approval.

[oleksandr-maksymikhin]

One more attempt

The merge-base changed after approval.

[oleksandr-maksymikhin]

Nimatallahi could you approve the review and try to merge to the main? Neither I nor Emre can do it. Even with approved review (by me not by Emre) there is notification "Review required".

The merge-base changed after approval.

[emrebiyik]

you should firstly delete constraints and learning_goals files. and then everythings is ok.

The unrelated files have been removed.

[emrebiyik]

Nimatallahi could you approve the review and try to merge to the main? Neither I nor Emre can do it. Even with approved review (by me not by Emre) there is notification "Review required".

Nima was unable to complete the merge. I’m currently looking into the issue to resolve it.

[oleksandr-maksymikhin]

Don't spend time. Just create a new branch and modify only this one file (communication.md). This branch looks defective. The other possible side effect is that when reverting this branch we can remove other PRs that have already been added to the main. Since today is the last date, it is better to avoid such experiments.

[oleksandr-maksymikhin]

one more attempt

The merge-base changed after approval.

[emrebiyik]

Don't spend time. Just create a new branch and modify only this one file (communication.md). This branch looks defective. The other possible side effect is that when reverting this branch we can remove other PRs that have already been added to the main. Since today is the last date, it is better to avoid such experiments.

Should we close this pull request, or keep it open while working on the new branch?

[emrebiyik]

All conflicts have been resolved, and apart from this file, the other unrelated files in the main branch will not be affected.