Re: [DISCUSS] Extend "Timecho Weekly Update" as IoTDB's community weekly update?

[Jialin Qiao <qi...@apache.org>]

Hi,

+1 for This week in IoTDB  or IoTDB Weekly Update.

Jialin Qiao

Christofer Dutz <ch...@c-ware.de> 于2025年6月30日周一 19:05写道：
>
> 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 <wa...@gmail.com>
> Datum: Montag, 30. Juni 2025 um 11:55
> An: dev@iotdb.apache.org <de...@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.

Re:Re: [DISCUSS] Extend "Timecho Weekly Update" as IoTDB's community weekly update?

[Ivan Soeng <ch...@163.com>]

unsubscribe

RE: [DISCUSS] Extend "Timecho Weekly Update" as IoTDB's community weekly update?

[Stephen Lawrence <st...@renesas.com>]

Hi,

> -----Original Message-----
> From: Pengcheng Zheng <ma...@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

Re: [DISCUSS] Extend "Timecho Weekly Update" as IoTDB's community weekly update?

[Pengcheng Zheng <ma...@gmail.com>]

Hi all,

Thanks for the feedback and suggestions.

The original purpose of the “Timecho Weekly Update” was to share our team’s
ongoing contributions to Apache IoTDB more transparently. While our
colleagues have been among the main code contributors recently, I don’t
think our company should represent the entire community to “announce”
project-wide updates. That’s why we’ve kept the title clearly tied to our
company Timecho so far.

That said, I fully agree that a more community-focused update would be
valuable.

@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.

@Tison – The format of “This Week in Rust” is a great inspiration. While we
currently don’t have the bandwidth (or enough community-wide content) to
match that level, we’ll work gradually in that direction.

Looking forward to building this together.


Best,

Pengcheng



Am Mi., 2. Juli 2025 um 09:18 Uhr schrieb Jialin Qiao <qiaojialin@apache.org
>:

> Hi,
>
> +1 for This week in IoTDB  or IoTDB Weekly Update.
>
> Jialin Qiao
>
> Christofer Dutz <ch...@c-ware.de> 于2025年6月30日周一 19:05写道：
> >
> > 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 <wa...@gmail.com>
> > Datum: Montag, 30. Juni 2025 um 11:55
> > An: dev@iotdb.apache.org <de...@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.
>