Skip to content

Meeting #2 (12.02.2018)

Jump to bottom Edit New page
Oğuz Kaan Yüksel edited this page Feb 17, 2018 · 26 revisions

1. Details

  • Location: Boğaziçi Northern Campus - Student Lounge
  • Date: 12 February 2018
  • Time: 15:00 - 16:20

Attendees

  • Gökhan Tekel
  • Didem Öngü
  • Hamdi Özgür Akaoğlu
  • Nazmican Çalık
  • İlyas Demirkıran
  • Yusuf Kalaycı
  • Serkan Özel
  • Kemal Tulum
  • Galip Ümit Yolcu
  • Oğuz Kaan Yüksel

2. Agenda

  • 2.1. Discuss GitHub's Projects
  • 2.2. Review label system
  • 2.3. Discuss hosting of external files used in the repo (images, etc)
  • 2.4. Ideation of product/team name
  • 2.5. Quick Git Review
    • 2.5.1. Basic concepts
    • 2.5.2. Conflict and resolution demo
  • 2.6. Discuss the git workflow
    • 2.6.1. Git commit semantics & styling
    • 2.6.2. Clean branch histories & branch structure
    • 2.6.3. Master branch protection & code review
  • 2.7. Organize Contribution Guide project
  • 2.8. Reconsider communication plan
  • 2.9. Organize the Requirements Elicitation process

3. Discussion

  • 3.1. GitHub's Projects section is more flexible than milestones. It can be utilized to handle more intricate milestone cases.
  • 3.2. Additional Platform label type, which specifies what the issue is on specifically, would be beneficial to add. Platform: Documentation, Platform: Frontend, Platform: Backend are considered.
  • 3.3. External files should be uploaded to the repository to avoid any broken url problems. Accumulation of such resources must be on a specific folder with an organized fashion.
  • 3.4. No suggestions have been made for the team/product name. Any candidate will be considered through the week for fun.
  • 3.5. Git review part demonstrated that we should have a Git Guide which we can frequently consult.
  • 3.6. Discussion of git workflow stressed communication and coherence among the group.
    • 3.6.1. Ionic Repository commit style is adopted. Not only syntactic consensus will help to develop a fluent and efficient communication but also semantical consensus i.e modularity and scope of commits, clean meaningful titles and so on.
    • 3.6.2. Branch workflow is considered including feature-branch & fix-branch & issue-branch styles. Importance of clean, meaningful linear history of the branches are emphasized. According to the specific division of labor, there will be a representing semantic branch division once the development phase begins.
    • 3.6.3. Protection of the branches, particularly master branch is discussed. Dangers of manipulation of git history is talked.
    • 3.6.4. Code review will be employed to increase quality and reliability of the product.
  • 3.7. A Contribution Guide with a supplement Git Guide is necessary to track the language we formed for our repository. As a reflection of the agile development, these guides should be updated regularly and if need arises new guides should be added.
  • 3.8. Communication Plan should be available as an exclusive file where the details of the communication should be elaborated extensively.
  • 3.9. Requirements Elicitation process must start from higher conceptual level toward the details. Segmentation of the requirements to different main parts should be supervised by all members of the group. Then, the details of a single main part should be considered extensively with a minimum of two supervisor.
  • 3.10. README.md should be updated in according to team/product name, contribution guidelines and project description.

4. Actions

ID Who What Deadline
4.1. Gökhan Tekel Setup Requirements Elicitation Project board 14 February 2018 - 23:59
4.2. Didem Öngü Add additional labels discussed 18 February 2018 - 23:59
4.3. Hamdi Özgür Akaoğlu Store external files on the repo 18 February 2018 - 23:59
4.4. Oğuz Kaan Yüksel Document Contribution & Git Guides 18 February 2018 - 23:59
4.5. Oğuz Kaan Yüksel Setup Git Workflow - master protection & code review -
4.6. Nazmican Çalık Setup Communication Plan 18 February 2018 - 23:59
4.7. Everyone Contribute to the Requirements Elicitation process 18 February 2018 - 23:59
4.8. Kemal Tulum Track what's need to be elicited from consumer 15 February 2018 - 15:59
4.9. İlyas Demirkıran Requirements Elicitation - Team Leader 18 February 2018 - 23:59
4.10. Yusuf Kalaycı Requirements Elicitation - Team Leader 18 February 2018 - 23:59
4.11. Serkan Özel Requirements Elicitation - Team Leader 18 February 2018 - 23:59
4.12. Galip Ümit Yolcu Requirements Elicitation - Team Leader 18 February 2018 - 23:59
4.13. Gökhan Tekel & Didem Öngü Update README.md file as discussed 18 February 2018 - 23:59

5. Resources

Actopus -- Culture, adrenalin and friendship project for web and android

🐙 Actopus Team

Documents

Deliverables

Products

Clone this wiki locally