Meeting #3

[abenteuerzeit]

Date: July 9, 2023

Transcript

Participants:

1. @abenteuerzeit
2. @DemetrPI
3. @bartt90
4. @piotrpalacz

Previous Meeting Context:

For the context of this meeting, please refer to the previous meeting's agenda and notes:

Meeting #2

TenantTalk Meeting Summary

A list of features and how to implement them. 2:45

• Assign an owner to the full stack of features.
• The main aim of the project.
• Residential housing reviews.

Introducing new member - Bartosz: How did you get into design?

• Using Photoshop, Adobe Illustrator and Figma for design.
• Basic design principles and design principles.
• How to manage individual objects and texts.
• How to create visualizations for pages.

Design questions and answers.

• How to get help with design questions.
• What it's like to live at a certain address.
• Focus on Poland, Kraków and localized content in general.
• Commercial projects, creating a functioning product.

Monetization strategy for the product.

• Presenting the product to investors from the Middle East and Central Asia.
• Monetization strategy.
• Action plan, draft up an email after the meeting.
• Coding and programming requirements.

How do you deal with pull requests?

• Concerns with Figma and pull requests.
• Legal advice from Peter and @DemetrPI
• Basic advice on how to choose an apartment.
• The general direction of the site.

The role of @piotrpalacz

• Peter is responsible for the front-end of the site.

Security settings and updates.

• Checking the security settings in the codebase.
• Working on the DevOps pipelines for publishing the website.
• Temporary website created for learning purposes.

Discussing database design ideas.

• Discussion Database Design Ideas #13, database design ideas.
• Discussion Pull Request Checklist #8 PR Checklist
• Discussion Semantic Commit Cheatsheet #9 atomic commits and semantic commit cheat sheet.
• How to write commits and describe changes in one sentence.
• Making 1000 short commits is better than 12 huge, unmanageable commits.

How frequently should we update the website?

• At least once before each meeting
• Creating anything at all that never existed before.
• Accessibility and usability checks would be good