What other teams did on Disaster Map in first 72 hours

• An application was developed on the first day in the field of artificial intelligence that converts text from a screenshot and extracts address, phone, and name information from this text and saves it to a database. EasyOCR was used to convert text and the OpenAI DaVinci model was trained to extract the address. On the third day, a model training was started using this model on a tweet that meets their needs. This model would be able to distinguish their needs.
• The legal team tried to support "Açık Yazılım Ağı" by preparing necessary legal texts for the personal data to be processed during this process, informing team members voluntarily about the risks that may be encountered, and providing legal advice. This was necessary due to the nature of the work done in terms of personal data.
• Test teams channeled our human resources to certain projects and tasks according to needs and requirements and made people who volunteered to lead responsible for planning. Afterwards, they started testing and created high-level requirements by documenting them. They detailed the errors in an Excel document, prioritized them, and moved them to GitHub, i.e. development teams.
• Moderation teams quickly directed incoming people on the server to relevant teams and channels to contribute, improved role settings to enable each team to work faster and more stable. Additionally, they constantly monitored and cleared spam and harmful messages on the server. Afterwards, they kept active communication with teams and solved communication issues such as informing and announcements.
• As the Cloud & Infra & DevOps team, they preferred cloud solutions together with the urgency of the process. They dockerized the projects and created CI&CD pipelines for production deployment to cloud environments that would be multi-cloud providers and technology-independent to provide the best support to 1000-person development teams both horizontally and vertically scalable. Thus, codes prepared independently by teams in terms of technology and human resources were deployed live on the relevant branches. They also resolved maintenance and zero downtime efforts by choosing serverless solutions for dependent databases, monitoring, cache, and streaming solutions in cloud environments. All working systems were designed as serverless and HA (high available).
• With the realization of application ideas, social media teams started marketing and communication activities to reach more people. Different sub-working groups were formed and organized quickly, from the design of the Açık Yazılım Ağı corporate identity to the preparation of content for social media accounts, collaboration with NGOs, and communication with influencers. Communication regarding applications and the community was done by these teams.