Skip to content

Decision Log

Jump to bottom
ahmet murat sencay edited this page Dec 17, 2025 · 4 revisions

This page records key technical and organizational decisions made during the project.

Branching Strategy

We decided to use a GitFlow-like branching strategy consisting of main, develop, and feature/* branches. This approach ensures controlled integration, prevents direct pushes to critical branches, and supports code review.

Pull Request and Review Workflow

All changes are introduced via pull requests. Direct pushes to main and develop branches are prohibited. At least one approving review is required before merging to ensure code quality and team collaboration.

Project Management Tool

GitHub Projects was selected to track tasks, assign responsibilities, and visualize weekly progress using a Kanban-style board.

Documentation Strategy

Project documentation is maintained using Markdown files (README.md, INSTALL.md, etc.) and GitHub Wiki pages for weekly reports, meeting notes, and decision tracking.

Team Communication

Weekly meetings are documented in the GitHub Wiki to ensure transparency and maintain a clear record of discussions and decisions.

Clone this wiki locally