My concern is that board member time is limited by other duties in the project. If everyone on the board agrees to sift through the #Team_Vectors content for stuff that needs the attention of the board, that's totally fine with me. Frankly, I don't expect anyone to do that. The idea is to make it easier for board members to see what's important.

And yes, I think before a board meeting, board members should have read through the purely on-topic conversations that go on in #board_room.

There is plenty going on in the various chat rooms to show the project is active. The most active chatrooms are actually #general and #inkscape_user. Everyone in the project knows how active the project is, even if a room is quiet for days (which is rare).

Some topics having to do internal policy matters of Inkscape can also get heated and quite long, creating an atmosphere which is not pleasant for those trying to work on vectors tasks, etc. I'd rather not subject new people who signed up for vectors duties to be met with walls of administrative conversation and conflict. It makes the project look unfriendly and in conflict without any context. Whereas if the conversation takes place in the board room, it's more expected that there will be strong differences of opinion, and doesn't expose people who just want to help the project and skip the politics to things they certainly didn't sign up for. :)

We can make announcements each time there's discussion in the board room about a particular topic, and since it's separate, it's not intermixed with development matters, or vectors matters, etc. and thus is easier to digest.

 

-C



On Thu, Apr 29, 2021 at 4:01 PM Ted Gould <ted@gould.cx> wrote:
On Apr 28 2021, at 5:14 pm, C R <cajhne@gmail.com> wrote:
Thus this new channel will be a digest for board members to scan through and see board-related matters before and after board meetings.

This is my concern with the proposal. I don't think that describes chat at all, the backlog is generally lost to time if people aren't there and joining in the conversation. And that's a benefit of chat. But we shouldn't expect that people read a chat room unless we've requested their attendance ahead of time (meeting).

Personally, I'm not super active in the chats, but when I do check in I haven't seen them overflowing with messages or situations where on-topic chat is blocked by board discussions. There's a rule on the internet about only making mailing lists when it has become painful, and rarely even then. The downside of segregating chat is that it makes the project seem less active (no one is chatting) and people don't see ancillary discussions (that they may not have realized applied to them).

Ted