Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
pub:company:communications [25.09.2024 12:26] – removed - external edit (Unknown date) 127.0.0.1 | pub:company:communications [23.10.2024 10:29] (current) – [Writing and Design Style] Predrag Tasevski | ||
---|---|---|---|
Line 1: | Line 1: | ||
+ | ====== Communications ====== | ||
+ | This page explains what every team member (// | ||
+ | |||
+ | ===== All hands ===== | ||
+ | |||
+ | Unicis organizes a meeting called the “All hands” every month. All team members, both internal and external, are required to attend the monthly “All Hands” meeting. All meetings are recorded and team members who can’t attend should watch the recording within a few days. | ||
+ | |||
+ | ===== Strategy ===== | ||
+ | |||
+ | You can read about company positioning and product strategy in Unicis Strategy (private). | ||
+ | |||
+ | ===== Competition ===== | ||
+ | |||
+ | We monitor the capabilities of competitors and adjacent products on our [[https:// | ||
+ | |||
+ | ===== Directly responsible individuals (DRIs) ===== | ||
+ | |||
+ | ^Area of responsibility | ||
+ | |Revenue | ||
+ | |Pricing | ||
+ | |Illustrations | ||
+ | |Website | ||
+ | |Ads, Social media, Video |CEO and CCO | | ||
+ | |Information Technology (IT) |CEO and CTO | | ||
+ | |Legal contracts | ||
+ | |Payroll, Bookkeeping | ||
+ | |Customer support, renewals & deployments|CCO | ||
+ | |Quality assurance (QA) |CEO and CTO | | ||
+ | |Feature and product | ||
+ | |Product documentation | ||
+ | |Engineering output and architecture | ||
+ | |Product development | ||
+ | |Invoicing | ||
+ | |||
+ | ===== Website(unicis.tech) ===== | ||
+ | |||
+ | Unicis website is built with [[https:// | ||
+ | |||
+ | ==== Docs ==== | ||
+ | |||
+ | The [[https:// | ||
+ | |||
+ | ==== Blog ==== | ||
+ | |||
+ | Blog articles can be published using [[https:// | ||
+ | |||
+ | ===== Marketing programs ===== | ||
+ | |||
+ | We only use open source marketing solutions, such as [[https:// | ||
+ | |||
+ | ==== Newsletter ==== | ||
+ | |||
+ | We use Mautic to communicate with our community and people who sign up for our newsletter. Use the Unicis template to make a [[https:// | ||
+ | |||
+ | {{tag> | ||
+ | ===== Unicis on Social Networks ===== | ||
+ | |||
+ | ==== Social Media ==== | ||
+ | |||
+ | The biggest asset of Unicis is its user community. Social media conversations give contributors a chance to answer technical questions and get feedback. | ||
+ | |||
+ | Unicis doesn’t focus on selling itself. Instead, conversations are already happening in our social spaces that allow Unicis to connect with the community. | ||
+ | |||
+ | Here are some ideas for social media posts: | ||
+ | |||
+ | * Unicis the Product: Updates, new features, and user testimonials about Unicis. | ||
+ | * Internal Progress: Highlight team achievements, | ||
+ | * Highlighting Community Contributions: | ||
+ | * Highlighting Unicis and Industry Accomplishments: | ||
+ | * Industry News about Our Field: Share news and information about our products and services. | ||
+ | * Upcoming Events, Interviews, and Podcasts: Promote upcoming events, webinars, interviews, and podcast appearances by - Unicis and its team members. | ||
+ | |||
+ | ^Platform | ||
+ | |X (ex-Twitter)|@UnicisTech | ||
+ | |Mastodon | ||
+ | |||
+ | ==== Unicis on LinkedIn ==== | ||
+ | |||
+ | The [[https:// | ||
+ | |||
+ | - Create a Post note: Make a [[https:// | ||
+ | - Provide Context: Include any context in the note to explain why the post is important. | ||
+ | - Await Approval: Please keep an eye out for approval. Your post will be reviewed by the team and used in a promoted post if it’s deemed appropriate. | ||
+ | |||
+ | ==== Ads ==== | ||
+ | |||
+ | Unicis employs advertising to disseminate information to a broader audience and encourage greater involvement within communities. The more people who actively use Unicis or contribute, the better Unicis will be. | ||
+ | |||
+ | ==== Events ==== | ||
+ | |||
+ | One of the most effective methods of promoting Unicis products and solutions is through participation in events. This presents an opportunity to directly engage with potential users and contributers, | ||
+ | |||
+ | ==== Podcast ==== | ||
+ | |||
+ | Right now, Unicis doesn’t have a podcast, but we plan to do it in the future. We invite podcasters to invite us to participate in your sessions and promote Unicis and what we are building. | ||
+ | |||
+ | ==== Video ==== | ||
+ | |||
+ | Unicis uses [[https:// | ||
+ | |||
+ | ===== Meetings ===== | ||
+ | |||
+ | * **Join the meetings on time**. At Unicis, we start meetings promptly and don’t wait for late arrivals. Since we usually use the [[https:// | ||
+ | * **Turn on your camera**. Enabling your camera makes communication more complete and easy. You are welcome to keep your camera on or turn it off when joining meetings with new participants you may not be familiar with yet. But make sure to turn on your camera when you lead or cohost a meeting or when you show off your work during a demonstration. | ||
+ | * **Be warm**. The first minute or two of a meeting should be spent being present and engaging in small talk. Since we work remotely, we often miss out on the informal conversations and human connections that happen in physical workspaces. In the first minute of the meeting, say “Hi!” and connect before going over the agenda. | ||
+ | * **Take notes**. Every meeting should have a [[communications|designated responsible person]] to ensure that: | ||
+ | * The agenda is made or prepared in advance. | ||
+ | * A designated notetaker is assigned to the meeting. | ||
+ | * All action items are recorded and assigned to the right people. | ||
+ | |||
+ | ==== Meeting agendas ==== | ||
+ | |||
+ | <WRAP danger> | ||
+ | Every work-related meeting should have a calendar invite with an editable agenda.</ | ||
+ | |||
+ | <WRAP info> | ||
+ | To create a meeting agenda please use one of the following options:</ | ||
+ | |||
+ | |||
+ | * [[https:// | ||
+ | * [[https:// | ||
+ | * | ||
+ | ==== External meeting scheduling ==== | ||
+ | |||
+ | When scheduling external meetings, please provide external participants with a link to the Unicis intranet applications to schedule with the relevant internal participants. See how to [[https:// | ||
+ | |||
+ | ==== Internal meeting scheduling ==== | ||
+ | |||
+ | In order for the internal team to be able to schedule a meeting, it is important to set your [[https:// | ||
+ | |||
+ | <WRAP info> **Hint** If the meeting is 1-to-1, you can use the [[https:// | ||
+ | |||
+ | ==== Modifying an event organized by someone else ==== | ||
+ | |||
+ | You can edit, duplicate or delete an calendar event by using the following [[https:// | ||
+ | <WRAP warning > **Tip**\\ | ||
+ | Only the calendar owner can send out invitations. The sharees are not able to do that, whether they have write access to the event’s calendar or not. </ | ||
+ | |||
+ | ==== Shared Calendars ==== | ||
+ | |||
+ | With Unicis Intranet - Nextcloud it is possible to [[https:// | ||
+ | |||
+ | ===== The Skip level One-on-One ===== | ||
+ | |||
+ | At Unicis, skip-level one-on-one meetings are designed to foster open communication, | ||
+ | |||
+ | ==== Jitsi ==== | ||
+ | |||
+ | We use Jitsi for online meetings at Unicis. It’s important that everyone on the team feels comfortable using it. The Jitsi settings are the same for all team members. Please read the [[https:// | ||
+ | |||
+ | <WRAP info> **Authentication Method**\\ | ||
+ | Use SSO credentials to be a moderator and host a Jitsi meeting.</ | ||
+ | |||
+ | Example: | ||
+ | |||
+ | * Username: '' | ||
+ | * Password: '' | ||
+ | |||
+ | ==== Recording meetings ==== | ||
+ | |||
+ | Recording meetings at Unicis is an important practice that improves transparency, | ||
+ | |||
+ | The video recording session should be uploaded to the [[https:// | ||
+ | |||
+ | <WRAP danger> **Important**\\ | ||
+ | Before you begin recording the session, please inform everyone in the meeting. </ | ||
+ | |||
+ | ===== Information classification ===== | ||
+ | |||
+ | At Unicis, all information is classified according to the [[https:// | ||
+ | |||
+ | * **Public**: Share with anyone, anywhere in the world | ||
+ | * **Internal**: | ||
+ | * **Confidential**: | ||
+ | |||
+ | ===== Email relays ===== | ||
+ | |||
+ | At Unicis, several special email addresses automatically send messages to the right people, ensuring efficient communication and quick responses. Each email address has a minimum response time (“Min RT”) and a direct responsible individual (DRI) who is in charge of reading and responding to emails. This [[https:// | ||
+ | |||
+ | ===== Matrix/ | ||
+ | |||
+ | At Unicis, we don’t email each other inside the company. Instead, we use Element to talk to other Unicians. | ||
+ | |||
+ | ==== Key Matrix channels ==== | ||
+ | |||
+ | ^Channel | ||
+ | |'' | ||
+ | |'' | ||
+ | |'' | ||
+ | |||
+ | ==== Matrix communications and best practices ==== | ||
+ | |||
+ | At Unicis, we use Element to communicate. We encourage the use of channels over direct messages and encourage the use of threads within the Element whenever possible. Threads help reduce noise and notifications for others who are following the channel. We also don’t use global tags in channels to keep the environment respectful. Employees are encouraged to post polls or inquiries in the relevant channel and mention their teammates. | ||
+ | |||
+ | ===== Discord ===== | ||
+ | |||
+ | We use [[https:// | ||
+ | |||
+ | ==== Key Discord channels ==== | ||
+ | |||
+ | ^Channel | ||
+ | |'' | ||
+ | |'' | ||
+ | |'' | ||
+ | |'' | ||
+ | |||
+ | ===== Source Code repositories ===== | ||
+ | |||
+ | For the product and documentation, | ||
+ | |||
+ | ==== GitLab labels ==== | ||
+ | |||
+ | Unicis uses special characters or words to organize and categorize GitLab issues. | ||
+ | |||
+ | ^Label | ||
+ | |'' | ||
+ | |'' | ||
+ | |'' | ||
+ | |'' | ||
+ | |'' | ||
+ | |'' | ||
+ | |'' | ||
+ | |'' | ||
+ | |'' | ||
+ | |'' | ||
+ | |||
+ | ==== GitHub labels ==== | ||
+ | |||
+ | ^Label | ||
+ | |'' | ||
+ | |'' | ||
+ | |'' | ||
+ | |'' | ||
+ | |'' | ||
+ | |'' | ||
+ | |'' | ||
+ | |'' | ||
+ | |'' | ||
+ | |'' | ||
+ | |'' | ||
+ | |||
+ | |||
+ | ===== Spending company money ===== | ||
+ | |||
+ | At Unicis, spending company money follows a simple approach. | ||
+ | |||
+ | - **Responsible Spending:** As you would your own money, make wise decisions and avoid unnecessary expenses. | ||
+ | - **Efficiency: | ||
+ | - **Autonomy: | ||
+ | - **Guidelines: | ||
+ | |||
+ | We make sure that company money is used responsibly and effectively to help us reach our goals at Unicis. | ||
+ | |||
+ | ===== Travel ===== | ||
+ | |||
+ | FIXME | ||
+ | |||
+ | ===== Vendor questionnaires ===== | ||
+ | |||
+ | In response to security questionnaires, | ||
+ | |||
+ | ===== Contract signature and approval ===== | ||
+ | |||
+ | To have the contract signed, you must request an approval in Unicis Intranet by [[https:// | ||
+ | |||
+ | ==== Contract Review ==== | ||
+ | |||
+ | The CEO must approve each contract. Only internal Unicians can ask for contract review. Each request for approval has the option of being accepted or rejected. The Intranet adds an '' | ||
+ | |||
+ | ==== Contract Signed ==== | ||
+ | |||
+ | We use an open source [[https:// | ||
+ | |||
+ | ===== Trust center ===== | ||
+ | |||
+ | In a [[..: | ||
+ | |||
+ | ===== Compensation and Benefits ===== | ||
+ | |||
+ | FIXME | ||
+ | |||
+ | ==== Time tracking ==== | ||
+ | |||
+ | We track how much time you spend on issues and merge requests as described in this [[https:// | ||
+ | |||
+ | ==== Invoicing ==== | ||
+ | |||
+ | Each invoice addresing to Unicis needs to include the below company details, otherwise it will be invalid. | ||
+ | |||
+ | <WRAP danger> **Company Details**\\ | ||
+ | Unicis.Tech OÜ | ||
+ | |||
+ | Address: Sepapaja tn 6, 15551 Tallinn, Estonia | ||
+ | |||
+ | Registry code: | ||
+ | |||
+ | VAT number: EE102590489. </ | ||
+ | |||
+ | <WRAP info> **Invoice Generator for Freelancer**\\ | ||
+ | Please use the [[https:// | ||
+ | |||
+ | ==== Benefits ==== | ||
+ | |||
+ | FIXME | ||
+ | |||
+ | ===== Team member onboarding ===== | ||
+ | |||
+ | Unicis is an open-source project, and anyone is welcome to contribute at any time. Before the start date for a core team member, they are welcome to contribute, but they are not expected to. Here are some recommendations for new team members: | ||
+ | |||
+ | //We welcome to Unicis!// | ||
+ | |||
+ | - Read about the company. | ||
+ | - Take the time to get trained | ||
+ | - Get used to the tools. | ||
+ | - Become immersed in the world of . | ||
+ | |||
+ | ===== Performance feedback ===== | ||
+ | |||
+ | At Unicis, we use a structured process to hold performance feedback sessions. | ||
+ | |||
+ | - **Scheduled Meetings:** Feedback sessions are held every six months. | ||
+ | - **Preparation: | ||
+ | - **Two-Way Dialogue:** Feedback sessions involve a discussion where both parties share their thoughts. | ||
+ | - **Setting Goals:** Managers and employees establish SMART objectives that align with company objectives and personal growth. | ||
+ | - **Continuous Support:** Support is given to employees to help them reach their goals and address performance issues. | ||
+ | - **Documentation: | ||
+ | - **Follow-Up: | ||
+ | |||
+ | This approach fosters a culture of continuous learning and growth at Unicis. | ||
+ | |||
+ | ===== Equipment ===== | ||
+ | |||
+ | Unicis currently does not provide company equipment or software licenses. | ||
+ | |||
+ | ===== Writing ===== | ||
+ | |||
+ | Learn how to communicate at Unicis, including guidelines for the tone of voice, our approach, grammar and mechanics, and more. | ||
+ | |||
+ | ==== Writing and Design Style ==== | ||
+ | |||
+ | **Writing** FIXME | ||
+ | |||
+ | ==== Design, Colour, Icons and Font ==== | ||
+ | |||
+ | |||
+ | //Design//: FIXME | ||
+ | |||
+ | //Color//: | ||
+ | <codify css> | ||
+ | color-primary: | ||
+ | color-primary-dark: | ||
+ | color-primary-darker: | ||
+ | color-primary-darkest: | ||
+ | color-primary-light: | ||
+ | color-primary-lighter: | ||
+ | color-primary-lightest: | ||
+ | code-font-size: | ||
+ | navbar-background-color: | ||
+ | navbar-link-color: | ||
+ | navbar-link-color-hover: | ||
+ | navbar-link-color-active: | ||
+ | navbar-link-background-color-active: | ||
+ | navbar-link-background-color: | ||
+ | dropdown-background-color: | ||
+ | footer-background-color: | ||
+ | heading-font-family: | ||
+ | menu-color: #d9faff; | ||
+ | button-background-color: | ||
+ | </ | ||
+ | |||
+ | //Font//: We use company wide font [[https:// | ||
+ | |||
+ | //Icons//: We use the following library [[https:// | ||
+ | |||
+ | ==== LanguageTool ==== | ||
+ | |||
+ | We use an open-source tool [[operations: | ||
+ | |||
+ | ==== Writing in Markdown and Frontmatter ==== | ||
+ | |||
+ | At Unicis, we use Markdown syntax and conventions. Here are some examples and a [[https:// | ||
+ | |||
+ | ===== Glossary ===== | ||
+ | |||
+ | Commonly used terms at Unicis. | ||
+ | |||
+ | ^Term^Meaning | ||
+ | |API |(Application Programming Interface) a software go-between that allows applications to communicate. | ||
+ | |DRI |Directly responsible individuals. | ||
+ | |PR |A pull request is a proposal to merge a set of changes from one branch into another. | ||
+ | |GRC |Term covering an organization’s approach across these three practices: governance, risk management, and compliance.| | ||
+ | |||
+ | {{tag> |