Emre Türker | Individual Contribution Report ‐ Milestone 2

• Member: Emre Türker

• Responsibilities:

  • Researching, determining, and implementing the flows of backend services.
  • Determining architecture of the code base for backend.
  • Preparing a part of the Milestone 2 Review related to describing the status of deliverables.
  • Reviewing the works done by other team mates and giving respective feedbacks.

• Main contributions:

  • Built entity classes: Decided on the fields of individual classes and determined the relations among them.
  • Developed the endpoints for accessing the necessary data that would be presented in profile pages.
  • Actively participated in the brainstorming activities related to determining the general ingredients for the character and games pages, also in the recommendation algorithm during labs.
  • Implemented the tag related endpoints, profile related endpoints.
  • Fixed a bug related to CORS and cookies not being set by the frontend.
  • Enhanced the controller and service for accessing the user information.
  • Wrote a part in the milestone related to the executive summary.
  • Integrated AWS S3 to the project. Which resulted in decreased response times, since it was taking long to send images as byte arrays from the backend to the frontend.
  • Implemented the report entity in collaboration with Omer Bahadiroglu.

• Code-related significant issues:

  • #364: Change in the registration.
  • #391: Entity classes implementation.
  • #392: Researching AWS S3 for image storage.
  • #403: Implementing Profile Page Related Endpoints.
  • #404: Update Registration Endpoint.
  • #437: Initialize report and like features, some refactors to backend.
  • #446: Create tag related functions.

• Management-related significant issues:

  • #367: Doing a task sharing for implementing the profile page.

• Pull requests:

  • Created and merged pull requests for the implementation of backend generally.
  • Reviewed pull requests related to the backend structure and user authentication features.
  • I have come across many conflicts. However, rather than trying to solve the conflicts via the merge request, I have talked to my team mate in person, or better, we solved the conflicts as a pair. That's why almost each merge request has a review in the "Seems fine, merging" format.
  • My pull Requests:
    • #398: Refactor entites
    • #434: Implement profile page related endpoints
    • #438: Report and like features
    • #442: Implement AWS S3 features
    • #443: Enhance profile related endpoints
    • #447: Implement tag related functions
  • Reviewed and merged pull requests:
    • #435: Forum post endpoints
    • #436: Comments endpoints
    • #445: Refactor post relateds
    • #451: Forum tag feature and minor enhancements