Hi, > -----Original Message----- > From: Pengcheng Zheng <maca...@gmail.com> > Sent: 11 July 2025 05:12 > To: dev@iotdb.apache.org > Subject: Re: [DISCUSS] Extend "Timecho Weekly Update" as IoTDB's community > weekly update? > > Hi all, > > Thanks for the feedback and suggestions. >
[snip] > @Chris - your point about not only sharing what has been done, but also > what is planned, is really helpful. I'll consider integrating upcoming > work > from GitHub issues and roadmaps, along with our internal progress, into > future updates. Hopefully, this can better engage contributors outside of > China-based channels and make it easier for everyone to align with ongoing > efforts. This is just an idea.. I do not begin to understand the Apache and IoTDB PMC and dev processes but, in the COVESA CDSP project we use a Github Kanban Project associated with the project source repository to organise within the OSS community. The flexibility of kanban allows us to bring a level of high level coordination across multiple companies. By adopting an organisationally light weight approach of Backlog (tasks to be triaged e.g. ideas), Next (accepted roadmap), In Progress, Hold and Done a wide group of stakeholders can quickly understand the state of the project. It also avoids duplicating detailed development processes that may exist within a company as they work on something. I think IoTDB is a bigger project but perhaps something light weight like that could help you coordinate at a high level, whilst allowing Timecho to maintain their presumably heavier duty internal processes. Github Kanban has access controls so you can keep access to known devs if you wish. A source project can also reference multiple boards if you wish to have separate boards for big projects. Of course, it does not free you from having a maintain the Kanban :) The biggest issue I have found is that normal items on the board are simply text boxes without any support for conversations. So we convert most items on the board to full github issues to allow that. Here is the CDSP project board (sorry for company URL expansion) https://github.com/orgs/COVESA/projects/8 which is linked from the Project tab of the CDSP source rep: https://github.com/COVESA/cdsp Best Wishes, Steve
