Update CHANGELOG for release v3.8.3-patch.2

.github/ISSUE_TEMPLATE/bug-report.yaml

@@ -0,0 +1,82 @@
+name: Bug Report
+title: "[BUG] "
+labels: ["bug"]
+description: "Create a detailed report to help us identify and resolve issues."
+# assignees: []
+
+body:
+  - type: markdown
+    attributes:
+      value: "Thank you for taking the time to fill out the bug report. Please provide as much information as possible to help us understand and replicate the bug."
+
+  - type: input
+    id: openim-sdk-version
+    attributes:
+      label: OpenIM SDK Version
+      description: "Please provide the version number of OpenIM SDK you are using."
+      placeholder: "e.g., 3.8.0"
+    validations:
+      required: true
+
+  - type: input
+    id: openim-server-version
+    attributes:
+      label: OpenIM Server Version
+      description: "Please provide the version number of OpenIM Server you are using."
+      placeholder: "e.g., 3.8.0"
+
+  - type: dropdown
+    id: sdk-platform
+    attributes:
+      label: SDK Platform
+      description: "Please specify the SDK platform you are using."
+      options:
+        - iOS SDK
+        - Android SDK
+        - Web WASM SDK
+        - Electron FFI SDK
+        - Flutter SDK
+        - uni-app SDK
+        - Unity SDK
+        - .NET SDK
+        - React Native SDK
+    validations:
+      required: true
+
+  - type: input
+    id: device-model
+    attributes:
+      label: Device Model
+      description: "Please provide the model of the device you are using."
+      placeholder: "e.g., iPhone 15, Samsung Galaxy S23"
+    validations:
+      required: true
+
+  - type: input
+    id: operating-system-version
+    attributes:
+      label: Operating System Version
+      description: "Please provide the version number of the operating system you are using."
+      placeholder: "e.g., iOS 16.1, Android 13"
+    validations:
+      required: true
+
+  - type: textarea
+    id: bug-description-reproduction
+    attributes:
+      label: Bug Description and Steps to Reproduce
+      description: "Provide a detailed description of the bug and a step-by-step guide on how to reproduce it."
+      placeholder: "Describe the bug in detail here...\n\nSteps to reproduce the bug on the client:\n1. Launch the application with specific configurations (mention any relevant config details).\n2. Perform the following actions in the app '...'.\n3. Observe the behavior and note any error messages or logs.\n4. Mention any additional setup relevant to the bug (e.g., SDK version, platform-specific settings)."
+    validations:
+      required: true
+
+  - type: markdown
+    attributes:
+      value: "If possible, please add screenshots to help explain your problem."
+
+  - type: textarea
+    id: screenshots-link
+    attributes:
+      label: Screenshots Link
+      description: "If applicable, please provide any links to screenshots here."
+      placeholder: "Paste your screenshot URL here, e.g., http://imgur.com/example"

.github/ISSUE_TEMPLATE/config.yml

@@ -0,0 +1,11 @@
+blank_issues_enabled: false
+contact_links:
+  # - name: "Bug Report"
+  #   description: "Report a bug in the project"
+  #   file: "bug-report.yml"
+  - name: 📢 Connect on slack
+    url: https://join.slack.com/t/openimsdk/shared_invite/zt-2ijy1ys1f-O0aEDCr7ExRZ7mwsHAVg9A
+    about: Support OpenIM-related requests or issues, get in touch with developers and help on slack
+  - name: 🌐 OpenIM Blog
+    url: https://www.openim.io/
+    about: Open the OpenIM community blog

.github/ISSUE_TEMPLATE/documentation.md

