-
Notifications
You must be signed in to change notification settings - Fork 1
Version Control System
Version control is a system that stores changes of a file or a folder so that we can call recall specific versions later. Since Github is a distributed version control system, GitHub offers many benefits for users. The reasons of using distributed version control systems may be becoming less error prone comparing to other controlling systems and handling with communication problem. The other two VCS' are Local VCS and Centralized VCS. Although Local VCS is simple, is is error prone since user must know where to copy the files. In Centralized VCS, because it has one central server, if the server falls, nobody can work on the project until server is recovered. Basically, distributed version control allows users work on a project without sharing a common network. To maintain this feature, providing speed and data integrity is absolutely important. Furthermore, with this control system, we do not need to have only one central repository and recovery of project becomes easier and files/projects usually do not corrupt. Because we do not need to have only one central server, even if one of the servers fall, with other servers we can recover and restore data and repositories. In Github, we can keep track of files' extension so that unneccessary files cannot be added into working folder so that we can maintain neater project environment. In addition, it is free, open source, has a user-friendly design. Since it uses command line and commands like Linux, you also do not need to learn too much extra thing for using Github.
[Version Control System] (https://git-scm.com/book/en/v2/Getting-Started-About-Version-Control)
[Distributed Version Control] (https://en.wikipedia.org/wiki/Distributed_version_control)
[Git] (https://en.wikipedia.org/wiki/Git_(software))
[This video is about what Github is] (http://git-scm.com/video/what-is-git)
[This video is about version control system] (http://git-scm.com/video/what-is-version-control)
- [Communication Plan] (Communication-Plan)
- Database Schema
- API Documentation
- [Description] (Project-Description)
- [Diagrams] (Diagrams)
- [Domain Analysis] (Domain-Analysis)
- [Features, Themes] (Features,-Themes)
- Mockups
- [Personas] (Personas)
- Plan
- Responsibility Assignment Matrix
- Requirements
- [Use Cases] (Use-Cases)
- [User Stories] (User-Stories)
- Peer Reviews
- Project Tutorial
- Repository Usage Manual
- [Test Plan] (Test-Plans)
- Ahmet Ercan Tekden
- Esma Özelbaş
- Ezgi Tekdemir
- Furkan Erdem Perşembe
- İsmail Enes Yılmaz
- İrem Zöğ
- Kayahan Taşyaran
- Mehmet Utkan Gezer
Preliminary Meetings:
- Meeting 1 (Feb 16)
- Meeting 2 (Feb 23)
- Meeting 3 (Mar 03)
- Meeting 4 (Mar 08)
- Meeting 5 (Mar 14)
- Meeting 6 (Mar 28)
- Customer Meeting 1 (Mar 31)
- Meeting 7 (Apr 05)
Meetings In-production:
- Meeting 8 (Sep 27)
- Meeting 9 (Oct 03)
- Meeting 10 (Oct 10)
- Git Meeting (Oct 14)
- Meeting 11 (Oct 17)
- Meeting 12 (Oct 24, expected)
- Meeting 13 (Oct 31)
- [Meeting 14 (Nov 7)] (Meeting-14)
- Meeting 15 (Nov 14)
- [Meeting 16 (Nov 21)] (Meeting-16)
- [Meeting 17 (Dec 5)] (Meeting-17)
- Meeting 18 (Dec 12)
- [Meeting 19 (Dec 19)] (Meeting-19)
within Sub-groups:
- Database Meeting (Oct 11)
- Android Meeting 1 (Oct 14)
- [Frontend Meeting 1 (Oct 14)](Frontend Meeting 1)
with Customer: