Egemen Kaplan ‐ Milestone 1 Individual Contributions Report

Member: Egemen Kaplan

Responsibilities

My responsibilities were:

• Revising the requirement specifications and sequence diagrams
• Creating the project plan
• Deciding on technologies to use for the web development
• Being a member of the web team and contributing to the web app code base
• Reviewing pull requests mainly done by the web team.

Main Contributions

At the start of the semester, I revised our project requirements and sequence diagrams and played a big part in the creation of the project plan. Every week, I worked intensively on the creation of the lab report, gathering information from the team as they discussed their plans. Later in the week I kept reminding the team about the tasks that need to be completed using our communication channels. I tried to review as many pull requests as possible in the areas of the project, where I had sufficient knowledge.

I became part of the web team and led the development process. After Bahri initialized the web project, I improved its structure and defined some conventions using Eslint. I implemented our routing system and the wrappers that will cover our entire app. I implemented some parts of our Oauth modals, a significant portion of our profile view and our toast mechanism (notification pop ups on the side of the screen). Finally I helped deploying the project. I wrote the dockerfile for Web project, joined Baki and Meriç in order to bring every part of project together and deploy it on EC2

Finally I helped deploying the project. I wrote the dockerfile for Web project, joined Baki and Meriç in order to bring every part of project together and deploy it on EC2, which was quite a taxing issue with countless unrecognizable error messages and endless search for the fixes.

Code Related Issues:

1. #225 - Web - Together with Bahri, we designed our first modal and later he added some styling to it through the React framework we are using, Bootstrap.
2. #229 - Web - Using model of our first modal (sign up), Bahri and I created two more modals that will be used during the forgot password flow.
3. #237 - Web - I improved the project structure overall to make it more maintainable and standardized.
4. #261 - Web - In order to dockerize our project I wrote a dockerfile, which we then used in:
5. #301 in conjunction with other backend dockerfiles and docker-compose.yaml. We completed the deployment of the backend and frontend of our project.
6. #274 - Web - I created the topbar and sidebar of the app, connected them with our Oauth modals and wrapped our entire project with these bars
7. #271 and #281 - Web - I created the profile and its overall layout. I implemented the profile header, post preview component and the list card that displays the recent posts’ previews’ of the user.
8. #290 - Web - connected our forgot password endpoints to our UI and added the toast mechanism for warning and info pop ups. Baki had great contributions to my work here.
9. #307 - Worked together with Baki to create our 0.1.0-alpha release

Management Related Issues

1. #192 - Revised the requirement specifications of our project together with Baki, Bahadır and Meriç.
2. #196 - Revised sequence diagrams with Begüm and Sude.
3. #201, #210, #255 - Mainly, I prepared the lab reports and gathered the information on the previous work and new plans of every subteam (backend, web, mobile) while they took advantage of being in the same place to discuss their plans.
4. #204 - Decided on which technologies to use for the Web project.
5. #206 - Created our first version of project plan with several teammates
6. #309 - Fixed the project plan after the feedback we received.
7. #329 - I created the table that lists the deliverables for the milestone 1 and their status.

All my pull requests:

1. #245 - Created this PR for my branch that is related to the issue #237
2. #250 - Reviewed this PR after we worked on the code together with Bahri. Later, I discovered a problem with package names that prevented our Eslint from working correctly and handled it.
3. #251 - Reviewed this PR. Pull request was to merge the feature branch with our “main” branch, which is against our branching policy. I fixed the destination to our “web-master” branch
4. #252 - Created this PR after the implementation of issue #229
5. #278 - Created this PR after the implementation of issue #274
6. #279 - Created this PR in order to transfer the new code from backend to the web so that we could start implementing the REST requests on our web side.
7. #283 - Reviewed this PR
8. #284 - Created this PR after implementation of issue #281
9. #291 - Reviewed this PR
10. #297 - I did the work mentioned in the issue #290 and created this PR. A conflict occurred during this merge due to another branch, split off from the same base as mine, being merged back into the base before my own. Both of these child branches did some changes to some common files. So, I pulled the branch to my local, resolved conflicts there and directly pushed the changes to the base branch.
11. #303 - Reviewed this PR
12. #308 - Reviewed this PR. There were tiny conflicts with routing that I could just solve with the online git editor and I made some suggestions to my team mate for the future. You can see more under the comments of the PR.

Additional Information

I believe I listed everything above, and mentioned everything I did, which doesn’t have its own issue in git, under the Main Contributions part of my report.