[OLD] Personal Effort (Muhammed Emin Arayıcı) - bounswe/bounswe2024group11 GitHub Wiki
Week #1 February 13 - February 19
| Task | Type | Estimated Time | Time Taken |
|---|---|---|---|
| Participated in the weekly group meeting, contributing to the discussion on project assignment and task allocation. | Meeting | 1.5 hours | 1.5 hours |
| Created and self-assigned my first issue on GitHub, detailing the need for a new feature in the project's navigation system. | Good first issue | 5 min | 5 min |
| Developed a bio page for the project wiki, providing a comprehensive background on my role, expertise, and contributions to the project. | Repo | 30 min | 1 hour |
| Explored the repository of Pynecone on GitHub, identifying potential integration opportunities and innovative features that could be adapted for our project. Also, explored how they use their repo interms of issues, wiki, etc. Check it here. | Research | 2 hours | 1.5 hours |
| Studied Git commit conventions and semantic versioning to ensure our project adheres to industry standards, improving our version control practices. | Research | 2 hours | 3.5 hours |
| Reviewed a summary of Git For Ages 4 And Up provided by my custom GPT tool, Video Transcript Summarizer, enhancing my understanding of Git concepts. | Research | 30 min | 30 min |
Week #4 March 5 - March 11
| Task | Type | Estimated Time | Time Taken |
|---|---|---|---|
| Attended the group meeting for project overview and assignment distribution. This meeting was crucial for understanding the project's objectives, timeline, and individual responsibilities moving forward. | Meeting | 1 hour | 70 min |
| Attended the group meeting for domain evaluation, contributing insights on potential challenges and opportunities in our domain options. The discussion helped refine our project scope and identify key areas for potential applications. | Meeting | 1 hour | 2 hours |
| Researched the Wikidata API, including its functionalities, how to integrate it into our project, and its benefits for enhancing our application's data richness. This research was documented and shared with the team for consideration in our development strategy. | Research | 3 hours | 3 hours |
Week #5 March 12 - March 18
| Task | Type | Estimated Time | Time Taken |
|---|---|---|---|
| Reviewed the project requirements and provided detailed feedback focusing on areas that could enhance the user experience and technical feasibility. This feedback was compiled in a document and shared with assignees of the issue. | Review | 1 hour | 2 hours |
| Reviewed all scenarios to ensure they aligned with the project goals and user needs. This involved analyzing the written scenarios against the project requirements and suggesting improvements for clarity and completeness. | Review | 1 hour | 1 hour |
| Created all desktop mock-up screens with Ümit Can Evleksiz in the workspace of our Figma team. This included designing interfaces for the main user interactions identified in the project requirements and scenarios. The final designs have been shared with the team for feedback. | Design | 5 hours | 6 hours |
| Revised the scenarios with Ümit Can Evleksiz to ensure consistency with the mock-up screens being designed. This included updating scenario descriptions to reflect the finalized design elements and user flows depicted in the Figma mock-ups. | Review | 30 mins | 30 mins |
| Put all desktop mock-up screens to the five different scenario pages in the wiki accordingly. Each screen was associated with its relevant user scenario to facilitate a comprehensive understanding of the user flow and to provide a visual guide for the team. You can see the mock-up screens in the Mock-ups section of the pages Scenario 1, Scenario 2, Scenario 3, Scenario 4, and Scenario 5. | Repo | 1 hour | 1 hour |
| Updated my personal efforts page on the project wiki, ensuring all contributions were accurately reflected and easily accessible for team review. | Repo | 2 hours | 3 hours |
| Updated the Responsibility Assignment Matrix (RAM) table to reflect current project roles and responsibilities, ensuring clarity and alignment within the team. | Repo | 1 hour | 30 min |
Week #6 March 19 - March 25
| Task | Type | Estimated Time | Time Taken |
|---|---|---|---|
| Revised the project plan with my colleagues Ceydanur Şen and Muhammet Emin Çiftçi based on the latest feedback, incorporating suggestions and adjusting tasks, timelines, and milestones accordingly to stay on track. | Planning | 3 hours | 4 hours |
| Moderated the weekly team meeting, facilitating discussion and distributing tasks for the second milestone, enhancing team coordination and focus. | Meeting | 1 hour | 1 hour |
| Updated the GitHub roadmap with Hasan Kerem Şeker to align with the second milestone of the project plan, ensuring that all project activities are accurately reflected and up to date for team and stakeholder reference. | Planning | 1 hour | 30 min |
Week #7 March 26 - April 1
| Task | Type | Estimated Time | Time Taken |
|---|---|---|---|
| Researched the creation of use-case diagrams and developed diagrams to clearly represent system interactions. | Research & Design | 5 hours | 12 hours |
Week #10 April 16 - April 22
| Task | Type | Estimated Time | Time Taken |
|---|---|---|---|
| Researched how to initialize a Django app, a React app, and a React Native app. | Research | 4 hours | 4 hours |
| Initialized the backend, web, and mobile apps during a weekly meeting. | Implementation | 1 hour | 1.5 hours |
Adjusted appropriate .gitignore files for each app. |
Implementation | 30 mins | 30 mins |
| Advanced Git techniques to enhance version control practices. | Learning | 2 hours | 1 hour |
| Researched how to implement API endpoints, including detailed documentation of each endpoint. | Research | 5 hours | 3 hours |
| Implemented API endpoints for the User model with Ceydanur Şen. All CRUD endpoints are ready. | Implementation | 5 hours | 4 hours |
| Researched how to write API unit tests. | Research | 5 hours | 4 hours |
| Wrote API unit tests for the User model with Mücahit Erdoğan Ünlü, ensuring robust functionality. | Implementation | 4 hours | 4 hours |
| Researched cloud platforms to identify optimal deployment solutions. | Research | 3 hours | 2 hours |
| Explored methods for securely sharing secrets within the development team. | Research | 2 hours | 3 hours |
Week #11 April 23 - April 29
| Task | Type | Estimated Time | Time Taken |
|---|---|---|---|
| Investigated various API authentication types to find a better suit for our application. Found, Instead of basic authentication, a token-based approach is more suitable for us. | Research | 3 hours | 4 hours |
| Researched how to dockerize backend applications. | Research | 4 hours | 5 hours |
| Dockerized the backend application, configuring Docker settings for optimal performance. | Implementation | 4 hours | 2 hours |
| Researched how to dockerize whole application including database. | Research | 5 hours | 6 hours |
| Dockerized database, backend, and frontend applications together with a docker-compose file and multiple Dockerfiles. | Implementation | 4 hours | 2 hours |
| Executed manual deployment of the application, optimizing deployment procedures. | Implementation | 3 hours | 2 hours |
| Researched and implemented CI/CD pipelines to streamline development and deployment processes. | Research & Implementation | 3 hours | 4 hours |
| As a service maintainer, performed multiple manual deployments to the test and prod environments, refining deployment accuracy. Also, maintained the databases. | Service Maintenance | 3 hours | 6 hours |
| Configured Bruno for project-specific needs. | Implementation | 1 hour | 30 min |