@@ -0,0 +1,20 @@
+---
+name: Documentation Update
+about: Propose updates to documentation, including README files and other docs.
+title: "[DOC]: "  # Prefix for the title to help identify documentation issues
+labels: documentation  # Labels to be automatically added
+assignees: ''  # Optionally, specify maintainers or teams to be auto-assigned
+
+---
+
+## Documentation Updates
+Describe the documentation that needs to be updated or corrected. Please specify the files and sections if possible.
+
+## Motivation
+Explain why these updates are necessary. What is missing, misleading, or outdated?
+
+## Suggested Changes
+Detail the changes that you propose. If you are suggesting large changes, include examples or mockups of what the updated documentation should look like.
+
+## Additional Information
+Include any other information that might be relevant, such as links to discussions or related issues in the repository.

.github/ISSUE_TEMPLATE/feature-request.yaml

@@ -0,0 +1,43 @@
+name: Feature Request
+title: "[FEATURE REQUEST] "
+labels: ["feature request","enhancement"]
+description: "Propose a new feature or improvement that you believe will help enhance the project."
+# assignees: []
+
+body:
+  - type: markdown
+    attributes:
+      value: "Thank you for taking the time to propose a feature request. Please fill in as much detail as possible to help us understand why this feature is necessary and how it should work."
+
+  - type: textarea
+    id: feature-reason
+    attributes:
+      label: Why this feature?
+      description: "Explain why this feature is needed. What problem does it solve? How does it benefit the project and its users?"
+      placeholder: "Describe the need for this feature..."
+    validations:
+      required: true
+
+  - type: textarea
+    id: solution-proposal
+    attributes:
+      label: Suggested Solution
+      description: "Describe your proposed solution for this feature. How do you envision it working?"
+      placeholder: "Detail your solution here..."
+    validations:
+      required: true
+
+  - type: markdown
+    attributes:
+      value: "Please provide any other relevant information or screenshots that could help illustrate your idea."
+
+  - type: textarea
+    id: additional-info
+    attributes:
+      label: Additional Information
+      description: "Include any additional information, links, or screenshots that might be relevant to your feature request."
+      placeholder: "Add more context or links to relevant resources..."
+
+  - type: markdown
+    attributes:
+      value: "Thank you for contributing to the project! We appreciate your input and will review your suggestion as soon as possible."

.github/ISSUE_TEMPLATE/other.yml

