Community Meeting Summary-[June 11, 2023] #7669
Cathy-lulu
started this conversation in
General
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Meeting Info
Date: June 11, 2023
Time: 8:00 PM(GMT+8)
Location: Online
Host: Meco
Attendance: RT-Thread Official Team & RT-Thread Community Committee Team
Meeting Type: Regular Community Meeting
Thanks for being with us at our latest community meeting! Here’s a recap of what we discussed:
Cathy led us in reviewing the post-conference report and discussing the topics for the 2023 RT-Thread Global Tech Conference. We also checked out a presentation from the Eclipse Foundation on RTOS vs Bare Metal, which included a comparison of several RTOSs. This sparked some great conversations within our community about the different RTOS options.
The team is hard at work on the Version 5.0.1 Release. At our recent community meeting, we put together a TODO list of tasks to complete before July.
TODO List
For the C++ part, only enable basic C++ support when C++ is enabled, without thread-related support. Thread support is a sub-switch. [cpp] support rt-thread CPP wrapper sub-switch macros #7660
For the C++ part, add cflags to reduce resource overhead https://github.com/RTduino/RTduino/blob/master/core/SConscript#L16
Create a community Code of Conduct and submit it to the GitHub repository.--Cathy
Merge rtdebug.h into rtdbg.h and discard rtdebug.h, leaving only rtdbg.h. Otherwise, there are two debug header files. Armink’s advice has been consulted (leave a version of .h with a #warning compile deprecation warning).
Add version 2 to the sensor framework and restore the original version to v1.
The issue of incompatibility between 5.0 and chip support packages needs further discussion.
CI care on simulator bsp.
Fix the issue of two volatiles in atomic under vs2019 compilation on bsp/simulator.
We’ve decided to continue supporting the 32-bit Windows 7 development environment in the env-windows repository. However, we won’t be making any further upgrades to it.
The Git in the env-windows repository needs to be upgraded, only upgrading 64-bit.
The QEMU in the env-windows repository needs to be upgraded, only upgrading 64-bit.
In the future, env will support online downloads.
In the env script repository, windows.ps1 needs to add an operation to prompt the user whether to delete the .env folder. Reference: RT-Thread/env@fe5b3a2 修复.env是否移除的提示,并增加在powershell上使用env的说明 env#209
To Do List for Env
Create Env tutorials and documentation in Chinese
Re-record Env tutorial videos: basic configuration, how to generate various projects
Integrate formatting into env: scons --formatting etc…
A doc is needed to introduce how to submit a software package
Shi is going to start by developing the generated template separately and promoting it. If everything goes smoothly, it will be merged into the env command along with its supporting documentation. You can find more information here: https://github.com/RT-Thread/rtthread-specification. Just a heads up - don’t add the template directly to the generate repository. It should be kept in its own separate repository.
The next Community Meeting is scheduled for June 25. We hope to see you there!
Beta Was this translation helpful? Give feedback.
All reactions