Contributions of Can Uzduran ‐ 451 Milestone 2

Member

Name: Can Uzduran
Group: 5

Responsibilities

Over the course of four weeks, I've participated in various feature and enhancements on back-end side of our project. Besides developing features throughout this milestone progress, I've also implementede some tests for our API. My main responsibilities can be listed as:

• Taking part of decision processes in front-end and mobile team, such as determining response formats and values of different endpoints.
• Taking part of decision processes in back-end team, such as implementation of endpoints or different service methods.
• Attending the lab hours and execute my role's needs if I'm moderator or note take on that corresponding week.
• Implementing various parts in back-end such as functionality of Review, Vote, Group, Achievements (Meta-achievements), etc..
• Making code and PR reviews extensively for the back-end team.
• Resolving bugs/fixes I've encountered.
• Making enhancement based on FE team and Mobile team needs
• Taking part in documentation of our testing logic as a back-end team

Ultimately, I believe that I was an active member and I've contributed equally to the team's efforts, working on various implementation, testing and documentation tasks.

Main Contributions

Week 6

Description	Type of Work	Issue	Time Spent
Review Implementation - BE	Feature	#640	3 hours
Documentation of Completed Endpoints	Documentation	#641	1 hours
Implement Voting Feature for Game Reviews BE	Feature	#642	4 hours
Writing Validation for Necessary Fields and DTOs	Feature	#643	3 hours

Week 7

Description	Type of Work	Issue	Time Spent
Create Group Endpoint Implementation - BE	Feature	#696	1 hours
Group Model Creation and Necessary Retrieving Endpoints (Filter, Search, Sort, Get Details)	Feature	#697	4 hours
Edit and Delete Functionalities for Group - BE	Feature	#714	1 hours

Week 8

Description	Type of Work	Issue	Time Spent
Implement Necessary Functionalities for Earned Achievements (Meta Achievements)	Feature	#790	3 hours
Adding "How do we test ?" Section to Lab Report - BE	Documentation	#812	2 hours

Week 9

Description	Type of Work	Issue	Time Spent
Writing JUnit Tests for Review Service	Test	#910	2 hrs
Writing JUnit Tests for Vote Service	Test	#918	2 hrs
Preparing an API Documentation	Documentation	#932	3 hrs
Preparing a Report for Review Service Test	Documentation	#933	2 hrs
Preparing a Report for Vote Service Test	Documentation	#934	2 hrs

Significant Work

Code Related

I have various code related contributions to the project but I believe that following four work is the most significant code related issues:

• Implementing Group Feature and Relevant Endpoints
• Implementing Review Feature and Relevant Endpoints
• Implementing Voting Feature and Relevant Endpoints
• Participated in Implementation of Profile and Achievement Features and Relevant Endpoints

Management Related

I have various management related contributions to the project but I believe that following two works are the most significant management related issues:

• Developing a Roadmap for Back-end Related Features
• Documenting and Explaining Our Testing and Development Processes as BE Team

Pull Requests

Created

Title	PR	Conflict
Backend/validation implementation	#653
tags are kept as ids instead - fix	#654
implemented game review functionality	#655
Voting Implementation - BE	#656
objects as query param fix	#661
Get reviews return username	#665
createdAt field is added to response dto of reviews	#667
review char limit fix	#725
Review improvements fixes	#730
Get game improvements and additions	#732
same tag was being added to game - fixed	#734
group implementation (get-all, get, create)	#740
bugfix on tag type validator	#741
Tag operations implementation (game and group)	#746
Delete group implementation	#753
Edit group functionality is added	#755
tag is populated in the response dtos	#762
Id and createdAt fields are added to response dto of getGroup	#768
Image controller swagger fix	#772
Group tag population fix	#829
Meta Achievements Implementation	#833
Auth service test fix (profile repository is mocked)	#835
Get group and tag fixes	#848
Changed return type of group detail	#853
Is deleted criteria is added twice, hence fixed	#860
arrays as query parameter fix (axios)	#877
Delete achievement fix	#895
JUnit tests for review service is implemented	#911
JUnit tests for vote service are implemented	#920

Merged

Title	PR	Conflict
added only admin or reviewer can update or delete reviews	#664
removed AdminRequired in delete review	#669
get-post-list now returns user object rather than just id	#672
get-post-list and get-post-detail improvements	#729
added group moderation(ban user, remove moderator, add moderator)	#750
populated tags in get-post-detail and get-post-list endpoints	#752
Add Game Icon Field to Create Game Page	#771
implemented apply to a private group feature	#874
modified tests according to password hashing	#659
Backend admin role	#660
Backend/achievement model	#826
added last activities(review, post, comment,vote)	#841
grant-achievement now adds achievement to profile instead of user	#846
Backend/profile	#854
implemented junit tests for comment service	#917
added group service unit tests	#921
Backend/junit achievement post	#929

Reviewed

Title	PR	Conflict
added only admin or reviewer can update or delete reviews	#664
removed AdminRequired in delete review	#669
get-post-list now returns user object rather than just id	#672
get-post-list and get-post-detail improvements	#729
added group moderation(ban user, remove moderator, add moderator)	#750
populated tags in get-post-detail and get-post-list endpoints	#752
Add Game Icon Field to Create Game Page	#771
implemented apply to a private group feature	#874
modified tests according to password hashing	#659
Backend admin role	#660
Backend/achievement model	#826
added last activities(review, post, comment,vote)	#841
grant-achievement now adds achievement to profile instead of user	#846
Backend/profile	#854
implemented junit tests for comment service	#917
added group service unit tests	#921
Backend/junit achievement post	#929

Additional Information:

I regularly attended the classes, labs, team meetings and back-end team meetings. I've also planned external meetings with front-end team members in order to avoid ambiguity among different tasks and discussed about requests and responses in general. I tried to contribute as equal as my team members and I took various tasks to achieve my best. I've also spent non-negligible effort on testing and documentation of my work.