Meeting minutes and action plans

Step 1 - Add your conversations to Bash

You can record your meeting or upload already recorded meetings to Bash:

1. Go to Create Topic and select Audio or Video to upload or press the New Recording button to use the built-in audio recorder.

2. Once your meeting has been uploaded, you can check the audio and then press Transcribe.

In this case, a meeting transcript was added to Bash and summarized:

Localization meeting summary

The main purpose of the meeting is to discuss localization. David has a proposal for adding languages to the app and wants feedback on the project. Users have been requesting different languages, including those spoken in India, Spanish-speaking countries, France, and Poland. It is important to consider localization because language can affect grammar and gender in different languages. It is suggested to avoid right-to-left languages for now due to UX changes. To accurately translate phrases like "Marta has updated something," it is necessary to know the grammatical gender of the person's name. It is better to ask users for this information rather than making assumptions. Other apps can be looked at for inspiration on how they handle localization challenges. The localization should be a user preference and not enforced. It is important to ensure that the translation takes into account proper grammar and context. Some anti-patterns in localization should be avoided, such as using the same word for different purposes or asking for a large number of gender pronouns. The goal of localization is to provide a better user experience for individuals who may not understand English well.

Step 2 - Draft meeting minutes

Now that your meeting is available in Bash, you can use different templates to for example draft meeting minutes:

• Go to Drafts and select the Meeting Minutes template

• Select your source document containing your transcript

• Customize your draft and get meeting minutes generated in seconds!

Generated by Bash

Agenda:

1. Introduction to localization proposal by David.
2. Discussion on languages to be added initially.
3. Importance of obtaining grammatical gender information from users.
4. Debate on translating dynamic text versus only UI text.
5. Exploring how other apps handle localization challenges.
6. User preference and enforcement of localization.
7. Consideration of anti-patterns and inclusivity.

Summary: The meeting focused on discussing localization for the company’s product and gathering feedback. David presented a proposal outlining various localization options. The team acknowledged the demand for different languages from users worldwide. The first question addressed the languages to be added, with emphasis on avoiding right-to-left languages for now due to UX changes. The team recognized the need to request grammatical gender information from users to ensure accurate translations, particularly in languages like Polish and Spanish. It was agreed upon that user preference should determine whether the interface is displayed in English or the localized language. The team also expressed the importance of researching how other apps handle similar localization challenges.

Decisions and Action Items:

1. Marta to research other apps with localization challenges, specifically focusing on Polish and Spanish.
2. Explore methods to obtain grammatical gender information from users.
3. Consider the translation of dynamic text versus only UI text for localization.

Step 3 - Copy, share, or export

Use the Quick Action Bar to copy, email, print, or export this content or share this topic using the Share Topic button.

Step 4 - Try other templates

Bash has over 50 built-in templates that you can use to get going with new documents in seconds. Try out turning voice recordings into blog posts, document outlines, or emails.

Note: Please follow all local law when recording any conversation.