@@ -0,0 +1,29 @@
+name: 🐧 Other
+description: Use this for any other issues. Please do NOT create blank issues
+title: "[Other]: <give this problem a name>"
+labels: ["other"]
+# assignees: []
+
+body:
+  - type: markdown
+    attributes:
+      value: "# Other issue"
+  - type: textarea
+    id: issuedescription
+    attributes:
+      label: What would you like to share?
+      description: Provide a clear and concise explanation of your issue.
+    validations:
+      required: true
+  - type: textarea
+    id: extrainfo
+    attributes:
+      label: Additional information
+      description: Is there anything else we should know about this issue?
+    validations:
+      required: false
+  - type: markdown
+    attributes:
+      value: |
+        You can also join our Discord community [here](https://join.slack.com/t/openimsdk/shared_invite/zt-2ijy1ys1f-O0aEDCr7ExRZ7mwsHAVg9A)
+        Feel free to check out other cool repositories of the openim Community [here](https://github.com/openimsdk)

.github/ISSUE_TEMPLATE/rfc.md

@@ -0,0 +1,26 @@
+---
+name: RFC - Feature Proposal
+about: Submit a proposal for a significant feature to invite community discussion.
+title: "[RFC]: "  # Prefix for the title to help identify RFC proposals
+labels: rfc, proposal  # Labels to be automatically added
+assignees: ''  # Optionally, specify maintainers or teams to be auto-assigned
+
+---
+
+## Proposal Overview
+Briefly describe the content and objectives of your proposal.
+
+## Motivation
+Why is this new feature necessary? What is the background of this problem?
+
+## Detailed Design
+Describe the technical details of the proposal, including implementation steps, code snippets, or architecture diagrams.
+
+## Alternatives Considered
+Have other alternatives been considered? Why is this approach preferred over others?
+
+## Impact
+How will this proposal affect existing practices and community users?
+
+## Additional Information
+Include any other relevant information such as related discussions, prior related work, etc.

.github/workflows/auto-invite-comment.yml

@@ -0,0 +1,38 @@
+name: Invite users to join OpenIM Community.
+on:
+  issue_comment:
+    types:
+      - created
+jobs:
+  issue_comment:
+    name: Invite users to join OpenIM Community
+    if: ${{ github.event.comment.body == '/invite' || github.event.comment.body == '/close' || github.event.comment.body == '/comment' }}
+    runs-on: ubuntu-latest
+    permissions:
+      issues: write
+    steps:
+      - name: Invite user to join OpenIM Community
+        uses: peter-evans/create-or-update-comment@v4
+        with:
+          token: ${{ secrets.BOT_GITHUB_TOKEN }}
+          issue-number: ${{ github.event.issue.number }}
+          body: |
+            We value close connections with our users, developers, and contributors here at Open-IM-Server. With a large community and maintainer team, we're always here to help and support you. Whether you're looking to join our community or have any questions or suggestions, we welcome you to get in touch with us.
+
+            Our most recommended way to get in touch is through [Slack](https://join.slack.com/t/openimsdk/shared_invite/zt-2ijy1ys1f-O0aEDCr7ExRZ7mwsHAVg9A). Even if you're in China, Slack is usually not blocked by firewalls, making it an easy way to connect with us. Our Slack community is the ideal place to discuss and share ideas and suggestions with other users and developers of Open-IM-Server. You can ask technical questions, seek help, or share your experiences with other users of Open-IM-Server.
+
+            In addition to Slack, we also offer the following ways to get in touch:
+
+            + <a href="https://join.slack.com/t/openimsdk/shared_invite/zt-2ijy1ys1f-O0aEDCr7ExRZ7mwsHAVg9A" target="_blank"><img src="https://img.shields.io/badge/Slack-OpenIM%2B-blueviolet?logo=slack&amp;logoColor=white"></a> We also have Slack channels for you to communicate and discuss. To join, visit https://slack.com/ and join our [👀 Open-IM-Server slack](https://join.slack.com/t/openimsdk/shared_invite/zt-2ijy1ys1f-O0aEDCr7ExRZ7mwsHAVg9A) team channel.
+            + <a href="https://mail.google.com/mail/u/0/?fs=1&tf=cm&[email protected]" target="_blank"><img src="https://img.shields.io/badge/gmail-%40OOpenIMSDKCore?style=social&logo=gmail"></a> Get in touch with us on [Gmail](https://mail.google.com/mail/u/0/?fs=1&tf=cm&[email protected]). If you have any questions or issues that need resolving, or any suggestions and feedback for our open source projects, please feel free to contact us via email.
+            + <a href="https://doc.rentsoft.cn/" target="_blank"><img src="https://img.shields.io/badge/%E5%8D%9A%E5%AE%A2-%40OpenIMSDKCore-blue?style=social&logo=Octopus%20Deploy"></a> Read our [blog](https://doc.rentsoft.cn/). Our blog is a great place to stay up-to-date with Open-IM-Server projects and trends. On the blog, we share our latest developments, tech trends, and other interesting information.
+            + <a href="https://github.com/OpenIMSDK/OpenIM-Docs/blob/main/docs/images/WechatIMG20.jpeg" target="_blank"><img src="https://img.shields.io/badge/%E5%BE%AE%E4%BF%A1-OpenIMSDKCore-brightgreen?logo=wechat&style=flat-square"></a> Add [Wechat](https://github.com/OpenIMSDK/OpenIM-Docs/blob/main/docs/images/WechatIMG20.jpeg) and indicate that you are a user or developer of Open-IM-Server. We will process your request as soon as possible.
+
+      # - name: Close Issue
+      #   uses: peter-evans/close-issue@v3
+      #   with:
+      #     token: ${{ secrets.BOT_GITHUB_TOKEN }}
+      #     issue-number: ${{ github.event.issue.number }}
+      #     comment: 🤖 Auto-closing issue, if you still need help please reopen the issue or ask for help in the community above
+      #     labels: |
+      #       accepted