Updated up to 2024-09-30

README.md

@@ -1,3 +1,58 @@
+# 2024-09-30
+
+## Ad Hoc
+- Reviewed document [Status Software - Privacy Policy_ DRAFT_20240814](https://docs.google.com/document/d/1J4w2q6-fdVkXyC4D0aaQMQPq1rhfCCiz4I8p5gVUVds/edit) #reviewed
+	- Some minor comments and questions but the document is basically ready.
+## Schedule
+- Core team sync call
+	- https://app.fireflies.ai/view/Core-Teams-Sync-Desktop-Mobile-::lnuOXX2H3GBzENHa
+	- [[2024-09-30 Status Core Sync]]
+
+---
+# 2024-09-27
+## Ad Hoc
+- Review document [Status Blog - Status vs Telegram](https://docs.google.com/document/d/1bSPxTITJW43b371uqSO3rdOkn96V8c4z63P13HCmSeY/edit#heading=h.d4m03guwjlrf) #reviewed 
+	- A detailed document
+	- Required some minor suggestions and tweaks
+- Reviewed document [Project Steering Committee - September Pre-read (Notes)](https://docs.google.com/document/d/1TYWvktmtgCtZykGmGiFxQzKTAyr6V55N81ZIUM3bvOU/edit) #reviewed
+	- Probably way too late
+	- Added a number of items particularly to the IFT Synergy Log
+	
+---
+# 2024-09-26
+## Schedule
+- Call with Leonard
+	- Show and tell across IFT
+	- Discussing Status tech stack across both OS platforms
+	- Legacy of John's tenure
+	- Future steps walkthrough of the apps
+- Call with Ícaro
+- Call with Volo
+
+# 2024-09-25
+
+## Program
+### Privacy Policy
+The following documents will be buried and not see the light of day.
+- [[Privacy in Status Software]]
+- [[Privacy With Status Infrastructure and Insights]]
+- [[Privacy With Status Third Parties]]
+
+
+---
+# 2024-09-24
+
+## Schedule
+- Call with Jarrad.
+- Mobile Core Planning Notes:
+	- https://www.notion.so/Planning-Call-Notes-10b8f96fb65c80a48bd7c10281b428ef
+
+## Ad Hoc
+- Created the following proposals
+	- [PROPOSAL: Cross-IFT Buddy Program](https://www.notion.so/PROPOSAL-Cross-IFT-Buddy-Program-10b8f96fb65c8023a207e1438bd5ab64)
+	- [PROPOSAL: IFT Team Swap Program](https://www.notion.so/PROPOSAL-IFT-Team-Swap-Program-10b8f96fb65c80b28feddf6d1e3bf1ca)
+
+---
 # 2024-09-23
 ## Issues
 - [Data collection and terms&conditions are the first major impresisons of opening the client #21293](https://github.com/status-im/status-mobile/issues/21293)
@@ -20,7 +75,7 @@
 	- [Blog - Privacy in Status Software](https://docs.google.com/document/d/1g-YbLE8CktKcax0jCb9ny1CA0CfMZmnFZDS2irZDWxo/edit#heading=h.hd4l8rfnepui)
 	- [Privacy With Status First Parties](https://docs.google.com/document/d/1pcH_ZFC2uJ_kBk12ERRFrq40yrhaNBwBP_IUE5V2Hho/edit#heading=h.jsrcqj80z4sp)
 	- [Privacy With Status Third Parties](https://docs.google.com/document/d/1I7fkrZzLsZcNXVZWPhq1D6-izbIel8XhWa7hXGQ2lfc/edit#heading=h.3ndm6euh3z9j)
-	- /todo add articles as attachments
+	- #todo  add articles as attachments
 ### Legal Repo
 - New explicit and accurate name: "status software legal documents"
   - https://github.com/status-im/status-software-legal-documents

attachments/2024-09/2024-09-30 Status Core Sync.md

@@ -0,0 +1,35 @@
+# Overview
+The Core Teams Sync (Desktop + Mobile) meeting focused on critical aspects affecting both platforms, beginning with a release coordination update highlighting the need for version compatibility amongst releases 229, 230, and 231, with the mobile team targeting an end-of-October release. The session addressed improvements in the bug reporting process, emphasizing the challenges of user privacy when collecting logged information, and explored the potential use of Sentry or Google Crash Reporting. The group discussed the establishment of a central repository for legal documents, stressing the importance of versioning and handling diverging features across platforms, while also raising concerns regarding the accuracy of app store information and the need for comprehensive privacy policies. Additionally, issues with community description synchronization were identified, particularly regarding the ‘last opened at’ property and its bandwidth implications. A discussion on state management revealed the misuse of Waku, prompting consideration of alternative solutions and a plan for implementing necessary changes. Action items were assigned to various members for follow-up on compatibility checks, error logging integration, privacy policy inquiries, synchronization removal, and community description contributions.
+# Notes
+## 🚀 Release Coordination (00:04 - 06:32)
+- Discussion on compatibility between versions 229, 230, and 231
+- Pairing fallback needs to be on the same version for both mobile and desktop
+- Mobile team considering release by the end of October
+- Wallet team expected to be ready by mid-October
+
+## 🐛 Bug Reporting and User Experience (07:20 - 17:41)
+- Discussion on improving bug reporting process
+- Challenges with requesting logs from users due to privacy concerns
+- Consideration of using Sentry or Google Crash Reporting for error logging
+- Need to be cautious about potentially sensitive data in logs
+
+## 📄 Legal Documents Repository (17:45 - 28:16)
+- Sam introduced a central repository for legal documents
+- Discussion on versioning and platform-specific policies
+- Consideration of how to handle diverging features across platforms
+
+## 🔐 Privacy Policy and App Store Information (28:16 - 36:14)
+- Icaro raised concerns about accuracy of app store information
+- Need for legal team to review and approve app store descriptions
+- Discussion on potential need for platform-specific privacy policies
+
+## 🔄 Community Description Synchronization (36:31 - 44:12)
+- Patrick identified issue with community description propagation
+- Discussion on the 'last opened at' property and its impact on bandwidth
+- Consideration of removing or modifying the synchronization process
+
+## 🗄️ State Management and Waku Usage (44:12 - 56:27)
+- Discussion on misuse of Waku for state management
+- Consideration of alternative solutions like Codex or blockchain
+- Need for a strategy to implement breaking changes over time
+- Invitation to contribute to ongoing discussion thread on community description