-
Notifications
You must be signed in to change notification settings - Fork 1
Güney Yüksel
Hi, I'm Güney. I study computer engineering at Boğaziçi University. Even though the focus of my education is on engineering, my goal is to become a game developer. I'm trying to achieve that goal with my current studio .
-
- C++
- C#
- Java
-
- Android Studio
- Unreal Engine
- Unity
-
- Creativity & Short-term planning
I love movies and games. I also enjoy writing short stories, especially for games.
Week 2
Task | Type | Time taken | Outcome | Related issue |
---|---|---|---|---|
Setting up a personal page. | Assignment | 15 min | I have a personal page in our repo. | #27 |
Creating the labels for the issues. | Documentation | 20 min | We have labels for our issues. | #1 |
Creating the template for the issues. | Documentation & Wiki | 10 min | We have a wiki page for issue templates | #20 |
Creating a part about my favorite repo. | Assignment & Wiki | 20 min | I wrote the part about Godot in our top Repos page | #21 |
Creating the template for the repo documentation. | Documentation & Wiki | 5 min | We have a wiki page on repo documentation for the assignment. | #21 |
Updated the labels. | Documentation | 5 min | Added learning and research labels. | #33 |
Created the issue template as a template rather than a wiki page | Documentation & Research & Learning | 20 min | We have a template prompt in the "New Issue" screen | #34 |
Add an image to the Group's Top Repos page. | Wiki | 5 min | My part of the Group's Top Repos page has a related image. | #35 |
Updating the older issues with the current template. | Documentation | 10 min | Older issues have clear descriptions. | #36 |
Create a project. | Planning & Research & Learning | 40 min | I have a better understanding of projects and there is a project about our first assignment. | #37 |
Week 3
Task | Type | Time taken | Outcome | Related issue |
---|---|---|---|---|
Updating the issue template. | Documentation | 5 min | New issue's will have an estimated time field. Also minor corrections were made about other fields. | #42 |
Recreating the research page about GitHub. | Documentation & Wiki & Learning | 90 min | We have a more detailed research page about Git and GitHub. | #44 |
Create an issue template as a form. | Documentation & Learning | 40 min | We have one more Issue template and now I have a basic understanding of YAML. | #45 |
Create a banner for the group. | Documentation | 15 min | We have a banner for our README file. | #56 |
Week 4
Task | Type | Time taken | Outcome | Related issue |
---|---|---|---|---|
Co-Write Web Application part. | Wiki | 40 min | I've added example part to the page | #60 |
Add a domain idea. | Planning | 30 min | I've added two different domain ideas to the related part | #70 |
Determine the requirements for the feed page. | Documentation & Wiki | 30 min | Requirements page has a part about feed page. | #76 |
Week 5
Task | Type | Time taken | Outcome | Related issue |
---|---|---|---|---|
Update the project with old issues. | Documentation | 17 min | The project has my old issues and correctly filled fields. | #86, #94 |
Add glossary to the requirements page. | Wiki & Documentation | 26 min | The requirements page has a glossary part. | #87 |
Write User Scenarios. | Wiki | 240 min | We have 5 different user scenarios. | #88 |
Add your photo to the README. | Wiki & Documentation | 1 min | README has my photo. | #75 |
Write Individual Contributions. | Wiki & Documentation | 20 min | Our milestone report has my individual contributions part. | #91 |
Review issues. | Review | 5 min | Necessary issues are reviewed. | #61, #82, #98 |
Additional explanations for time-consuming tasks
-
#37. This is my first encounter with GitHub Projects. Even though the learning curve for projects is pretty steep, it took some time to get used to it and fill in the necessary fields about the issues accordingly. I've also lost quite some time while researching a bot to automatically fill in some fields like progress, size, start date, and end date when the issue is opened or closed.
-
#44. Similar to the GitHub Projects, the major time-consuming part was the learning part, but this time it was not so steep. I overestimated my knowledge of Git, so I needed to study it all over again. This part took about an hour. Then I started to write the page. After that, I decided to add a fun facts part because of some stuff I've read while learning Git.
-
#60. Even though the part I wrote was relatively small, I've researched multiple different APIs to find adequate examples.
-
#88. I needed to think a lot to come up with five distinct and original scenarios. Also, I've spent quite a lot of time trying to create and edit each image via AI tools.
🏠 Home
- 💬 Communication Plan
- 🎯 General Plan
- 🗂️ Project Plan
- 📊 Customer Milestone 1 Report
- 📊 Customer Milestone 2 Report
- 📊 Customer Milestone 3 Report
- 📕 User Manual
- 📕 System Manual
- Software Requirements
- API Doc
- RAM
- Sequence Diagram
- Class Diagram
- Use-Case Diagram
- Mockups
- User Scenario 1 - Quiz generation
- User Scenario 2 ‐ Find forum from the Quiz
- User Scenario 3 ‐ Ask Question in the Forum
- User Scenario 4 - Solve a Quiz Sent by Another User
- User Experience Enhancement Plans and Actions
- Final Presentation scenario
- UI Interfaces
- User Stories
- Lab Report #1 | 24.09.2024
- Lab Report #2 | 01.10.2024
- Lab Report #3 | 08.10.2024
- Lab Report #4 | 15.10.2024
- Lab Report #9 | 10.12.2024
Lab Meeting Notes
Team Meeting Notes
🧑🏻💻 About Us
🗂️ Templates
CmpE 352
- Customer Milestone 1 Report
- Customer Milestone 2 Report
- Customer Milestone 3 Report
- UML Use-Case Diagram
- UML Class Diagram
- Sequence Diagrams
- API Documentation
- RAM | Responsibility Assignment Matrix
🗃️ All Project Files
📝 352 Meeting Notes
- Meeting #11 | 11.05.2024
- Frontend Meeting Notes #2 | 07.05.2024
- Meeting #10 | 07.05.2024
- Frontend Meeting Notes #1 | 08.04.2024
- Backend Meeting Notes
- Mobile Team Meeting Notes
- Meeting #9 | 28.04.2024
- Meeting #8 | 22.04.2024
- Meeting #7 | 04.04.2024
- Meeting #6 | 27.03.2024
- Meeting #5 | 15.03.2024
- Customer Meeting #1 | 15.03.2024
- Meeting #4 | 07.03.2024
- Meeting #3 | 03.03.2024
- Meeting #2 | 26.02.2024
- Meeting #1 | 19.02.2024