Hi Chris, > but also what is planned to be worked on
Agree. The most valuable experience I learned from running an open-source project is to share (rough) ideas early, publicly and inclusive. In other words, "You're Not Alone" and you don't need to do everything by yourself. So does the Timecho company. Waiting random open-source contributors to read the code, figure out the issues, writing down a proposal and driving it to implementation is a mystery. Typically, one writes down help wanted/good first issues that he/she doesn't have enough time to fill the details, provides the background and possible start point, shares issues with the community and mentors volunteers to move it forward, even without getting fully resolved. This is how open-source works. Here are some examples from Apache OpenDAL 1. https://github.com/apache/opendal/issues/5505 2. https://github.com/apache/opendal/issues/5474 3. https://github.com/apache/opendal/issues/6163 Hopefully it helps. Best. tison. On 2025/06/30 11:04:56 Christofer Dutz wrote: > Hi Tison, > > I had mentioned before, that I would also welcome very much not only to hear > what has been done, but also what is planned to be worked on. This way more > people can raise their interest in helping with things on the roadmap. It > might help people from the outside get engaged, or even help people involved > in the project, who don’t follow the china-based communication channels. I > personally have no idea how to contribute to the general roadmap besides > ideas to scratch my own itches. > > Chris > > Von: tison <wander4...@gmail.com> > Datum: Montag, 30. Juni 2025 um 11:55 > An: dev@iotdb.apache.org <dev@iotdb.apache.org> > Betreff: [DISCUSS] Extend "Timecho Weekly Update" as IoTDB's community weekly > update? > Hi, > > In the last board meeting (06-18), it was discussed that the currently > regular "Timecho Weekly Update" can be extended as IoTDB's community > weekly update so that it becomes more inclusive. Basically, change the > title and call for participation in the community. Perhaps you can > refer to "This Week in Rust" [1][2] and so on. > > [1] https://github.com/rust-lang/this-week-in-rust > [2] https://this-week-in-rust.org/ > > It's fine that the Timecho team actively shares their contributions to > the IoTDB, and I'm glad to see these kinds of shares that may trigger > more engagement. So you can take this email as a suggestion on the > possibility of running the weekly meeting more inclusively. > > Best, > tison. >
